View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Operations Change Analysis |  Team Design Spotify Model Mapping |
|---|---|---|---|
Purposedifferent | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 45-90 min | 45-120 min | 90-180 min |
Participantsdifferent | 3-12 | 2-6 | 5-15 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Spotify Model Map, Action List |
Tagsno overlap | AlignmentStakeholdersTeam | ChangeRoot causeTroubleshootingComparison | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
