View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Intervention MappingRisk StormingEvaporating CloudARID (Active Reviews for Intermediate Designs)
| Criterion | ![]() Systems Thinking Intervention Mapping | ![]() Architecture Risk Storming | ![]() Systems Thinking Evaporating Cloud | ![]() Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 1-5 Tage | 60-90 min | 60-120 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-12 | 4-12 | 2-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ChangeSystems thinkingCapability | RiskArchitectureWorkshopValidation | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureEngineeringFeedbackValidationTasks |



