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 Argument Mapping
Decision Making
Argument Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 hAs needed2-6 h15-30 min
Participantsdifferent
1-84-153-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleIncident Log, Action Tracker, Stakeholder UpdatesEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsRoot cause notes, Countermeasures
Tagsno overlap
SensemakingDecisionRationale
IncidentOperationsReliability
CausalityIncidentRoot causeTimeline
Root causeIncidentLeanProblem solving
Add more methods