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 |  Decision Making Decision Framing Workshop |  Facilitation Stakeholder Mapping |  Facilitation Expectation 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 decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 60-120 min | 60–90 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 4-10 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Team API Document | Decision Frame, Decision Question, Criteria List, Evidence Plan | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCommunicationService | Decision framingAlignmentCriteriaOptions | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |