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 arc42 |  Facilitation Delegation Poker |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-2 Tage | 45-90 min | 15-45 min |
Participantsdifferent | 3-10 | 1-4 | 3-10 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Architecture Document, Context View, Runtime View, Deployment View | Delegation Board, Decision Boundaries, Role Agreements | ADR File, Decision Log, Rationale |
Tagsno overlap | RolesResponsibilityTeamFacilitation | ArchitectureDocumentationCommunication | AutonomyRolesTeam | ArchitectureRationaleDocumentationGovernance |