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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Purposedifferent
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Complexitydifferent
LowMediumHigh
Timedifferent
15-45 minAs needed2-6 h
Participantsdifferent
1-34-153-10
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleIncident Log, Action Tracker, Stakeholder UpdatesEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
IncidentOperationsReliability
CausalityIncidentRoot causeTimeline
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.