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 |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 1-4 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 2-6 | 1-5 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |