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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.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
1-2 Tage30-60 min20-60 min15-45 min
Participantsdifferent
1-42-81-41-3
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewFishbone Diagram, Cause Categories, Investigation BacklogRunbook, Checklist, Escalation PathADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
Root causeQualityOperations
OperationsReliabilityDocumentation
ArchitectureRationaleDocumentationGovernance
Add more methods