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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.When growth ideas surface quickly, the temptation to build immediately instead of learning is high. A Growth Experiment frames an assumption so target group, lever, and measurement are clear before the first deployment.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
LowMediumMediumHigh
Timedifferent
20-45 min1-3 h1-2 Wochen1-4 Wochen
Participantsdifferent
3-123-101-61-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Lessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement BacklogExperiment card, Result summary, Next betExperiment results, Decision log, Learning summary
Tagsno overlap
LearningOperationsImprovement
ProcessOperationsImprovement
MarketingGrowthExperimentsLearning
ExperimentsGrowthAnalyticsValidation
Add more methods