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 |  Business Strategy Balanced Scorecard |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | High | Low |
Timedifferent | Ongoing | Halber Tag bis mehrere Wochen | 60–90 min |
Participantsdifferent | 2-12 | 4-12 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Balanced Scorecard, Strategic Measures, Initiative Map | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | FlowVisual managementDelivery | StrategyMetricsExecution | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
