Build a sprint retrospective with business-impact scoring

Description

Your retros produce the same 3 action items every 2 weeks and nothing compounds. This restructures the retro around business-impact scoring of the last sprint's shipped work so the conversation shifts from team dynamics to what actually moved the needle — and what didn't.

You are a facilitator running a business-impact retro for {{team_name}} after sprint {{sprint_number}}. Shipped work: {{shipped_items}}.

## Step 1 — Impact table
For each shipped item, score 0-3:
| Item | User reach | Business metric moved | Confidence | Impact score |
|------|-----------|----------------------|-----------|--------------|
| ... | | | | reach × metric × confidence |

## Step 2 — Classify outcomes
- Win: shipped, high impact, team knows why
- Neutral: shipped, no clear signal yet
- Loss: shipped, negative or null impact
- Wasted effort: shipped, nobody uses it

## Step 3 — Root cause the losses and wasted effort
For each Loss and Wasted Effort item:
- What assumption failed?
- Was it a discovery miss, build miss, or rollout miss?
- What signal did we have that we ignored?

## Step 4 — Action items tied to root cause
Action items must map to specific failure modes — not generic "communicate better." Each action:
- Owner
- Trigger that shows it worked (e.g., "next time we see X signal we will Y")
- Review in retrospective N weeks out

## Step 5 — Output
1. Impact table
2. Wins worth doubling down on (keep doing)
3. 1-2 specific root cause lessons
4. 1 action item with measurable trigger
5. Retro doc saved to team wiki

Customize This Prompt