View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Product Discovery Opportunity Scoring |  Product Discovery Jobs to Be Done |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1-4 h | 60-120 min | 1-3 Wochen | 1-2 Tage |
Participantsdifferent | 1-5 | 3-6 | 5-12 Interviews | 10-50 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Opportunity Score Table, Top Outcomes | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | ArchitectureCommunicationVisualization | PrioritizationDiscoveryOutcomesNeeds | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer |