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 for Alignment Mapping.
Facilitation
Alignment Mapping
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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
LowMediumLowLow
Timedifferent
1-2 h1-2 h60–90 min1-2 h
Participantsdifferent
3-104-122-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision QuestionsStakeholder Map, Engagement Plan, Risk NotesInception Canvas, Risks, Goal List, Open Questions
Tags1 shared
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
StakeholdersAlignmentFacilitationChange
AlignmentArchitectureCanvas
Add more methods