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 Architecture Decision Record |  Facilitation Expectation Mapping |  Decision Making DACI |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 15-45 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-10 | 1-3 | 3-12 | 2-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | ADR File, Decision Log, Rationale | Expectation Map, Alignment Notes, Agreements | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersTeam | DecisionRolesGovernanceAlignment |