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 |  Domain Modeling Context Map |  Decision Making Force Field Analysis |  Product Strategy DIBB |
|---|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-120 min | 1-3 h | 45-90 min | 1-2 h |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | WasteLeanProcess improvement | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |