View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Systems Thinking Intervention Mapping |  Systems Thinking Evaporating Cloud |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 60-90 min | 1-5 Tage | 60-120 min | 45-90 min |
Participantsdifferent | 4-12 | 4-12 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskDecisionDiscovery |