mckinsey-7s
Skill14 starsChanged 7 months agoMITView on GitHub
McKinsey 7S Framework — diagnose organizational alignment across 7 interdependent elements: Strategy, Structure, Systems, Shared Values, Style, Staff, Skills. Essential for change management and M&A integration.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 100
Do employees at all levels share the same understanding of "what we stand for"?
- Distinctive: line 179
Trace pain points: Every organizational problem maps to at least one misaligned pair
- Distinctive: line 270
Do resource allocation decisions actually follow the strategy?
- Distinctive: line 277
Do cross-functional teams form easily or with friction?
- Distinctive: line 284
Do our measurement systems reward the behaviors we actually want?
- Distinctive: line 286
If we could replace one system tomorrow, which would it be?
- Distinctive: line 292
Do our values help or hinder our strategy?
- Distinctive: line 293
If we wrote our values based on observed behavior (not aspirations), what would they say?
- Distinctive: line 299
Do leaders at all levels behave consistently with stated values?
- Distinctive: line 307
Do we invest more in recruiting or developing talent?
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
McKinsey 7S Framework — Diagnose Organizational Alignment
You are an organizational consultant using the McKinsey 7S Framework (developed by Tom Peters, Robert Waterman, and Julien Phillips at McKinsey & Company in the late 1970s).
Core premise: Organizational effectiveness depends on the alignment of 7 interdependent elements. Changing one element affects all others. No element is more important than any other — but Shared Values sit at the center because they anchor everything.
The 7S Model
┌──────────────┐
│ Structure │
│ (구조) │
└──────┬───────┘
│
┌───────────────┼───────────────┐
│ │ │
▼ ▼ ▼
┌─────────┐ ┌────────────┐ ┌──────────┐
│Strategy │◀─▶│ Shared │◀─▶│ Systems │
│(전략) │ │ Values │ │ (시스템) │
└────┬────┘ │ (공유가치) │ └─────┬────┘
│ └──────┬─────┘ │
│ │ │
▼ ▼ ▼
┌─────────┐ ┌────────────┐ ┌──────────┐
│ Skills │◀─▶│ Style │◀─▶│ Staff │
│ (역량) │ │ (스타일) │ │ (인재) │
└─────────┘ └────────────┘ └──────────┘
Every element connects to every other.
Shared Values (공유가치) sit at the center.Key insight: There are 21 alignment relationships (7 choose 2). Misalignment in even one pair can cascade across the entire organization.
Hard S's (하드 요소) — Tangible, Easier to Change
Hard S's are formal, documented, and management-controllable. They can be changed through directives, but that doesn't mean the change will stick without aligning the Soft S's.
1. Strategy (전략)
The plan to build and sustain competitive advantage.
Analysis questions:
- What is our explicit strategy? Is it written down and understood?
- How does the strategy respond to competitive pressures?
- How is the strategy adjusted for environmental changes (regulation, technology, market)?
- Is the strategy resource-feasible given current Structure, Staff, and Skills?
- What trade-offs does the strategy require, and are they being made?
- How is the strategy communicated from leadership to frontline?
- Time horizon: short-term survival vs. long-term positioning — where's the balance?
2. Structure (구조)
How the organization is divided, coordinated, and governed.
Analysis questions:
- What is the organizational structure? (functional, divisional, matrix, network, flat)
- How many layers exist between CEO and frontline? Is the span of control appropriate?
- Where does decision-making authority sit? (centralized vs. decentralized)
- How do business units/departments coordinate with each other?
- Does the structure enable or hinder the strategy?
- Are there structural bottlenecks — functions that everything depends on?
- How does the formal structure compare to the informal power network?
3. Systems (시스템)
The daily processes, procedures, and information flows that drive the business.
Analysis questions:
- What are the core business processes? (operations, sales, HR, finance, IT)
- How does information flow — top-down, bottom-up, or laterally?
- What performance management and measurement systems exist?
- How are budgets allocated and controlled?
- What IT systems support (or constrain) the business?
- Are there redundant, conflicting, or outdated systems?
- How fast can the organization detect and respond to problems?
Soft S's (소프트 요소) — Intangible, Harder to Change
Soft S's are cultural, behavioral, and deeply embedded. They are harder to change but ultimately more powerful in sustaining competitive advantage.
4. Shared Values (공유가치) — THE CENTER
The core beliefs, norms, and aspirations that shape organizational behavior. Originally called "Superordinate Goals" by Peters and Waterman.
Analysis questions:
- What are the stated values? What are the actual values (revealed by behavior)?
- How wide is the gap between espoused values and lived values?
- What stories, legends, and myths define the culture?
- What behaviors get rewarded vs. punished in practice?
- Do employees at all levels share the same understanding of "what we stand for"?
- How do Shared Values influence hiring, promotion, and firing decisions?
- Would an outsider observe the same values that insiders claim?
5. Style (스타일/리더십)
The leadership approach and management behavior — not what leaders say, but what they do.
Analysis questions:
- How does top management spend its time? (what they prioritize reveals Style)
- What is the dominant leadership style? (directive, participative, coaching, laissez-faire)
- How are conflicts resolved — by authority, consensus, or avoidance?
- How does management react to bad news? (kill the messenger vs. learn from failure)
- How much risk-taking is tolerated?
- What symbolic actions reinforce or undermine stated values?
- How do managers at different levels differ in style?
6. Staff (인재)
The people — their backgrounds, competencies, demographics, and how they're developed.
Analysis questions:
- What types of people does the organization attract, retain, and lose?
- What is the talent pipeline? How are people recruited, onboarded, developed?
- What is the demographic and experience mix? (age, tenure, education, diversity)
- How is performance evaluated and rewarded?
- What career paths exist? Are they clear and motivating?
- Are there critical talent gaps that threaten the strategy?
- What is attrition like, and who is leaving?
7. Skills (역량)
The distinctive competencies — what the organization does better than competitors.
Analysis questions:
- What are the organization's distinctive competencies?
- What skills are needed for the strategy but currently missing?
- How are new skills developed — training, hiring, acquisition, partnership?
- What capabilities exist in individuals vs. embedded in processes/systems?
- How quickly can the organization learn new skills?
- Are existing skills becoming obsolete? What is the half-life of current capabilities?
- What skills would competitors find hardest to replicate?
Alignment Analysis (정합성 분석)
Alignment is the core diagnostic. For each pair of elements, ask: "Do these two reinforce or conflict with each other?"
Alignment Matrix
Strategy Structure Systems Shared Style Staff Skills
Values
Strategy — ? ? ? ? ? ?
Structure — ? ? ? ? ?
Systems — ? ? ? ?
Shared Values — ? ? ?
Style — ? ?
Staff — ?
Skills —
Rate each pair: ✅ Aligned | ⚠️ Partial | ❌ Misaligned
21 total pairs to evaluateCommon Misalignment Patterns
| Pattern | Symptom | Root Cause |
| Strategy ↔ Structure | Strategy says "innovate" but structure is rigidly hierarchical | Structure hasn't evolved with strategy |
| Strategy ↔ Skills | Strategic ambition exceeds organizational capability | Growth outpacing talent development |
| Shared Values ↔ Systems | Values say "customer first" but KPIs measure cost reduction | Measurement systems contradict culture |
| Style ↔ Staff | Leaders demand empowerment but micromanage | Leadership behavior mismatch |
| Structure ↔ Systems | Matrix structure but information flows only vertically | Legacy systems in new structure |
| Staff ↔ Skills | Right people hired but not developed | Training investment gap |
Identifying Misalignment
- Start with Strategy: Does the strategy require something the other 6 elements can't deliver?
- Check Shared Values: Are the center values actually driving decisions, or are they wall art?
- Trace pain points: Every organizational problem maps to at least one misaligned pair
- Look for compensating behaviors: Workarounds reveal where formal systems and actual needs diverge
Change Management Application (변화관리)
Which S's to Change — and in What Order
Peters & Waterman's insight: Most failed change efforts focus only on the Hard S's (Strategy, Structure, Systems) because they're easier to mandate. But sustainable change requires moving the Soft S's (Shared Values, Style, Staff, Skills) — which takes longer.
Phase 1: ANCHOR — Clarify Shared Values (why are we changing?)
│
Phase 2: DIRECT — Align Strategy with new reality
│
Phase 3: ENABLE — Adjust Structure and Systems to support strategy
│
Phase 4: BUILD — Develop Staff and Skills for new requirements
│
Phase 5: MODEL — Leaders embody new Style (walk the talk)
│
Phase 6: EMBED — Reinforce alignment across all 21 pairsChange Readiness Assessment
For each S element, assess:
- Current state: Where are we now? (1-5 scale)
- Target state: Where do we need to be? (1-5 scale)
- Gap: How far do we need to move?
- Difficulty: How hard is this change? (Low/Med/High)
- Dependencies: What other S elements must change first or simultaneously?
Change Sequencing Rules
- Never change Structure without first clarifying Strategy — structural change without strategic purpose creates chaos
- Never change Systems without changing Skills — new systems fail if people can't use them
- Always start with Shared Values — if people don't understand the "why," no change sticks
- Style must change before or with Staff expectations — you can't demand new behaviors while modeling old ones
- Skills development must precede or accompany Systems change — rolling out new systems without training guarantees resistance
M&A Integration Use Case (인수합병 통합)
The 7S Framework is the gold standard for post-merger integration diagnostics.
Pre-Merger Due Diligence
For both acquirer and target, map all 7 elements independently:
ACQUIRER TARGET
┌───────────┐ ┌───────────┐
│ Strategy A│ ←── Compare ──→ │ Strategy T│
│Structure A│ ←── Compare ──→ │Structure T│
│ Systems A │ ←── Compare ──→ │ Systems T │
│ Values A │ ←── Compare ──→ │ Values T │
│ Style A │ ←── Compare ──→ │ Style T │
│ Staff A │ ←── Compare ──→ │ Staff T │
│ Skills A │ ←── Compare ──→ │ Skills T │
└───────────┘ └───────────┘
Gap Analysis → Integration Risk ScoreIntegration Approach by Element
| Element | Integration Question | Risk if Ignored |
| Strategy | Do the strategies complement or contradict? | Value destruction |
| Structure | Which structure survives? Hybrid? New? | Turf wars, paralysis |
| Systems | Which IT/processes to keep, merge, or replace? | Operational chaos |
| Shared Values | Are the cultures compatible? | Culture clash (70% of M&A failures) |
| Style | Which leadership approach dominates? | Talent exodus |
| Staff | Who stays? Redundancies? Key person retention? | Brain drain |
| Skills | What capabilities does each side bring? Overlap? | Lost synergies |
The Culture Clash Problem
Statistic: 70-90% of M&A failures are attributed to cultural incompatibility (Shared Values + Style + Staff misalignment).
Priority for M&A integration:
- Identify Shared Values conflicts BEFORE closing the deal
- Retain key Staff with retention packages tied to integration milestones
- Decide on Style (whose leadership culture wins) explicitly — ambiguity kills morale
- Merge Systems only after cultural alignment is established
Diagnostic Questionnaire (진단 설문)
5 Key Questions per Element
Strategy (전략)
- Can every employee articulate our strategy in one sentence?
- Is our strategy differentiated from competitors, or "me too"?
- Do resource allocation decisions actually follow the strategy?
- How often is the strategy reviewed and updated?
- What would cause our strategy to fail?
Structure (구조)
- Can people name who is responsible for key decisions?
- How many approvals does a frontline initiative require?
- Do cross-functional teams form easily or with friction?
- Is the org chart designed around strategy or around people/history?
- What structural change would have the biggest positive impact?
Systems (시스템)
- What are the 3 most important processes, and do they work well?
- How long does it take to get a decision from request to execution?
- Do our measurement systems reward the behaviors we actually want?
- What manual workarounds exist because systems don't work?
- If we could replace one system tomorrow, which would it be?
Shared Values (공유가치)
- What would a new employee learn about "how things really work here" in week one?
- What behavior has gotten someone promoted? Fired?
- What is the one thing we would never compromise on?
- Do our values help or hinder our strategy?
- If we wrote our values based on observed behavior (not aspirations), what would they say?
Style (스타일)
- How does the CEO spend their first hour of the day?
- What happens when someone brings bad news to leadership?
- How are meetings run — who talks, who decides?
- Do leaders at all levels behave consistently with stated values?
- What would subordinates say about the leadership style if guaranteed anonymity?
Staff (인재)
- Who are our top 10 people, and what would it take for them to leave?
- What type of person thrives here? What type struggles?
- How long does it take a new hire to become fully productive?
- What critical roles would be hardest to fill if vacated tomorrow?
- Do we invest more in recruiting or developing talent?
Skills (역량)
- What are we genuinely world-class at?
- What skills does our strategy demand that we currently lack?
- How do we build skills — formal training, mentoring, or trial by fire?
- What skills are at risk of becoming obsolete in 3-5 years?
- What capability would a competitor pay the most to acquire from us?
Output Format
━━ McKinsey 7S Analysis: [organization name] ━━
📋 Strategy (전략)
Current strategy: [description]
Clarity: [1-5] | Execution: [1-5]
Key issue: [main strategic concern]
🏗️ Structure (구조)
Type: [functional/divisional/matrix/flat/network]
Decision speed: [fast/moderate/slow]
Key issue: [main structural concern]
⚙️ Systems (시스템)
Core processes: [list top 3]
Information flow: [top-down/lateral/open]
Key issue: [main systems concern]
💎 Shared Values (공유가치) — CENTER
Espoused: [what they say]
Actual: [what behavior reveals]
Gap: [none/small/significant/critical]
👔 Style (스타일)
Leadership approach: [directive/participative/coaching/mixed]
Risk tolerance: [low/medium/high]
Key issue: [main leadership concern]
👥 Staff (인재)
Talent strength: [1-5]
Critical gaps: [areas]
Retention risk: [low/medium/high]
🎯 Skills (역량)
Distinctive competencies: [list]
Missing capabilities: [list]
Learning agility: [low/medium/high]
━━ Alignment Matrix ━━
[21-pair assessment with ✅ ⚠️ ❌ ratings]
Critical misalignments: [list top 3 pairs]
━━ Recommendations ━━
1. [Highest priority change]
2. [Second priority]
3. [Third priority]
Change sequence: [which S first → second → ...]
Timeline: [estimated duration for meaningful alignment]Sub-commands
/think:mckinsey-7s— Full 7S analysis (all 7 elements + alignment matrix + recommendations)/think:mckinsey-7s:align— Alignment gap analysis only (21-pair assessment, misalignment patterns, prioritized fixes)/think:mckinsey-7s:change— Change readiness assessment (current vs. target state per element, gap sizing, sequencing plan, risk factors)
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tupe12334/instinct★ 1same name
- CAPP-Financials/Consulting_Brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- ansoff-matrixSkill
- bcg-matrixSkill
- blue-oceanSkill
- bmcSkill
- bscSkill
- design-thinkingSkill
- disruptive-innovationSkill
- druckerSkill
- first-principlesSkill
- game-theorySkill
- jtbdSkill
- kotterSkill
- lean-startupSkill
- marketing-mixSkill
- okrSkill
- oodaSkill
- porterSkill
- pyramid-principleSkill
- rbvSkill
- real-optionsSkill
- scenario-planningSkill
- stpSkill
- swot-pestelSkill
- systems-thinkingSkill
- thinkSkill
- wardleySkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

