View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Intervention Mapping | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|
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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | 1-5 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min |
Participantsdifferent | 4-12 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | ChangeSystems thinkingCapability | ArchitectureEngineeringFeedbackValidationTasks | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






