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 Opportunity Solution Tree | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model |
|---|---|---|---|
Purposedifferent | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h Setup, laufend | 15-45 min | 1-4 h |
Participantsdifferent | 2-6 | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






