View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery Cost of Delay |  Product Discovery Assumption Mapping |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | Ongoing | 90-180 min | 45-60 min | 45-90 min |
Participantsdifferent | 2-12 | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | CoD Table, Prioritization Sequence | Assumption map, Test backlog, Risk ranking | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | FlowVisual managementDelivery | PrioritizationDeliveryEconomicsDecision | AssumptionsRiskExperimentsValidation | AssumptionsRiskDecisionDiscovery |