McKinsey 7S Model Explained With Practical Examples
McKinsey 7S model explained in plain language: what each element means, how to score alignment, and a worked example for a 40-person company in change.
The McKinsey 7S model is a checklist for finding out why a company is not delivering its strategy. It looks at seven elements (strategy, structure, systems, shared values, style, staff, and skills) and asks whether they point the same direction. When you change one, such as launching a new offer, the others usually lag behind, and the gap between them is where your results leak.
What the 7S model is, and what it is not
Tom Peters and Robert Waterman developed the model at McKinsey in the late 1970s, and it became famous through their book In Search of Excellence. The core idea is simple: organizations do not fail at change because the strategy was wrong. They fail because the rest of the company was built for the old strategy.
The model is a diagnostic. It tells you where things are out of line. It does not tell you what strategy to pick, how your market is moving, or what your competitors will do. For those jobs you need other tools, like PESTLE analysis for the external environment or Porter's Five Forces for industry structure.
Think of 7S as the internal checkup you run after you have decided where you are going.
The seven elements in plain language
The model splits the elements into hard and soft. Hard elements are things you can point to in a document. Soft elements live in behavior and habit, which makes them harder to change and more important.
The hard elements
Strategy. Where you will compete and how you plan to win. Not the slide, the actual choices: which customers you serve, which you turn down, and what you spend money on. If your stated strategy says "premium" but your sales team discounts to close every deal, your real strategy is discounting.
Structure. Who reports to whom, how teams are split, and who makes which decisions. In a 30-person company this is often an informal org chart plus a few unwritten rules about who can say yes to what. Structure is where you find out that three people believe they own pricing.
Systems. The recurring processes and tools that run the business: how leads are tracked, how projects are scoped, how people are paid, how performance is reviewed, how cash is forecast. Systems are the most underrated element because they quietly reward behavior. If your commission plan pays on new-logo revenue, nobody will work on renewals, whatever the strategy memo says.
The soft elements
Shared values. The beliefs people actually act on, not the ones on the wall. The model puts this in the center because every other element connects to it. A useful test: what gets people praised or quietly criticized here?
Style. How leadership behaves, not how it describes itself. Do founders make decisions in hallways or in meetings? Do they ask for bad news or punish it? Style is what staff copy.
Staff. The people you have: how many, in which roles, with what experience and motivation. This is about fit between the people and the strategy, not about whether they are good in general.
Skills. What the company, as a whole, can do well. A team of excellent individual designers may still lack the skill of running a repeatable onboarding process. Skills are capabilities you could demonstrate to a customer.
A quick reference
| Element | Ask this | Warning sign |
|---|---|---|
| Strategy | What do we say no to? | Nobody agrees on the top three priorities |
| Structure | Who decides, and who is accountable? | Decisions bounce between two or more people |
| Systems | What does our process reward? | Metrics and incentives pull against the strategy |
| Shared values | What do people actually get praised for? | Stated values and daily behavior disagree |
| Style | How does leadership spend its time? | Founders override the new process under pressure |
| Staff | Do we have the right people in the right roles? | Key roles filled by people who did not choose them |
| Skills | What can we do reliably that others cannot? | The new offer depends on capabilities nobody has built |
Step-by-step: diagnosing misalignment during change
You can run this in a single working session. The goal is a ranked list of misalignments, not a perfect picture.
- Write the change in one sentence. For example: "Move from one-off projects to monthly retainers." If you cannot write it in one sentence, you have found a strategy problem already.
- Define the target state for each S. What would structure, systems, staff, and the rest look like if the change had fully landed? Keep each answer to one or two lines.
- Describe the current state with evidence. Use data, not impressions: org charts, the compensation plan, the last ten sales calls, utilization reports, turnover numbers. Where you have no evidence, write "unknown" and treat that as a finding.
- Score each element from 1 to 5 for how close current state is to target. A 1 means the element actively works against the change. A 5 means it supports it fully.
- Score the links. Pick the three weakest elements and ask which other elements they conflict with. A weak system paired with a strong strategy is the classic pattern.
- Find the root pair. Usually one or two elements are causing the rest of the drag. Run a short 5 Whys on your lowest score to check you are fixing a cause and not a symptom.
- Pick no more than three fixes, each with an owner, a date, and a measurable result.
Get 5 to 8 people into the scoring, including at least two who are not in leadership. Leaders consistently rate style and shared values higher than their teams do, and that gap is itself useful data.
Worked example: a 45-person agency moving to retainers
Take a marketing analytics agency with $6.2M in annual revenue and 45 people. For years it sold fixed-scope projects: dashboards, audits, and attribution builds. Revenue was lumpy and the founders wanted predictability. Five months ago they announced a shift: grow recurring retainers from 20% of revenue to 60% within 12 months.
At month 5, retainers are at 27% of revenue. Utilization has fallen from 74% to 61%. Two of the six senior analysts have given notice. The founders feel the strategy is right and the team "just isn't getting it."
They run a 7S session with eight people. Here is what they find.
| Element | Score | Evidence |
|---|---|---|
| Strategy | 4 | Clear target, but no definition of who qualifies for a retainer |
| Structure | 2 | Project managers still own client relationships; nobody owns retention |
| Systems | 1 | Sales commission is 8% of first-year project value; delivery is tracked by project margin |
| Shared values | 2 | Team prides itself on "big, clever builds"; ongoing monitoring work is seen as dull |
| Style | 2 | Founders still jump into new project pitches personally and skip renewal calls |
| Staff | 3 | Strong builders, but few people who like steady account work |
| Skills | 2 | No repeatable onboarding, no health reporting, no pricing model for recurring scope |
The strategy is fine. It is the best-scored element. The damage is in systems and structure. Sales reps earn more from one $40,000 project than from a $4,000 per month retainer that would be worth $48,000 in a year, because the commission is front-loaded on project value. Delivery managers are judged on project margin, so they treat retainer clients as a drag on it. Nobody has retention as a job.
The 5 Whys on systems confirms it: retainers are not selling because reps are not paid to sell them, and reps are not paid to sell them because the compensation plan was never touched when the strategy changed.
The three fixes they choose:
- Systems: change commission to 6% of first-year contract value for retainers and 4% for projects, with a 2% bonus on renewal. Effective next quarter.
- Structure: name one account lead per retainer client, and make one senior analyst the head of retention with a target of 90% annual renewal.
- Skills: build a standard onboarding and a monthly health report, owned by that same lead, ready in 8 weeks.
Staff and values are left alone for now. They will shift as the incentives and roles change, and the team can review them again at month 9. Six months later, retainers are at 44% of revenue and utilization is back to 70%. They are behind the 60% target but moving in the right direction, and the cause of the lag is now visible and fixable.
Notice what the founders did not do. They did not rewrite the strategy, and they did not run a culture workshop. They found the specific place where the old business was still wired in.
Common mistake: scoring what you wish were true
The most common error is rating elements by intention. A founder says "our values are collaboration and learning" and scores shared values a 5. The evidence says otherwise: the last post-mortem was skipped, and the person who raised a problem in the last all-hands has not spoken up since.
How to avoid it: require one piece of evidence for every score. Pay attention to what is rewarded, who gets promoted, and what happens to people who bring bad news. If someone cannot name an example, the score is a guess, and you should mark it as unknown.
Other mistakes that waste the exercise
Treating all seven elements as equally weighted. They are not. In most small-company change efforts the break is in systems or style, because those are the ones nobody revisits after the strategy meeting. Look for the element that is quietly rewarding the old behavior.
Fixing the soft elements with talk. Announcing new values or running a team offsite rarely moves shared values. Behavior shifts when the hard elements change and leaders act differently. Change the commission plan, the meeting agenda, or who owns an account, and the values follow.
Running it once. Alignment drifts. Re-run the scoring every 3 to 6 months during a major change, and compare scores. You are looking for the trend more than the number.
Letting leadership score alone. The founders in the example rated style a 4 before the session. The team rated it a 2. That gap was the single most useful finding of the day.
Where 7S fits with other tools
7S is strongest when you already know what you want to change and need to find out why it is not sticking. It pairs well with a gap analysis: use gap analysis to measure the distance between current and target results, then use 7S to understand which parts of the organization are producing that distance.
If your fixes turn out to need more people hours than you have, check them against a simple capacity plan before committing. The example agency's head of retention role only worked because they freed 12 hours a week from a senior analyst who was previously spending that time on pitches.
Once the fixes are in place, you need a way to see whether they work. A balanced scorecard can track the handful of measures that tell you the change is landing: renewal rate, utilization, and recurring revenue share, for example.
Skip 7S if you have not decided on a strategy, or if your problem is entirely external, such as a collapsing market or a new competitor. It will not help you there.
Key takeaways
- The 7S model checks whether strategy, structure, systems, shared values, style, staff, and skills point the same way. Misalignment, not a bad strategy, is the usual reason change stalls.
- Score each element from 1 to 5 against a written target state, and require evidence for every score. Mark anything you cannot support as unknown.
- Systems and style are the most common culprits. Compensation plans, metrics, and what leaders do under pressure often reward the old behavior.
- Fix hard elements first (incentives, ownership, processes) and expect the soft elements to follow. Do not try to fix culture with announcements.
- Limit the output to three fixes with owners, dates, and measurable results, then re-score in 3 to 6 months.
- Include people outside leadership in the scoring. The gap between founder and team ratings is often your best finding.
Frequently asked questions
- What are the 7 elements of the McKinsey 7S model?
- The seven elements are strategy, structure, systems, shared values, style, staff, and skills. Strategy, structure, and systems are the hard elements you can write down. Shared values, style, staff, and skills are the soft elements that show up in behavior.
- When should a small business use the 7S model?
- Use it when a change is underway or just finished and results are lagging the plan. Typical triggers are a new strategy, a merger, a leadership change, or a jump in headcount. It is a diagnostic for misalignment, not a tool for choosing a strategy.
- How long does a 7S assessment take?
- For a company under 100 people, plan on one 90 minute workshop with 5 to 8 people plus a few hours of evidence gathering beforehand. The follow-up work of fixing the misaligned elements takes weeks or months.
- Is the 7S model still relevant?
- Yes, as a checklist for alignment. It dates from the late 1970s and says nothing about markets or competitors, so pair it with an external analysis. Its value is forcing you to look at the people and culture side, which most change plans skip.
Related playbooks
Balanced Scorecard for Small Business: A Practical Guide
Learn how to adapt the four-perspective Balanced Scorecard framework for your small business, with a worked example, a copyable template, and a step-by-step setup guide.
BCG Matrix Product Prioritization: A Small-Business Guide
Use the BCG matrix for product prioritization: sort your offers into stars, cash cows, question marks and dogs, then decide what to fund, harvest or cut.
PESTLE Analysis for Strategic Planning: A Step-by-Step Guide
Learn how to run a PESTLE analysis for strategic planning: walk through all six factors with a worked small-business example, scoring method, and a copyable template.
RICE Scoring Model Prioritization: A Step-by-Step Guide
Learn how RICE scoring model prioritization works. Score Reach, Impact, Confidence and Effort with a worked example and rank competing ideas objectively.