methodatlas
Compare

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 Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h1-2 h60-120 min1-3 h
Participantsdifferent
3-123-102-85-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
System Map, Dependencies, Leverage PointsArchitecture Canvas, Goals, Constraints, Quality AttributesConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
Systems thinkingMappingBoundariesChange
CanvasArchitectureAlignmentWorkshop
Theory of ConstraintsAssumptionsSystems thinking
FacilitationConsensusWorkshopAlignment
Add more methods