View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  Agile Example Mapping |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Low | Medium | Low |
Timedifferent | Wochen bis Monate | 30-60 min | 90-180 min | 45-90 min |
Participantsdifferent | 3-12 | 3-7 | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Example Map, Acceptance Criteria, Open Questions | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ProcessDivergenceInnovation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |