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 of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
MediumLowLowLow
Timedifferent
90-180 min initial, dann laufend1-2 h60–90 min45-90 min
Participantsdifferent
3-82-82-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
KPI Tree, Owner ListDIBB document, Belief list, Bet list, Learning reportStakeholder Map, Engagement Plan, Risk NotesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
MetricsStrategyAlignmentMeasurement
StrategyDecisionAssumptionsHypothesis
StakeholdersAlignmentFacilitationChange
ChangeDecisionStrategy
Add more methods