The point of a lessons-learned review is not to write a document that gets filed and forgotten — it is to stop the same mistakes from recurring on the next project. That only happens when you get past symptoms to root causes and turn each lesson into a recommendation someone can actually adopt. This builder turns your review notes into a prompt that does exactly that.
How it works
You describe the project type, its outcome, the key issues, and the team’s reflections. The builder wraps them in a prompt that tells the model to facilitate a blame-free lessons-learned analysis. For each issue it applies the 5 Whys to find the root cause, judges whether the problem is a one-off or systemic, and produces a specific recommendation assigned to a role. It also captures what went well so the report is balanced, and prioritises the top three recommendations by impact. Choose your format, copy the prompt, and run it.
Why root cause matters
A lesson that says “the vendor delivered late” is useless — every project has late vendors. The useful version asks why: the contract had no milestone penalties, because procurement was rushed, because the project started before the budget was approved. Now you have a lesson you can act on: never start delivery before budget sign-off. The 5 Whys is the difference between a report that gets filed and one that changes how the organisation works.
Tips for better output
- Run the review first, then the prompt. The model structures and analyses; it cannot tell you what actually happened. Capture the team’s honest reflections before you build the prompt.
- Include the good as well as the bad. Lessons worth repeating matter as much as mistakes to avoid, and a balanced report is more likely to be read and trusted.
- Feed the top three into your playbook. The prioritised recommendations are designed to drop straight into a process-improvement backlog or a project management playbook.