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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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
LowHighHigh
Timedifferent
20-60 minHalber Tag1-4 Wochen
Participantsdifferent
1-45-201-6
Formatdifferent
AsyncWorkshopAsync
Outputdifferent
Runbook, Checklist, Escalation PathSimulation Notes, Gaps List, Updated RunbooksExperiment results, Decision log, Learning summary
Tagsno overlap
OperationsReliabilityDocumentation
ResilienceOperationsIncident
ExperimentsGrowthAnalyticsValidation
Add more methods

Often compared together

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

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem