Death to the Project Post-Mortem!
Posted by Plish on November 30, 2012
Turn to any business magazine, look in project management books, (Microsoft’s site even has a template for it!) and one of the best practices of project management is to conduct a post-mortem just after a project has been completed, and right before it’s officially ‘closed.’ The purpose is to get everyone on the team together to examine what went well in the project, what went wrong, and record this information so that others can learn.
Don’t get me wrong, the concept is a good one and should be practiced. What I have a problem with, in particular, is use of the phrase, ‘post-mortem.’
By now you know that I’m a big fan of the power of words and metaphors – they shape how we solve problems and approach the world. So it probably won’t surprise you then that my aversion to the phrase is tied to all the meaning around the words, ‘post-mortem.’
Think about it.
The term literally means: after death. But what’s dead? You just finished something that myriads of people put their hearts and souls into, and now that that something is impacting the world, you call it dead? The project is closed, not dead. As a matter of fact, all projects, even those that resulting in the closing of a chapter, are births, not deaths! They are the beginning of something new.
By bringing the concept of death into the mix, there is a meaning conveyed that what just happened was not life-giving. It’s a not-so-subtle reminder that what just happened needs to be dissected and analyzed, and perhaps even robbed of deeper meaning and import*. Perhaps worst of all, it creates a sense that no continuity with this ‘dead thing’ is required.
On the contrary, the work of marketing, manufacturing, sales and product monitoring is kicking into full gear!
My point here is that it’s not about ending something, as much as it’s about a continuity of learning! Sure, one project ends, another begins. It’s a never-ending cycle. The commonality is that before, during and after a project, there needs to be a recursive aspect, a learning process that is ingrained into the culture. That mindset only comes about if there’s less emphasis on analyzing ‘that which died,’ and more emphasis on learning each day what works, what doesn’t, and growing from that. And, for that to happen, we need to put the term,”Project Post-Mortem” to death, and replace it with a more forward thinking term.
I like: ‘Lessons Learned.’
What would you call it?
One day after sleeping badly, an anatomist went to his frog laboratory and
removed, from a cage, a frog with white spots on its back. He placed it on a
table and drew a line just in front of the frog. “Jump frog, jump!” he shouted.
The little critter jumped two feet forward. In his lab book, the anatomist
scribbled, “Frog with four legs jumps two feet.”
Then, he surgically
removed one leg of the frog and repeated the experiment. “Jump, jump!” To which,
the frog leaped forward 1.5 feet. He wrote down, “Frog with three legs jumps 1.5
Next, he removed a second leg. “Jump frog, jump!” The frog
managed to jump a foot. He scribbled in his lab book, “Frog with two legs jumps
Not stopping there, the anatomist removed yet another leg.
“Jump, jump!” The poor frog somehow managed to move 0.5 feet forward. The
scientist wrote, “Frog with one leg jumps 0.5 feet.”
eliminated the last leg. “Jump, jump!” he shouted, encouraging forward progress
for the frog. But despite all its efforts, the frog could not budge. “Jump frog,
jump!” he cried again. It was no use; the frog would not response. The anatomist
thought for a while and then wrote in his lab book, “Frog with no legs goes
This entry was posted on November 30, 2012 at 2:52 pm and is filed under Best Practices, Creative Environments, culture of innovation, innovation, Innovation Tools, Project Management, Team-Building. Tagged: Best Practices, culture of innovation, innovation, Innovation Tools, innovative culture, lessons learned, metaphor, post mortem, project management, project post mortem, Team-Building. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.