View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Decision Framing Workshop | ![]() Architecture C4 Model | ![]() Architecture Request for Comments | ![]() Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-120 min | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 4-10 | 1-5 | 3-20 Reviewer | 2-10 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Decision Frame, Decision Question, Criteria List, Evidence Plan | Context Diagram, Container Diagram, Component Diagram | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | Decision framingAlignmentCriteriaOptions | ArchitectureCommunicationVisualization | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |



