Use when a strategy or major organizational change isn't gaining traction despite being sound on paper — auditing whether structure, systems, shared values, skills, style, and staff are all aligned with the new strategy rather than still calibrated to the old one.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill apply-seven-s-framework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apply Seven S Framework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-apply-seven-s-framework)More formats (shields.io, HTML) on the badges page.
---
name: apply-seven-s-framework
description: Use when a strategy or major organizational change isn't gaining traction despite being sound on paper — auditing whether structure, systems, shared values, skills, style, and staff are all aligned with the new strategy rather than still calibrated to the old one.
source: McKinsey & Company — Waterman, Peters & Phillips, "Structure Is Not Organization" (Business Horizons, 1980); Peters & Waterman, "In Search of Excellence" (1982)
tags: [organizational-alignment, change-management, mckinsey-7s, strategy-execution, organizational-diagnosis, culture]
related: [design-organizational-structure, apply-tactical-adaptation, design-team-culture]
---
# Apply Seven-S Framework
Audit all seven organizational elements — Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff — for alignment with each other, and treat any misaligned element as the actual blocker on execution, instead of assuming a stalled strategy is a strategy problem.
## Why This Is Best Practice
**Origin:** McKinsey consultants Robert Waterman, Tom Peters, and Julien Phillips introduced the framework in "Structure Is Not Organization" (Business Horizons, 1980), arguing that organizational effectiveness depends on far more than restructuring the org chart — it requires alignment across seven interdependent elements, split into three "hard" elements (Strategy, Structure, Systems) that are relatively easy to define and change, and four "soft" elements (Shared Values, Skills, Style, Staff) that are harder to define but often the actual source of implementation failure. Peters and Waterman popularized it further in "In Search of Excellence" (1982).
**Adopted by:** The 7S framework has been standard McKinsey and broader management-consulting diagnostic tooling for over four decades and is taught in organizational-design and change-management curricula globally. It is the standard reference framework whenever a consulting engagement or internal strategy team needs to explain why a well-designed strategy is failing to produce results in execution.
**Impact:** The framework's central diagnostic insight is that organizations overwhelmingly default to changing only the hard elements — announcing a new strategy, redrawing the org chart, rolling out a new reporting system — while leaving the soft elements (the values people actually act on day to day, the skills the current staff actually have, the leadership style modeling the change, and who is actually staffed against the new priorities) unchanged. Post-mortems on failed strategic initiatives and mergers repeatedly identify this hard/soft misalignment — not a flawed strategy itself — as the proximate cause of execution failure.
**Why best:** Diagnosing execution failure by re-examining the strategy alone misses the far more common failure mode: the strategy is sound, but the organization implementing it is still calibrated to the old strategy in ways the strategy document itself doesn't touch. The 7S framework forces a check across all seven elements simultaneously, surfacing misalignment (e.g., a new customer-centric strategy sitting inside a structure, incentive system, and skill base still optimized for the old product-centric approach) that a strategy-only review would never find.
Sources: Waterman, Peters & Phillips, "Structure Is Not Organization" (Business Horizons, 1980); Peters & Waterman, "In Search of Excellence" (1982); McKinsey organizational-diagnosis practice
## Steps
### Step 1: Define the intended Strategy precisely
State the strategy the organization is trying to execute in specific, falsifiable terms — not a slogan. This is the reference point every other element gets checked against; a vague strategy statement makes every subsequent alignment check unfalsifiable too.
### Step 2: Audit the three "hard" elements against the strategy
- **Structure**: Does the org chart's reporting lines, team boundaries, and decision rights actually route authority and information the way the strategy requires? A strategy requiring cross-functional speed sitting inside a siloed functional structure is misaligned.
- **Systems**: Do the processes and procedures — planning cycles, budgeting, performance measurement, IT systems — reinforce or fight the strategy? A strategy emphasizing innovation measured by a budgeting system that punishes any spending variance is misaligned.
- **Strategy** (re-check): Confirm the strategy as stated is still the one actually being resourced day to day, not a different de facto strategy revealed by where money and attention actually go.
### Step 3: Audit the four "soft" elements against the strategy
- **Shared Values**: Do the values people actually act on — not the values posted on the wall — support the strategy? A strategy requiring customer-first tradeoffs inside a culture that actually rewards internal politics or short-term numbers is misaligned.
- **Skills**: Does the organization's actual current capability match what the strategy requires? A strategy requiring a new capability (e.g., data science, international operations) without a credible plan to build or hire that skill is misaligned.
- **Style**: Does leadership's actual behavior — how they spend time, what they ask about in reviews, what they visibly reward — model the strategy, or still model the old one? Leaders who talk the new strategy but spend their time and attention on old-strategy metrics undercut it regardless of what they say.
- **Staff**: Are the specific people staffed against the priorities the strategy requires — not just headcount totals, but the right people with the right skills against the right initiatives? A strategy's top priority understaffed relative to a legacy initiative is misaligned regardless of the org chart's formal priority ranking.
### Step 4: Identify which specific element(s) are the actual blocker
Across all seven, identify the specific element or elements out of alignment with the stated strategy — not a general sense that "execution is hard." Misalignment is usually concentrated in one or two elements (commonly Systems, Style, or Skills) rather than spread evenly across all seven; find the specific one(s) actually blocking traction.
### Step 5: Sequence the fix — soft elements usually need more time and different tools than hard elements
Structure and Systems can be changed by decree relatively quickly. Shared Values, Skills, Style, and Staff typically require sustained effort — training, leadership modeling, hiring and role changes, and repeated reinforcement over months, not a single announcement. Do not expect a soft-element misalignment to resolve on the same timeline as a structural reorg; plan the soft-element fix with a longer, more sustained intervention.
## Rules
- Never diagnose stalled execution as purely a strategy problem before checking all seven elements — the strategy is frequently sound; the organization implementing it is what's misaligned.
- Distinguish stated values from actual values, and stated priorities from actual staffing and time allocation — audit what people do, not what the organization says it values.
- Do not assume a hard-element change (restructuring, new system) alone will produce alignment — soft elements (values, skills, style, staff) require separate, sustained intervention and typically lag behind hard-element changes.
- Identify the specific misaligned element(s) rather than treating "poor execution" as a diffuse, unlocatable problem — the framework's value is in localizing the blocker, not confirming that alignment in general matters.
## Examples
**Post-merger integration:** Two companies merge and announce a unified customer-facing strategy (Strategy, Structure — new org chart — both changed on paper). Six months later, the strategy hasn't taken hold: the legacy compensation system (Systems) still rewards each former company's old product lines separately, leadership from each side (Style) still models allegiance to their original company's priorities in meetings, and front-line staff (Staff, Skills) haven't been cross-trained on the other company's products. The audit identifies Systems, Style, and Skills — not Strategy or Structure — as the actual blockers, and the fix targets compensation redesign, leadership alignment sessions, and a cross-training program rather than another restructuring.
**Digital transformation stall:** A traditional retailer announces a digital-first strategy and builds a new digital team (Structure). A year later, digital initiatives are still deprioritized in practice: the annual planning and budgeting system (Systems) still allocates capital by historical channel revenue share, favoring stores; store managers (Style, as the dominant leadership voice) still get the most executive attention in reviews; and the organization lacks in-house digital-product skills (Skills), routing every digital decision through slow external vendors. The 7S audit locates Systems, Style, and Skills as misaligned, redirecting the fix toward a new capital-allocation process, elevated digital leadership visibility, and a hiring plan — rather than yet another team reorganization.
## When NOT to Use
- When the strategy itself is the actual problem — flawed market assumptions, wrong customer targeting, or an uncompetitive value proposition — 7S assumes the strategy is sound and diagnoses organizational alignment around it; use a market/competitive-analysis skill first to validate the strategy itself.
- For a small, single-team change where "alignment across seven organizational elements" is disproportionate to the scale of the change — reserve this for organization-wide or business-unit-level strategy execution problems.
- When the organization needs a one-time structural decision rather than an ongoing alignment audit — for a single structural question (e.g., how to draw reporting lines), use `design-organizational-structure` directly instead of the full seven-element audit.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!