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 |  Growth Funnel Analysis |  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. | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | 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 | 1-3 h | 60–90 min |
Participantsdifferent | Ein Team plus Stakeholder | 1-5 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Team API Document | Funnel report, Drop-off analysis, Optimization hypotheses | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TeamAlignmentCommunicationService | AnalyticsConversionGrowth | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
