The structure
Five steps from empty room to working session
Step 1: Set up the board (5 min)
Draw three columns: To Discuss, Discussing, Discussed. On a whiteboard, sticky-note paper, or a digital board like Miro or FigJam. Hand out sticky notes (physical or digital) to each participant. Briefly explain the format for first-timers: anyone can add a topic, the group votes on order, each topic gets a 5-minute timebox with the option to extend.
Step 2: Generate topics (10 min)
Silent writing. Each participant writes one topic per sticky note, as many as they want, and places them in the To Discuss column. Topics should be concrete (a specific question or problem) rather than abstract ("process"). The silent-first rule matters: it prevents the loudest voice from anchoring the topic list and ensures introverts contribute.
Step 3: Dot-vote priorities (5 min)
Each participant gets 3 dots and places them on the topics they most want to discuss. Dots can be stacked (multiple dots on one topic) or spread. The topics with the most dots move to the top of the To Discuss column. This produces a participant-prioritised agenda in five minutes that an external facilitator could not produce in an hour of preparation.
Step 4: Work the queue (35-40 min)
Pull the top sticky into Discussing. Set a 5-minute timer. The person who wrote the topic frames it briefly (30 seconds), then open discussion. When the timer ends, roman vote: thumbs up (keep going for another 5 minutes), sideways (neutral), down (move on). Majority wins. Move the discussed topic to the Discussed column. Pull the next one. Repeat until time runs out. The kanban-style flow makes work-in-progress visible and creates a natural rhythm that group conversations without a board tend to lose.
Step 5: Close (5 min)
Round-robin one-sentence takeaway from each participant. Note any topics that need follow-up beyond the session. Photograph the board for the meeting record. Lean Coffee rarely produces formal action items the way a structured retro does; the value is the conversation itself plus a small number of insights each participant takes back to their work.
When it works
Three use cases where Lean Coffee outperforms a structured agenda
CoP
Community of practice meetings
Engineering guilds, designer chapters, PM circles. The participants are the only ones who know what they want to talk about each month, and the topics shift with what is current in their work. A structured agenda would be wrong six times out of seven.
Meetup
Agile and product meetups
Local meetup chapters often default to Lean Coffee because the attendee list changes every month and no one has standing to set the agenda. The format also works without a designated speaker, which lowers the bar for organising a meetup.
Adhoc
Team ad-hoc discussions
When the team blocks 60 minutes to "talk about what is on our minds," Lean Coffee gives structure to what would otherwise drift. Use occasionally (once a quarter, not every week) to surface concerns that do not fit the regular meeting cadence.
When it does not work
When to pick a different format
Lean Coffee is not a universal format. It fails predictably in three situations.
When you need to make a specific decision
Lean Coffee is exploratory by design. If the meeting exists to pick between three known options, use the structured 30-minute decision format instead. The self-organising structure dilutes decision energy.
When the topic space is bounded by policy or compliance
Board meetings, governance reviews, regulatory check-ins all require specific topics in a specific order. Lean Coffee's emergent structure cannot satisfy fiduciary or compliance requirements. Use the board meeting template or Robert's Rules agenda.
When the group has not built psychological safety
Self-organising formats require participants to feel safe contributing without external structure to lean on. For new teams or teams with active interpersonal friction, use a more structured format that does not require participants to expose their own topic choices.
FAQ
Common questions about Lean Coffee
What is Lean Coffee?
Lean Coffee is a self-organising meeting format invented by Jim Benson and Jeremy Lightsmith in Seattle in 2009. Participants generate the agenda at the start of the meeting using sticky notes, dot-vote to prioritise, then work through topics in 5-minute timeboxes using a kanban board (To Discuss, Discussing, Discussed). The format requires no advance agenda and no formal facilitator, which makes it well suited to community-of-practice meetings, ad-hoc team discussions, and meetup-style gatherings.
How many people does Lean Coffee work for?
Best at 4 to 12 people. Below 4 the dot-voting becomes trivial (everyone votes for everything). Above 12 the format starts to fracture because not everyone gets airtime in each topic. For 12+ groups, split into multiple Lean Coffee tables of 6 to 8.
How long should a Lean Coffee meeting be?
60 to 90 minutes is the typical length. Below 45 minutes the format barely has time to work through the topic-generation and voting steps before running out of discussion time. Above 90 minutes participant attention drops measurably. The 60-minute slot supports about 5 to 7 topics at 5 minutes each plus the setup overhead.
Do you really need a kanban board?
Yes, even if it's drawn on a whiteboard or paper. The visible board is the entire point: it makes the work-in-progress visible, signals when a topic is timeboxed out, and prevents drift. For virtual Lean Coffees, use a Miro or FigJam board with three columns. Skip the board only if the group is fewer than 5 people who all know the format well.
What is the 'roman vote' in Lean Coffee?
At the end of each 5-minute timebox, participants vote with thumbs: up (keep discussing this), sideways (neutral, fine either way), down (move on). Majority decides whether to extend the topic by another 5 minutes or move to the next item. The Roman-style thumb vote is fast, visible, and prevents endless extension on a single topic that's not actually moving forward.
Can you use Lean Coffee for sprint retros?
Yes, as a fifth retro format alongside Start-Stop-Continue, 4Ls, Sailboat, and Mad-Sad-Glad. It works particularly well for teams that have run conventional retros for years and need a format change. The self-organising structure shifts the energy and surfaces topics that wouldn't fit the conventional columns. Use the sprint retrospective template's 5-phase structure as the wrapper.
Related formats
Other emergent and self-organising formats
Liberating Structures
Nine microstructures including 1-2-4-all, troika consulting, and impromptu networking.
Brainstorming session
Structured ideation with divergent-then-convergent format, related to but distinct from Lean Coffee.
Sprint retrospective (5 formats)
Where Lean Coffee fits as a fifth retro format alongside Start-Stop-Continue and others.
2-hour workshop
Structured working-session alternative when the topic is known and bounded.