View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Decision Making OODA Loop |  Domain Modeling Context Map |  Decision Making Delphi Method |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. | 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 | Medium | Medium | High |
Timedifferent | Ongoing | 15-60 min je Zyklus | 1-3 h | 1-4 Wochen |
Participantsdifferent | 2-12 | 1-8 | 2-8 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | FlowVisual managementDelivery | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy |