Run effective agenda-less meetings with Lean Coffee
Run effective agenda-less meetings with Lean Coffee
Most recurring team meetings have the same structural problem: the agenda was set by whoever sent the calendar invite. Topics arrive in order of whoever thought of them first, or whoever has the most organisational gravity. The thing the whole team actually needs to talk about is number seven, and you never get to seven.
Lean Coffee is a response to what a meeting actually is — a group of people with more things to discuss than there is time to discuss them — rather than a response to what we'd like it to be. It doesn't pretend the agenda is comprehensive or that the order matters. Instead, it hands that authority to the room, collectively, in real time. The team decides what gets discussed. The most important things float to the top. Everything else gets noted and, if nobody votes for it, it probably wasn't critical anyway.
The format works especially well for regular recurring meetings that have started to feel like they're going through the motions: weekly retrospectives, team check-ins, project syncs. Or for teams that consistently have more to talk about than time to talk about it.
What is Lean Coffee?
Lean Coffee is a structured, agenda-less meeting format developed by Jim Benson and Jeremy Lightsmith in Seattle in 2009. The name comes from the lean software development movement. The core idea: topics are generated by everyone in the room, prioritised democratically, and discussed in strict timeboxes, so the conversation is always on the most pressing thing and never gets stuck.
Unlike most meeting formats, the agenda is built in the first five minutes of the meeting itself.
When to reach for it
- When recurring meetings feel like they've calcified around the same topics and the same voices
- When the team consistently has more to discuss than the meeting allows
- When unresolved issues recirculate from one meeting to the next without resolution
- When the agenda is effectively set by one person and others disengage
- When a team retrospective format needs refreshing
How to run it
Before the meeting:
- Assign a process facilitator. This is not the most senior person in the room. It is whoever is wearing the process hat for this session. In regular teams, rotate this role — more on why below.
In the meeting:
- Generate topics. Give everyone 3–5 minutes to write topics on sticky notes — one topic per note. In person, these go on a whiteboard. Remotely, use a shared digital whiteboard. Topics can be anything: a question, a problem, a decision, an update that needs discussion. Crucially, they're written before anyone has spoken, so early contributions don't anchor the room.
- Brief the topics. Each person reads out their topics, one sentence each — no discussion yet. The facilitator groups obvious duplicates.
- Vote. Each person gets one dot per topic, as many topics as they want. Anonymous voting matters here: if people can see who voted for what, status dynamics reassert themselves and topics get avoided. Use a digital tool that obscures individual votes, or have everyone place dots simultaneously in person.
- Prioritise. Stack the topics by votes, highest to lowest. This is the order of discussion.
- Discuss. Start the timer. Simple topics: 4 minutes. Complex topics: 8 minutes. At the end of each timebox, the facilitator calls time and takes a quick show of hands: continue or move on? If the group wants to continue, run one extension — half the original timebox (2 or 4 minutes). Then move on regardless. If a topic clearly warrants a dedicated conversation, the facilitator notes it and suggests it gets calendared separately with the right people in the room.
- Continue down the list until time runs out. Anything not reached is noted. The team decides at the close whether anything unaddressed needs to be carried forward or calendared.
Why it works
Psychological safety and participation research (Edmondson, 1999) consistently shows that who speaks first shapes what gets said. When a senior person opens a meeting with their priorities, the frame is set and deviation feels costly. Lean Coffee removes that dynamic by generating topics anonymously before discussion begins. Everyone's concern is on the board before anyone has positioned theirs as more important.
Timeboxing is a well-established mechanism from the lean and agile traditions: hard limits on discussion time force prioritisation and prevent Parkinson's Law: the tendency for work (or conversation) to expand to fill the time available. The extension mechanism matters here. Without an offramp, groups either run over on one topic and abandon the rest, or feel guilty stopping a conversation that's going somewhere. The half-timebox extension gives the group a legitimate way to say this needs more time without letting it take over the meeting.
Shared ownership of process (as distinct from content) is the structural move that makes rotating the facilitator role significant. In most teams, process authority is invisible and unequally distributed. Whoever called the meeting holds it by default. Making the role explicit, named, and rotated means everyone experiences what it costs to hold it, and no one gets to use it as a soft proxy for organisational power.
What to watch for
The facilitator who responds to content. The process facilitator's job is to tend the container: to track time, run the extension vote, steward the close of one topic and the open of the next. The moment they respond to what's being said, they've stepped out of role and the process starts to drift. The clearest signal that a facilitator needs coaching: they're talking about the topic rather than managing the timebox.
Visible voting. If people can see whose dot is whose, they vote for what's safe. The anonymity isn't a nice-to-have. Tt's the mechanism that makes the prioritisation honest. Use simultaneous physical voting or a tool that keeps individual votes private.
The topic that won't die. Some topics are genuinely complex and need more than a Lean Coffee slot. The extension mechanism handles this, but the facilitator needs to be willing to name it clearly: "This is important and it needs its own conversation — let's get it calendared." Leaving it in the queue to recirculate is the failure mode.
Over-voting. Lean Coffee works best when topics are plentiful and time is scarce, so the prioritisation does real work. If a team consistently votes for everything, the signal is either that topics are too few or that people don't trust the format to carry things forward. Both are worth addressing.
Go deeper
- Jim Benson & Jeremy Lightsmith — leancoffee.org
- Jim Benson & Tonianne DeMaria Barry, Personal Kanban (the parent methodology)
- Amy Edmondson, Psychological Safety and Learning Behavior in Work Teams (1999)
- Digital template: Miro/Canva — [coming soon]