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 Constraint Analysis | ![]() Facilitation Expectation Mapping | ![]() Facilitation Power Interest Grid |
|---|---|---|---|---|
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 stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 30-90 min | 45-90 min | 30-60 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Expectation Map, Alignment Notes, Agreements | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | TeamAlignmentCommunicationService | ConstraintsDecisionPlanningOptions | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentPlanning |



