View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Working Backwards |  Architecture C4 Model |  Decision Making DACI |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 4-8 h, mehrere Iterationen | 1-4 h | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-6 | 1-5 | 2-10 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Context Diagram, Container Diagram, Component Diagram | DACI Matrix, Decision Owner, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureCommunicationVisualization | DecisionRolesGovernanceAlignment | ArchitectureDecisionAsyncGovernance |