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 Evaporating Cloud | ![]() Systems Thinking Intervention Mapping | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 60-120 min | 1-5 Tage | 1-2 h |
Participantsdifferent | 2-8 | 4-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ChangeSystems thinkingCapability | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






