Lean Coffee Retrospective: Let the Team Build the Agenda

Introduction

A retrospective format should make reflection easier, not distract the team with decoration. Facilitators do not always know which issue deserves attention.

This guide explains the approach in practical terms: what it is, why it is useful, when to use it, how to apply it step by step, and which mistakes to avoid.

What is it?

A Lean Coffee retrospective is a structured but agenda-less meeting. Participants propose topics, vote on what matters most, and discuss them in short timeboxes. At the end of each timebox, the group votes to continue or move to the next topic.

Why is it useful?

Facilitators do not always know which issue deserves attention. Lean Coffee gives the team control over the agenda while preventing one discussion from consuming the entire meeting. It works especially well when concerns are varied or when a standard template feels restrictive.

Benefits

• Creates a participant-driven agenda.
• Prioritizes discussion democratically.
• Controls time through explicit continuation votes.
• Adapts easily to sprint, project, or team-health topics.

When should you use it?

Use Lean Coffee when there is no single retrospective theme, the team has many possible topics, seniority may influence the agenda, or previous retrospectives spent too long on the first issue. Avoid it when the team needs a guided safety or incident process.

How to do it

1. Explain the flow. Describe topic creation, voting, discussion timeboxes, and the continue-or-move vote.
2. Generate topics. Ask participants to write one topic per card. Prompts can include what helped, what hurt, what surprised us, and what needs a decision.
3. Clarify and combine. Read the cards, merge duplicates, and ensure each topic is understandable.
4. Vote on the agenda. Give each participant a limited number of votes and order topics by score.
5. Discuss in timeboxes. Start with five to eight minutes. At the end, vote thumbs up to continue, sideways for one short extension, or down to move on.
6. Capture decisions and actions. Record conclusions, owners, and follow-up instead of relying on memory.

Real example

A platform team entered a retrospective with concerns about testing, roadmap changes, on-call load, and review delays. Voting placed review delays first. After eight minutes, the team agreed on a reviewer rotation and moved on rather than repeating the same arguments. The second topic produced an on-call handoff checklist. Two high-value actions were completed within a 50-minute session.

Common mistakes

• Allowing broad topics such as communication without clarifying the specific problem.
• Giving unlimited votes and losing meaningful prioritization.
• Ignoring the timebox when a senior participant wants to continue.
• Recording conversation but not decisions or actions.

FAQ

How many topics should each person add?

One to three is usually enough. Encourage participants to combine related thoughts.

What if the top topic is sensitive?

The facilitator should restate the safety rules and may switch to anonymous input or a more structured format if needed.

Can Lean Coffee be asynchronous?

Topic collection and voting can be asynchronous, but interpretation and difficult decisions usually benefit from live discussion.

Conclusion

Lean Coffee provides freedom without chaos. The team chooses the agenda, voting creates focus, and timeboxes protect the meeting. Its value depends on capturing clear outcomes before moving to the next topic.

Call To Action

Set up a Lean Coffee board in SprintsPlans, collect topics, vote anonymously, and keep the conversation focused with a visible priority order.