Lessons that transfer
The event is specific to your project. The cause is what the next team can recognise in time to act on — and a recommendation with nobody to carry it is a wish.
Lessons that transfer to the next project
The cause matters more than the event. "The integration was late" does not transfer; "we committed to a date before seeing the API" does.
Lessons
By category
Worth strengthening
What is checked
- No recommendation — the lesson is an anecdote. Something happened and nobody said what to do differently.
- A recommendation with no owner — a wish. Nobody will carry it into the next project.
- No cause recorded — a note. The cause is the part that transfers; the event is specific to this project.
- All negative or all positive — a warning about the review rather than the project.
Record the cause, not the event
"The integration was three weeks late" is a fact about this project and useless to the next one. "We committed to an integration date before anyone had seen the third-party API" is a pattern, and the next team can recognise it in time to act.
The test is whether someone on a completely different project could read the lesson and change what they do. If not, it is a record rather than a lesson.
An all-failure review is a signal about the room
If a retrospective produces nothing worth repeating, the usual explanation is not that nothing went well. It is that the session did not feel safe enough to say so, or that it was run as an accountability exercise.
Such reviews also tend not to be believed by whoever reads them next, which wastes the genuine findings alongside the missing ones.
Lessons only count when someone owns them
The universal failure of lessons learned is that they are captured beautifully and never reach anyone who could act. A recommendation with a name against it has a chance; one without is a document that gets filed and cited by nobody.