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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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
LowHighLowLow
Timedifferent
1-2 hHalf day60–90 min1-2 h
Participantsdifferent
3-103-122-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesLeverage Map, Action StrategyStakeholder Map, Engagement Plan, Risk NotesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
Systems thinkingChangeStrategy
StakeholdersAlignmentFacilitationChange
AlignmentArchitectureCanvas
Add more methods