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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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.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
MediumMediumLowHigh
Timedifferent
1-3 h60-180 min15-30 min2-6 h
Participantsdifferent
3-123-102-63-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsRoot cause notes, CountermeasuresEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
KnowledgeMappingRisk
IncidentTimelineSite Reliability Engineering
Root causeIncidentLeanProblem solving
CausalityIncidentRoot causeTimeline
Add more methods