Lessons learned that don’t die in a folder

Every methodology demands a lessons-learned session at closeout. Almost none of them produce a lesson anyone ever reads again. The document gets written in the last tired week of a project, saved to a folder named after the project, and never surfaces at the exact moment a future team is about to make the same mistake. It’s organizational memory with amnesia built in.

Capture in flight, not just at the wake

A retrospective at the end captures what you remember — which is the dramatic stuff and the last two weeks. The quiet, expensive lessons happened in month three and are long forgotten by closeout. Log them as they happen. A thirty-second note when something surprises you is worth more than an hour of reconstructed memory at the end.

Tag it so it can be found

A lesson is only useful if it finds the person who needs it. “Data migration is harder than estimated” buried in the ERP-project folder helps no one. The same lesson, tagged by theme — data, estimation, vendor — and searchable across every project, surfaces for the next team the moment they start planning a migration. The filing system is the feature.

Every lesson needs a verb

“We should have communicated better” is not a lesson; it’s a sigh. A real lesson is specific and actionable: “Book the data-cleansing window two sprints before cutover, not one — we ran out of runway twice.” If a lesson doesn’t change what a future team does, it’s a diary entry. Give it an action, and ideally a home in your next estimate or checklist.

Institutional knowledge is a genuine competitive advantage — but only if it’s alive. Capture early, tag ruthlessly, make it searchable, and insist every lesson carries an action. Do that and your tenth migration is easy because your first nine taught you something.