Org alignment / transformation diagnosis
McKinsey 7S
Seven interdependent elements, strategy, structure, systems, shared values, style, staff, and skills, that all have to align for an organization to perform well.
Its power is diagnostic: change one element and the model forces you to ask what else has to move.
- Problem
- Org alignment / transformation diagnosis
- Altitude
- Enterprise
- Effort to run
- Moderate
- Evidence base
- Established
Theory & origin
Waterman, Peters and Phillips published the 7S framework in 1980 (Structure Is Not Organization) as a reaction against the era's obsession with redrawing boxes on an org chart. Their insight: strategy and structure are only two of seven interdependent elements. Add systems, style, staff, skills and the shared values at the center, and you see why changing one thing without the others is why transformations stall. The model is deliberately non-quantitative. Its value is as a diagnostic checklist of interdependencies.
Key components
The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.
Explore the model
How a consultant runs it
- 01 Interview across levels to describe the current state of each of the seven elements, especially the lived shared values, not the stated ones.
- 02 Define the target state each element needs to reach for the new strategy to work.
- 03 Map the misalignments: where does today's structure, systems or leadership style contradict where the strategy needs to go?
- 04 Sequence the changes so hard and soft elements move together: new structure alongside new incentives and new leader behavior, never structure alone.
- 05 Keep the 7S map as a standing reference through the transformation, to catch knock-on effects early.
When to use
- 01 Diagnosing why a strategy or transformation is stalling
- 02 Post-merger integration: mapping where two organizations clash
- 03 Pressure-testing an org redesign for knock-on effects
When not to use
- 01 As a quantitative measurement tool. It is a checklist of questions, not a scorecard.
- 02 When the problem is clearly single-element, like pure pay benchmarking
- 03 For fast operational decisions. It is a deliberate, slow lens.
Worked example
A bank launches an agile transformation (Strategy) and reorganizes into squads (Structure), but performance reviews stay individual and annual (Systems), and executives still demand steering-committee sign-off (Style). Mapping it against 7S exposes the misalignments. The fix is sequenced changes to Systems and Style, not more agile training.
Common pitfalls
- 01 Auditing each S in isolation. The interconnections are the whole point of the model.
- 02 Treating Shared Values as the stated values instead of the lived ones
- 03 Producing a 7-row table with no change actions attached to it
Sample deliverable
One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.
Input
- Strategy4.2 / 5
- Structure3.8 / 5
- Shared values2.6 / 5
- Style2.1 / 5
- Systems1.9 / 5
Process
Interview scores per element are mapped against the new strategy
Alignment scan: agile transformation
- Systems at 1.9annual reviews block agile
- Style at 2.1committees hoard decisions
- Sequencefix Systems and Style first