View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Business Strategy Value Chain Analysis |  Delivery Communication Plan |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 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 | High | Low | Low |
Timedifferent | Half day initial, dann laufend | Half day | 45-90 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-8 | 2-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Team API Document | Value Chain Map, Lever List | Communication Plan, Channel Matrix, Message Cadence | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCommunicationService | StrategyBusiness modelDiagnosisAnalysis | CommunicationStakeholdersDeliveryPlanning | AlignmentStakeholdersTeam |