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 | ![]() Agile Three Amigos | ![]() Operations Standard Work Analysis |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-120 min | 30-60 min | 15-30 min | 1-3 h |
Participantsdifferent | 2-8 | 3-7 | 3 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Standard Work Sheet, Deviation List, Improved Standard, Training Needs |
Tagsno overlap | WasteLeanProcess improvement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | LeanProcessQuality |



