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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.
Complexitysame
LowLowLowLow
Timedifferent
20-60 min30-120 min1-4 h15-45 min
Participantsdifferent
1-42-61-51-3
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathObservation Notes, Improvement IdeasContext Diagram, Container Diagram, Component DiagramADR File, Decision Log, Rationale
Tagsno overlap
OperationsReliabilityDocumentation
LeanObservationProcessOperations
ArchitectureCommunicationVisualization
ArchitectureRationaleDocumentationGovernance
Add more methods