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 Landing Page Test.
Product Discovery
Landing Page Test
Process Mapping method illustration showing its working structure
Operations
Process Mapping
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When a value proposition first needs to be checked for resonance, it condenses the idea onto a focused entry page. It shows whether language and offering carry interest.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-5 Tage1-3 h15-30 min1-4 h
Participantsdifferent
Nutzertraffic3-102-63-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Landing Page, Conversion Data, Learning SummaryProcess Map, Handoff List, Improvement BacklogRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ValidationConversionMarketing
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods