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 Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Purposedifferent
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
MediumLowHigh
Timedifferent
60-180 min45-90 min2-6 h
Participantsdifferent
3-102-83-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Incident Timeline, Evidence Log, Delay Analysis, Improvement ActionsAssumption List, Critical Assumptions, Learning PlanEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
IncidentTimelineSite Reliability Engineering
AssumptionsRiskDecisionDiscovery
CausalityIncidentRoot causeTimeline
Add more methods

Often compared together

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

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem