Sofia Almeida·
Ran our quarterly ops retro through this synthesis prompt: 60 sticky notes in, five themes and three committed changes out. Meeting ended twenty minutes early.
Clusters raw retrospective input into themes, tensions, and a small set of committed changes with owners.
Retro Sticky-Note Synthesizer
You are a retrospective facilitator. I will paste the raw input from our team retro — sticky notes, form responses, or chat messages, in whatever messy state they arrived. Team size: {{team_size}}. Retro scope: {{scope_and_period}}.
Synthesize:
1. **Theme clustering.** Group the raw items into 4-7 themes. Name each theme by the underlying dynamic, not the surface complaint ("handoffs lack owners", not "communication"). Under each theme, quote 2-3 representative raw items verbatim — people need to see their words survived the synthesis. Count how many items fed each theme so weight is visible.
2. **Tension pairs.** Retros often contain contradictory feedback ("too many meetings" AND "I never know what's going on"). Surface every contradiction as a tension pair and name the real trade-off underneath. Do not resolve them — flag them for discussion, with one question that would move the conversation forward.
3. **Sentiment check.** Rough distribution: how much of the input is frustration vs appreciation vs suggestion? If one theme carries disproportionate emotional weight (strong language, repetition across people), say so — item counts alone miss intensity.
4. **Committed changes.** Propose exactly 3 changes for next period, drawn from the heaviest themes. Rules: each change must be specific enough that a stranger could verify in the next retro whether it happened, each needs an owner role (I will fill names), and at least one must be a STOP (something we cease doing) rather than an addition. Teams over-add and under-stop.
5. **Parking lot.** Everything real but not actionable this period, so people see it was heard, not dropped.
End with a 60-second read-aloud summary I can open the discussion with. Neutral tone — the facilitator voice, not management's.
Ergebnisse
## Retro Synthesis — Q2 Ops Team (58 items, 9 people)
### Themes
**1. Handoffs lack owners (14 items)**
> "tickets bounce between us and support for days" · "I thought Marta had it, Marta thought I had it" · "the vendor escalation sat for a week because nobody was 'it'"
**2. Interrupt load is eating focus time (11 items)**
> "I get pinged ~20x a day and 15 could have been a ticket" · "my only deep work happens before 9am"
**3. The new intake form is working (9 items — appreciation)**
> "requests finally arrive with the info we need" · "intake form = chef's kiss"
**4. Tooling sprawl (8 items)** — three trackers, nobody sure which is canonical.
**5. On-call handover quality (6 items)** — Monday person inherits mysteries.
Parking lot feeds: 10 items.
### Tension Pairs
- "Too many status meetings" (4 items) ↔ "I don't know what other pods are doing" (5 items). Underlying trade-off: synchronous cost vs. ambient awareness. Question: *what would make status visible without a meeting?*
- "We need stricter process" ↔ "process is why simple things take a week". Trade-off: consistency vs. cycle time. Question: *which steps have caught a real error in the last quarter?*
### Sentiment Check
Roughly 55% frustration / 20% appreciation / 25% suggestion. **Intensity flag:** Theme 1 carries disproportionate heat — 5 of 9 people raised it independently and the language ("days", "nobody") is the strongest in the set. Treat as the retro's center of gravity even though the meeting-tension pair may be louder in discussion.
### Committed Changes (proposal)
1. **Every cross-team ticket gets a single named owner at creation** — verifiable: sample 20 tickets next retro, count owned-at-creation. Owner role: intake lead.
2. **STOP: retire the legacy tracker** — read-only by week 2, archived by week 6. Verifiable trivially. Owner role: ops tooling owner.
3. **Interrupt budget: pings that outlive 10 minutes become tickets** — verifiable via a 1-question pulse check next retro. Owner role: team leads model it first.
### 60-Second Opener
"Fifty-eight notes from nine of you. The loudest theme by count and by heat: cross-team handoffs without a clear owner — five of you raised it independently. Good news: the intake form is unambiguously working, nine notes say keep it. We have two genuine tensions to discuss, not solve: meetings versus awareness, and process versus speed. And we are proposing three changes — including finally killing the old tracker. Let's start with handoffs."
Modell: Grok 3
26 Likes15 SavesScore: 17
1 Kommentar
Grace Williams·
Quoting raw items verbatim under each theme is what makes people trust the synthesis. Paraphrase kills retros.
