Lean Coffee
A facilitated, time-boxed meeting format for structured, participatory discussion and democratic prioritization of topics.
Classification
- ComplexityMedium
- Impact areaOrganizational
- Decision typeOrganizational
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Dominant voices can skew prioritization
- Timeboxes may lead to superficial outcomes
- Lack of follow-up leads to lost actions
- Use clear timeboxes and a visible timer
- Encourage everyone to suggest topics
- Document decisions immediately
I/O & resources
- Participant topic suggestions
- Timer or time control
- Visualization tool (board, whiteboard, tool)
- Prioritized topic list
- Assigned actions and owners
- Brief record of decisions
Description
Lean Coffee is a facilitated, time-boxed meeting format for focused, participatory discussions without a preset agenda. Participants propose and democratically prioritize topics, addressing each in short iterations. It is useful for retrospectives, community sessions and ad-hoc decision making. Promotes focus, shared ownership and efficient time use.
✔Benefits
- Quick prioritization of topics by the group
- Encourages equality and engagement
- Efficient use of limited meeting time
✖Limitations
- Not suitable for very detailed, long decision processes
- Depends on active participation
- Requires facilitation discipline and preparation
Trade-offs
Metrics
- Number of topics handled per hour
Measures efficiency and throughput of discussions.
- Decisions/actions per session
Counts concrete, assigned actions after the session.
- Participant satisfaction
Short survey on perceived usefulness and efficiency.
Examples & implementations
Startup retrospective
A small product team used Lean Coffee weekly to prioritize blockers and make quick decisions.
Community meetup
A developer community ran Lean Coffee sessions for knowledge sharing and spontaneous topic blocks.
Product idea sprint
A product team used Lean Coffee to prioritize many ideas in one day and assign owners.
Implementation steps
Explain rules and timeboxes
Let participants propose topics
Prioritize topics (e.g. dot voting)
Discuss each topic in a fixed timebox
Document outcomes and actions
Clarify follow-up dates and responsibilities
⚠️ Technical debt & bottlenecks
Technical debt
- Growing list of unresolved topics without owners
- Missing integration with task tracking systems
- Inconsistent facilitation practice leads to inefficiency
Known bottlenecks
Misuse examples
- Using it as a substitute for deep workshops on complex topics
- Running sessions without clear time structure
- Only dominant voices discuss; no broad participation
Typical traps
- Too short timeboxes prevent meaningful discussion
- Topics remain unaddressed due to missing prioritization
- Lack of clear documentation leads to missed actions
Required skills
Architectural drivers
Constraints
- • Limited meeting time
- • Depends on team culture
- • Requires physical or digital board