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
Paper illustration of many question cards around one challenge
Facilitation
Question Burst
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
When a problem gets covered up too quickly with answers, Question Burst puts the better question at the center. The format opens the thinking space before the group commits to an interpretation.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.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.
Complexitysame
LowLowLowLow
Timedifferent
15-30 min1-2 h60–90 min1-2 h
Participantsdifferent
2-83-82-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Question List, Reframed Challenge, Learning PromptsInception Canvas, Risks, Goal List, Open QuestionsStakeholder Map, Engagement Plan, Risk NotesArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
QuestionsReframingFacilitationSensemaking
AlignmentArchitectureCanvas
StakeholdersAlignmentFacilitationChange
CanvasArchitectureAlignmentWorkshop
Add more methods