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 Strategy Map |  Facilitation Stakeholder 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. | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 2-4 h workshop plus review | 60–90 min |
Participantsdifferent | Ein Team plus Stakeholder | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Team API Document | Strategy Map, Objective Set, Cause-Effect Hypotheses | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | TeamAlignmentCommunicationService | AlignmentExecutionGoalsCausality | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
