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 Solution Tree |  UX Research Empathy Mapping |  Architecture C4 Model |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | 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. | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h Setup, laufend | 30–60 min | 1-4 h | 2-8 h |
Participantsdifferent | 2-6 | 4-8 | 1-5 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | Empathy Map, Assumptions List, Research Gaps | Context Diagram, Container Diagram, Component Diagram | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | SynthesisQualitativeWorkshop | ArchitectureCommunicationVisualization | Domain-Driven DesignEventsDiscoveryWorkshop |