View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Operations Family Tree Analysis |  Facilitation Stakeholder Mapping |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 2-4 h | 60–90 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-12 | 2-6 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Family Tree Diagram, Pattern Notes, Systemic Measures | Stakeholder Map, Engagement Plan, Risk Notes | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AlignmentStakeholdersTeam | Root causePatternsIncidentSystemic | StakeholdersAlignmentFacilitationChange | Root causeSafetySystemicIncident |