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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Purposedifferent
When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.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.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 hOngoing1-4 Wochen1-5 Tage
Participantsdifferent
4-102-121-6Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Current-state map, Future-state map, Bottleneck listKanban board, WIP policies, Flow metricsExperiment results, Decision log, Learning summaryClick Data, Interest Signal, Learning Decision
Tagsno overlap
LeanFlowWasteDelivery
FlowVisual managementDelivery
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandDiscovery
Add more methods