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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.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.
Complexitydifferent
HighLowMediumMedium
Timedifferent
1-4 Wochen45-90 min90-180 min initial, dann laufend2-4 h
Participantsdifferent
1-63-123-83-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Experiment results, Decision log, Learning summaryForce Field Map, Change Levers, Risk NotesKPI Tree, Owner List7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ChangeDecisionStrategy
MetricsStrategyAlignmentMeasurement
OrganizationStrategyAlignmentChange
Add more methods