Lean Coffee vs. Retrospective: When to Use Which

Two meetings, two starting points

Teams often ask whether Lean Coffee can replace their sprint retrospective, or whether it's just another retro format. The short answer: they overlap, but they're built for different jobs. Knowing the difference helps you choose the right one on any given day, and it helps you avoid a retro that feels like a chat, or a Lean Coffee that turns into a status meeting.

What is a retrospective?

A retrospective is a recurring meeting in which a team looks back on a recent period of work, usually a sprint or iteration, and decides how to improve. It is one of the events in Scrum, but teams using Kanban, SAFe or no framework at all run them too.

A typical retro follows a facilitated structure:

1. Set the stage. Check in and create a safe space.
2. Gather data. What happened? What went well, what didn't?
3. Generate insights. Why did it happen? Look for patterns and root causes.
4. Decide what to do. Pick one or two concrete improvements.
5. Close. Wrap up and, often, reflect on the retro itself.

The facilitator usually picks a format for the gather-data step, such as Start/Stop/Continue, Mad/Sad/Glad, the Sailboat or 4Ls (Liked, Learned, Lacked, Longed for). Changing retrospective formats now and then keeps the conversation fresh.

What is Lean Coffee?

Lean Coffee is a structured but agenda-less meeting, created in 2009 in Seattle by Jim Benson and Jeremy Lightsmith. Participants write down topics, pitch each in a sentence, dot-vote, and then discuss them in order of votes, one at a time, in short timeboxes of typically five to eight minutes. At each time-up the group votes whether to keep going or move on. The full mechanics are covered in what is Lean Coffee.

The key difference is who owns the agenda. In a retro, the facilitator designs the structure and the theme is fixed: the last sprint. In Lean Coffee, the participants set the agenda on the spot, and it can cover anything.

Lean Coffee vs. retrospective at a glance

When to use a retrospective

Choose a classic retrospective when:

• You need to look back on a specific period and connect outcomes to causes.
• Something went wrong and the team needs a structured, blame-free way to understand it.
• You want to dig deep into one theme rather than skim several.
• The team is new and benefits from guided questions to build a shared picture.
• You want to track improvement actions from one sprint to the next.

When to use Lean Coffee

Choose Lean Coffee when:

• You don't know what people want to talk about, and don't want to guess.
• The topics go beyond the sprint: career questions, tooling, cross-team friction, strategy.
• You're bringing together people from several teams, like a community of practice or a guild.
• Your retros feel stale and people are going through the motions.
• You want to hear from quieter voices. Voting on topics gives everyone equal weight in setting the agenda.

Running a Lean Coffee retro

Lean Coffee works surprisingly well as a retrospective format, as long as you add a little focus. A lean coffee retrospective keeps the Lean Coffee mechanics but scopes the topics to the last iteration.

How to run it

1. Set the frame. Open with one sentence: "Topics should be about how the last sprint went, or how we work together."
2. Check in quickly. A one-word round or a one-to-five rating of the sprint takes two minutes and warms people up.
3. Gather topics. Give everyone three to five minutes to write topics. Phrasing them as questions helps: "Why did the release slip again?" is easier to discuss than "release".
4. Pitch and cluster. Each person reads their topics in a sentence. Merge duplicates.
5. Dot-vote. Two or three votes per person is common.
6. Discuss in timeboxes. Start with the top topic, five to eight minutes each, with a keep-going vote at time-up and shorter extensions of two to four minutes.
7. Capture an action or takeaway per topic. Not every topic needs an action, but every action needs an owner.
8. Close with a commitment. In the last five minutes, pick the one or two actions the team will actually do next sprint.

That final step is what turns a Lean Coffee into a retro. Without it, you get a good conversation but not necessarily improvement. For timeboxing and wrap-up tips, see how to facilitate a Lean Coffee.

Tips for a better Lean Coffee retro

• Pre-seed with data. Share a few facts before the session (cycle time, incidents, what was delivered) so topics are grounded.
• Allow topics to be added before the meeting. It helps people who need time to reflect.
• Revisit last sprint's actions first. Two minutes on "did we do what we said?" keeps accountability alive.
• Rotate the facilitator. Lean Coffee is easy to facilitate, so it's a good format to share the role.

Combining both

You don't have to choose one forever. Some patterns that work well:

• Alternate. Run a structured retro one sprint and a Lean Coffee retro the next. The change of rhythm keeps both fresh.
• Lean Coffee inside a retro. Use a classic format such as Start/Stop/Continue for gathering data, then dot-vote the items and discuss them Lean Coffee style, in timeboxes.
• Retro inside a Lean Coffee. If a Lean Coffee topic reveals a real problem, park it and give it a dedicated retrospective with proper root-cause analysis.
• Separate cadences. Keep the sprint retro for the delivery team and run a monthly Lean Coffee for a wider group, like a department or a community of practice.
• Let leftovers roll over. Topics that didn't make it into a retro can go to the next Lean Coffee, and vice versa.

Common pitfalls

Treating Lean Coffee as a retro without closure

Great conversations, no decisions. If you use Lean Coffee as a retro, always reserve time at the end to commit to actions.

Skimming everything, solving nothing

Short timeboxes are a feature, but if the group always votes to move on after five minutes, big issues never get the depth they need. When a topic clearly deserves more, schedule a separate session for it.

Letting the loudest voices set the agenda

Lean Coffee protects against this with voting, but only if votes are cast independently. Vote silently and simultaneously, and consider keeping votes hidden until everyone is done.

Running the same retro format forever

A retro that always asks the same three questions gets the same three answers. Lean Coffee is one of several retrospective formats worth rotating in.

Forgetting the actions

Whatever the format, write down actions with an owner, and check them at the start of the next session.

Running a Lean Coffee retro in LeanBrew

If you want to try a Lean Coffee retro without whiteboard prep, LeanBrew walks the group through the phases: Gather (everyone adds topics, including before the meeting), Vote (each person spends a few beans, with votes private until the reveal) and Discuss (top topics on stage in short timeboxes, with a Keep going / No preference / Move on vote at time-up). Notes, actions and owners end up in the minutes and on an action board, so checking last sprint's actions is easy. You can set up a recurring session per sprint, and topics you didn't reach roll over automatically. Start a free 30-day trial and run your next retro with it.

Frequently asked questions

Can Lean Coffee replace a sprint retrospective?

It can, as long as you scope the topics to the last iteration and end with one or two concrete improvement actions. Many teams alternate Lean Coffee retros with more structured formats instead of replacing retros entirely.

What is a Lean Coffee retro?

A Lean Coffee retro is a retrospective that uses the Lean Coffee format: the team writes and votes on topics about the last sprint, discusses them in short timeboxes, and closes by committing to improvement actions.

What is the main difference between Lean Coffee and a retrospective?

A retrospective is a facilitator-structured look back at a specific period of work. Lean Coffee has no predefined agenda; participants propose and vote on the topics, which can be about anything.

How often should you run a Lean Coffee retro?

As often as your regular retro, usually at the end of each sprint. Many teams use it every second or third retro to break the routine of a fixed format.

Which retrospective formats combine well with Lean Coffee?

Formats with a clear gather-data step, such as Start/Stop/Continue, Mad/Sad/Glad or 4Ls, combine well: collect items with the format, then dot-vote and discuss them Lean Coffee style.