Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Documenting Lessons Learned: What Have You Learned?

~ By Kenneth Darter

Woman thinking and the words what have you learned?

Being able to document lessons learned after a project is complete (or even in the middle of it) is one of the biggest responsibilities a project manager has on a project. If one does not understand the mistakes of past projects, then one is doomed to repeat them over and over. In this role, the project manager becomes part historian and part archivist. Lessons learned are not just useful in the business world; they can be helpful on any project in which one is involved - at home or in your volunteer work or in your own personal hobbies. Lessons learned can make all the difference on future projects and help them to succeed, but first, they must be documented correctly.

The Good and the Bad

Lessons learned should not just focus on the mistakes that were made; they should also document the good things that happened in the project. Otherwise, all of the processes and decisions that helped the project succeed might be lost and that would be just as bad as forgetting about the mistakes that were made. Oftentimes, everyone focuses on the mistakes that were made, and, while that is important, the project team needs to recognise what worked and make sure that those processes and techniques can be repeated in future projects.

In the Moment

The best place and time to capture lessons learned is in the moment that the project is happening. Even though people may be busy and overwhelmed just working on the project, someone should be working to capture those items that might turn into lessons learned at the end of the project. The best time to get these items documented is right after they have happened. Otherwise, people tend to forget about what they did or even gloss over the problems and issues that occurred. They might even start telling tall tales about what happened; lessons learned need to be a truthful reflection, not a fish story.

Solicit Data

This is primarily the project manager’s responsibility, but everybody on the project should be aware that they can provide ideas and insight into the lessons learned. This truly needs to be a collaborative effort in order to succeed. Recording lessons learned should be a regular part of project management and needs to be included in the weekly and monthly processes. Once people on the team get used to providing this input, the project manager may get overwhelmed with the response. While the paperwork might get tedious, the rewards are well worth the effort.

Publish or Preserve

Once all of the information is collected and reviewed and revised, then it is important to make sure that it is published so that everyone involved in the project is aware of the lessons learned, both positive and negative. It is also vital that this information be preserved so that the organisation and the project teams can have it the next time a similar project is being executed. Without the lessons learned from previous projects, future projects will fall into the same routines and pitfalls that occurred in previous projects.


Comments (1)

Topic: Documenting Lessons Learned: What Have You Learned?
5/5 (1)
Gravatar
Full StarFull StarFull StarFull StarFull Star
4th May 2015 10:40pm
Sashieka Stevens (Jamaica) says...
Very good presentation, at times we forget the importance of documentation while doing projects and then we fall in the same trap over and over again. This presentation has broaden my understanding of documenting the good and the bad in doing any project.

Add a comment



(never displayed)



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

12 Tips for Being a Good Manager

Businessman revealing the inner superhero

Keeping a project management team running smoothly can be a challenge, especially when budgets are lean and expectations are high.

Work Breakdown Structure Made Easy

Work Breakdown Structure

The Work Breakdown Structure is a deliverable-oriented, hierarchical decomposition of the work to be completed by a project team.

Helping Project Teams Succeed

Business team brainstorming using coloured labels on a table in an office

Project teams will be successful when the right environmental conditions exist; sadly this is not always the case.

Effort Estimating: A Primer

Effort time money blue dice representing the ingredients for business

Good estimating is a skill like any other, it can be developed with practice to the point where it may seem like magic to the uninformed.

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

Duncan Haughey commented on…
Psychology for Project Managers
- Thu 22 October 5:10pm

Michael Fayamba commented on…
RACI Matrix
- Sun 18 October 6:34pm

Muhammed Ayub commented on…
Understanding the Project Management Triple Constraint
- Fri 9 October 8:54am

Latest tweets

General Project Management • Job opportunities as you get older https://t.co/wEbf7foa16 about 3 hours ago

General Project Management • Re: Why is it important to develop a product-thinking mindset? https://t.co/jcA2QT4laM about 1 day ago

General Project Management • Why is it important to develop a product-thinking mindset? https://t.co/IUW782zrve about 1 day ago