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 |  Operations Standard Work Analysis |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
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 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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-120 min | 1-3 h | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 2-6 | 3-7 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | WasteLeanProcess improvement | LeanProcessQuality | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |