PlaybookPrompts

Extract durable learning principles from a project debrief

Education & Learning reflectionknowledge-managementprofessional-learning

Project debriefs produce lessons-learned documents that nobody reads again. This prompt turns raw debrief notes into generalizable principles you can actually apply on the next project.

Prompt
I just finished a project and have debrief notes I want to turn into durable learning — principles I'll actually remember and apply, not a list of things that went wrong.

Here are my debrief notes:
{{DEBRIEF_NOTES}}

Project context: {{PROJECT_CONTEXT}}

1. Read the notes and identify 5-8 discrete lessons buried in them. For each lesson, extract: the specific thing that happened, why it happened (root cause, not surface cause), and what a different decision would have produced.
2. For each lesson, write a generalizable principle — a rule I could apply in a future project that is different in content but similar in structure. The principle should be specific enough to give me actual guidance, not so general it's obvious (avoid things like "communicate more").
3. Flag any lessons that are specific to this project's unusual constraints and unlikely to transfer. Don't turn those into principles — note them as one-time observations instead.
4. Organize the transferable principles into two buckets: things I should do differently from day one on a future project, and things I should check at a specific milestone.
5. Write a one-paragraph "If I could do this project again" summary I could share with a colleague starting a similar project.

Note: This works best when {{DEBRIEF_NOTES}} includes what went wrong AND what went right. Learning from successes is as important as learning from failures.
Variables to fill in
  • {{DEBRIEF_NOTES}}
  • {{PROJECT_CONTEXT}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DEBRIEF_NOTES}}{{PROJECT_CONTEXT}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.