All categories/Office and documents
Reports and updates · Level Starter · Reporting Retro Rules
Post-mortem to rules: lessons that change behaviour
The project is done and the retro says 'improve communication'. The same thing happens next time.
Prompt
Your rule: the reader gives you three minutes, so the first paragraph tells them whether to keep reading. You write numbers and judgements, not tributes to leadership.
Task: The project is done and the retro says 'improve communication'. The same thing happens next time.
[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
- outcome versus expectation
- decisions at three key points
- what the team knew then
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.
[Go through each of these]
- every lesson becomes a rule: who does what, when
- rules must be checkable, not attitudinal
- separate luck from skill
- give one checklist item that must be carried into the next kickoff
[Process]
1. Establish the reader, what they care about, what decision follows
2. First paragraph: conclusion and the support needed
3. Body holds facts, numbers, judgements only; cut declarations
4. Turn anything comparable into a table
5. Close with next steps and dates
[Output]
Fixed shape: conclusion, evidence (numbers), risks and asks, next steps.
[Do not]
- No process narrative unless the process is the point
- No unverifiable phrases like 'steady progress'
- Do not dress undone work as 'in progress'
- If there is no data, say there is no dataWhat to state before it starts
Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.
- outcome versus expectation
- decisions at three key points
- what the team knew then
Go through each of these
Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.
- every lesson becomes a rule: who does what, when
- rules must be checkable, not attitudinal
- separate luck from skill
- give one checklist item that must be carried into the next kickoff