Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Learning from Project Failures

~ By Kenneth Darter

Success and failure directional signs

As project managers, some of the most important lessons we learn come from failures. Whether the entire project failed, or part of it failed, or even if the project succeeded in spite of a big failure on the part of the project manager or the project team, there is something to be learned from a failure. And the best part of learning from a bad experience is that it is very hard to forget the lesson. No matter what happened though, it is important to keep things in perspective and be able to move forward. In order to make this happen, it can be helpful to process the failure and determine what the lesson is that needs to be carried forward to the rest of the project or other projects. While there may not be a need to do this formally, the project manager should still go through these steps in order to make sure that the issues that led to failure do not happen again.

Step 1: Input

Before a lesson can be learned from failure, the project manager should make sure to get input from all the different parties involved. This input might include other project managers involved in the project, the resources working on the project, the executives or sponsors involved in the project, or even external stakeholders. All of the opinions and viewpoints of these individuals should be solicited as soon as possible after the failure occurs so that the project manager collecting the information can get a firsthand account of what happened; even a brief interlude like a month or two can colour a person’s memory of events.

Step 2: Determination

Once the information has been gathered from the different sources available, then the project manager should put together a determination of what caused the failure and what would have prevented it. Performing this step might involve asking a lot of "what if" questions in order to come up with a good understanding of what happened and the lesson to be carried forward. Some examples might include:

  • What if the requirements had been right when development started?
  • What if the project schedule had been created before the end date was decided upon?
  • What if the risk had been mitigated instead of accepted?

Step 3: Validate

Once a determination has been made, the project manager should spend some time validating the lesson learned with the same individuals that were responsible for providing input in the first step. The other viewpoints and opinions will help refine the determination and improve it in order for it to be more useful to future projects. Once the validation is done, the project manager may need to go back through the determination process until it is complete and verified.

Step 4: Communicate

The last step is to communicate the lessons learned from the failure to all of the resources involved on the project and to the stakeholders and other decision makers. All of the information and conclusions gathered by the project manager should become part of the enterprise knowledge going forward for other projects that might encounter the same issues or problems. If possible, the project manager should also shout it to the world from the rooftops. After all, lessons learned from failure can benefit everyone in the field, not just the project manager directly involved in collecting the information.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
What is the month after April?
Notify me of new comments via email.
Remember my form inputs on this computer.

Who is the Project Manager?

Businessman illustrating a project managers key role

A dilemma: should you appoint someone who is an experienced project manager or someone who will champion the change?

What Is the Mission of Your Project?

Illustration of a blackboard showing words Mission Statement

The stakeholders in a project can have lots of different goals, but a software project is more than just the sum of its parts.

Soft Power for Success

Businessman touching a power button

Soft power is the ability to get people to work with you by attracting them to be part of what you stand for; rather than to coerce, force or pay them.

Successful Projects: It's Not Rocket Science

A woman with pen in hand standing next to an image of a rocket

Avoiding the common pitfalls of IT project management is not rocket science; it is simply a case of taking some sensible measures.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Philip VonSteinmann commented on…
A Brief History of Project Management | Project Smart
- Wed 8 July 3:34am

Michael Contorno-Hubbard commented on…
Better Coaching Using the GROW Model
- Fri 26 June 2:09pm

Arnel Dela Cruz commented on…
Use Your Whole Brain: Leveraging Right-Brained Thinking in a Left-Brained World
- Wed 24 June 7:16am

Latest tweets

General Project Management • Re: What are the best remote working tips these days? https://t.co/rncJH3IyhU about 6 days ago

General Project Management • Re: What are the best remote working tips these days? https://t.co/6lAUs5iU8E about 6 days ago

General Project Management • Re: What are the best remote working tips these days? https://t.co/ZwSkgfQXPA about 6 days ago