Lean Coffee Retrospective

The only single-column format here — no categories, just an open, priority-ordered agenda the group builds together.

Free · No credit card · Guests join by link

The board

TOPICS

What do you want to talk about today?

Lean Coffee started as a meetup format with no agenda and a stack of sticky notes: anyone proposes a topic, the group votes, and you talk about the highest-voted item until interest runs out, then move to the next. Adapted for a retro, it strips away the categories entirely — there's no Start, no Stop, no Strengths. There's just one column: topics.

That absence of structure is the point. Category-based formats implicitly tell people what kind of thing to write; an open agenda lets whatever is actually on someone's mind surface, whether it's a process complaint, a technical question, or something that doesn't fit neatly into 'strength' or 'risk.' It's the least opinionated format in this catalog — best used when you don't yet know what the retro needs to be about.

When to use a Lean Coffee Retrospective

You don't know what the retro needs to cover yet — team energy or focus is scattered
Recurring category-based retros feel stale and the team wants a genuinely open floor
A cross-functional or ad-hoc group with no shared retro history and no obvious column scheme
Mid-crisis or mid-incident check-ins, where whatever's urgent should surface first, not fit a template

How to run a Lean Coffee Retrospective

1
Write one topic per card, no category needed
Everyone adds cards to the single Topics column — a question, a complaint, an idea, anything worth the group's time. There's no wrong column because there's only one.
2
Vote to set the agenda, not just to flag interest
Token votes here do double duty: the vote order becomes the literal agenda for discussion, most-voted topic first.
3
Time-box each topic and check in before moving on
Give each topic a rough time budget. When it's up, do a quick thumbs-up/down: keep going or move to the next topic. This is Lean Coffee's classic continuation check, and it's what keeps one loud topic from eating the whole meeting.
4
Reveal authors only if it helps
Since topics are usually questions or process points rather than personal reflections, some teams reveal authorship immediately instead of waiting for a formal reveal phase — use whichever fits the topic.
5
Convert only the topics that need one into action items
Not every discussed topic needs a follow-up — some just needed airing. Create action items for the ones that do.

Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.

Read the full facilitation guide

Example cards

What good cards look like for a software team. Specific, about the work, never about a person.

TOPICS

Are we doing too many meetings?
How should we handle urgent requests from Sales?
Should we try mob programming on the next spike?
What's really blocking the data migration?

A 45-minute agenda

0–5 minWrite topics, one per card
5–8 minVote to set the order
8–38 minDiscuss topics in seven-minute rounds; thumbs up to keep going
38–45 minAgree actions for the topics that need one

Common mistakes

Topics too broad to finish, like "our process". Ask for a question the group can answer.
One topic eating the whole session. Use the timebox and the thumbs vote.
Ending without actions. Not every topic needs one, but the important ones do.
Skipping the vote and taking topics in the order they were written.

Frequently asked questions

What is a Lean Coffee retrospective?

It's a retro built around one open agenda instead of fixed categories. People propose any topic worth discussing, the group votes on what to talk about first, and discussion proceeds in vote order with a time-check after each topic.

Why only one column instead of three?

Categories like Strengths/Risks/Learnings implicitly steer what people write. Lean Coffee removes that steering — useful when you genuinely don't know what's on the team's mind, or when recurring categorized retros have started to feel like a formality.

How do you stop one topic from taking over the whole retro?

Time-box it and do a continuation vote — thumbs up to keep discussing, thumbs down to move to the next topic. This is the core Lean Coffee mechanic and it's what keeps the agenda genuinely priority-ordered instead of first-come-first-served.

Is Lean Coffee good for teams new to retros?

It can go either way. Newer teams sometimes find an open agenda intimidating without categories to anchor on; teams who've outgrown categorized retros often find it liberating. If you're unsure, try Strengths·Risks·Learnings first and switch to Lean Coffee once retros feel routine.

Can Lean Coffee replace the sprint retrospective?

Now and then, yes. It works well when the team has plenty to talk about and a fixed format would get in the way. As a permanent replacement it can drift, so alternate it with a structured format every few sprints.