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 Delegation Poker |  Architecture Architecture Decision Record |  Facilitation Responsibility Poker |
|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 15-45 min | 45-90 min |
Participantsdifferent | 3-10 | 1-3 | 3-10 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | ADR File, Decision Log, Rationale | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | AutonomyRolesTeam | ArchitectureRationaleDocumentationGovernance | RolesResponsibilityTeamFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
