Mckinsey 7s

Concept of the skill

What it is: McKinsey 7S is an organizational-alignment framework for diagnosing whether seven internal elements reinforce one another: shared values, strategy, structure, systems, style, staff, and skills. It is used when a team needs to understand why an organization can or cannot execute a strategy, transformation, merger, reorg, or operating-model change.

Mental model: Treat the organization as an interdependent system. Map current and target states for all seven elements, then look for contradictions and reinforcing loops rather than assuming the visible structure is the whole organization.

Why it exists: Agents often jump from a strategy gap to one favorite fix: change the org chart, add OKRs, hire people, run training, or change culture. This skill makes the agent inspect the whole organization system before recommending the intervention.

What it is NOT: It is not Five Forces, Value Chain, VRIO, SWOT/TOWS, OKRs, Playing to Win, a generic change-management checklist, or a standalone culture framework.

Adjacent concepts: organization design, operating model, strategy execution, change readiness, transformation management, post-merger integration, culture, leadership style, capability building, process systems, staff model, shared values.

One-line analogy: 7S tunes the organization as a connected instrument, not as seven separate parts.

Common misconception: The seven headings are not independent boxes. The framework is about fit among elements; an answer that lists the seven elements but does not test alignment has not applied 7S.

McKinsey 7S

Domain Context

Use McKinsey 7S for internal organization-alignment questions: strategy execution, transformations, operating-model changes, post-merger integration, major reorgs, scaling bottlenecks, culture-to-strategy gaps, capability-building needs, and leadership or system friction. Use public, aggregate, or synthetic examples only. Do not include personal data, employee-level facts, customer data, payment data, secrets, confidential deal details, or private business facts in examples or evals.

The framework is strongest when the user asks why a strategy is not becoming execution, why a reorg did not change behavior, why a transformation is blocked, or whether a change plan covers the organization system. It is weaker when the question is about external industry attractiveness, value-chain economics, durable resource advantage, quantified option value, or goal-setting mechanics.

McKinsey's 2025 operating-model work explicitly refreshes the classic 7S framework into a broader "Organize to Value" system. If the user asks for current McKinsey operating-model redesign in a volatile environment, name that newer source and consider using it as the primary frame. If the user specifically asks for 7S, use the classic framework while disclosing that the newer McKinsey model exists for deeper current operating-model design.

Coverage

This skill teaches agents to:

1. Frame the organization, strategic change, decision, time horizon, and evidence boundary.
2. Map the seven elements: shared values, strategy, structure, systems, style, staff, and skills.
3. Separate current state, target state, evidence, assumptions, and uncertainty for each element.
4. Diagnose fit, contradictions, reinforcing loops, and missing support across elements.
5. Identify whether the root cause is in one element, the interaction between elements, or an unclear target strategy.
6. Convert the diagnosis into interventions, owners, sequencing, and monitoring triggers.
7. Distinguish 7S from adjacent strategy, organization, and execution methods.
8. Keep analysis privacy-safe by using aggregate or synthetic examples and avoiding employee-level details.

Philosophy of the skill

7S is useful because organizations often treat performance gaps as isolated problems. A strategy does not execute because it was announced. A structure does not work because boxes moved. A culture does not change because values were written down. Capabilities do not improve because training happened once.

The framework asks whether the elements support the same change. A structure may conflict with the strategy. Systems may reward the old behavior. Leaders may model a style that contradicts shared values. Staff may lack capacity, and skills may not match the strategy. The useful output is therefore not a tidy seven-row table. The useful output is a causal alignment diagnosis: which elements conflict, which elements reinforce, and which few interventions would change the system.

Workflow

1. Frame the alignment question

Start by defining the scope and target. Do not begin with the seven headings until the change being tested is clear.

Organization, unit, or team:
Strategic change or performance gap:
Decision this analysis must inform:
Current time horizon:
Target outcome:
Evidence available:
Known constraints:
Privacy boundary:

If the user cannot name the target strategy or change, pause and clarify the intended direction. 7S cannot test alignment against a vague aspiration.

2. Map the seven elements

Use the seven elements as prompts for evidence, not as a fill-in-the-blanks exercise.

Shared values are not generic culture. They are the operating beliefs and priorities that shape decisions. If they are not visible in trade-offs, incentives, leadership behavior, or systems, mark them as claimed rather than proven.

3. Build current-state and target-state rows

For each element, record current and target states separately.

Element:
Current state:
Target state:
Evidence:
Gap:
Confidence:
Dependencies on other elements:
Risk if unchanged:

Do not score alignment before this distinction is clear. A system can be internally consistent with the old strategy and misaligned with the new one.

4. Diagnose element-to-element fit

The main work is the interaction map. Ask how each element supports or blocks the others.

Name contradictions directly. A useful 7S diagnosis sounds like: "The stated strategy needs cross-functional speed, but structure and systems still optimize local functional efficiency, and leadership style escalates decisions upward."

5. Prioritize root causes

Do not recommend one action per element. Find the few constraints that create the most misalignment.

Prioritize by decision impact, dependency, reversibility, time to effect, risk, and evidence strength.

6. Convert diagnosis into a change plan

End with actions that change the organization system.

Intervention:
7S element(s) addressed:
Contradiction it resolves:
Owner role:
First concrete step:
Metric or signal:
Review date:
Risks:
Evidence still needed:

Sequence changes so supporting elements move together. Do not recommend a reorg without naming the systems, style, staff, and skills changes needed for the structure to work.

Output Template

McKinsey 7S Alignment Review

Scope:
Strategic change or performance gap:
Target outcome:
Evidence boundary:

7S map:
| Element | Current state | Target state | Evidence | Gap | Confidence |

Alignment diagnosis:
1. Reinforcing fit:
2. Contradictions:
3. Hidden root causes:
4. Missing evidence:

Priority interventions:
1. Action:
   Elements addressed:
   Contradiction resolved:
   Owner:
   Metric:
   Next review:

Residual risks:
Downstream method:

Boundary Rules

Verification

Before presenting a 7S output, check:

• The organization or unit of analysis is named.
• The target strategy, change, or performance gap is concrete enough to test.
• All seven elements were considered, and omissions are explained.
• Current state and target state are separated for each material element.
• The answer diagnoses interactions among elements, not just one heading at a time.
• At least three fit relationships or contradictions are named.
• Recommendations tie back to specific element gaps and owners.
• The answer does not treat structure as the whole organization.
• If the user asked for current McKinsey operating-model redesign, the 2025 Organize to Value refresh is mentioned as a more current adjacent model.
• No personal data, employee-level details, customer data, secrets, or confidential facts are exposed.

Do NOT Use When

References

• references/mckinsey-7s-sources.md - source notes from McKinsey, the 1980 Business Horizons article record, and the 2025 McKinsey operating-model refresh.
• references/upstream-displacement-2026-06-08.md - audit-loop upstream-displacement check for this concept skill.