Lean Coffee: the complete guide

What is Lean Coffee?

Lean Coffee is a meeting format in which the participants decide the agenda at the start of the meeting, not beforehand. Everyone proposes topics, the group votes on what matters most, and then discusses the topics one at a time, in order of votes, inside short timeboxes. When a timebox ends, the group decides together whether to keep going or move on.

That's the whole idea. It sounds almost too simple, but it fixes a surprising number of meeting problems at once:

• No stale agenda. The topics are whatever is on people's minds today, not what someone guessed last week.
• Everyone gets a voice. Anyone can put a topic on the board, and everyone votes with equal weight.
• The important things come first. Voting puts the topics with the most energy at the top, so if you run out of time, you've run out of the least important topics.
• No endless rabbit holes. Timeboxes and a quick group check keep discussions from dragging on after they've stopped being useful.

People often describe Lean Coffee as "structured but agenda-less." The structure lives in the process, not in a list of topics prepared in advance.

Where Lean Coffee comes from

Lean Coffee was started in 2009 in Seattle by Jim Benson and Jeremy Lightsmith. They wanted a way to get together and have useful conversations about Lean and agile topics without the overhead of organizing speakers or an agenda. The group met over coffee, and the name stuck: Lean for the Lean thinking behind the format, Coffee because that's literally how it began.

The format spread quickly through the agile community, first as a meetup format and later inside companies. The community site is leancoffee.org, which describes the basic format and lists groups around the world.

A big part of Lean Coffee's DNA comes from personal Kanban, which Jim Benson also popularized. The board you use in a Lean Coffee is essentially a tiny Kanban board: work (in this case, topics) flows from left to right, you limit work in progress to one topic at a time, and everything is visible to everyone.

The Lean Coffee format, step by step

A Lean Coffee meeting has four phases. The exact timings vary, but the flow is always the same.

1. Set up the board. Draw or create three columns: To Discuss, Discussing, Discussed.
2. Gather topics. Everyone writes topics they'd like to talk about, one per sticky note, and briefly pitches each one to the group.
3. Vote. Everyone gets a small number of votes (usually two or three dots) and places them on the topics they most want to discuss.
4. Discuss. Sort the topics by votes. Move the top topic to Discussing, start the timer, talk. When time is up, the group votes to continue or move on. Repeat until the meeting ends.

Let's look at each phase in more detail.

1. Set up the board

The classic Lean Coffee board has three columns:

Only one topic sits in Discussing at a time. That single rule does a lot of the work: it keeps the conversation focused and makes it obvious to everyone what's being discussed.

Some groups add a fourth area for actions or takeaways, so outcomes don't get lost on the backs of sticky notes.

2. Gather topics

Give everyone a few minutes to write down topics. One topic per note, written clearly enough that someone else can read it from a distance (or on screen). A few guidelines help:

• Keep it short. A few words or a question works best: "How do we handle urgent bugs mid-sprint?" beats a paragraph.
• Anything goes, within the purpose of the meeting. If the Lean Coffee is for the team, topics should be relevant to the team. If it's an open meetup, the net is wider.
• Quantity is fine. People can add several topics. Voting will sort them out.

Once topics are written, each author gets a few seconds (think 15 to 30 seconds per topic) to pitch it: what it is and why it matters to them. This isn't the discussion yet; it's just enough context for people to vote sensibly. If two topics are basically the same, merge them now.

Stuck for topics? Our list of Lean Coffee topic ideas has prompts for teams, leadership groups and communities of practice.

3. Vote

Each participant gets a fixed number of votes, commonly two or three. They can spread them across topics or put more than one on a single topic if they feel strongly. This is classic dot voting.

When everyone has voted, sort the To Discuss column so the topic with the most votes is at the top. Ties can be broken with a quick show of hands or by the facilitator's judgment; it rarely matters much.

A small but useful refinement is private voting: people vote without seeing each other's choices until everyone is done. This avoids bandwagon effects, where the first few dots attract all the others. In a physical room that's hard to do; digital tools make it easy.

4. Discuss in timeboxes

Now the actual conversation starts. Move the top topic into Discussing, start a timer and let the author kick off.

Timeboxes are usually 5 to 8 minutes for the first round. That feels short the first time, and that's the point: it forces the conversation to get to the substance quickly.

When the timer goes off, the group votes on whether to continue. The usual method is often called Roman voting:

If most thumbs are up, add a shorter extension, usually 2 to 4 minutes, and check again when that runs out. If the majority is sideways or down, capture any takeaway, move the note to Discussed and pull the next topic in.

Before moving a topic to Discussed, take ten seconds to write down what came out of it: a decision, an insight, an open question, or an action with an owner. That's what makes a Lean Coffee useful after the meeting ends, not just during it.

Lean Coffee rules (the short version)

There's no official rulebook, but most Lean Coffee sessions follow the same handful of principles. If you want something to put on a slide or read out at the start, use this:

1. Anyone can propose a topic. One topic per note.
2. Pitch it briefly. A sentence or two, then move on.
3. Everyone votes equally. Usually two or three votes per person.
4. Discuss in vote order. Highest votes first.
5. One topic at a time. Only one note in Discussing.
6. Respect the timebox. When the timer goes, the group votes to continue or move on.
7. The group decides, not the loudest voice. Roman voting settles whether to continue.
8. Capture outcomes. Write down takeaways and actions before moving on.

The rules are intentionally light. What matters is the spirit behind them: a democratic agenda, focus on one thing, and short conversations that stop when they've stopped being useful.

A typical Lean Coffee agenda

Although the topics aren't known in advance, the shape of the meeting is. Here's a typical Lean Coffee agenda for a one-hour session with a team of five to eight people:

With a 7-minute timebox and a few extensions, expect to get through roughly four to six topics in an hour. For recurring sessions with regulars, you can shave the welcome down to a minute and give that time to discussion.

For a full facilitator script with 45- and 60-minute versions, see how to facilitate a Lean Coffee.

When to use Lean Coffee

Lean Coffee works whenever a group has things to talk about but you can't (or don't want to) predict exactly what they are. Common uses:

• Team syncs. A weekly or biweekly Lean Coffee replaces a status meeting nobody enjoys with a conversation about what actually matters this week.
• Retrospectives. Lean Coffee makes a good alternative retro format, especially when a team is tired of the same "went well / to improve" exercise. See Lean Coffee vs. retrospective for a detailed comparison.
• Communities of practice. Guilds and chapters (testing, front-end, product, agile coaching) use it to surface shared problems without someone having to prepare a talk.
• All-hands Q&A. Employees add questions, vote them up, and leadership answers the most-voted ones first, in timeboxes.
• Management team meetings. Leadership teams use it to spend time on the topics that need the group, rather than on updates that could have been an email.
• Meetups and unconferences. The original use case. It needs almost no preparation and works well with strangers.
• Onboarding. New hires add questions, and a few experienced colleagues discuss the top-voted ones.

When Lean Coffee is not the right fit

It's a flexible format, but not a universal one. Consider something else when:

• You need a specific decision by the end of the meeting. Lean Coffee is great for surfacing and exploring, less so for driving a single, pre-defined decision to closure. Use a decision meeting with a clear proposal instead.
• The content is fixed. Training sessions, formal reviews and presentations have a known agenda, so building one on the spot adds nothing.
• There's a crisis. An incident call needs a lead and a clear sequence, not a vote on what to talk about.
• The group is very large and in one conversation. Beyond roughly ten people in a single discussion, many people won't get to speak. Split into multiple tables instead (more on that below).

Lean Coffee group size

Lean Coffee works well for 3 to about 10 people in one conversation. Below three, you don't really need a process. Above ten, discussions start to feel like a panel with an audience.

For larger groups, the usual approach is to split into tables: several Lean Coffee groups running in parallel, each with its own board and timekeeper. At a meetup, people simply pick a table. At an all-hands, you can split by random assignment or by interest. A short plenary at the end, where each table shares one or two takeaways, ties it together.

Tips for a better Lean Coffee

A few small habits make a noticeable difference.

State the purpose up front. "This is our team Lean Coffee; topics about our work, our process and how we collaborate" gives people enough of a frame to write relevant topics.

Appoint a timekeeper. The facilitator can do it, but in a recurring session it's nice to rotate. The timekeeper's only job is to call time and prompt the Roman vote, which frees everyone else to focus on the conversation.

Keep the first timebox short. It's tempting to set 10 or 15 minutes "to give topics room." Resist that. Short timeboxes with the option to extend work better than long ones that fill up with repetition.

Let the author open. The person who proposed the topic kicks off with what they want out of it: advice, a decision, a sanity check, just venting. That frames the discussion and helps everyone know when it's done.

Write down outcomes, not transcripts. One line per topic is enough: "Agreed to try pairing on urgent bugs for two sprints; Sam to set up a trial."

Carry leftovers forward. Topics you didn't get to aren't lost. In a recurring Lean Coffee, bring them back next time and let the group re-vote alongside new topics. Priorities change, and some topics quietly resolve themselves.

Ask for quick feedback. Thirty seconds at the end ("What should we do differently next time?") keeps the format fresh.

Running Lean Coffee remotely

Lean Coffee translates well to video calls, but sticky notes on a wall obviously don't. You need a shared board everyone can add to, a way to vote (ideally private until everyone is done), a visible timer, and a lightweight way to do the Roman vote.

Remote sessions also benefit from a bit more structure: call on people by name during pitches, use the chat or reactions for quick signals, and keep cameras on if your culture allows it. Our guide to remote Lean Coffee goes deeper into tools, hybrid setups and pitfalls.

Common Lean Coffee mistakes

These come up often, especially in the first few sessions:

• Skipping the vote. Without voting, you're back to "whoever talks first sets the agenda."
• Ignoring the timer. Once people see that time isn't enforced, timeboxes stop meaning anything.
• Letting pitches turn into discussions. Keep pitches to a sentence or two. The discussion comes later.
• No record of outcomes. A good discussion without a takeaway fades within a day.
• Treating it as a status meeting. "Update on project X" makes a poor topic. "Project X is slipping, how can we help?" makes a good one.
• The same people talk every time. The facilitator should actively invite quieter voices in, for example by asking the author or someone who voted for the topic to share first.

Running your Lean Coffee in LeanBrew

If you'd rather not juggle a whiteboard, a timer app and a spreadsheet for notes, LeanBrew is built for exactly this format. A session moves through Gather (everyone adds topics, no agenda in advance), Vote (each person spends a few beans, and votes stay private until the reveal) and Discuss (the top topics go on stage in short timeboxes; when time is up the room votes Keep going, No preference or Move on). Notes, actions and owners end up in the minutes, and leftover topics roll over to the next session with fresh votes.

Guests join with a link by typing their name, with no sign-up or install, and every screen stays in sync in real time. For recurring sessions you can keep a reusable board, schedule weekly or biweekly sessions, and get Slack reminders. You can start a free 30-day trial, and pricing is per host; participants never pay.

Frequently asked questions

What is Lean Coffee in simple terms?

Lean Coffee is a meeting where the group creates its own agenda at the start. Everyone proposes topics, votes on them, and then discusses them one by one in order of votes, in short timeboxes, deciding together when to move on.

Who invented Lean Coffee?

Lean Coffee was created in 2009 in Seattle by Jim Benson and Jeremy Lightsmith. It began as an informal group meeting over coffee to talk about Lean and agile topics without a planned agenda.

How long should a Lean Coffee meeting be?

Most Lean Coffee meetings run 45 to 90 minutes, with one hour being the most common. Individual topics usually get a 5 to 8 minute timebox, with shorter extensions of 2 to 4 minutes when the group votes to keep going.

How many votes does each person get in Lean Coffee?

Each participant usually gets two or three votes. They can spread their votes over different topics or put several on one topic they care strongly about.

What is Roman voting in Lean Coffee?

Roman voting is the quick check at the end of each timebox. Everyone shows a thumb: up to keep discussing, sideways for no preference, and down to move on to the next topic.

Is Lean Coffee a good retrospective format?

It works well as an occasional retro, especially to break a routine, because the team sets the topics itself. Scope it to the last iteration and still end with concrete improvement actions; the Lean Coffee vs. retrospective guide explains how.