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 Spotify Model Mapping |  Engineering Goal Question Metric |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 90-180 min | 90-180 min | 45-90 min |
Participantsdifferent | 3-8 | 5-15 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Spotify Model Map, Action List | GQM Table, Metric Profiles | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | FlowMeasurementConstraints | TeamOrganizationAlignmentDiagnosis | MetricsMeasurementEngineeringAlignment | AlignmentStakeholdersTeam |