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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 h120 min initial, dann laufend45-90 min90-180 min initial, dann laufend
Participantsdifferent
3-123-63-123-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsHEART-GSM Table, DashboardForce Field Map, Change Levers, Risk NotesKPI Tree, Owner List
Tagsno overlap
Systems thinkingTradeoffsLeadership
MetricsUX researchMeasurementSatisfaction
ChangeDecisionStrategy
MetricsStrategyAlignmentMeasurement
Add more methods