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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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
30-90 min1-3 hMultiple workshops over several weeks1-4 Wochen
Participantsdifferent
3-121-52-81-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Postmortem Doc, Action Items, TimelineFunnel report, Drop-off analysis, Optimization hypothesesHooked loop, Trigger map, Reward design, Ethics checkExperiment results, Decision log, Learning summary
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
AnalyticsConversionGrowth
GrowthBehaviorRetention
ExperimentsGrowthAnalyticsValidation
Add more methods