Staying Positive About Your First Lessons Learned
Lessons learned. The project post-mortem (a horrible term). Or, as many project managers call it, a complete waste of time.
Why is that? Our agile colleagues regularly conduct retrospectives, which aren’t quite the same thing, but which provide tremendous value if conducted properly. Yet the lessons-learned process has a reputation of being a finger-pointing session that focuses more on complaining than it does about improving anything. And even if recommendations do come from it, the assumption is that those recommendations will disappear into a black hole where the PMO lives, never to be seen again.
That reputation has been widespread for a long time, so it must be based on some truth. Undoubtedly, there are organizations that run successful lessons-learned sessions, and I know of many organizations that have found tremendous innovations as a result of them. But the majority of lessons-learned sessions don’t achieve much. So as a new project manager, how do you buck that trend? Or do you simply ignore them in the belief that you’ll be wasting your time?
Problems from the approach
I believe that lessons learned are tremendously valuable. I also believe that most organizations destroy that value because of how they define the process. In most organizations, lessons learned is a mandated task after all of the other work is complete. It occurs at a
Please log in or sign up below to read the rest of the article.