View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Facilitation Delegation Poker |  Decision Making DACI |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-4 h | 45-90 min | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-5 | 3-10 | 2-10 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Delegation Board, Decision Boundaries, Role Agreements | DACI Matrix, Decision Owner, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureCommunicationVisualization | AutonomyRolesTeam | DecisionRolesGovernanceAlignment | ArchitectureDecisionAsyncGovernance |