Monday, 28 September 2009 00:00

People: Common Failure Symptoms

Rate this item

(0 votes)

In daily talks and presentations, I am often asked what the most common reasons are for project failures. I usually turn the question around and ask people what they think. It is a fun exercise and people list a mixture of symptoms and sources. As mentioned in the previous blog, one must drill past the symptoms and get down to the problem itself. It is my firm belief that most project problems are rooted in the people, however people are creatures of habit.

For conversation purposes, it is handy to classify the common problems into three categories—team, process and customer (see Table 1).

Team concerns are usually communication, attitude and motivational, skill set, internal scope creep and interrelationship problems. To address these takes a soft-skills approach. Training in organization development and working with difficult people is a great plus (more on this in an upcoming blog).

Problem Area	Symptom
Team	Interrelationships Communication Attitude and motivation Internal Scope Creep Skill set
Process	Risk Management Change Management and Scope Issues Documentation Estimation and Scheduling
Customer	Difficult, trying to get something outside of scope Incomplete understanding of product (manifesting as scope issues) Lack of Project Management (manifesting as scope issues)
Table 1: Major Failure Reasons

Internal scope creep is a nasty beast where the team is increasing scope by suggesting features to the customer. This requires close involvement with the team and training on the results of expanding scope. The root of this is the inability of the team members to say "no." The Project Manager needs to step in and use all means to correct this behavior.

Process problems are relatively straightforward to solve. They are:

Change management and scope control;
Document coordination;
Estimation and scheduling;
Risk management.

The worst of these to fix is a broken or misapplied process. The reason? A process has followers and people who believe in it—they have read it in a book, someone has told them they have to do it or they are unwilling to move away from it since it is their comfort zone. Changing the process may be more like changing the culture. Results change a culture, culture does not change results. Show results and the organization will follow.

Customer issues come in a variety of shapes and sizes but many times the solution is training the customer in project management techniques or their product. It may also require educating the project team in the customer’s way of doing things. This is especially true in international projects. The most common problem is a customer’s lack of understanding of the product. This may be solved by implementing a better change management process or moving to an Agile methodology. Poor Project Management skills can only be solved by education of the customer.

Regardless of the issues, it still takes drilling down to find the source. The project audit finds the symptom and project analysis finds the root cause. After identifying the source, it must be fixed and the people need to buy into the solution and help implement the changes. Identification is just the beginning of the work.

Read 13059 times

Tagged under

Related items

People vs Process Track Session/Keynote Example

<p>Sorry, your browser cannot display frames!</p>

If you want educational keynote many of our presentations can be keynotes or track sessions. In the example below, the presentation People or Process: Which Impacts Project Success More? is given as a track session.

Example People vs Process keynote as a track session

This session was given at the PMI Sioux Empire Professions Development Day help in Sioux Falls SD on September 9, 2014.
Transform Your Project Leadership: For Professionals Leading Projects or Company Initiatives
Todd Williams contributed Chapter 7, "Leaders Listen." You can buy it on Amazon.

More coming soon!
Filling Execution Gaps: How Executives and Project Managers Turn Corporate Strategy into Successful Projects

What Filling Execution Gaps Covers

Filling Execution Gaps

by Todd C. Williams
ISBN: 978-1-5015-0640-6
De G Press (DeGruyter), September 2017

Project alignment, executive sponsorship, change management, governance, leadership, and common understanding. These six business issues are topics of daily discussions between executives, middle management, and project managers; they are the pivotal problems plaguing transformational leadership. Any one of these six, when improperly addressed, will hex a project's chances for success. And, they do—daily—destroying the ability companies to turn vision into value.

Check it out on Amazon or the Filling Execution Gaps website

Without the foundation of a common understanding of goals and core concepts, such as value being critical to success, communication stops and projects fail.

Without change management, users fail to adopt project deliverables, value is lost, and projects fail.

Without maintaining alignment between corporate goals and projects, projects miss their value targets and projects fail.

Without an engaged executive sponsor, scope increases, goals drift, chaos reigns, value is lost, and projects fail.

Without enough governance, critical connections are not made, steps are ignored, value is overlooked, and projects fail.

Too much governance slows progress, companies cannot respond to business pressures, value drowns in bureaucracy, and projects fail.

Without strong leadership defining the vision and value, goals are not set, essential relationships do not form, teams do not develop, essential decisions are not made, and projects fail.
Filling Execution Gaps: Building Success-Focused Organizations

Executives define vision, strategy, and goals to advance the business. Projects enable companies to meet those goals. Between strategy and projects, there is a lot of work to be done—work that lays the foundation for project and operational success. Through experience and research, six common gaps exist in organizations that inhibit project success—an absence of common understanding, disengaged executive sponsors, misalignment with goals, poor change management, ineffective governance, and lackluster leadership.
Get Recognized as a Leader: Four Core Leadership Actions

Leaders make decisions. This requires a core set of actions to gather the best information, hear out the concerns of others, and making a decision that everyone will follow—even if there is not unanimous agreement with the decision. Although there are hundreds of actions leaders must take, there are four core actions that all great leaders do—listening, dialog and discussion, selling a vision, and eliminating blame. This session will discuss those actions in a roundtable format that we call a "What Would You Do?" session. In these sessions, the presenter acts as a moderator spending 10 to 15 minutes per topic working with the audience talking about what the action is, how to best do it, and hearing from the group on how they have carried out the action. This brings significant audience interaction, involvement, and broader education.