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 |  Facilitation Expectation Mapping |  Delivery Communication Plan |  Team Design Team API |
|---|---|---|---|---|
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 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Wochen bis Monate | 45-90 min | 45-90 min | Half day initial, dann laufend |
Participantsdifferent | 3-12 | 3-12 | 2-6 | Ein Team plus Stakeholder |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Expectation Map, Alignment Notes, Agreements | Communication Plan, Channel Matrix, Message Cadence | Team API Document |
Tagsno overlap | ProcessDivergenceInnovation | AlignmentStakeholdersTeam | CommunicationStakeholdersDeliveryPlanning | TeamAlignmentCommunicationService |