View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |  Product Strategy KPI Tree |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | Half day | 90-180 min | 90-180 min initial, dann laufend |
Participantsdifferent | 3-8 | Team-Leads plus Architecture | 5-15 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | KPI Tree, Owner List |
Tagsno overlap | FlowMeasurementConstraints | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | MetricsStrategyAlignmentMeasurement |