View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Team Design Team API |  Delivery Communication Plan |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | Half day initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | 2-8 | Ein Team plus Stakeholder | 2-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Team API Document | Communication Plan, Channel Matrix, Message Cadence | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | StrategyAnalysisPlanning | TeamAlignmentCommunicationService | CommunicationStakeholdersDeliveryPlanning | AlignmentStakeholdersTeam |