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 |  Facilitation Stakeholder Mapping |  Facilitation Consensus Workshop |
|---|---|---|---|
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. | 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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 60–90 min | 1-3 h |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 5-30 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes | Consensus Clusters, Theme Titles, Priority Areas |
Tags1 shared | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange | FacilitationConsensusWorkshopAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
