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 |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 15-45 min | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 3-10 | 1-3 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AutonomyRolesTeam | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |