View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Waste Analysis |  Agile Example Mapping |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-120 min | 30-60 min | Ongoing |
Participantsdifferent | 2-8 | 3-7 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Example Map, Acceptance Criteria, Open Questions | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | WasteLeanProcess improvement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
