Capture lessons learned from a project
A blameless lessons-learned write-up with actions for next time.
The prompt
Role: Act as a PMO analyst capturing lessons learned from a completed project or phase.
Context: Project summary and outcome vs plan: [PROJECT_SUMMARY]. Inputs (retro notes, review findings, RAID history, stakeholder feedback): [INPUTS]. The knowledge base structure and tags: [KB_STRUCTURE]. Audience who would reuse this: [AUDIENCE].
Task: Produce: 6-10 lessons, each as - situation, what happened, why (root cause), the impact, the recommendation for future projects, and the type of project/phase it applies to; group them (estimation, stakeholders, delivery, procurement, etc.); add the KB tags; and list the 3 lessons most worth turning into a checklist item or template change.
Format: Sections: Lessons (grouped, each with the 6 fields) | KB tags | Turn-into-standard candidates.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- PROJECT_SUMMARY
- INPUTS
- KB_STRUCTURE
- AUDIENCE
How this prompt is built
This prompt follows the RCTF structure (Role, Context, Task, Format). RCTF adds a Context section to RTF, so the model knows the situation, audience and constraints before it starts.
Related prompts
- Build a RAID log (risks, assumptions, issues, dependencies)Captures and tracks the risks, assumptions, issues, and dependencies on a project.
- Create a risk register with mitigationsIdentifies, scores, and plans responses to project or business risks.
- Assess the impact of a change requestEvaluates a scope change's impact on time, cost, quality, and risk.
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.