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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 h20-60 min1-3 h1-2 Tage
Participantsdifferent
3-101-45-301-4
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesRunbook, Checklist, Escalation PathConsensus Clusters, Theme Titles, Priority AreasArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
OperationsReliabilityDocumentation
FacilitationConsensusWorkshopAlignment
ArchitectureDocumentationCommunication
Add more methods