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 for Contextual Inquiry.
UX Research
Contextual Inquiry
Paper illustration for Kaizen Event.
Operations
Kaizen Event
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Purposedifferent
When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.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.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.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 Wochen0.5-5 Tage1-4 Wochen1 h bis mehrere Wochen
Participantsdifferent
4-12 Beobachtungen4-101-61-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Field Notes, Workflow Insights, Pain PointsKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateExperiment results, Decision log, Learning summaryPDCA Log, Experiment Plan, Learning Outcome, Standard Change
Tagsno overlap
UX researchObservationContext
LeanContinuous improvementOperations
ExperimentsGrowthAnalyticsValidation
Continuous improvementLeanExperiments
Add more methods