Fix Stale Retrospectives
The most common retro problem: teams fall into the same format every sprint. "What went well, what didn't, what to improve" — repeated verbatim for months. Engagement drops, answers get shorter, and the retro becomes a box-ticking exercise.
Adding randomness to the format breaks this pattern. Spin 3-4 topics from the wheel. The uncertainty of what comes next keeps the team engaged. Add prompts specific to your current sprint challenges to keep it relevant.
How to Structure the Retro
Step 1: Spin 3-4 topics
Select the discussion areas for the session before anyone arrives.
Step 2: 5-10 min each
Time-box each topic. Set a visible timer to maintain pace.
Step 3: Action items
End each topic with one concrete action item, not just discussion.
Step 4: Refresh wheel
Update prompts every 2-3 sprints to maintain engagement.
Advanced Retro Prompts
Beyond the defaults, consider adding team-specific prompts: "On-call pain points", "Documentation gaps", "Cross-team dependency blockers", "Tech debt that slowed us down", "Ceremony that should be shorter", "Tool that frustrated the team". The more specific to your current context, the more useful the conversation.
Frequently Asked Questions
How do we structure a retro using this wheel?▾
Spin 3-4 times to pick the topics for the session. Spend 5-10 minutes on each. This keeps retros focused and under 45 minutes, which prevents the energy drain of open-ended sessions.
Can we add our own retro formats?▾
Yes. Replace defaults with prompts specific to your team's current challenges — 'On-call pain points', 'Documentation gaps', 'Cross-team dependencies'. The wheel works for any retrospective format.
How often should we change the prompts?▾
Every 2-3 sprints. Using the same prompts repeatedly reduces engagement. Refresh the wheel with new questions when you notice shorter answers and less discussion.