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 Problem Framing 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 team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitysame | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 60–90 min | 60-120 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tags1 shared | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
