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.

Selected:KanbanCost of DelayAssumption MappingA/B Testing
Criterion
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
MediumHighMediumHigh
Timedifferent
Ongoing90-180 min45-60 min1-4 Wochen
Participantsdifferent
2-123-82-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Kanban board, WIP policies, Flow metricsCoD Table, Prioritization SequenceAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
FlowVisual managementDelivery
PrioritizationDeliveryEconomicsDecision
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods