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 C4 Model |  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. | 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. | 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 | Medium |
Timedifferent | 60-120 min | 1-4 h | 1-3 Wochen |
Participantsdifferent | 3-6 | 1-5 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Opportunity Score Table, Top Outcomes | Context Diagram, Container Diagram, Component Diagram | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | PrioritizationDiscoveryOutcomesNeeds | ArchitectureCommunicationVisualization | CustomerOutcomesNeeds |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
