View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Intervention Mapping | ![]() UX Research User Interviews | ![]() Domain Modeling EventStorming | ![]() UX Research Empathy Mapping |
|---|---|---|---|---|
Purposedifferent | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 1-5 Tage | 30–60 min per interview | 2-8 h | 30–60 min |
Participantsdifferent | 4-12 | 1 participant per interview | 5-12 | 4-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Interview Notes, Themes, Insight Summary | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Empathy Map, Assumptions List, Research Gaps |
Tagsno overlap | ChangeSystems thinkingCapability | QualitativeResearchCustomerDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop | SynthesisQualitativeWorkshop |



