View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Responsibility Poker |  Architecture Views and Beyond |  Facilitation Expectation Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 Tage | 45-90 min | 60-90 min |
Participantsdifferent | 3-10 | 1-4 | 3-12 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Architecture Views, Cross-view Notes, Rationale | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class |
Tagsno overlap | RolesResponsibilityTeamFacilitation | DocumentationStakeholdersArchitecture | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance |