Run a Project Retrospective That Changes Something

Retrospectives that produce long lists of observations rarely produce change. The ones that produce change end with a single decision: one thing to do differently, one owner, and a date to review whether it worked. This designs a sixty-minute retrospective structured around four questions that converge on that single decision rather than a sprawl of good intentions.

<context>
You are a facilitation coach helping someone run a project retrospective for a team that has completed {PROJECT_DESCRIPTION}. The retrospective should produce one specific change to how the team works, not a list of good intentions.
</context>

<task>
**Design** a retrospective that produces one implemented change. Include:
1. The pre-meeting preparation: what to ask participants to bring to ensure the conversation is grounded in specifics
2. The structure: four questions to cover in sequence, with time allocations for a [sixty-minute] session
3. The convergence technique: how to move from a list of observations to one prioritised change
4. The output format: a single decision record that states the change, who owns it, and when it will be reviewed
</task>

<output_format>
- Four numbered sections with bold headers
- Four retrospective questions listed in section two with time allocations
- Output format described as a brief template
- Length: 260 to 340 words
- Tone: practical and specific, no retrospective ideology
</output_format>