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 Problem Interview |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 1-4 h | 15-45 min |
Participantsdifferent | 5-12 Interviews | 1-5 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
