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 |  Team Design Team API |  Facilitation Stakeholder 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 | Medium | Low | Low | Low |
Timedifferent | Wochen bis Monate | Half day initial, dann laufend | 60–90 min | 45-90 min |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ProcessDivergenceInnovation | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |