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 Salience Model |  Delivery RAID Log |  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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 60-90 min | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-6 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Team API Document | Salience Diagram, Strategy per Class | RAID Log, Status Report Source | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | TeamAlignmentCommunicationService | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentPlanning |