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 arc42 |  Architecture Architecture Decision Record |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | 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. | 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. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h Setup, laufend | 1-2 Tage | 15-45 min | 30-60 min |
Participantsdifferent | 2-6 | 1-4 | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Completed Experiment Canvas, Success Metric |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ExperimentsValidationDiscoveryHypothesis |