Organization Explore

McKinsey 7S Framework

The McKinsey 7S framework checks the fit among strategy, structure, systems, shared values, style, staff, and skills.

The questionIf we change one part of this organization, which of the other six will pull against it?

Also written 7-S. Shared values were called superordinate goals in the original article.

Model · Robert Waterman, Tom Peters, and Julien Phillips, 1980

StrategyWhere to compete and how
StructureUnits and reporting lines
SystemsProcesses, budgets, measures
StyleWhat leaders actually do
StaffWho is hired and promoted
SkillsWhat the firm is good at

Schematic of the seven elements, with shared values drawn in the middle and every element linked to every other.

When to use it

A client has announced a reorganization and the only workstream is the new org chart.
A merger team needs a common list for comparing two companies, including the parts that do not show up in a data room.
A strategy is not being carried out and nobody can say whether the cause is the plan, the people, or the way leaders behave.
The client asks for a 7S by name. Executives often know it, so it gets a hearing for culture and leadership topics that a less familiar model would not.

When to avoid it

You need to explain a performance gap by cause. Nadler-Tushman and Burke-Litwin make directional claims about what drives what, and 7S does not.
The task is to design a new organization from a settled strategy. Galbraith's Star Model gives a design sequence; 7S only checks the result.
The sponsor wants a scored assessment. 7S has no scales or measures, so any score is something the team invented.
The organization is small enough that the founder can describe all seven elements in one conversation.

Overview

The 7S framework lists seven elements of an organization and asks whether they agree: strategy, structure, systems, shared values, style, staff, and skills. It is a diagnostic checklist. It shows a team that a change in one element, usually structure, will stall if the others pull the other way, and it supports the choice of which mismatches to fix first.

It has no arrows and no measures. Nadler-Tushman and Burke-Litwin say which factors drive which. The 7S framework does not, so the order of fixes and any judgment of fit come from the team. Its practical advantage is familiarity. Executives know the name and accept shared values and leadership style as part of the agenda once they appear on the drawing.

The seven elements

Strategy

The choices about where to compete and how to win, and the allocation of resources that follows. In a 7S review the question is whether the other six elements support the strategy as written, or a different strategy that the organization is actually running.

Structure

How the work is divided and coordinated. Units, reporting lines, decision rights, and the formal links between them. The 1980 article's point was that structure is the element managers change most readily and the one that settles the least on its own.

Systems

The formal and informal procedures that run the business day to day. Budgeting, planning, performance measurement, information systems, and approvals. Systems often contradict the structure, for example when a new cross-unit team is still measured on unit profit.

Shared values

The few beliefs about purpose and conduct that people in the organization hold in common, whether or not they appear in a values statement. Drawn in the middle because they shape the other six. The test is behavior under pressure, not the wording on the wall.

Style

How senior leaders behave, judged by where they spend their time, what they ask about in meetings, and what they reward and punish. People take their cue from these patterns more than from announcements.

Staff

The people side as a whole. Who is recruited, how they are developed and promoted, which roles are seen as the route to the top, and what kind of people end up in them.

Skills

The capabilities the organization as a whole is good at, such as product engineering, cost control, or account management. A new strategy often needs a skill the organization has never had to build.

What it is not

A causal model. There are no arrows, and the framework does not say which element drives which, or what to fix first. The team has to supply that judgment and say it is a judgment.
A measurement tool. Nothing in the framework defines a scale for fit, so a red, amber, and green grid reflects the opinions of whoever filled it in.
A hierarchy with strategy at the top. The authors drew it with no starting point. Putting strategy first is a choice you make for a given engagement, not part of the model.

The steps

Fix the reference point

Agree what the elements are supposed to fit, such as the new strategy, the merged company, or the operating model in the business case. Without that anchor every element looks fine on its own terms. What comes out is one sentence the sponsor signs off on.
Describe each element as it works

Collect documents for the hard elements and evidence for the soft ones. Interview two levels below the executive team, sit in on a few meetings, and look at who was promoted last year. Write a short description of each element in its current state, with the evidence beside it.
Check the pairs

Seven elements make twenty-one pairs. Go through them and mark where two elements push behavior in opposite directions, such as a structure built for collaboration with a bonus that pays for unit results. Most of the findings sit in the pairs, not in the single elements.
Pick the binding conflicts

Choose the two or three conflicts that would block the reference point on their own. Say why each one binds and how long it will take to change. Soft elements usually take years, which affects the order.
Sequence the fixes

Because the framework gives no order, the team has to propose one and defend it. Assign an owner to each fix and set a date to repeat the review once the first changes have landed.

In practice

An industrial distributor had decided to serve its largest customers from a central key-account team instead of through local branches. Twelve months in, the key-account team existed and the large customers were still ordering through the branches. The CEO asked for a 7S review, because the board had seen one at a previous company. The consultant took the strategy as fixed and described the other six elements as they worked in practice. Structure matched the strategy. Systems did not, because branch managers were still paid on branch revenue, including the revenue the key-account team was meant to take over. Style followed the money: regional vice presidents praised branch heads who kept their big customers. Staff and skills showed the same pattern. Every senior manager had come up through a branch, and nobody in the business could build a contract price for a national customer.

The shared value that came up in nearly every interview was that the branch owns the customer. The recommendation was short. Move the bonus to account-level results, have regional leaders review key accounts with the central team, hire a pricing lead from outside, and stop presenting branch rankings at the quarterly meeting.

What you leave with

A one-sentence reference point that the seven elements are tested against.
A description of each element as it actually operates, with evidence.
A list of conflicting pairs, with the two or three that block progress marked.
A proposed order of fixes, owners, and the reasoning behind that order.

Failure points

Seven boxes and no pairs

The team writes a paragraph per element, rates each one, and stops. The framework's value is in the interactions, and a list of seven separate assessments misses the conflicts that cause the trouble.

Espoused values in the middle

The shared values box gets filled from the published values statement. The real shared values, visible in how decisions are made under pressure, can contradict the statement, and the review never finds out.

Hard elements only

Strategy, structure, and systems have documents and owners, so they get most of the analysis. Style and shared values get a sentence each, which repeats the structure-first habit the framework was written to correct.

Scores presented as findings

A heat map of fit scores goes to the board. Nobody can say what a 3 means or who decided it, and the first challenge from an executive who disagrees undoes the work.

A diagnosis with no order

The review shows that everything is connected to everything, which is true and gives the client nothing to do on Monday. Without a stated sequence, the program defaults to changing the structure again.

The failures above are usually Framing: the wrong problem was chosen before this framework was applied.

Origin

The three authors were consultants in McKinsey's San Francisco office, where Waterman and Peters led the organizational effectiveness practice. Their June 1980 article in Business Horizons, "Structure Is Not Organization," argued that reorganizing usually means redrawing the chart, and that six other elements decide whether a change works. They thanked Anthony Athos of Harvard as instrumental in developing the framework, and said the drawing had no starting point or implied hierarchy. The seventh element was then called superordinate goals, meaning the guiding values and aspirations behind a business. Later writing renamed it shared values.

Richard Pascale and Athos used the seven elements in The Art of Japanese Management (1981), and split them into three hard elements (strategy, structure, systems) and four soft ones. The 1980 article had not drawn that line, and it listed systems with style, skills, and superordinate goals as the variables managers tend to neglect. Peters and Waterman then carried the framework to a wide audience in In Search of Excellence (1982). It carries McKinsey's name, and no trademark claim on it is known.