We wrote lessons learned, but nobody reuses them. How do we change that?
Lessons disconnected from future decisionsTurn important lessons into owned changes to estimating, templates, reviews, or operating practices. Place them where the next team makes the relevant decision, and check whether the change was used. A retrospective document alone does not create organizational learning.
What to do now
- Select lessons with a clear future application
- Assign an owner to change the relevant practice
- Embed the change in a usable working artifact
- Check adoption in a subsequent project
When to escalate
A recurring failure has no owner willing to change the underlying practice.
The sponsor and accepting business or service owner
Example
A missed vendor lead time becomes a required check in the next project's planning template.
Mistake to avoid
Archiving a long lessons document and calling the learning complete.
Prevent a repeat
Verify that transferred obligations and important lesson actions are completed after the project closes.
Suggested ApprovedFlow setup
- Projects
- Documents
- Tasks
- Approvals
Keep the closure decision and final evidence with the project and transfer accepted residual actions to named ongoing owners. See the platform
Related cases
- Our lessons have owners, but actions still disappear. How do we follow through?Unmonitored improvement commitments
- The same project failure happened again. How do we check whether lessons worked?Unverified effectiveness of improvements
- The new system changes people's responsibilities, but nobody told them. What now?Unmanaged role transition
- Our dashboard is green while the site has unresolved work. How do we fix it?Summary disconnected from evidence