Lean Coffee
The timer is the format. Without the five-minute box and the thumbs vote, you're just having a meeting.
An emergent-agenda format from Jim Benson and Jeremy Lightsmith (Seattle, 2009). Topics get pitched, dot-voted, ranked, and discussed in five-minute timeboxes. A Roman vote — thumbs up to extend, thumbs down to move on — keeps any one topic from eating the meeting.
When to use
When the team has more topics than time, when the agenda is genuinely contested, or when the last three retros went over because there was too much to talk about. Don't run it as your default — running Lean Coffee on a quiet sprint produces a thin agenda and an awkward silence. Skip it for a team in conflict; you'll spend eight minutes arguing about what to vote on.
How it runs
Pitch topics, two minutes
Everyone writes topics on cards, one per card. No discussion of which are good — the dot vote sorts that. The pitch phase is fast or it eats the meeting.
Dot-vote and rank
Each person gets three dots, distributed however. Sort the cards by votes; that's the agenda for the rest of the meeting. The ranking is the agenda — you don't argue about order.
Five-minute timebox per topic
Pick the top card. Set a five-minute timer. Discuss until the timer fires, then run the Roman vote — thumbs up to extend, thumbs down to move on, sideways to abstain. Majority decides.
Halve the extension
First extension is two minutes. Next is one. After that, move on regardless. The extension rule is the load-bearing piece — without it, the first hot topic eats the meeting.
Capture commitments at the end
Last five minutes: any topic that warranted action gets a name and a deadline. Lean Coffee surfaces the agenda; the commitment phase is what makes it a retrospective.
Why it works
Most retros let the loudest person frame the agenda. Lean Coffee replaces them with a vote and a timer. The dot vote distributes the agenda-setting power; the timer enforces the team's collective attention budget; the Roman vote prevents anyone from monologuing. It's the format that admits the agenda is the hard part of a retro and solves for it directly.
Variations
- Two dots instead of three for a smaller team — three dots from six people produces a flat ranking.
- Anonymous topic pitching for politically charged sprints. The dot vote is already anonymous; making the pitch anonymous too removes the last political signal.
- Run a 'closing Lean Coffee' at end-of-quarter — pitch the patterns from the past three months and vote on which to address.
Facilitator notes
The facilitator's job is the timer, not the discussion. Don't add your own topics — your card competes with the team's, and you'll either underrank yourself or distort the vote. If a topic gets no votes, drop it; the team has voted with its silence and that's an answer.
Pitfalls
- Skipping the timer. The five-minute box is the format. Without it you've run a roundtable.
- Letting the first topic run for twenty minutes. That's the meeting. Halve the extension rule exists because this is the default failure mode.
- Generating a thin agenda. If the dot-vote total is half the cards or less, the team didn't have topics — switch to SSC and end early.
- Running it as a status meeting. If topics are 'updates on X', it's not a retro, it's a standup with a fancy name.
Remote tips
The Roman vote on video is the hardest part of remote Lean Coffee — three quick reactions in a 12-tile grid is unreadable. Use a shared poll widget or have everyone type +/- in chat on the timer; visual hand votes don't scale. Keep the topic board sorted by votes on screen so the agenda is always visible.
Example outputs
- Topic (12 votes, 8 minutes): the design review queue is still the bottleneck — what do we change?
- Topic (5 votes, 5 minutes): standup is too long. Three-sentence updates from now on.
- Topic (1 vote): Friday demo format. Dropped — nobody wanted to discuss it; not the meeting today.
- Commitment: standup format change. Owner: Priya. Effective Monday.
FAQ
- Lean Coffee or Start/Stop/Continue?
- Lean Coffee when the team has more topics than time and the agenda is contested — letting the room set the agenda by vote is the value. SSC when you want a simple, repeatable format you can run every sprint without thinking about it. SSC is the better default.
- Can I skip the timer?
- No. The timer is the format. Skip the timer and you've removed the only forcing function — the meeting becomes a roundtable where the most senior person sets the duration of every topic.
- What if the team can't generate topics?
- Lean Coffee assumes engagement. If the topic pitch produces six cards from a team of eight, end early and run SSC next sprint instead. The format doesn't work in low-energy retros.
Related activities
Recommended use cases
Sprint Retrospectives
Run a fast, repeatable retro at the end of every sprint.
Remote Teams
Run retrospectives that work when nobody's in the same room.
Teams That Hate Icebreakers
The function is real. The format is wrong. Run a temperature check and get to the work.
All-Hands Meetings
Most retro formats break above twenty-five people. The page's job is naming which ones survive.