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 |  Delivery RAID Log |  Operations RACI Matrix |
|---|---|---|---|---|
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. | 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. | With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 15-45 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 3-10 | 1-3 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | RACI Matrix, Responsibility Map, Decision Notes |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | RolesResponsibilityGovernanceOperations |