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 |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 45-90 min | 30-240 min | 60-90 min |
Participantsdifferent | 3-12 | 1-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Salience Diagram, Strategy per Class |
Tagsno overlap | AlignmentStakeholdersTeam | TroubleshootingProblem solvingDiagnosis | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
