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 Systems Mapping |  Architecture Software Architecture Canvas |  Systems Thinking Evaporating Cloud |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 60-120 min | 1-2 h |
Participantsdifferent | 3-12 | 3-10 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Architecture Canvas, Goals, Constraints, Quality Attributes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | Systems thinkingMappingBoundariesChange | CanvasArchitectureAlignmentWorkshop | Theory of ConstraintsAssumptionsSystems thinking | AlignmentArchitectureCanvas |