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 Context Map | ![]() Domain Modeling Domain Context Map | ![]() UX Research Personas | ![]() UX Research Affinity Diagramming |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 h | 1-3 Tage | 45–90 min |
Participantsdifferent | 2-8 | 3-10 | Internes Team | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Persona Profiles, Needs Summary, Scenario Notes | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | ResearchCustomerSynthesis | SynthesisQualitativeRoot cause |



