The hard S's
The plans and the formal setup: what the company has decided and written down.
- 1
- Strategy
- 2
- Structure
- 3
- Systems
The McKinsey 7S framework, the seven S's, worked
The McKinsey 7S framework says an organization changes well only when seven things line up: strategy, structure, systems, shared values, style, staff and skills. McKinsey consultants Robert Waterman, Tom Peters and Julien Phillips introduced it in 1980 to show that a new org chart alone rarely changes how a company works. In a case, use it when a strategy, merger or turnaround stalls in execution. Soreno, an AI voice interview practice app for consulting, investment banking and other finance candidates, runs a free M&A case with no sign-up, where you judge whether a deal will work, and full mock cases with scored feedback.
Updated
- What it looks at
- One organization, seven parts
- And how well the parts fit each other
- Origin
- Waterman, Peters and Phillips
- McKinsey, Business Horizons, June 1980
- Worked case
- 7 S's, 4 out of line
- Invented by us, every number shown
- Free practice
- No sign-up
- A full M&A case with a timer
What is the McKinsey 7S framework?
The 7S framework comes from "Structure Is Not Organization", a 1980 Business Horizons paper by three consultants in McKinsey's San Francisco office. Their claim: effective organizational change is the relationship between structure, strategy, systems, style, skills, staff and what they then called superordinate goals, and not structure alone. Tom Peters writes that superordinate goals later became shared values. The diagram puts that seventh S in the middle with no starting point or ranking, because any of the seven can be the one that drives change.
The soft S's
The people and the culture. Peters' summary of the idea: hard is soft, soft is hard.
- 4
- Shared values
- 5
- Style
- 6
- Staff
- 7
- Skills
Worked example: Pinewood Software (ours)5 steps
Pinewood Software, an invented company, sold mostly to small teams. A year ago it set out to win large companies and set a target of 40 enterprise deals. It closed 12. The CEO asks why the new strategy isn't working. This case and every number in it are invented by Soreno for practice.
Size the gap
12 of 40 deals, 30% of target
Pinewood missed by 28 deals. Before blaming the market, check that buyers are interested: in this case the pipeline is full and deals stall late, so the problem is inside the company.
Check each S
4 of 7 S's work against the plan
Strategy: fits. Clear and written down: win companies with 1,000 or more staff. Structure: fits. A new enterprise team, with its own head, reporting to the CEO. Systems: doesn't fit. Commission is paid on monthly bookings, so a deal that takes months pays nothing for most of a year. Staff: doesn't fit. The enterprise team was filled from the existing inside sales reps. Skills: doesn't fit. The company is great at fast, low-touch sales. Few people have run a long, multi-buyer deal. Style: doesn't fit. The founders still open every all-hands with weekly sign-ups and spend no time on enterprise calls. Shared values: fits. "Software anyone can start using in a minute" still holds for large buyers if the product stays simple.
Find the driver
Systems pay for the old strategy
An enterprise deal takes about 7 months here, and commission pays on monthly bookings. Reps are paid to keep selling small deals, so they do. The strategy and the new team were the quick part, and they are already in place.
Check the people
9 of 60 reps, 15%, have sold enterprise
Staff and skills both point the same way: the enterprise team is the old team with a new name. And as long as the founders celebrate only weekly sign-ups, the rest of the company reads that as the real priority.
Recommend
Change the pay plan first, then the people
Pay enterprise reps on signed annual contracts, hire a handful of reps who have closed large deals, and have the CEO join the biggest late-stage calls each week. Don't reorganize again, the structure is fine. The main risk: small team sales dip while reps switch, so keep that team on its old plan.
The seven S's, as the 1980 paper defines themFrom the 1980 paper
Each definition below is a short paraphrase of the 1980 paper.
1
Strategy
The actions a company plans in response to, or ahead of, changes outside it: its customers and competitors. The paper calls it a company's way of saying how it will create unique value.
2
Structure
How tasks are divided and then coordinated. The paper's point is that coordination, making the whole thing work, is the harder half.
3
Systems
All the procedures, formal and informal, that make the organization go day by day: budgeting, training and cost accounting. The authors say that if one S threatens to dominate the others, it could well be systems.
4
Style
How top management comes across through what it does, including how it spends its time. In the paper's words, organizations may listen to what managers say, but they believe what managers do.
5
Staff
The people, in the sense of how a company develops them, especially its future managers. Not line and staff.
6
Skills
What the company does best, its dominating capabilities. The paper notes a new skill may only take root once the old one is dismantled.
7
Shared values (first called superordinate goals)
Guiding concepts: a set of values and aspirations, often unwritten, that go beyond the formal statement of objectives. The fundamental ideas a business is built around.
What the framework is forThe paper's own account
From the paper's conclusion and its notes on the diagram.
Fit
Progress in one S needs the others
The authors say it is difficult, perhaps impossible, to make significant progress in one area without progress in the others.
Pace
Strategy and structure move fastest
Changes in strategy and structure may happen quickly on the surface. A new system, a retraining program or a new shared goal could take years, and real change moves at the pace of all seven.
The soft side
Take it seriously
The paper argues that style, systems, skills and superordinate goals, long treated as soft, can be observed directly and even measured, and can matter at least as much as strategy and structure. Peters adds that there was no precedence among the seven.
Uses
From checklist to fit test
At its simplest, the authors say, it works as a checklist. At its most powerful, it makes you focus on how the seven interact and fit.
From Waterman, Peters and Phillips, Structure Is Not Organization (1980) and Tom Peters, A Brief History of the 7-S Model (2011).
How do you use the 7S framework in a case interview?
In our experience, almost no case asks for the 7S by name. It earns its place when the numbers say a plan should work and the company still isn't delivering. Here is how a strong answer uses it.
Start from the result that is missing
Name the gap first: deals not closed, synergies not captured, a turnaround behind plan. Then use the seven S's to ask why.
Test fit, don't describe
For each S, say whether it supports the plan or works against it. A list of seven descriptions with no verdict tells the interviewer nothing.
Pick the one to change first
Close with the S that drives the rest and what you would change in it. Often it is a system, such as pay or budgeting, not the org chart.
Leave it out for market questions
Skip it for market sizing, pricing, profitability math or whether an industry is attractive. Use a profit tree, Porter's five forces or a market entry structure there.
6 case questions where the 7S framework helps
Each of these has an organization side: a merger, a deal, a fix or a team that has to work differently. Under each is what a strong answer does.
Mergers and deals
Two organizations that have to work as one.
Two regional airlines are considering a merger. How would you estimate the synergies?
Sizes cost and revenue synergies first, then checks whether the two airlines' systems, skills and cultures can be combined fast enough to capture them. Practice it, see a model answer
A large food company wants to acquire a plant-based snack startup. Should it?
Values the startup, then asks what makes it work, such as fast product launches and its founders' style, and whether the buyer's systems would slow it down. Practice it, see a model answer
A private equity firm is considering buying a regional chain of dental clinics. How would you assess the deal?
Tests the market and the returns, then the people side: how dentists are paid today and what a new owner's systems would change for them. Practice it, see a model answer
Fix the organization
The plan is set, and execution is the problem.
A hospital's emergency room wait times have doubled in a year. How would you structure the problem?
Maps patient flow to find the bottleneck, then looks past beds to staffing, scheduling systems and how shifts are led. Practice it, see a model answer
One of your client's three divisions is losing money. Should they fix it, sell it or close it?
Compares the value of each option. A fix plan names what has to change beyond the org chart: systems, skills and who leads it. Practice it, see a model answer
Close the case
One recommendation, with the reason behind it.
You have finished the analysis on a market entry case and the CEO walks in. What is your recommendation?
Leads with the answer, then the figure behind it, the main risk and the next step, including who in the company has to act. Practice it, see a model answer
What mistakes do candidates make with the 7S framework?
The ones we hear most when candidates bring the 7S into a case.
Opening a case with it
Most cases start with a business question, such as profit, growth or a deal. Bring in the seven S's once you know the problem sits inside the organization.
Reciting seven boxes
Walking through every S at the same depth wastes time. Spend it on the two or three that work against the plan.
Fixing the org chart
The paper's whole point is that structure is not organization. A reorganization alone often leaves pay, skills and habits pulling the old way.
Treating the soft S's as vague
Style and shared values can be checked: how the CEO spends the week, what gets praised at the all-hands, who gets promoted. Use facts like these.
Forgetting the outside world
The 7S looks inside one company. If customers have left or a rival cut prices, start there, with SWOT or five forces.
Find why the plan stalled out loud
Soreno's AI interviewer runs a full case, hands you the facts on the deal and the people when you ask, pushes back on your diagnosis and scores the session. Start your free week.
Questions people ask
What is the McKinsey 7S framework?
A model of seven parts of an organization that have to fit together for change to work: strategy, structure, systems, shared values, style, staff and skills. It was introduced in a 1980 paper by McKinsey consultants Robert Waterman, Tom Peters and Julien Phillips.
What are the 7 S's?
Strategy, structure, systems, shared values, style, staff and skills. The 1980 paper draws them around the seventh S, then called superordinate goals, in the middle, with no starting point and no ranking.
Who created the 7S framework?
Robert H. Waterman Jr., Thomas J. Peters and Julien R. Phillips of McKinsey's San Francisco office, who published it in Business Horizons in June 1980. Peters writes that it took shape at a session in San Francisco with Anthony Athos of Harvard Business School and Richard Pascale. Peters and Waterman then included it in In Search of Excellence (1982).
What are the hard and soft S's?
Strategy, structure and systems are the hard S's. Shared values, style, staff and skills are the soft S's. Tom Peters, one of the authors, sums up the idea as hard is soft, soft is hard: the people, values and skills are the real bedrock, and the plans and numbers are often the soft part.
Is it shared values or superordinate goals?
Both name the same S. The 1980 paper calls it superordinate goals. Tom Peters, one of the authors, writes that the name later became shared values.
Should I use the 7S framework in a case interview?
Use its logic when a strategy, merger or turnaround is failing in execution. Skip it for sizing, pricing, profitability or industry questions, where a profit tree, five forces or a market entry structure fit better.
What is the difference between the 7S framework and SWOT?
SWOT lists an organization's strengths, weaknesses, opportunities and threats, inside and out. The 7S looks only inside, and tests whether seven parts of the organization pull in the same direction.
What are the limits of the 7S framework?
In our view, three. It looks only inside the company, so it can't tell you whether the strategy itself is right. It gives no order of priority, which the 1980 paper says is deliberate: the diagram has no starting point. And it names what to check, not how to measure it, so bring your own facts to each S.
When was the 7S framework introduced?
The work began in 1977 with an internal McKinsey project on organization effectiveness, part of an effort launched by managing director Ron Daniel. The framework was published in June 1980, in the paper Structure Is Not Organization.