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
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.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.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.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
MediumHighMediumHigh
Timedifferent
1-3 hHalber TagAs needed1-4 Wochen
Participantsdifferent
1-55-204-151-6
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Funnel report, Drop-off analysis, Optimization hypothesesSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder UpdatesExperiment results, Decision log, Learning summary
Tagsno overlap
AnalyticsConversionGrowth
ResilienceOperationsIncident
IncidentOperationsReliability
ExperimentsGrowthAnalyticsValidation
Add more methods