McKinsey 7S

The original McKinsey 7S, in brief

Developed at McKinsey & Company in the late 1970s by Tom Peters and Robert Waterman, working with Richard Pascale and Anthony Athos. First set out in “Structure Is Not Organization” (Waterman, Peters and Phillips, Business Horizons, 1980) and made famous by “In Search of Excellence” (1982).

The 7-S framework first appeared in "Structure Is Not Organization," by Robert H. Waterman Jr., Tom Peters and Julien Phillips of McKinsey's San Francisco office, in Business Horizons in June 1980¹. It grew out of an internal McKinsey task force, started in 1977, on why changes to organizations so often failed to stick¹. The authors credited Harvard professor Anthony Athos as central to it¹. Peters later wrote that Athos insisted every word begin with S, and that Richard Pascale was part of the two-day session where the model took shape².

The core claim is in the title. Redrawing the org chart does not change the organization. The authors argued that real change depends on how seven things relate to each other: structure, strategy, systems, style, skills, staff, and what they called superordinate goals¹. They said the alliteration was deliberate, to help people remember it¹.

Within two years the center had a new name. Pascale and Athos used the framework in The Art of Japanese Management (1981) to compare Matsushita with ITT³. Peters and Waterman then made it famous in In Search of Excellence (1982), by which point superordinate goals had become shared values⁴². McKinsey still presents 7-S as a model of coordination, not of structure⁵.

Common misreadings

• "Shared values come first." The 1980 diagram put superordinate goals in the middle, but the authors wrote that it had "no starting point or implied hierarchy"¹. Which element drives a change depends on the company. If any element was likely to dominate, they suggested it was systems¹.
• "Every company has shared values." The authors observed that superordinate goals were missing in most organizations, and present in most of the best performers¹. Finding none is a finding.
• "Three hard elements, four soft." That tidy split is how the model is usually taught⁶. The 1980 article drew the line differently. It grouped systems with style, skills and superordinate goals as things managers tend to dismiss as soft, and argued that all of them can be observed and even measured¹.
• "It is a planning tool." It describes the organization that has to carry out a plan. The authors called using it as a checklist its most trivial use. The point is how the seven fit together¹.
• "Staff means headcount." In the original, staff means the people and how the company develops them, especially how it grows its future managers¹.

McKinsey 7S examples

When McKinsey 7S fits, where it struggles, and what it does not answer

How to implement McKinsey 7S

1. Start from the change. Name what is prompting the review: a new strategy, a reorganization, a merger, or a strategy that is stalling.
2. Describe each element as it is today. Interview the leadership team, or ask everyone the same questions anonymously so the soft elements are described honestly.
3. Describe each element as the strategy needs it. Write the target state for all seven, starting with shared values.
4. Find the misfits. Compare pairs: does the structure support the strategy? Do the systems reward the style you want? The biggest gaps usually sit in the soft elements.
5. Turn the biggest gaps into priorities. Choose two or three to fix first, each with an owner and a date. Soft elements take longest, so start them early.

Adopting McKinsey 7S: the first cycle and the rhythm

First cycle. Plan on two to three weeks. Gather views on each of the seven through short interviews or an anonymous survey. Reach beyond the top team: style is best judged by the people who work under it. Then hold one working session of about half a day to compare how things are today with what the strategy needs, and choose the gaps to close.

Rhythm. 7-S has no cadence of its own. Run it again when something large changes, or once a year at your planning retreat, to see whether the gaps you chose have closed. Track those gaps between runs in whatever system you already use for goals.

How long change takes. The original authors warned that changing systems, retraining staff or building commitment to a new shared goal could take years, while strategy and structure can move faster on the surface¹. Expect the soft gaps to outlast the hard ones. The model never runs by itself; it is a lens you pick up when you need it.

What derails it. Filling in seven boxes and stopping there. Describing only today, with no target to compare against. Letting the top team rate its own style. Ending with a diagnosis and no owners.

Common McKinsey 7S mistakes

• Treating it as seven boxes to fill. The value is in how the elements fit each other, not in describing each one well.
• Only looking at the hard elements. Strategy, structure and systems are easy to change on paper. Style and staff are usually why the change does not stick.
• Describing today, not what is needed. Without a target state there is no gap, and without a gap there is nothing to decide.
• Running it before the strategy is settled. 7S checks fit against a strategy. If the strategy is still open, decide it first.
• Ending with a diagnosis and no owners. A good 7S session ends with the two or three gaps you will close, who owns each, and by when.

Does McKinsey 7S work? The evidence

The original support was experience, not a study. The 1980 authors said they had used the framework for about a year in teaching, workshops and client work, and concluded that it seemed to work¹. That is a practitioner's judgment, and they presented it as one.

The book that made 7-S famous has been tested, with disputed results. Michelle Clayman, writing in the Financial Analysts Journal in 1987, followed 29 of the "excellent" companies from In Search of Excellence. Their financial ratios began to decline almost across the board from the date they were picked. Over five years, a portfolio of them beat the S&P 500 by about 1% a year, while a portfolio of 39 low-ranked companies beat it by over 12% a year⁹. A 2024 review in Management Learning notes that later work disputed those financial findings, and that critics also faulted how the companies were chosen⁷. None of this tests 7-S itself. It tests the book's choice of companies.

Direct tests of the framework are few. Most are surveys in a single sector that use the seven elements as headings for a questionnaire. A typical one, published in BMC Health Services Research in 2022, surveyed 249 physicians in 22 departments of public hospitals in the Warsaw region of Poland. The soft elements scored lower than the hard ones, with staff, skills and style lowest. The authors noted that their simple statistical tests could not rule out other explanations¹⁰.

The research for this page found no study that follows organizations over time and shows that better fit among the seven causes better results once other factors are accounted for. Read 7-S as a well-reasoned checklist backed by long practice, not as a tested model of cause and effect. Kaplan's 2005 case that the balanced scorecard complements it is a design argument from the scorecard's co-creator, not a test⁶.

McKinsey 7S compared

McKinsey 7S glossary

Fit

How well the seven elements support each other. The whole point of the model.

Hard S's

Strategy, structure and systems, as the model is usually taught. Easier to write down and change.

Soft S's

Shared values, style, staff and skills. Harder to see and slower to change.

Superordinate goals

The 1980 name for shared values: the guiding ideas and aims, often unwritten, that go beyond formal objectives¹.

Shared values

The core beliefs and sense of purpose that hold the organization together. Drawn at the center of the diagram.

Systems

The formal and informal procedures that run the work, such as budgeting, training and cost accounting¹.

Style

How leaders actually behave, including where they spend their time and what that signals, and the culture it reflects¹.

Staff

The people, and how the organization hires, develops and places them.

Skills

What the organization as a whole is distinctively good at, not the talents of individuals¹.

Free tools that help