Insights

The McKinsey 7S model: how to use it, with an assessment template

The 7S model tests whether strategy, structure, systems and the softer side of an organisation are pulling in the same direction. Here is where it came from, how to run an assessment and a worked example you can adapt.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

The McKinsey 7S model is a framework for checking whether the parts of an organisation fit together. It looks at seven connected elements: strategy, structure, systems, shared values, style, staff and skills. Its central idea is that changing one element, such as structure or systems, without adjusting the others is likely to stall the change.

It is most useful at moments of deliberate change: a new strategy, a merger, a separation, a restructure or a major system implementation. In each case, leaders tend to focus on the elements they can change by decision and underestimate the ones that change slowly.

What the 7S model is for

Most organisational change is planned through the elements that are easiest to draw: a new strategy, a new structure chart, a new system. The 7S model is a check against that habit. It asks whether the people, the skills, the leadership style and the shared values will support the new design, and what has to change in each for the whole to work.

Used well, it is a diagnostic and a planning aid at once. It helps a leadership team see why a change is not landing, and it gives them a structured list of what to fix before they announce the next one.

Where the McKinsey 7S framework came from

The framework came out of McKinsey around 1980. Tom Peters and Robert Waterman, working with colleagues including Julien Phillips and with the academics Richard Pascale and Anthony Athos, wanted a better way to think about how organisations work than the structure chart. Waterman, Peters and Phillips published it in a 1980 article in Business Horizons, arguing that structure is only one part of an organisation and often not the part that matters most.

Pascale and Athos used the framework in The Art of Japanese Management in 1981, and Peters and Waterman used it again in In Search of Excellence in 1982, which brought it to a wide audience. The central element was originally called superordinate goals and was later renamed shared values, which is how it is taught today.

Hard and soft elements of the 7S model

The seven elements are usually grouped into hard and soft. The hard elements are easier to define, and leaders can change them relatively quickly by decision. The soft elements are harder to describe and slower to change, and in practice they decide whether the hard changes stick.

ElementTypeWhat it meansWhat to look at
StrategyHardThe plan for building and keeping an advantage over competitorsWhether it is clear, understood and reflected in budgets and decisions
StructureHardHow the organisation is divided and who reports to whomLayers, spans of control, decision rights, where accountability sits
SystemsHardThe processes, procedures and technology that run the business day to dayPlanning, budgeting, reporting, performance measures and core systems
Shared valuesSoftThe core beliefs and purpose that hold the organisation togetherWhat people actually prioritise when nobody is watching
StyleSoftHow leaders behave and how decisions are really madeWhere leaders spend their time, how conflict and bad news are handled
StaffSoftThe people: how many, what kind, and how they are recruited, developed and deployedWorkforce mix, succession, where the best people are placed
SkillsSoftThe distinctive capabilities of the organisation as a wholeWhat it is genuinely good at, and what the strategy now needs

Shared values sit at the centre of the usual diagram, connected to every other element, because they shape all of them and are shaped by them in turn. When an assessment finds a serious mismatch, it is often between the values an organisation states and the style its leaders actually show.

How to use the McKinsey 7S model, step by step

  1. Define the change you are testing. An assessment needs a reason, such as a new strategy, a merger, a separation or a programme that is not landing. Without one it becomes a description of the organisation with no conclusion.
  2. Describe the current state of each element. Use evidence rather than opinion: interviews at several levels, a short survey, the structure chart, process and system documentation, and how recent decisions were actually made.
  3. Describe the desired state. For each element, what must be true for the strategy or change to work? Start with strategy and shared values, then work through the rest.
  4. Find the gaps and the misalignments. Look at each element’s gap, then at the connections between elements. A new structure that current systems cannot report on, or a strategy that needs skills the organisation lacks, are the findings that matter.
  5. Prioritise and plan. Not every gap needs closing at once. Decide which misalignments would stop the change, and sequence the actions so that hard and soft changes support each other.
  6. Look again. Repeat the assessment at key milestones. The soft elements move slowly, and the only way to know they are moving is to check.

Comparing current and desired states is a form of gap analysis, and the same discipline applies: be specific about today, or the gaps will be too vague to act on.

7S model example: an ERP that went live but did not deliver

This example is hypothetical. A mid sized distribution business has gone live on a new ERP, and the system works, but six months later the expected benefits have not appeared. Month end is no faster, managers still run their own spreadsheets and the finance team is working longer hours than before. The leadership team runs a 7S assessment to find out why.

ElementCurrentDesiredGapAction
StrategyGrowth by acquisition, using one finance platform to absorb new businesses quicklyUnchangedClear at the top, but staff cannot see how the ERP connects to itRestate the link between the ERP and the growth plan in leadership communications
StructureFinance still organised by legacy business, each with its own processesOne finance function with named process ownersOld reporting lines kept after go liveAppoint owners for record to report, procure to pay and order to cash
SystemsERP live, with spreadsheets and email approvals still running alongsideERP as the single source for reporting and approvalsParallel running never formally endedSet a date to retire the spreadsheets and move approvals into the system
Shared values‘Get it right locally’‘One business, one set of numbers’Local autonomy valued above the standard processLeaders model and reward use of the standard process
StyleDirectors ask for bespoke reports and accept workaroundsDirectors use standard reports and challenge workaroundsLeaders signal that the old way is still acceptableReview adoption measures at every leadership meeting
StaffFinance team stretched, and two key super users left after go liveStable team with named super users in each areaKnowledge concentrated in too few peopleBackfill the super user roles and build cover into job descriptions
SkillsStrong accounting skills, weak system and data skillsConfident use of ERP reporting and self serviceTraining covered transactions, not analysisTargeted reporting training, with coaching from super users

The pattern is common in system led change. The systems element changed on go live day, while structure, style, shared values and skills did not, and they quietly pulled people back to the old way of working. Most of the actions are not technical, which is why benefits depend as much on change management as on the build.

Questions to ask for each element

Use these as a starting template for interviews or a workshop, and record the evidence behind each answer in the assessment table.

  • Strategy: Can people three levels below the executive describe the strategy in the same way? Do budgets and priorities follow it?
  • Structure: Who makes which decisions, and how many layers does a decision pass through? Does the structure match how work actually flows?
  • Systems: Which processes and systems run the business, and what workarounds sit alongside them? What do the performance measures reward?
  • Shared values: What does the organisation say it stands for, and what do its people say it really stands for?
  • Style: How do senior leaders spend their time? How are mistakes and bad news handled?
  • Staff: Are the right number and mix of people in the right roles? How are good people developed and kept?
  • Skills: What is the organisation distinctively good at, and which capabilities does the new strategy need that it does not yet have?

When to use it, and its limits

The model suits mergers and integrations, separations and carve outs, restructures, operating model changes and system implementations that are not delivering their benefits. It is also a useful lens in due diligence, because the soft elements are the ones that never appear in a data room.

Separations test it hardest, because almost every element has to be built or rebuilt at the same time. Christopher Fagan was Project Director on the National Grid separation, where structure, systems and staff all had to be rebuilt at once: every software supplier was bought under his lead, SAP S/4HANA replaced Oracle, and contractors were sourced for capital work and day to day capacity.

The model has limits. It describes internal alignment but says little about the outside world, since competitors, customers and regulation only enter through strategy. It gives no weighting, so a team can spend as long on a minor style point as on a broken structure. Pair it with an external view, such as a value chain analysis of where advantage comes from, and treat it as something you revisit rather than complete.

Common mistakes

  • Treating it as a checklist. The value is in the connections between elements, not in seven separate descriptions.
  • Only interviewing the top team. Leaders describe the organisation they intend. The people doing the work describe the one that exists.
  • Skimping on the soft elements. They are harder to evidence, so they get a line each, yet they are usually where the answer is.
  • Desired states written as slogans. ‘A culture of ownership’ is not something you can plan towards. Say what people will do differently.
  • No actions or owners. An assessment that ends with a diagram has not finished.

How it fits with operating model and organisation design

The McKinsey 7S model is a diagnostic. Once it has shown where the misalignments are, the fixes usually land in three places: the operating model, which sets how structure, processes and systems combine; organisational design, which works through structure, roles and decision rights; and change and adoption work for the softer elements.

PEF works with leadership teams on this kind of change through our strategy consulting and business transformation services. Christopher Fagan brings 19 years of transformation and systems delivery to that work, and we stay to design and build the changes with your people rather than leaving a framework on the table.

Common questions

What is the McKinsey 7S model?

The McKinsey 7S model is a framework for assessing whether the parts of an organisation are aligned. It covers seven connected elements: strategy, structure, systems, shared values, style, staff and skills. Its premise is that changing one element in isolation rarely works, so any major change should be tested against all seven. It is widely used for mergers, restructures and large system implementations.

What are the hard and soft elements of the 7S model?

The hard elements are strategy, structure and systems. They are relatively easy to define, and leaders can change them by decision. The soft elements are shared values, style, staff and skills. They are harder to describe and slower to change, but they usually decide whether changes to the hard elements actually stick. Shared values sit at the centre and connect to every other element.

Who created the McKinsey 7S framework?

The framework was developed at McKinsey around 1980 by Tom Peters and Robert Waterman, working with colleagues including Julien Phillips and with the academics Richard Pascale and Anthony Athos. It was first published in a 1980 article in Business Horizons and reached a wide audience through Peters and Waterman’s 1982 book In Search of Excellence.

How do you do a 7S analysis?

Start with the change you are testing, such as a merger or a new strategy. Describe the current state of each of the seven elements using evidence from interviews, documents and recent decisions. Then describe the desired state, identify the gaps and the misalignments between elements, and agree prioritised actions with owners. Repeat the assessment at key milestones to check the softer elements are moving.

Is the 7S model still relevant?

Yes, provided it is used as a diagnostic rather than a diagram. Its central point, that strategy and structure fail when systems, skills, leadership style and values pull the other way, applies as much to an ERP implementation or a separation today as it did in 1980. Its main weakness is a limited view of the outside world, so pair it with market and customer analysis.

Related reading: What is an operating model?, Value chain analysis, Gap analysis and Organisational design.

Change not landing the way you planned?

We can run a 7S assessment with your leadership team, find the misalignments holding the change back and help you fix them in structure, systems and ways of working.

Book a confidential conversation

Sources: Waterman, R. H., Peters, T. J. and Phillips, J. R., Structure Is Not Organization, Business Horizons, 1980; Pascale, R. T. and Athos, A. G., The Art of Japanese Management, 1981; Peters, T. J. and Waterman, R. H., In Search of Excellence, 1982

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.