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 Alignment Mapping | ![]() Facilitation Expectation Mapping | ![]() Operations MORT Analysis | ![]() Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 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 | Medium | Low | High | Medium |
Timedifferent | 1-2 h | 45-90 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 4-12 | 3-12 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Alignment Map, Open Issues, Decision Questions | Expectation Map, Alignment Notes, Agreements | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | AlignmentStakeholdersStrategyFacilitation | AlignmentStakeholdersTeam | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |



