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 | ![]() Architecture Architecture Inception Canvas | ![]() Systems Thinking Leverage Points | ![]() 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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 | Low | High | Low |
Timedifferent | 60-120 min | 1-2 h | Half day | 1-2 h |
Participantsdifferent | 2-8 | 3-8 | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Inception Canvas, Risks, Goal List, Open Questions | Leverage Map, Action Strategy | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | AlignmentArchitectureCanvas | Systems thinkingChangeStrategy | CanvasArchitectureAlignmentWorkshop |



