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 Problem Framing Workshop |  Facilitation Alignment Mapping |  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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 60-120 min | 1-2 h | 60–90 min |
Participantsdifferent | Ein Team plus Stakeholder | 4-10 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Team API Document | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | TeamAlignmentCommunicationService | FacilitationAlignmentDiscovery | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |