Lean Coffee Retrospective

Lean Coffee retrospective

Lean Coffee is one of the few retrospective formats where the facilitator doesn't set the agenda; the team does. Instead of predefined columns, team members bring their own topics, vote to prioritise them, and work through the highest-voted items in order. Every conversation the team has is one they explicitly chose to have.

The format takes its name from the Lean Coffee meeting style, created by Jim Benson and Jeremy Lightsmith. It recreates the feel of an informal coffee-shop conversation: ideas surface organically, discussions stay focused, and nothing runs longer than the team wants it to.

When to choose Lean Coffee

• When the team has specific topics they're burning to discuss. Standard formats steer teams through predefined categories. Lean Coffee gets out of the way.
• When retrospectives have started to feel repetitive. If the team is answering "What went well?" on autopilot, handing agenda control back to them often resets engagement.
• When the facilitator wants to step back. Lean Coffee is self-organising by design. It's a strong choice when the Scrum Master wants the team to own the session rather than be guided through it.
• When there's unfinished business. If something significant happened this sprint, a difficult stakeholder conversation, a production incident, a team change, Lean Coffee gives people a natural way to raise it without the facilitator having to engineer the opportunity.
• For experienced teams. Teams new to retrospectives often benefit from more structure. Lean Coffee rewards teams who are already comfortable raising issues and debating them directly.

Warm up: what's on your mind?

Before opening the board, ask the team one question to surface what's already occupying their thinking:

"If you could solve one problem from this sprint with a magic wand, what would it be?"

Or use TeleRetro's AI Icebreaker Bot to generate something suited to the mood in the room.

Then:

1. Start icebreaker music: café ambience works well here; it reinforces the format's spirit.
2. Switch on anonymous brainstorming mode so people generate topics independently.
3. Set a 5-minute timer for topic generation.

Don't rush this phase. Topics generated under pressure tend to be safe and generic — the more topics in To Discuss, the better the session.

☕️ To Discuss

What topics do you want to talk about?

This column is the beating heart of Lean Coffee. Team members add anything that's on their mind: process issues, interpersonal dynamics, technical concerns, wins worth examining, or questions they've been sitting with. There are no wrong topics.

Encourage specificity. "Communication" is a topic. "The handover between front-end and back-end during the checkout feature" is a conversation.

💬 Discussing

Which topic are we working through right now?

One card lives here at a time. Move the highest-voted topic into Discussing when the session starts.

Set a timer for 5–8 minutes. When it ends, run a quick vote: thumbs up to continue for another 5 minutes, thumbs down to move on. This keeps topics time-boxed without the facilitator having to be the one to cut the conversation short; the team decides together.

Capture any action items before closing a topic. It's easy to have a rich discussion and then move on without committing to anything.

✅ Discussed

What have we resolved?

Cards move here when the team votes to close them. Keep the card visible; it's a useful record of what the team addressed, especially if you export the summary after the session.

If you run out of time before working through every topic, note which ones didn't get discussed. They're candidates for the start of next sprint's retro or a follow-up async conversation.

Facilitating the discussion

Your role as facilitator in a Lean Coffee session is mostly logistical:

• Manage the timers so discussions don't run indefinitely.
• Run the continue/move-on votes clearly and move cards between columns.
• Prompt for action items before each topic closes.
• Watch the clock so high-voted topics later in the list don't get cut short by an overlong first discussion.

A rough time split for a 60-minute session: 10 minutes for topic generation and voting, 5–8 minutes per topic (expect to cover 5–7 topics at this pace), 5 minutes to close and review actions.

Resist the urge to add your own topics as the facilitator. Lean Coffee is explicitly a team-owned format.

Variations

Silent voting only. If the team is prone to social voting (choosing topics because others chose them), switch to emoji-only voting and reveal all votes simultaneously.

Themed Lean Coffee. Add a loose constraint before topic generation, "today's topics should relate to team health, not delivery," when you want to steer without setting a fixed agenda.

Combined with Pulse Survey data. Run a Pulse Survey before the session and share the results as the team generates topics. It grounds abstract feelings in actual data and often sparks topics people wouldn't have thought to add themselves.

Related formats

• Start, Stop, Continue: When you want a structured agenda with three clear action-oriented columns instead of a team-driven one.
• DAKI: Drop, Add, Keep, Improve. More prescriptive than Lean Coffee but similarly action-focused.
• Mad Sad Glad: When you want to surface emotional responses before jumping to topics and solutions.
• Sailboat: When the team needs a warmer, visual metaphor to get conversation flowing before tackling specific issues.

All formats are available on every TeleRetro plan. See pricing for details.

Start a Lean Coffee Retro View all retro templates

---

Frequently Asked Questions

What is the Lean Coffee retrospective format?

Lean Coffee is an agenda-free retrospective format where the team, not the facilitator, decides what to discuss. Team members propose topics, vote to prioritise them, and work through the highest-voted items in order. Each topic is time-boxed, and the team votes at the end of each time box on whether to keep discussing or move on. This gives every team member an equal voice in shaping the conversation, regardless of seniority or confidence.

When should you use Lean Coffee for a retrospective?

Lean Coffee works well when the team has specific pressing topics they want to address, when the facilitator wants to step back from driving the agenda, or when standard retrospective formats have started to feel repetitive. It suits self-organising teams who are comfortable with ambiguity. It works less well for brand-new teams who need more structure, or when the facilitator has a specific outcome they need the session to reach.

How do you run a Lean Coffee retrospective?

1. Generate topics: give the team 5–10 minutes to add topics to the To Discuss column. Encourage anything on their minds, not just process issues.
2. Vote: each person votes for the topics they most want to discuss. Use TeleRetro's voting feature or emoji voting.
3. Discuss in order: move the highest-voted topic to Discussing and set a timer for 5–8 minutes.
4. Timebox check: when the timer ends, the team votes thumbs-up to continue for another 5 minutes, or thumbs-down to move on.
5. Capture actions and move on: once a topic closes, capture any action items, move the card to Discussed, and start the next topic.

How is Lean Coffee different from other retrospective formats?

Most retrospective formats give the team predefined columns to fill. What went well? What could be improved? Lean Coffee has no preset topics. Everything comes from the team. This makes it more flexible and team-driven, but it also means the quality of the session depends on the topics people bring. It is one of the few formats where the facilitator's role is almost entirely logistical rather than editorial.

What are some alternatives to the Lean Coffee retrospective?

If you want more structure than Lean Coffee provides, consider:

• Start, Stop, Continue: direct action-language format with three preset columns
• DAKI: Drop, Add, Keep, Improve; four columns that keep the conversation action-focused
• Sailboat: visual metaphor format that works well when the team needs a warmer, less direct conversation
• Mad Sad Glad: emotions-first format that often surfaces topics that structured formats miss