Chapter 15: McKinsey 7S - Aligning the Organisation to Execute the Strategy

~~Chapter 15: McKinsey 7S - Aligning the Organisation to Execute the Strategy~~

Video: McKinsey 7S: New Video Coming

Video: Change Management in Case Solutions: How to Make Your Recommendation Actually Happen with People

Learning Objectives

By the end of this chapter, you should be able to:

explain the seven organisational elements that influence performance;
distinguish the hard and soft elements of organisational alignment;
identify inconsistencies among strategy, structure, systems, values, leadership, staff, and skills;
evaluate whether an organisation is prepared to implement a proposed strategy;
compare the organisation's current state with the state required by the recommendation;
identify organisational barriers that could prevent successful execution;
understand how changing one element may affect the others;
prioritise the organisational gaps that matter most;
connect the 7S Framework with change management and implementation planning;
develop recommendations that are strategically sound and organisationally feasible.

Why This Matters

A strategy can be analytically strong, financially attractive, and supported by customer demand and still fail. Why? Because organisations don't execute strategies through recommendations and presentation slides. They execute them through:

people;
leadership;
decisions;
responsibilities;
systems;
incentives;
skills;
routines;
relationships;
culture.

A strategy may fail because:

employees lack the required skills;
leadership doesn't support the change;
departments have conflicting priorities;
incentives encourage the wrong behaviour;
technology cannot support the new process;
decision rights are unclear;
the organisational structure creates barriers;
the organisation lacks enough people or capacity;
employees don't understand why the change is necessary;
the proposed strategy conflicts with deeply held organisational values.

These are not minor implementation details. They determine whether the strategy can become reality. The McKinsey 7S Framework helps teams examine whether the organisation is internally aligned to execute its strategy. Its seven elements are:

Strategy;
Structure;
Systems;
Shared Values;
Style;
Staff;
Skills.

The purpose is not to find seven separate problems. It is to understand whether the seven elements support one another and support the strategy.

Discover Your MAD Skills Principle

A strategy that doesn't fit the organisation will struggle to become reality.

A team might recommend digital transformation because customers increasingly prefer digital service, but implementation may require:

new technical skills;
different decision-making processes;
greater collaboration across departments;
updated performance measures;
revised employee roles;
changes to leadership behaviour;
a culture more comfortable with testing and learning.

If the recommendation changes only the technology, it has not addressed the organisational transformation. A useful 7S analysis follows this progression: Proposed Strategy → Organisation Requirements → Alignment Gaps → Change Actions → Execution.

Where McKinsey 7S Fits

McKinsey 7S is an organisational alignment and implementation tool. It is particularly valuable when a case involves:

organisational transformation;
restructuring;
digital transformation;
rapid growth;
declining organisational performance;
a merger or acquisition;
integration;
culture;
leadership;
workforce capability;
implementation failure;
strategic change;
international expansion;
innovation;
operating-model redesign;
resistance to change.

The framework can help answer questions such as:

Is the organisation prepared to execute the strategy?
What must change internally?
Where are the most important alignment gaps?
Which implementation barriers are being overlooked?
Does the organisation have the required skills and staff?
Are systems and incentives supporting the strategy?
Is leadership modelling the required behaviour?
Does the recommendation fit the organisation's values and Culture?

McKinsey 7S may add less value when the case contains no meaningful organisational question. If the decision is a narrow pricing adjustment or short-term financial calculation, a full 7S analysis may be unnecessary. The case determines the tool.

Understanding Organisational Alignment

Alignment exists when the seven elements reinforce one another and support the organisation's objectives. For example, an organisation pursuing operational efficiency might require:

a focused strategy;
clear responsibilities;
standardised systems;
values supporting consistency and improvement;
leadership that uses data and reinforces discipline;
employees with process-improvement skills;
staffing levels appropriate to demand.

An organisation pursuing rapid innovation may require:

a strategy focused on experimentation;
cross-functional teams;
flexible funding and approval systems;
values supporting learning;
leadership that tolerates responsible failure;
employees with creative and technical skills;
enough staff capacity to test new ideas.

Neither configuration is automatically better. The question is whether the organisation's elements align with its strategy and with one another.

Alignment Is Not Sameness

Alignment doesn't mean every team thinks, behaves, or operates identically. Different parts of an organisation may require different:

structures;
systems;
leadership approaches;
skills;
staffing models.

A research team may need greater autonomy than a compliance function. A premium-service division may require different skills and incentives from a low-cost operating unit. Alignment means those differences are intentional and collectively support the strategy.

The Seven Elements

The seven elements are often grouped into:

Hard Elements

Strategy;
Structure;
Systems.

These are usually more visible and easier to document or change formally.

Soft Elements

Shared Values;
Style;
Staff;
Skills.

These can be more difficult to observe, measure, and change because they involve people, behaviour, Culture, and accumulated capability. The hard and soft elements are equally important. Changing an organisational chart is relatively straightforward. Changing the behaviour, trust, skills, and informal relationships behind the chart may take much longer.

1. Strategy

Strategy defines what the organisation is trying to accomplish and how it intends to create value or advantage. It includes choices about:

customers;
markets;
products and services;
competitive position;
growth;
capabilities;
resource allocation;
priorities;
what the organisation will not do.

Questions to Ask

What is the organisation trying to accomplish?
Is the strategic direction clear?
Are priorities understood across the organisation?
Are resources aligned with those priorities?
Does the organisation make meaningful choices?
Does the proposed recommendation fit the broader direction?
Has leadership explained why the strategy matters?
Do departments interpret the strategy consistently?
Is the strategy realistic given the organisation's capabilities?
What must the organisation stop doing?

Warning Signs

too many competing priorities;
vague strategic language;
inconsistent interpretations;
resources spread across too many initiatives;
departments pursuing conflicting goals;
no clear customer or competitive focus;
a recommendation disconnected from organisational capability.

A strategy cannot guide execution if employees don't understand the choices it requires.

2. Structure

Structure explains how responsibilities, authority, reporting relationships, and coordination are organised. It may involve:

functions;
business units;
geographic divisions;
product groups;
project teams;
reporting lines;
centralisation;
decentralisation;
decision rights;
spans of control;
formal and informal coordination.

Questions to Ask

Who is responsible for the strategy?
Who makes the important decisions?
Are decision rights clear?
Does the structure support collaboration?
Are teams organised around functions, customers, products, or geography?
Are there too many management layers?
Where do decisions become delayed?
Are responsibilities duplicated or missing?
Does information move across organisational boundaries?
Will the recommendation require new roles, teams, or governance?

Warning Signs

unclear ownership;
duplicated responsibilities;
slow decisions;
functional silos;
excessive hierarchy;
weak cross-functional coordination;
conflicting authority;
a new initiative without an accountable leader.

Changing structure may involve:

creating a cross-functional team;
establishing a program office;
assigning a senior sponsor;
clarifying decision rights;
centralising a capability;
decentralising local decisions;
redesigning roles.

However, changing the organisational chart alone rarely creates alignment.

3. Systems

Systems are the formal and informal processes through which work is performed, decisions are made, information is shared, and performance is managed. They include:

planning;
budgeting;
technology;
communication;
hiring;
training;
performance management;
incentives;
data collection;
reporting;
approvals;
quality control;
customer feedback;
project management;
risk management.

Questions to Ask

Which systems support the current way of working?
Which systems would the proposed strategy require?
Can the technology support the change?
Are data accurate, accessible, and timely?
Do performance measures reinforce the strategy?
Do incentives encourage the desired behaviour?
Are approval processes slowing decisions?
How is customer or employee feedback used?
Are processes consistent across the organisation?
What must be redesigned, integrated, or removed?

Warning Signs

fragmented technology;
duplicate data entry;
incentives that conflict with strategy;
measures focused only on short-term results;
slow approval processes;
poor information sharing;
outdated procedures;
inconsistent implementation;
decisions based on incomplete data.

Systems often determine what people actually do. Leadership may say innovation matters, but if budgeting requires immediate returns and performance measures punish failed experiments, the system communicates a different priority.

4. Shared Values

Shared Values are the beliefs, principles, norms, and assumptions that shape organisational behaviour. They sit at the centre of the 7S Framework because they influence all the other elements. Shared values may concern:

customers;
quality;
ethics;
innovation;
collaboration;
risk;
inclusion;
sustainability;
performance;
accountability;
learning;
employee wellbeing.

Shared values are not merely the statements written on the organisation's website. The real values of an organisation are revealed through:

what leaders pay attention to;
which behaviours are rewarded;
which behaviours are tolerated;
how difficult decisions are made;
how employees are treated;
how customers are treated;
how failure is handled;
where resources are allocated.

Questions to Ask

What does the organisation claim to value?
What behaviour is actually rewarded?
What happens when values conflict with short-term performance?
Does the proposed strategy fit the Culture?
What assumptions shape decision-making?
How does the organisation respond to risk and failure?
Do employees trust leadership?
What behaviours would need to change?
Which existing values could support the transformation?
Which cultural norms could resist it?

Warning Signs

stated values contradicted by incentives;
low trust;
blame-oriented behaviour;
resistance to information sharing;
short-term results prioritised over customer or employee outcomes;
avoidance of difficult conversations;
change fatigue;
leadership behaviour inconsistent with organisational messages.

Culture should not be treated as a vague explanation for every problem. Teams should identify the specific behaviours, assumptions, and organisational mechanisms affecting execution.

5. Style

Style refers primarily to how leaders and managers behave and make decisions. It includes:

leadership approach;
communication;
decision-making;
delegation;
accountability;
visibility;
risk tolerance;
conflict management;
feedback;
the behaviours leaders model.

Style may be:

directive;
participative;
coaching-oriented;
entrepreneurial;
consensus-driven;
data-driven;
risk-averse;
centralised;
empowering.

No single leadership style is appropriate in every situation. A crisis may require fast, centralised decisions. Innovation may require greater autonomy and tolerance for experimentation. A major transformation may require a clear direction combined with meaningful employee participation.

Questions to Ask

How are important decisions made?
Who is involved?
How does leadership communicate?
Do leaders model the behaviour the strategy requires?
Is constructive disagreement encouraged?
How is failure handled?
Are employees trusted to act?
Is leadership aligned around the recommendation?
Who will sponsor the change?
How visible and credible is that sponsor?

Warning Signs

leaders communicating conflicting priorities;
excessive control;
low employee voice;
avoidance of accountability;
poor feedback;
leaders asking others to change without changing themselves;
decisions made too slowly or without consultation;
no credible sponsor for the initiative.

Employees will often judge the importance of a change by what leaders consistently do, not by what leaders announce.

6. Staff

Staff concerns the people within the organisation and how the workforce is recruited, deployed, supported, developed, and retained. It includes:

workforce size;
workforce composition;
roles;
recruitment;
retention;
succession;
engagement;
workload;
deployment;
diversity;
career development;
employee experience.

Questions to Ask

Does the organisation have enough people?
Are employees in the right roles?
Which roles are critical to the strategy?
Are workloads sustainable?
Are key positions difficult to fill?
Where is turnover highest?
Are employees engaged?
Does the workforce reflect the customers and communities served?
What new roles will the strategy require?
Can existing employees transition into those roles?
What recruitment or retention risks exist?

Warning Signs

chronic understaffing;
high turnover;
unclear roles;
excessive dependence on a few individuals;
change added to already overloaded employees;
weak succession;
critical hiring delays;
employee groups excluded from planning;
insufficient support during implementation.

"Staff" is not simply a headcount question. It concerns whether the organisation has the right people, in the right roles, with the capacity and support to execute.

7. Skills

Skills are the capabilities and areas of expertise of the organisation and its people. They may include:

technical skills;
analytical skills;
customer-service capability;
sales capability;
project management;
leadership;
change management;
digital expertise;
partnership management;
innovation;
operational excellence;
regulatory knowledge;
cross-functional collaboration.

Skills can exist at several levels:

individual;
team;
organisational;
partner network.

Questions to Ask

What does the organisation do especially well?
Which skills support the current strategy?
Which skills does the proposed strategy require?
Where are the capability gaps?
Are important skills concentrated in a few people?
Can the required skills be developed internally?
Which skills should be hired, acquired, borrowed, or accessed through partners?
How long will development take?
How will the organisation retain critical knowledge?
How will learning be transferred across teams?

Warning Signs

outdated capabilities;
limited digital or analytical expertise;
dependence on one expert;
weak management capability;
training disconnected from strategy;
knowledge trapped in departments;
no capability-development plan;
assuming employees will learn during implementation without time or support.

Skills analysis should be closely connected to the Value Chain, VRIO, workforce planning, and implementation.

Understanding the Connections

The seven elements influence one another. For example, a company adopts a strategy based on digital self-service. That strategy may require:

a structure connecting technology, operations, and customer service;
systems providing integrated customer data;
shared values supporting accessibility and experimentation;
a leadership style that enables cross-functional decisions;
staff in new digital and customer-success roles;
skills in user experience, analytics, cybersecurity, and product management.

If only the technology system changes, the transformation is incomplete.

Example of Misalignment

Suppose an organisation says it wants to become more innovative.

Element	Current condition
Strategy	Innovation is presented as a strategic priority
Structure	Decisions remain centralised in several management layers
Systems	Budgets require immediate returns from every initiative
Shared Values	Failure is treated as poor performance
Style	Leaders approve all significant decisions
Staff	Employees have little time for experimentation
Skills	Teams lack customer-testing and rapid-prototyping experience

The problem is not an absence of innovative ideas. The organisation is not aligned to support innovation. A stronger recommendation would address:

decision rights;
innovation funding;
pilot criteria;
leadership behaviour;
employee capacity;
experimentation skills;
learning systems.

Current State Versus Required State

One of the most practical ways to use 7S is to compare how the organisation operates today with how it must operate for the strategy to succeed. A current-to-required analysis might look like this:

Element	Current state	Required state	Important gap
Strategy	Broad growth across several markets	Focused entry into one priority segment	Strategic priorities must be narrowed
Structure	Functions operate independently	Cross-functional market-entry team	Coordination and ownership
Systems	Separate customer and operational data	Integrated performance dashboard	Technology and information gap
Shared Values	Emphasis on avoiding mistakes	Responsible testing and learning	Cultural barrier
Style	Decisions concentrated at the top	Clear direction with delegated pilot decisions	Leadership and decision-right gap
Staff	Existing employees already at capacity	Dedicated implementation team	Capacity gap
Skills	Strong operations, limited digital expertise	Digital product and analytics capability	Capability gap

The purpose is not to produce seven equal recommendations. The purpose is to identify the gaps most likely to prevent execution.

Prioritising Alignment Gaps

Not every gap deserves the same attention. Prioritise organisational gaps using five criteria.

1. Strategic Importance: How essential is the element to the recommendation?

2. Severity: How large is the difference between the current and required state?

3. Interdependence: How many other elements depend on resolving the gap?

4. Difficulty and Time: How difficult and time-consuming will the change be?

5. Risk of Inaction: What happens if the gap is not addressed?

A team may identify seven gaps but focus the recommendation on two or three critical ones. For example:

the organisation lacks the required digital skills;
customer and operational data are fragmented;
no leader owns the transformation.

These gaps affect Skills, Systems, Structure, and Style. Addressing them may unlock improvement across several other elements.

Organisational Readiness for Change

The 7S Framework helps identify what must change. Change-readiness analysis asks whether the organisation is prepared to make those changes. Readiness may depend on:

clarity of the reason for change;
leadership alignment;
employee trust;
available capacity;
past change experience;
urgency;
workforce skills;
resource availability;
communication;
incentives;
stakeholder support;
the scale of disruption.

Questions to Ask

Do employees understand why change is necessary?
Is leadership genuinely aligned?
Is there a credible sponsor?
Does the organisation have enough time and capacity?
Have previous changes succeeded or failed?
Are employees experiencing change fatigue?
What groups are likely to support or resist the change?
What will employees gain or lose?
Are managers equipped to lead the transition?
Are the required resources committed?
How will progress and feedback be managed?

A strategy may be organisationally desirable but not immediately ready for full implementation. The team may need to recommend:

a pilot;
phased implementation;
capability development;
leadership alignment;
employee consultation;
manager training;
additional resources before scaling.

Connecting 7S to Change Management

The 7S Framework and change management answer related but different questions.

· McKinsey 7S Asks: What organisational elements must align?

· Change Management Asks: How will people move from the current way of working to the required way of working?

who is affected;
what behaviour must change;
why people may support or resist;
what communication is required;
what Training or support is needed;
which leader owns the change;
what systems or incentives must change;
how progress will be measured;
how feedback will shape implementation.

People Are Not an Implementation Footnote

Teams frequently place "employee training" at the end of an implementation plan, as if it would resolve every people-related issue. Training will not solve:

unclear strategy;
conflicting incentives;
weak leadership;
excessive workload;
distrust;
poor communication;
missing authority;
structural barriers;
a culture that punishes the desired behaviour.

A meaningful people plan addresses more than knowledge. Employees may need:

awareness of why the change matters;
involvement in designing the change;
clarity about new roles;
confidence in leadership;
time to practise;
tools and resources;
coaching;
reinforcement;
aligned incentives;
evidence that the change is working.

Turning Alignment Gaps into Implementation Actions

A strong 7S recommendation translates gaps into specific actions.

Alignment gap	Action	Owner	Measure
No clear transformation owner	Appoint an executive sponsor and program lead	CEO	Governance established within 30 days
Fragmented customer data	Integrate priority data into one pilot dashboard	Technology lead	Dashboard adoption and data accuracy
Limited digital expertise	Hire product lead and train cross-functional pilot team	HR and digital sponsor	Roles filled and competency assessment
Risk-averse approval process	Create defined pilot funding and decision rights	CFO and sponsor	Approval time and number of tests completed
Employee uncertainty	Conduct manager briefings and employee design sessions	Change lead	Understanding, participation, and feedback
Incentives focused only on short-term sales	Add adoption and customer-outcome measures	HR and sales leader	Balanced performance scorecard implemented

The actions should be:

specific;
sequenced;
owned;
measurable;
resourced;
connected to the recommendation.

Sequencing Organisational Change

Not all seven elements can change simultaneously. A practical sequence might be:

· Align the Direction

o Clarify:

o strategy;

o leadership commitment;

o priorities;

o scope;

o the reason for change.

· Establish Ownership

o Define:

o implementation leader;

o decision rights;

o governance;

o cross-functional participation.

· Build the Foundation

o Address:

o critical systems;

o staffing;

o capabilities;

o resources;

o initial process changes.

· Test the New Model

o Use:

o pilots;

o employee feedback;

o customer feedback;

o performance measures;

o learning reviews.

· Reinforce the Change

o Align:

o incentives;

o performance management;

o communication;

o recognition;

o leadership behaviour;

o ongoing learning.

· Scale and Sustain

o Expand successful practices while monitoring:

o adoption;

o capability;

o performance;

o employee experience;

o customer outcomes;

o emerging alignment problems.

The sequence will vary, but the implementation plan should recognise dependencies. For example, employees should not be held accountable for a new process before they have the skills, systems, authority, and time required to perform it.

A Worked Example

Return to the regional meal-kit company examined in Chapters 11–14. The proposed strategy is to launch a partnership-led pilot in a new Canadian city. The strategy builds on the company's ability to combine:

regional supplier relationships;
culinary expertise;
flexible menu development.

However, the company has never operated outside its home region.

Strategy

Current State: The company has discussed broad expansion, but has not clearly prioritised markets, customer segments, or the conditions required for scaling.

Required State: The organisation needs a focused pilot strategy with:

one city;
a defined target segment;
clear performance thresholds;
limited initial investment;
expansion triggers.

Gap: The company must replace a broad growth ambition with a focused test-and-learn strategy.

Structure

Current State: The founders make most important decisions. Operations, marketing, culinary development, and technology work largely within their own functions.

Required State: The pilot requires:

Gap: No person or team currently owns the complete market-entry process.

Systems

Current State: Customer, inventory, supplier, and delivery data are fragmented. Performance reporting focuses on sales rather than contribution margin, retention, waste, and delivery reliability.

Required State: The pilot requires:

integrated operational reporting;
partner service standards;
demand forecasting;
real-time order visibility;
pilot performance measures;
a regular learning-review process.

Gap: Existing systems cannot provide the information needed to operate and evaluate the pilot.

Shared Values

Current State: The company values local relationships and product creativity, but employees are accustomed to informal decision-making and rapid last-minute changes.

Required State: The pilot requires:

local authenticity;
operational discipline;
evidence-based experimentation;
accountability;
and learning from customer feedback.

Gap: The organisation must preserve its creativity while developing more consistent processes.

Style

Current State: The founders are highly involved and make many operational decisions.

Required State: Leadership must:

communicate the pilot's purpose;
establish clear boundaries;
delegate day-to-day decisions;
tolerate responsible experimentation;
use evidence to determine whether to scale.

Gap: The founders must shift from direct control to sponsorship and disciplined governance.

Staff

Current State: Existing managers and employees are responsible for the home market.

Required State: The pilot needs:

a market-entry lead;
local operations support;
supplier coordination;
partner management;
and sufficient customer-service capacity.

Gap: Adding the pilot to existing workloads would create execution risk.

Skills

Current State: The company is strong in culinary development, relationships with local suppliers, and customer engagement. It is weaker in:

geographic expansion;
partner governance;
integrated forecasting;
digital product management;
structured experimentation.

Required State: The organisation must retain its existing competencies while developing the new capabilities required to transfer them into another market.

Gap: The organisation has a strong source of differentiation but lacks several scaling capabilities.

Prioritised Alignment Gaps

The team identifies three critical gaps:

no accountable cross-functional pilot structure;
fragmented systems and performance measures;
insufficient staff capacity and expansion capability.

These gaps influence several 7S elements simultaneously.

Organisational Actions

The recommendation should therefore include:

Establish Pilot Governance

appoint a senior sponsor;
select a dedicated pilot lead;
create a cross-functional team;
define partner-management responsibility;
establish decision rights.

Build the Pilot System

integrate priority customer, inventory, and delivery data;
develop a pilot dashboard;
establish partner service standards;
measure contribution margin, retention, waste, and delivery reliability;
hold biweekly learning reviews.

Develop and Add Capability

protect existing culinary and supplier-development expertise;
train the pilot team in experimentation and market entry;
recruit or contract local operational expertise;
provide change and project-management support;
document a repeatable supplier-onboarding process.

Manage the People Transition

explain why the pilot is being launched;
clarify what will and will not change in the home market;
involve affected employees in process design;
protect employees from unsustainable workload;
provide role-specific Training;
use feedback to adjust the model.

The 7S analysis has transformed a market-entry recommendation into an organisationally credible implementation plan.

McKinsey 7S Is Not the Recommendation.

Completing a 7S analysis doesn't determine the organisation's strategy. A complete process is:

define the proposed strategy;
determine what the strategy requires from the organisation;
assess the current state of each element;
identify important misalignments;
examine how the gaps affect one another;
prioritise the barriers most likely to prevent execution;
develop organisational actions;
integrate those actions into the implementation plan;
assign ownership and resources;
measure adoption, capability, and results;
adjust as the organisation learns.

The framework tests whether the organisation can execute the recommendation. It doesn't replace strategic analysis, financial evaluation, stakeholder analysis, risk assessment, or change management.

Measuring Organisational Change

The organisation should measure both implementation activity and actual adoption.

Strategy Measures

employee understanding of priorities;
resource alignment;
strategic milestones;
and progress against intended outcomes.

Structure Measures

decision time;
role clarity;
cross-functional participation;
issue-escalation time;
and accountability.

Systems Measures

system use;
data accuracy;
process compliance;
approval time;
reporting frequency;
and incentive alignment.

Shared Values Measures

employee perceptions;
observed behaviours;
psychological safety;
collaboration;
trust;
and willingness to raise problems.

Style Measures

leadership visibility;
communication consistency;
decision delegation;
feedback quality;
and sponsor effectiveness.

Staff Measures

staffing levels;
workload;
turnover;
absenteeism;
engagement;
role coverage;
and retention of critical employees.

Skills Measures

competency assessments;
training completion;
demonstrated proficiency;
capability transfer;
time to competence;
and dependence on external expertise.

Training completion alone doesn't prove that employees can or will use the new skills. Measures should connect to behaviour and performance.

Winning the Room: Presenting McKinsey 7S.

A slide containing seven boxes filled with organisational observations can overwhelm the audience. The judges don't need a description of the entire organisation. They need to understand why the strategy could fail and how the implementation plan addresses that risk.

Lead with the Alignment Conclusion

For example: The pilot is strategically attractive, but the organisation is not currently structured or equipped to execute it.

Focus on the Critical Gaps

Instead of explaining all seven elements equally, identify the two or three misalignments that matter most:

no accountable pilot owner;
fragmented operational data;
insufficient expansion capability.

Show the Connections

Explain how the gaps reinforce one another: Without a dedicated pilot owner, functions will continue making isolated decisions. Fragmented information will prevent the team from identifying problems quickly, while limited staff capacity will shift attention away from the home market.

Connect Each Gap to an Action

Critical gap	Implementation response
No clear ownership	Appoint sponsor and pilot lead
Fragmented data	Build integrated pilot dashboard
Limited capacity and skills	Add dedicated staff and local expertise

Explain the People Impact

Show:

who is affected;
what changes for them;
what support they receive;
how resistance or workload will be managed;
how adoption will be measured.

The analytical chain becomes: Strategy Requirement → Alignment Gap → Execution Risk → Organisational Action.

Coach's Lens

Don't use McKinsey 7S to identify seven unrelated problems. Use it to identify alignment. If your strategy requires a highly innovative organisation but:

leadership is risk-averse;
incentives reward only short-term performance;
budgets require immediate returns;
systems punish unsuccessful experiments;
employees lack testing skills;
staff have no time to develop ideas,

then the strategy and organisation are misaligned. The solution is not an "innovation workshop." The recommendation must address the organisational conditions preventing innovation. I often ask teams what must be true inside the organisation for this strategy to work, then which of those conditions doesn't exist today. Those two questions turn strategy into implementation.

Common Mistakes

· Treating the Seven Elements as Independent. The elements influence and reinforce one another. Explain the most important connections and misalignments.

· Giving Every Element Equal Attention: Not every element is equally important to every case. Prioritise the gaps most likely to impede execution.

· Focusing Only on the Hard Elements: Strategy, structure, and systems are more visible, but values, leadership, people, and skills may determine whether change is adopted. Examine both formal design and human behaviour.

· Shared Values as Website Statements: Published values may differ from actual behaviour. Examine what leaders reward, tolerate, measure, and fund.

· Recommending Restructuring Too Quickly: Changing reporting lines doesn't automatically solve coordination, capability, trust, or leadership problems. Identify the root cause of misalignment before changing the structure.

· Using Training as the Entire People Plan: Training cannot solve unclear roles, poor systems, conflicting incentives, low trust, or insufficient capacity. Address the complete environment surrounding the required behaviour.

· Ignoring Employee Capacity: Teams often add implementation responsibilities to already overloaded employees. Assess workload, staffing, priorities, and which work will stop.

· Assuming Leadership Support: A strategy may have executive approval without active sponsorship or consistent leadership behaviour. Identify the sponsor, required actions, and accountability.

· Treating Resistance as Irrational: Employees may have legitimate concerns about workload, job security, feasibility, fairness, or past failures. Understand the reasons for resistance and respond with evidence, participation, support, and clarity.

· Describing Culture Vaguely: "Culture must change" is too broad to implement. Identify the specific behaviours, incentives, assumptions, and leadership actions that must change.

· Ignoring Dependencies: A new performance measure may fail if data systems are not ready. New roles may fail if decision rights remain unclear. Sequence changes based on their dependencies.

· Using 7S Without an Organisational Question: Don't force the framework into every case. Use 7S when organisational alignment or implementation materially affects the decision.

· Stopping at Diagnosis: Identifying misalignment doesn't resolve it. Convert each priority gap into an owned, sequenced, and measurable action.

MAD Skills Drill

Choose a proposed strategy for an organisation.

Step 1: Define the Strategy

State clearly:

what the organisation will do;
who it will serve;
how it will create value;
what will change.

Step 2: Define the Required Organisation

For each of the seven elements, answer what must be true for this strategy to succeed.

Step 3: Assess the Current State

Describe how the organisation operates today. Support the assessment with evidence where possible.

Step 4: Identify the Gaps

Compare the current and required states. For each gap, identify:

what is missing;
why it matters;
which other elements it affects;
the risk if it is not addressed.

Step 5: Prioritise

Select the two or three gaps most likely to prevent execution. Use:

strategic importance;
severity;
interdependence;
difficulty;
risk of inaction.

Step 6: Develop Organisational Actions

For each priority gap, specify:

the action;
owner;
timing;
resources;
affected employees;
support required;
measure of success.

Step 7: Test Change Readiness

Ask:

Is leadership aligned?
Do employees understand the reason for change?
Is sufficient capacity available?
Are the required systems and skills in place?
Where might resistance occur?
Should implementation be phased or piloted?

Step 8: Deliver the Insight

Prepare a 60-second explanation answering:

What does the strategy require from the organisation?
Where is the greatest current misalignment?
Why does that gap threaten execution?
What organisational action should address it?
How will the organisation know the change is working?

Don't explain all seven elements. Focus on the alignment gaps that changed the implementation plan.

Chapter Summary

The McKinsey 7S Framework helps case teams connect strategy to organisational reality. Its seven elements are:

Strategy;
Structure;
Systems;
Shared Values;
Style;
Staff;
Skills.

The framework's value doesn't come from describing each element independently. It comes from understanding whether the elements:

support one another;
support the strategy;
create barriers to execution;
must change for the recommendation to succeed.

A strong 7S analysis follows this progression: Proposed Strategy → Required Organisational Conditions → Current State → Alignment Gaps → Organisational Actions → Execution. A strategically attractive recommendation may fail if:

leadership is not aligned;
structure prevents coordination;
systems reward the wrong behaviour;
values conflict with the change;
staff lack capacity;
skills are missing;
employees are not supported through the transition.

A weak 7S analysis describes the organisation. A strong 7S analysis explains what must change inside the organisation to make the strategy possible.

Key Takeaways

✓ McKinsey 7S evaluates whether an organisation is internally aligned to execute its strategy.

✓ The seven elements are Strategy, Structure, Systems, Shared Values, Style, Staff, and Skills.

✓ Strategy, structure, and systems are often described as hard elements; shared values, style, staff, and skills are soft elements.

✓ Hard and soft elements are equally important to execution.

✓ Organisational alignment means the seven elements reinforce one another and support the strategy.

✓ Don't analyse the elements as seven independent categories. Focus on their connections.

✓ Compare the organisation's current state with the state required by the recommendation.

✓ Prioritise gaps based on strategic importance, severity, interdependence, difficulty, and risk of inaction.

✓ A change to one element often requires changes to several others.

✓ Shared values should be assessed through actual decisions, incentives, behaviour, and resource allocation, not only formal statements.

✓ Leadership support must be demonstrated through visible sponsorship, consistent communication, decisions, resources, and behaviour.

✓ Training is only one part of a people plan. Employees also need clarity, capacity, authority, systems, incentives, communication, and reinforcement.

✓ Organisational readiness may determine whether the strategy should be piloted, phased, delayed, or redesigned.

✓ Convert priority alignment gaps into specific actions with owners, resources, timing, and measures.

✓ McKinsey 7S identifies what must align; change management explains how people will move from the current state to the required state.

✓ In the presentation, focus on the organisational gaps that threaten the recommendation, not on describing all seven elements.

Looking Ahead

McKinsey's 7S framework examines the organisation's internal alignment, but organisations don't operate solely through internal structures, systems, and people. They also depend on relationships with:

customers;
employees;
suppliers;
partners;
governments;
investors;
communities;
regulators;
other affected groups.

The next chapter introduces Stakeholder Analysis, which helps teams identify who can influence the strategy, who will be affected by it, and how those relationships should shape the recommendation and implementation.