View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Bottleneck AnalysisSpotify Model MappingStarfish RetrospectiveTeam Cognitive Load Assessment
| Criterion |  Operations Bottleneck Analysis |  Team Design Spotify Model Mapping |  Agile Starfish Retrospective |  Team Design Team Cognitive Load Assessment |
|---|---|---|---|---|
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 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 90-180 min | 45-90 min | 60-90 min |
Participantsdifferent | 3-8 | 5-15 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Spotify Model Map, Action List | Starfish Board, Practice Changes, Experiments | Cognitive Load Profile, Action List |
Tagsno overlap | FlowMeasurementConstraints | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementExperimentsTeam | TeamComplexityImprovementDiagnosis |