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
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
HighMediumMediumHigh
Timedifferent
2-6 h60-180 min45-60 min1-4 Wochen
Participantsdifferent
3-103-102-81-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Event Timeline, Causal Factor Chart, Cause List, Corrective ActionsIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
CausalityIncidentRoot causeTimeline
IncidentTimelineSite Reliability Engineering
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods