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 Interview | ![]() UX Design Customer Journey Canvas |
|---|---|---|---|
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 are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 1-4 h | 30-60 min je Interview | 1-3 h |
Participantsdifferent | 1-5 | 5-12 Interviews | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Interview Notes, Opportunity Themes, Customer Quotes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | ArchitectureCommunicationVisualization | DiscoveryInterviewsOpportunityCustomer | JourneyCustomerService designCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






