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 |  Delivery Communication Plan |  Decision Making Constraint Analysis |  Team Design Team API |
|---|---|---|---|---|
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. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 30-90 min | Half day initial, dann laufend |
Participantsdifferent | 3-12 | 2-6 | 2-8 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Communication Plan, Channel Matrix, Message Cadence | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Team API Document |
Tagsno overlap | AlignmentStakeholdersTeam | CommunicationStakeholdersDeliveryPlanning | ConstraintsDecisionPlanningOptions | TeamAlignmentCommunicationService |