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 Force Field Analysis |  Product Strategy ICE Scoring |  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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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 | Low | High |
Timedifferent | Ongoing | 45-90 min | 30-60 min | 90-180 min |
Participantsdifferent | 2-12 | 3-12 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Force Field Map, Change Levers, Risk Notes | ICE Table, Top Idea List | CoD Table, Prioritization Sequence |
Tagsno overlap | FlowVisual managementDelivery | ChangeDecisionStrategy | PrioritizationScoringGrowthDecision | PrioritizationDeliveryEconomicsDecision |