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 | ![]() Facilitation Team Charter | ![]() Team Design Spotify Model Mapping | ![]() 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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 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 | 2-4 h | 90-180 min | 45-90 min |
Participantsdifferent | 3-8 | 3-12 | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | FlowMeasurementConstraints | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |



