View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Kepner-Tregoe |  UX Design Service Blueprinting |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | High | High | Medium |
Timedifferent | 2-8 h | 0.5-2 Tage | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 2-8 | 6-12 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Analysis, Decision Analysis, Risk Plan | Service Blueprint, Fail Points, Ownership Map | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Problem solvingRoot causeDecisionOperations | Service designOperationsJourneyBlueprint | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |