Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Hypothesis-Driven Troubleshooting Stakeholder Salience Model Stakeholder Mapping Alignment Mapping

Criterion	Engineering Hypothesis-Driven Troubleshooting	Facilitation Stakeholder Salience Model	Facilitation Stakeholder Mapping	Facilitation Alignment Mapping
Purposedifferent	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.	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.	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.
Complexitydifferent	Medium	Medium	Low	Medium
Timedifferent	30-240 min	60-90 min	60–90 min	1-2 h
Participantsdifferent	1-6	3-6	2-8	4-12
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary	Salience Diagram, Strategy per Class	Stakeholder Map, Engagement Plan, Risk Notes	Alignment Map, Open Issues, Decision Questions
Tagsno overlap	TroubleshootingProblem solvingDiagnosis	StakeholdersFacilitationAlignmentGovernance	StakeholdersAlignmentFacilitationChange	AlignmentStakeholdersStrategyFacilitation

Add more methods