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 |  Decision Making Risk Matrix |  Product Discovery Hypothesis Prioritization Canvas |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | Ongoing | 30-60 min | 60-90 min | 90-180 min |
Participantsdifferent | 2-12 | 3-10 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Risk Matrix, Top Risk List | Prioritization Canvas, Hypothesis Backlog | CoD Table, Prioritization Sequence |
Tagsno overlap | FlowVisual managementDelivery | RiskDecisionPrioritizationAssessment | ExperimentsPrioritizationDiscoveryHypothesis | PrioritizationDeliveryEconomicsDecision |