Lessons learned
Turn experience into a specific improvement with an owner.
The idea
Lessons learned examine what happened, why, and what should change. They apply to incidents, projects, exercises, and ordinary operations. Focus on systems and decisions rather than blame. Evidence and participant perspectives help identify causes, while actions need owners and verification. A useful lesson changes practice; storing a retrospective document without follow-up rarely improves the next outcome.
In practice
After a recovery exercise, the team discovers that backup credentials depend on the unavailable identity service and assigns a tested independent recovery path.
A common misunderstanding
A list of observations is not complete improvement work unless the important actions are implemented and checked.
Check your understanding
How do you know a lesson was applied?
Think it through: The intended change is implemented, evidence verifies its effect, and the relevant guidance is updated.
Convert an observation into changed behavior
A lesson is useful when it explains what happened, why it mattered, and what the organization will do differently. A statement such as communication was poor identifies a frustration but provides little direction. A more actionable observation might say that service owners received the pilot schedule too late to allocate testers, causing the review to slip.
Separate evidence from hindsight. People often know more after an event than they could reasonably have known during it. Review the available information, incentives, and constraints before attributing the outcome to carelessness. This produces improvements in systems and decisions rather than a list of people to blame.
A fictional deployment review
A rollout fails on several older laptops because the test group contained only recently purchased devices. The team records the missing compatibility coverage and changes its pilot selection criteria. A named owner updates the test plan before the next deployment, and the next review checks whether the broader sample was actually used.
The lesson is not that all pilots must be larger. The problem was that the sample did not represent a relevant difference in the environment. This distinction avoids turning one failure into an expensive rule that does not address its cause. Useful learning stays connected to the mechanism that produced the result.
Write a follow-through action
Choose a fictional delayed access migration. Describe one observed event, its effect, a plausible contributing condition, and one improvement. Assign an owner and a way to verify completion. Finally, state what evidence would show the improvement helped. A lesson repository becomes valuable when people can retrieve and apply relevant experience, not merely when it contains many retrospective documents.
Keep exploring
References & further reading
Original explanations, with primary references for deeper study.
UK Government: Project Delivery Functional Standard