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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitysame
LowLowLowLow
Timedifferent
20-60 min30-120 min15-45 min1-2 Tage
Participantsdifferent
1-42-61-31-4
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathObservation Notes, Improvement IdeasADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
OperationsReliabilityDocumentation
LeanObservationProcessOperations
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods