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 Interview | ![]() Operations A3 Problem Solving | ![]() Architecture C4 Model |
|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Medium | Low |
Timedifferent | 30-60 min je Interview | 45-90 min | 1-4 h |
Participantsdifferent | 5-12 Interviews | 2-5 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | A3 Report, Action Plan, Root Cause Analysis | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | LeanProblem solvingCoachingOperations | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






