Participant-Driven Retrospective

Purpose

The Participant-Driven Retrospective applies the participant-driven discussion format to a retrospective: participants propose topics, vote on them, and then discuss them in priority order with strict timeboxes. It gives the team democratic control over the agenda and ensures the most important topics get discussed first, eliminating facilitator bias.

At a glance

• Group size: 4–15 people
• Duration: 30 minutes
• Difficulty: Intermediate
• Facilitation style: Semi-structured
• Setting: Both / Remote-friendly

How to run

1. Each participant writes 1–3 retro topics on sticky notes (3 minutes).
2. Brief pitch: each person explains their topics in one sentence (5 minutes).
3. Dot-vote: each person gets 3 votes to distribute across all topics (2 minutes).
4. Sort topics by votes. Discuss the top-voted topic for 5 minutes. At the end, thumbs up/down to continue or move on.
5. Repeat for remaining topics until time runs out. Capture actions for each discussed topic (20 minutes).

Materials needed

• Sticky notes
• Dot stickers or markers for voting
• Timer
• Kanban-style board: To Discuss, Discussing, Discussed

Pitfalls & common mistakes

• Not enforcing the timebox — the power of participant-driven discussion is its discipline.
• Allowing the pitch phase to become a full discussion.
• Not capturing actions during each topic discussion.

Inclusion & accessibility

• Democratic voting ensures everyone's priorities are heard, not just the loudest voices.
• Allow anonymous topic submission.
• For remote teams, use tools like Parabol or a Miro template for participant-driven discussion.

Variations

• Silent Participant-Driven Discussion: written discussion in a shared document, then vote on what to discuss live.
• Participant-Driven Discussion + Action Board: add a fourth column for committed actions.
• Themed Participant-Driven Discussion: restrict topics to a specific theme (e.g., only technical debt).

When NOT to use this

• When the facilitator already knows there is one critical topic that must be discussed — pre-set the agenda.
• When the team is very small (under 4) and open discussion flows naturally.

Source & further reading

• Jim Benson and Jeremy Lightsmith, Lean Coffee (leancoffee.org).
• Retromat (retromat.org).