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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication 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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-30 min60–90 min1-2 h60-120 min
Participantsdifferent
2-82-83-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Question List, Reframed Challenge, Learning PromptsStakeholder Map, Engagement Plan, Risk NotesArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
QuestionsReframingFacilitationSensemaking
StakeholdersAlignmentFacilitationChange
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
Add more methods