View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Operations Waste Analysis |  Decision Making Force Field Analysis |  Decision Making Delphi Method |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 h | 45-120 min | 45-90 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Waste Map, Prioritized Waste, Improvement Backlog | Force Field Map, Change Levers, Risk Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | WasteLeanProcess improvement | ChangeDecisionStrategy | ForecastingExpertsDecisionStrategy |