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 Timeline |  Team Design Spotify Model Mapping |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | Medium | Low | Low |
Timedifferent | 30-90 min | 90-180 min | 60–90 min | 45-90 min |
Participantsdifferent | 2-12 | 5-15 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TimelineFacilitationSequence | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |