Doesn't Lean Coffee just become whoever-talks-most's retro?

Only if you skip the dot-vote and the time-boxes. The format depends on both. The dot-vote prevents the loudest voice from setting the agenda. The time-boxes prevent any one topic from absorbing the whole meeting. With both in place, Lean Coffee is genuinely democratic. Without either, it isn't.

How does the move-on vote work?

At the end of each five-minute round, the facilitator asks 'Continue this topic for five more minutes, or move on?'. Each person votes thumbs up (continue) or thumbs down (move on). Majority wins. If exactly tied, move on. The format depends on the team taking the vote seriously, not voting to continue out of politeness.

Should we use Lean Coffee every sprint?

No. Lean Coffee is occasional. Every sprint and the team loses the structure that prescribed formats provide. A reasonable cadence is once every five or six retros, between rotations through Start, Stop, Continue, 4Ls, and KALM. Use it when something specific is on everyone's mind that doesn't fit a prescribed shape.

What if the team doesn't bring topics?

That's diagnostic. If the team can't surface a single thing they want to discuss, they're either disengaged from the retro process or in such a steady state that no retro is necessary. Either way, run a different format and inquire into the silence at a later time.

How does this produce action items?

It often doesn't. Lean Coffee is a discussion format, not an action format. If you need action items, end the meeting with five minutes of 'what will we commit to from this discussion?'. Treat the action-capture as a separate phase, not as something the format produces automatically.

The toolkit · Lean Coffee

Lean Coffee retrospective

An open-agenda retro. The team brings the topics, the format gets out of the way. Pull a prompt to start the conversation.

15 prompts · 1 columns · free

☕

Topics to surface

What's a topic you've been meaning to bring up but haven't?

15 prompts in this bucket

Try another framework

Frameworks that pair well with Lean Coffee.

Start, Stop, Continue

The classic. Three columns, fast to run, hard to argue with.

Glad, Sad, Mad, Wondering

Mad/Sad/Glad with a curiosity dimension. Surfaces uncertainty, not just emotion.

Mad, Sad, Glad

Emotional check-in. Surfaces the stuff data can't see.

Or see all 10 retro frameworks.

About the Lean Coffee retrospective

Lean Coffee is the retrospective format that doesn't prescribe categories. Instead of filling in pre-defined columns, the team brings the topics. Each person writes the things they want to discuss on sticky notes, the team groups them, dot-votes, and discusses the top items in time-boxed rounds. The format is named after Lean Coffee meetups, where it originated, and works for retros for the same reason: it gets the meeting out of the team's way. Use Lean Coffee when the prescribed retro categories feel forced, when the team has been together long enough to know what they need to discuss, or when something specific is on everyone's mind that doesn't fit cleanly into any standard format. The trade-off: no built-in commitments, no implicit shape. Lean Coffee is a discussion format, not an action format. Pair it with a separate commitments check-in if you need the meeting to produce backlog items.

When Lean Coffee is the right call

When the team is mature enough to surface its own agenda. When something specific is on everyone's mind that doesn't fit Start, Stop, Continue or 4Ls (a recent decision, an upcoming change, a topic that's come up in side conversations). When the team is tired of the prescribed-categories formats and engagement is dropping. When you have less time than usual and want to spend it on what matters most rather than ticking through columns.

How Lean Coffee differs from every other retro format

Every other format on this page prescribes the question. Lean Coffee inverts that: the team prescribes the questions, the format prescribes the rules of discussion (time-boxes, voting, move-on signals). That makes it the most flexible format and the least structured. It's the right call when the team can be trusted to surface the right things and the wrong call when the team needs scaffolding to get past surface answers.

Common mistakes with Lean Coffee

First: skipping the dot-vote. Without it, the loudest voice picks the topic. The whole format falls apart. Second: ignoring the time-boxes. Lean Coffee depends on the discipline of the five-minute round and the move-on vote. A team that lets discussions sprawl will run out of time on round one and never reach the topics that needed to be discussed. Third: treating it as a default format. Lean Coffee is an occasional change of pace, not a weekly cadence. Run it every sprint and the team loses the discipline that makes prescribed formats work.

Lean Coffee for an async retro

Open a doc on Monday with one heading per topic the team submits. Give everyone until Wednesday end-of-day to add topics and emoji-vote. Run a thirty-minute synchronous call Thursday on the top three voted topics. The async-vote-then-sync-discuss pattern preserves the format's spirit and works well for distributed teams.

Frequently asked

Doesn't Lean Coffee just become whoever-talks-most's retro?: Only if you skip the dot-vote and the time-boxes. The format depends on both. The dot-vote prevents the loudest voice from setting the agenda. The time-boxes prevent any one topic from absorbing the whole meeting. With both in place, Lean Coffee is genuinely democratic. Without either, it isn't.
How does the move-on vote work?: At the end of each five-minute round, the facilitator asks 'Continue this topic for five more minutes, or move on?'. Each person votes thumbs up (continue) or thumbs down (move on). Majority wins. If exactly tied, move on. The format depends on the team taking the vote seriously, not voting to continue out of politeness.
Should we use Lean Coffee every sprint?: No. Lean Coffee is occasional. Every sprint and the team loses the structure that prescribed formats provide. A reasonable cadence is once every five or six retros, between rotations through Start, Stop, Continue, 4Ls, and KALM. Use it when something specific is on everyone's mind that doesn't fit a prescribed shape.
What if the team doesn't bring topics?: That's diagnostic. If the team can't surface a single thing they want to discuss, they're either disengaged from the retro process or in such a steady state that no retro is necessary. Either way, run a different format and inquire into the silence at a later time.
How does this produce action items?: It often doesn't. Lean Coffee is a discussion format, not an action format. If you need action items, end the meeting with five minutes of 'what will we commit to from this discussion?'. Treat the action-capture as a separate phase, not as something the format produces automatically.

When not to use it

New teams without practice surfacing topics, or teams in active conflict where an open agenda will become a venting session. New teams need scaffolding (run Start, Stop, Continue or Rose, Bud, Thorn instead). Teams in conflict need facilitation (Mad, Sad, Glad with a strong facilitator).

How to run a Lean Coffee retro

1Block 30 minutes for a sprint Lean Coffee. The format compresses well because the team picks what matters.
2Open with no prompt. Give everyone three minutes of silent writing to surface the topics they want to discuss. One topic per sticky note.
3Each person reads their topics aloud, briefly. Group similar topics. No discussion yet.
4Dot-vote. Two votes per person, can stack on one topic. Order the topics by votes.
5Discuss the top topic for five minutes. At five minutes, ask: 'Continue another five, or move on?'. Majority decides. Move on if undecided.
6Repeat with the next topic until time runs out. Topics that don't get discussed roll to the next retro or the next 1:1.
7Send the topics list (with votes) in Slack within an hour, even the ones that didn't get discussed. The list itself is useful information about what the team is carrying.