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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
LowLowMediumMedium
Timedifferent
20-60 min1-2 Tage45-60 min60-120 min
Participantsdifferent
1-41-42-82-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathArchitecture Document, Context View, Runtime View, Deployment ViewAssumption map, Test backlog, Risk rankingCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
OperationsReliabilityDocumentation
ArchitectureDocumentationCommunication
AssumptionsRiskExperimentsValidation
ArchitectureCommunicationStakeholdersCanvas
Add more methods