Lessons learned without the eye roll
Why post-mortems fail and how to run a retro that actually surfaces useful insights.
The phrase 'lessons learned' triggers a Pavlovian eye roll in most project teams - and for good reason. Most lessons learned sessions produce a document that gets filed away and never influences future projects.
The problem is structural: we ask 'what went wrong?' which makes people defensive, and we hold the session at the end when everyone just wants to move on.
A better approach: run lightweight retrospectives continuously. After each phase or sprint, ask three questions: (1) What should we start doing? (2) What should we stop doing? (3) What should we keep doing? Keep it to 30 minutes and capture one action per person.
The secret is to assign ownership and follow up. An insight without an owner is just a diary entry. Give each action a named person and a deadline, and review it at the start of the next retro. That's how learning becomes process.