What is Lean Coffee — the self-organizing meeting format

Lean Coffee is a structured meeting format with no pre-defined agenda. Participants gather, propose topics on the spot, vote on which ones matter, and discuss each in a strict 5-minute timebox. When the time runs out, the group votes again: continue or move on.

Invented in Seattle in 2009 by Jim Benson and Jeremy Lightsmith, it is used daily by agile teams, OKR retrospectives, product standups, community meetups, and — increasingly — remote-first companies who want meetings that end on time and produce decisions.

The five rules

1. No agenda before the meeting. The group builds it live.
2. Topic proposal. Everyone writes the topics they care about (one per card).
3. Dot voting. Each person gets a small number of votes (usually 2–3) to distribute across topics.
4. Ranked discussion. Topics are discussed in vote order, highest first.
5. Fixed timebox per topic. 5 minutes. When it ends, the group votes: continue 3 minutes, or move on.

Why it works when traditional agendas fail

A traditional meeting agenda is written by one person, usually a manager, usually the day before. It reflects their model of what matters. It is almost always wrong by at least one topic — the one thing that has actually changed in the past 24 hours and that nobody anticipated.

Lean Coffee inverts the flow. Knowledge is distributed: each person in the room holds a fragment of the truth — a stuck ticket, a customer complaint, a process friction, a new idea. The format lets that knowledge surface before any time is spent discussing it. The group then allocates its attention by vote, not by hierarchy.

This maps directly onto what Friedrich Hayek called the knowledge problem: no central planner can aggregate dispersed, tacit knowledge as well as the market-like process of revealed preference. The vote is the price signal of the meeting.

The 5-minute timebox is not arbitrary

Five minutes is long enough to state a problem, hear two or three reactions, and agree on a next step — or to conclude that the topic needs offline work. It is short enough that nobody is tempted to solve the problem in the room. Lean Coffee is an alignment format, not a working session.

Parkinson's law — work expands to fill the time available for its completion — is particularly cruel to meetings. A topic given 30 minutes will take 30. A topic given 5 will usually reach a useful conclusion by minute 4.

Running Lean Coffee remotely

The format translates naturally to distributed teams, but it needs three things that in-person Lean Coffee takes for granted: a shared board, a visible timer, and a clear speaker rotation.

That is what Punkto provides. Participants propose topics as cards, vote in one click, and the facilitator moves topics between columns (Proposed → To discuss → Discussing → Done) in real time. A cascading timer shows both the topic countdown and the total session. A raise-hand queue manages speaking turns without anyone having to unmute to say “I wanted to add —”.

Typical cadence

• 0–5 min: Topic proposal. Everyone adds cards.
• 5–8 min: Dot voting.
• 8–55 min: Discussion, topic by topic, 5-minute timebox each. Continue votes at each boundary.
• 55–60 min: Action items and next owners. Export or email summary.

When Lean Coffee is the wrong tool

Lean Coffee is not for every meeting. It works best for:

• Regular sync meetings (weekly syncs, agile standups, retrospectives)
• Cross-functional alignment where nobody has full context
• Community meetups and open-space conferences
• Product reviews and stakeholder check-ins

It is a bad fit for meetings with a single predefined deliverable: a contract negotiation, a design critique of a specific artifact, an incident post-mortem where the facts are already known. Those need a linear agenda.

If you find yourself running three of your five weekly meetings as Lean Coffee, you are probably doing it right. If all five fit the format, one of them should probably not exist at all.

Further reading. The original leancoffee.org page documents the in-person protocol. Jim Benson's writing on personal kanban pairs well with it.