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 for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
2-6 h60-180 min1-2 Tage15-45 min
Participantsdifferent
3-103-101-41-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Event Timeline, Causal Factor Chart, Cause List, Corrective ActionsIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
CausalityIncidentRoot causeTimeline
IncidentTimelineSite Reliability Engineering
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods