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 | ![]() UX Research Personas | ![]() Product Discovery Opportunity Solution Tree |
|---|---|---|---|
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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 1-4 h | 1-3 Tage | 1-2 h Setup, laufend |
Participantsdifferent | 1-5 | Internes Team | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Persona Profiles, Needs Summary, Scenario Notes | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | ArchitectureCommunicationVisualization | ResearchCustomerSynthesis | DiscoveryOutcomesExperimentsOpportunity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






