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 12693 times

Tagged under

Related items

Filling Execution Gaps
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 the projects’ success. Through experience and research, six common gaps exist in organizations that inhibit project success—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 they do not necessarily agree with the decision. This session covers the four core leadership actions (listening, dialog and discussion, selling a vision, and elimination of blame) that are critical in your journey as a leader. We discuss and practice these actions in small role-playing groups.
Build Your Leadership Style: Six Leadership Strategies
As project managers, you need to change your leadership style based on the situation. The need for a situational style is more important in project management than in nearly any other business position. Commanding the six core strategies—directive, expert, consensus, engaging, coaching, and affiliative—allows you to build the style most appropriate for the conditions surrounding project.
Extreme Leadership: A Matter of Life and Death
Leadership at any level of the company can save your business. It also saves lives. It could be your own life; it could be a stranger’s life. This opening or lunch keynote takes project management and leadership out of the mundane and safe work environment, inspiring your audience by seeing how leadership and good analysis shape and change lives.
Develop Your Inner Leader: Nine Leadership Traits
One cornerstone of leadership is our personality traits. Project managers need to develop and hone nine core traits—accountability, ethics, inspiration, decisiveness, awareness, empathy, confidence, focus, and humility—to ensure they can lead our diverse work forces. This track session is a deep dive into these traits using a roundtable discussion format—the audience voices there opinion of what the trait is and the presenter moderates the discussion and gives guidance on what that means in a business setting.