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 Fault Tree Analysis | ![]() Facilitation Stakeholder Salience Model | ![]() Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 2-6 h | 60-90 min | 45-90 min |
Participantsdifferent | 3-8 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Salience Diagram, Strategy per Class | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | RiskRoot causeSafety | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






