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 Architecture Decision Record |  Architecture C4 Model |  Decision Making DACI |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 15-45 min | 1-4 h | 30-60 min |
Participantsdifferent | 2-6 | 1-3 | 1-5 | 2-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | DecisionRolesGovernanceAlignment |