View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling EventStorming |  Product Discovery Problem Interview |  Architecture Architecture Decision Record |  Product Discovery Concierge MVP |
|---|---|---|---|---|
Purposedifferent | 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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-8 h | 30-60 min je Interview | 15-45 min | 1-4 Wochen |
Participantsdifferent | 5-12 | 5-12 Interviews | 1-3 | 3-10 Kunden |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Evidence, Risk Notes, Customer Segments | ADR File, Decision Log, Rationale | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | DiscoveryInterviewsValidation | ArchitectureRationaleDocumentationGovernance | MVPValidationServiceDiscovery |