Free Webcast: Learn How To Build Better Products – Find Out Now ›
Popular Today in Business: All Popular Articles

9 Lessons Learned in Project Management

Product Management

Are you familiar with the lessons learned concept? You know, those meetings supposedly held after the project completion. These meetings are really important, and the main purpose is to gather feedback and ideas. How can you persuade your team to participate on lessons learned meetings? Here are the main Dos and Don’ts.

9 Lessons Learned in Project Management image full5Lessons Learned in Project Management by HousatonicSoftwa

Dos:

  1. The good, the bad, the ugly: The best lessons learned meetings I have participated were organized in 3 steps: the Good, the Bad the Ugly. Have your team gather around a round table. Give everybody the chance to nominate a good, a bad and an ugly fact about the project. Everybody must contribute with an idea, and do not move to next item on the list until we have found sufficient goods.
  2. Praise your team: Well done! Not only you as project manager have to praise your people, but Lessons Learned meetings are a great chance for team members to praise each other for great skills, great solutions they found together, or just a wonderful time as a team.
  3. Speak your minds: Good or bad use these meetings to share your feedback. Don’t be afraid to complain about an idea or a team mate. Just throw away that chip from your shoulder, so we can happily start a new project.
  4. Brainstorming: Can we do things in a simpler manner? Fabulous ideas may come from any team member.
  5. Prevention is cheaper than cure. Lessons Learned meetings should generate ideas to prevent trouble. We just hate the “What if?” questions that arise after disaster happens. Is there a simpler/secure way of doing things?
  6. Keep it simple, stupid. In many Lessons Learned meetings we realized there were simpler methods to solve a specific task or the documentation process.
  7. Improving as we do things: You don’t need to wait for the project to end to have the Lessons Learned meetings. Meetings organized as the project progresses can bring fabulous ideas that help the ongoing project.

Don’ts

  1. Documents only? No. Meetings are a must. One of my best yet most introvert team players I have worked with really hated these meetings. He thought Lessons Learned are very judgmental and time consuming, and not everybody feels comfortable throwing stones at their mates. Yet the real issue with the documents is that they are written by someone and they die in a locker. And what is the value? Zero!
  2. Don’t just send a follow up survey: Yes everybody is busy. But surveys will only captivate part of the feedback. Lessons learned meetings are a great time to speak and be listened to.

How important is putting together a simple process for collecting feedback when a project reaches its end? Very! Once the learning has been captured, do share the best practices with the other team to avoid making the same mistakes.

Try Housatonic FREE project viewer software  to share your projects in MPP form with your team while minimizing time and costs. All 2010 MPP files are supported, including password protected files.

Comments on this Article: 0

Add a Comment

Add a Comment:


Thank you for adding to the conversation!

Our comments are moderated. Your comment may not appear immediately.