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 | ![]() Architecture C4 Model | ![]() Facilitation Problem Framing Workshop |
|---|---|---|---|
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. | 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 a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 1-4 h | 60-120 min |
Participantsdifferent | 5-12 Interviews | 1-5 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Context Diagram, Container Diagram, Component Diagram | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureCommunicationVisualization | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






