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 Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Purposedifferent
Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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
MediumLowMediumMedium
Timedifferent
90-180 min45-90 min2-4 h90-180 min initial, dann laufend
Participantsdifferent
3-63-123-123-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
GQM Table, Metric ProfilesForce Field Map, Change Levers, Risk Notes7S Assessment, Alignment Gaps, Change ActionsKPI Tree, Owner List
Tagsno overlap
MetricsMeasurementEngineeringAlignment
ChangeDecisionStrategy
OrganizationStrategyAlignmentChange
MetricsStrategyAlignmentMeasurement
Add more methods