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 Domain Context Map |  Decision Making Force Field 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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 45-120 min | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Domain Context Map, Boundary Notes, Ownership Map | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | WasteLeanProcess improvement | Domain-Driven DesignContextBoundaries | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
