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 |  Systems Thinking Systems Mapping |  Domain Modeling 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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-120 min | 1-3 h | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | System Map, Dependencies, Leverage Points | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | WasteLeanProcess improvement | Systems thinkingMappingBoundariesChange | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy |