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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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 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
LowMediumLowLow
Timedifferent
1-2 h45-90 min60–90 min1-2 h
Participantsdifferent
3-83-82-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Inception Canvas, Risks, Goal List, Open QuestionsCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsStakeholder Map, Engagement Plan, Risk NotesArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
AlignmentArchitectureCanvas
Systems thinkingFramingStakeholders
StakeholdersAlignmentFacilitationChange
CanvasArchitectureAlignmentWorkshop
Add more methods