methodatlas
Compare

View methods side by side.

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

Criterion
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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
LowMediumLowMedium
Timedifferent
45-90 min30-240 min30-60 min1-2 h
Participantsdifferent
3-121-62-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryPower Interest Grid, Strategy per StakeholderAlignment Map, Open Issues, Decision Questions
Tagsno overlap
AlignmentStakeholdersTeam
TroubleshootingProblem solvingDiagnosis
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersStrategyFacilitation
Add more methods