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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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
LowLowMediumHigh
Timedifferent
30-120 min1 h bis mehrere Wochen60-120 min1-4 Wochen
Participantsdifferent
2-61-83-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Observation Notes, Improvement IdeasPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summary
Tagsno overlap
LeanObservationProcessOperations
Continuous improvementLeanExperiments
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Add more methods