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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 hHalber Tag1-2 h1-3 h
Participantsdifferent
3-105-204-125-30
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesSimulation Notes, Gaps List, Updated RunbooksAlignment Map, Open Issues, Decision QuestionsConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
ResilienceOperationsIncident
AlignmentStakeholdersStrategyFacilitation
FacilitationConsensusWorkshopAlignment
Add more methods