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 Current Reality Tree | ![]() UX Research Customer Journey Mapping | ![]() Operations MORT Analysis | ![]() Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | 2-6 h | 2-4 h | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-8 | 4-10 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current Reality Tree, Core Problems, Intervention Ideas | Journey Map, Pain-point List, Opportunity Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Systems thinkingRoot causeConstraintsCausality | JourneyServiceService design | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |



