How to fill in the McKinsey 7S Model
Check whether seven parts of the organisation actually agree with each other. This guide walks every block in the recommended order — what belongs there, the questions that unlock it, and patterns from real canvases.
The McKinsey 7S model examines seven interdependent elements of an organisation: three 'hard' ones that management can change directly — strategy, structure, systems — and four 'soft' ones that are far harder to move — shared values, skills, style, and staff.
Its argument is that these elements have to be mutually reinforcing, and that most strategies fail not because they are wrong but because the other six elements were never changed to match. A new strategy delivered through the old structure, the old incentives, and the old management style will lose to the status quo every time, because six of seven forces are pulling the other way.
Developed at McKinsey & Company in the late 1970s by Tom Peters, Robert Waterman, and Julien Philips, and popularised in In Search of Excellence (1982). Shared values sit at the centre because the other six are meant to align around them.
Strategy
How do we intend to win?
The plan for building and sustaining competitive advantage: which markets, which customers, which capabilities, and — crucially — what you are choosing not to do. A strategy everyone would agree with is usually not a strategy, because it rules nothing out and therefore guides no decision.
Ask yourself
- What is our stated basis of competition?
- What have we explicitly decided not to pursue?
- Could most people here state the strategy accurately?
- Does the strategy rule anything out?
Patterns that work
- State the choices, not the aspirations
- A strategy nobody could argue against is not making choices
- Test comprehension: ask five people to state it and compare answers
Structure
How is the organisation arranged?
Reporting lines, business units, centralisation, and coordination mechanisms. Structure is the element leaders reach for first because it is visible and changeable by decree — which is exactly why reorganisations so often fail to deliver: the chart changes, and systems, style, and shared values do not.
Ask yourself
- Does the structure match how work actually flows?
- Where do handoffs cause delay or blame?
- Are decisions made where the information is?
- Which team's goals conflict with another's by design?
Patterns that work
- Compare the org chart to the actual flow of work
- Structural conflicts between teams are designed in, not accidental
- Changing structure alone is the most common reorganisation failure
Systems
What are the daily processes and tools?
The procedures, workflows, IT systems, and — most importantly — the measurement and incentive systems that govern daily work. If you only examine one thing here, examine what gets measured and rewarded, because that is what people will optimise regardless of what the strategy says.
Ask yourself
- What gets measured, and what gets rewarded?
- Which process everyone works around?
- Do our systems support the new strategy or the old one?
- Where does approval slow real work down?
Patterns that work
- Incentives beat instructions: people optimise what is measured
- Any process that is routinely worked around is a real finding
- Systems inherited from the old strategy will quietly enforce it
Skills
What is the organisation genuinely good at?
The distinctive capabilities of the organisation as a whole, not the CVs of individuals. The useful question is which capability would be hardest for a competitor to replicate — and, separately, which capability the new strategy requires that you do not currently have. That gap is usually the real reason a strategy stalls.
Ask yourself
- What are we genuinely better at than competitors?
- Which capability does the new strategy require that we lack?
- Are our strongest skills the ones the strategy needs?
- What would take a competitor years to copy?
Patterns that work
- Organisational capability, not individual credentials
- Name the gap between skills you have and skills the strategy needs
- Legacy strengths that no longer serve the strategy are a real cost
Style
How do leaders actually behave?
The leadership and management style as experienced from below, including how decisions get made, how disagreement is handled, and what leaders spend their attention on. Style is inferred from behaviour under pressure rather than from intent — what happens when a deadline slips or bad news arrives tells you more than any values statement.
Ask yourself
- How are decisions actually made — consultation or directive?
- What happens when someone brings bad news?
- Where do leaders spend their attention?
- Is disagreement safe here?
Patterns that work
- Behaviour under pressure reveals style; stated intent does not
- How bad news travels upward is the single most diagnostic question
- Leadership attention is a signal everyone reads accurately
Staff
Who is here, and how are they managed?
The people: numbers, roles, demographics, recruitment, development, retention, and morale. Distinct from Skills — this is about the human resource itself rather than what the organisation can do. Look for the mismatch between the staff you have and the staff the strategy assumes, since strategies routinely presuppose a workforce nobody has budgeted to hire.
Ask yourself
- Do we have the right number of the right people?
- What does the strategy assume about hiring?
- Where is turnover highest, and why?
- How is morale, honestly?
Patterns that work
- Compare the workforce you have with the one the strategy assumes
- Turnover concentrated in one team is a finding about that team's systems
- Key-person dependency belongs here, and it is nearly always understated
Ready to fill yours in?
The editor carries this whole guide with it — every block has these prompts and starter notes built in. Free, no signup, autosaves in your browser.
Open the McKinsey 7S editor