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 Change Analysis |  UX Research Tree Testing |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 45-120 min | 1-2 Tage | 60-90 min |
Participantsdifferent | 2-6 | Based on research question | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Findability Metrics, Path Analysis, Revised IA | Salience Diagram, Strategy per Class |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Information architectureNavigationFindability | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
