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
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Purposedifferent
When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
1-2 Tage90-180 min45-90 min1-3 h
Participantsdifferent
10-503-83-104-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Kano Matrix, Feature Classes, Priority ThemesCoD Table, Prioritization SequenceRanked Backlog, Cost-of-Delay AssumptionsCurrent-state map, Future-state map, Bottleneck list
Tagsno overlap
SatisfactionPrioritizationCustomer
PrioritizationDeliveryEconomicsDecision
LeanEconomicsSequencePrioritization
LeanFlowWasteDelivery
Add more methods