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
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration for Flywheel.
Growth
Flywheel
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.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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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
MediumMediumMediumHigh
Timedifferent
1-3 h60-180 min60-120 min1-4 Wochen
Participantsdifferent
1-53-103-81-6
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
Funnel report, Drop-off analysis, Optimization hypothesesIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summary
Tagsno overlap
AnalyticsConversionGrowth
IncidentTimelineSite Reliability Engineering
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Add more methods