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 Scoring |  Architecture arc42 |  Architecture Architecture Decision Record |  Product Discovery Jobs to Be Done |
|---|---|---|---|---|
Purposedifferent | When opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. | 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-120 min | 1-2 Tage | 15-45 min | 1-3 Wochen |
Participantsdifferent | 3-6 | 1-4 | 1-3 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Opportunity Score Table, Top Outcomes | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | PrioritizationDiscoveryOutcomesNeeds | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | CustomerOutcomesNeeds |