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

“A strategy is only as strong as the organisation’s ability to execute it.”

Learning Objectives

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

• explain the purpose of the McKinsey 7S framework

• identify and explain the seven organisational elements thatof influencethe performance;model

• distinguish between the hard and soft elements of organisational alignment;alignment

• understand how the seven elements interact

• identify inconsistenciesmisalignment amongbetween strategy, structure, systems, values, leadership, staff,strategy and skills;organisational design

• evaluate whether

  diagnose anorganisational organisation is preparedbarriers to implementexecution

• use McKinsey 7S to evaluate a proposed strategy;strategic change

• compare

  connect organisational alignment to implementation

• identify which organisational elements must change to support a recommendation

• use the organisation'sframework currentto statedevelop withmore 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 managementrealistic and implementationimplementable planning;
strategies
• develop recommendations that are strategically sound and organisationally feasible.

---

Why This Matters

A case team can develop an excellent strategy.

AThe strategymarket canopportunity may 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:attractive.

The

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

A strategyanalysis may fail because:

• employees lack the required skills;
• leadership doesn't support the change;
recommendation.
• departments

  The organisation may even have conflicting priorities;

• incentives encourage the wrongnecessary 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.

resources.

TheseAnd are not minor implementation details. They determine whetheryet the strategy can becomestill reality.fail.

Why?

Because strategy and execution are not the same thing.

An organisation may lack:

• the right structure

• the necessary skills

• appropriate systems

• leadership support

• employee commitment

• aligned incentives

• shared values

A recommendation that ignores these issues may look attractive on a slide but collapse when the organisation tries to implement it.

The McKinsey 7S Frameworkframework helps teamscase solvers examine whether the organisation is internally aligned to execute its strategy. Its seven elements are:strategy.

The

• Strategy;
central
• Structure;
question
• Systems;
is:
• Shared Values;
• Style;
• Staff;
• Skills.

The“What purposemust isbe notaligned inside the organisation for this strategy to find seven separate problems. It is to understand whether the seven elements support one another and support the strategy.work?”

---

Discover Your MAD Skills Principle

ADon't just ask whether the strategy thatis doesn'tright. fitAsk whether the organisation willis strugglebuilt to becomemake reality.it happen.

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 7SThis is anone 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 areof the most important alignmentdistinctions gaps?between strategy formulation and strategy execution.

  A strategy may require:

  • new capabilities

  • Which implementation

    different barriersreporting relationships

  • new technology

  • different incentives

  • new leadership behaviours

  • employee training

  • different decision-making processes

  If those changes 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?
• Doesignored, the recommendation fitmay be strategically sound but operationally unrealistic.

  That is why strong case solutions connect:

  Strategy → Organisation → Execution

  ---

  What Is the organisation'sMcKinsey values7S Framework?

  The McKinsey 7S framework examines seven interconnected organisational elements:

  1. Strategy

  2. Structure

  3. Systems

  4. Shared Values

  5. Style

  6. Staff

  7. Skills

  The framework is commonly divided into two groups.

  Hard Elements

  These are generally easier to identify and Culture?change:

  • Strategy

  • Structure

  • Systems

  Soft Elements

  These are more behavioural and organisational:

  • Shared Values

  • Style

  • Staff

  • Skills

  McKinseyThe 7S may add less value when the case contains no meaningful organisational question. If the decisiondistinction is auseful, narrowbut pricingdon't adjustmentinterpret or"soft" short-termas financial calculation, a full 7S analysis may be unnecessary. The case determines the tool.unimportant.

  UnderstandingIn Organisationalmany Alignment

  implementation

  Alignment exists whenchallenges, 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 equallythe important.hardest—and Changingmost animportant—to organisationalchange.

  chart

  ---

  The Central Idea: Alignment

  The 7S framework is relativelynot straightforward.simply Changingseven theseparate behaviour,questions.

  trust,

  Its skills,real andpurpose informalis relationshipsto behindexamine thealignment.

  chart

  For example:

  A company may takeadopt mucha longer.strategy based on innovation.

  1.But Strategyif:

  • Strategyits definesstructure whatis highly centralized

  • its systems reward risk avoidance

  • its leaders punish failure

  • employees lack innovation skills

  • hiring focuses on operational efficiency

  then the organisation is tryingnot toaligned accomplishwith andits how it intends to create value or advantage. It includes choices about:strategy.

  The

  • customers;
  problem
  • markets;
  isn't
  • products and services;
  • competitive position;
  • growth;
  • capabilities;
  • resource allocation;
  • priorities;
  • whatnecessarily the organisation will not do.
  strategy.

  QuestionsThe to Ask

  • Whatproblem is the organisationsystem 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 whysurrounding the strategy.
    matters?

  ---

  • Do

    1. departmentsStrategy

    interpret

    Strategy the strategy consistently?

  • Is the strategy realistic givenrepresents the organisation's capabilities?plan for achieving its objectives and creating competitive advantage.

    It answers questions such as:

    • Where will we compete?

    • How will we compete?

    • Which customers will we target?

    • What mustvalue thewill organisationwe stopprovide?

      doing?

    • What capabilities will we build?

    • How will we create an advantage?

    When using 7S, don't simply restate the case's strategy.

    Ask:

    WarningWhat Signsorganisational changes does this strategy require?

    For example, a strategy of rapid digital expansion may require:

    • too many

      technology competinginvestment

      priorities;
    • vague strategic

      new language;skills

    • inconsistent interpretations;

      different customer processes

    • resources spread

      faster acrossdecision-making

      too many initiatives;
    • departments pursuing

      new conflictingperformance goals;

    measures
    • no clear customer or competitive focus;
    • a recommendation disconnected from organisational capability.

    AThe strategy cannotis guide execution if employees don't understandtherefore the choicesstarting itpoint requires.for the alignment analysis.

    ---

    2. Structure

    Structure explainsdescribes how responsibilities, authority, reporting relationships, and coordinationdecision-making are organised.organized.

    It may involve:

    Consider:

    • functions;

      organizational hierarchy

    • business units;

      reporting relationships

    • geographic divisions;

      departments

    • product groups;

      business units

    • project teams;

      geographic divisions

    • reporting lines;

      centralized vs. decentralized decision-making

    • centralisation;
    • decentralisation;

    cross-functional

    • decisionteams
      rights;
    • spans of control;
    • formal and informal coordination.

    QuestionsStructure can either enable or constrain strategy.

    Example

    Suppose an organisation wants to Askprovide an integrated customer experience.

    But sales, marketing, service, and product teams operate independently with separate goals.

    The structure may make the strategy difficult to execute.

    The strategic solution may therefore require:

    • Who is

      cross-functional responsibleteams

      for

    • revised reporting relationships

    • shared objectives

    • centralized customer information

    Key Question

    Does the strategy?

  • Who makes the important decisions?
  • Are decision rights clear?
  • Does theorganisation's structure support collaboration?
  the
  • Are teams organised around functions, customers, products, strategy—or geography?
  get
  • Arein thereits 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 Signsway?

  • 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 formalprocesses and informal processesroutines through which workthe isorganisation performed,operates.

  decisions are made, information is shared, and performance is managed.

  They may include:

  • planning;

    budgeting

  • budgeting;

    performance measurement

  • technology;

    information systems

  • communication;

    customer relationship management

  • hiring;

    inventory systems

  • training;

    hiring processes

  • performance management;

    reporting systems

  • incentives;

    quality control

  • data collection;

    planning processes

  • reporting;
  • approvals;

  decision-making

  • qualityroutines
    control;
  • customer feedback;
  • project management;
  • risk management.

  QuestionsSystems toare Ask

  often
  invisible
  • Whichin systemsa supportcase because they are embedded in how the currentorganisation wayworks.
    of

    But working?

  they
  • Whichcan systemshave wouldenormous influence on execution.

    Example

    A company says innovation is a priority.

    But its approval process requires six management levels before an idea can be tested.

    The problem may not be employee creativity.

    The problem may be the proposedsystem.

    strategy

    Key require?

  Question
  • Can

    Do the technologyorganisation's support the change?

  • Are data accurate, accessible, and timely?
  • Do performance measuressystems reinforce the strategy?
  behaviours
  • Dorequired incentives encourageby 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 Signsstrategy?

  • 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 Frameworkframework.

  because

  They they influence allrepresent the otherbeliefs, elements.principles, Sharedand valuespriorities maythat concern:shape how the organisation behaves.

  Examples might include:

  • customers;

    customer focus

  • quality;

    innovation

  • ethics;

    safety

  • innovation;

    sustainability

  • collaboration;

    quality

  • risk;

    teamwork

  • inclusion;

    entrepreneurship

  • sustainability;
  • performance;

  operational

  • accountability;
  excellence
  • learning;
  • employee wellbeing.

  Shared values influence decisions even when they are not merely the statements written oninto theformal organisation'spolicies.

  website.

  The realCritical Test

  Don't confuse stated values ofwith anactual values.

  An organisation aremay revealed through:say:

  what

  “We leadersput paycustomers attentionfirst.”

  to;

  • which

    But behaviours are rewarded;

  • which behaviours are tolerated;
  • how difficult decisions are made;
  • howif employees are treated;
  rewarded
  • howalmost customersentirely areon treated;
  short-term
  • howsales failurevolume, isthe handled;
  organisation
  • wheremay resourcesactually arebe allocated.
  communicating:

  Questions“Hit toyour Asksales target.”

• The case solver should therefore look for evidence of values in behaviour.

  Key Question

  What does the organisation claimactually reward, tolerate, and prioritize?

  ---

  5. Style

  Style refers to value?leadership behaviour and the way management operates.

  It includes:

  • leadership approach

  • What behaviour

    communication isstyle

    actually rewarded?
  • What happens

    decision-making whenbehaviour

    values conflict with short-term performance?
  • Does the

    tolerance proposedfor strategyrisk

    fit the Culture?
  • What assumptions

    openness shapeto decision-making?ideas

  • How does

    collaboration

    the organisation respond to risk and failure?
  • Do employees

    degree trustof leadership?control

  • What behaviours

    visibility wouldof needleaders

    to change?
  • Which existing values could support the transformation?
  • Which cultural norms could resist it?

  WarningLeadership Signsstyle can strongly influence implementation.

  Consider two organisations pursuing the same innovation strategy.

  One leadership team:

  • stated values

    encourages contradictedexperimentation

    by incentives;
  • low trust;

    accepts reasonable failure

  • blame-oriented behaviour;

  empowers

  • resistanceemployees
    to information sharing;
  • short-term results prioritised over customer or employee outcomes;
  • avoidance of difficult conversations;
  • change fatigue;
  • leadership behaviour inconsistent with organisational messages.

  CultureThe 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:other:

  • leadership approach;

    requires extensive approval

  • communication;

    avoids risk

  • decision-making;
  • delegation;

  punishes

  • accountability;
  failed
  • visibility;
  experiments
  • risk tolerance;
  • conflict management;
  • feedback;
  • the behaviours leaders model.

  StyleThe same strategy may be:produce very different results.

  Key

  directive;

  Question

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

  No singleDoes leadership stylebehaviour 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 modelreinforce 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 Signsstrategy?

• 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 concernsrefers to the people within the organisationorganisation.

and how the workforce is recruited, deployed, supported, developed, and retained. It

This includes:

• workforce size;composition

• workforce composition;

  talent

• roles;

  recruitment

• recruitment;

  retention

• retention;

  succession

• succession;

  staffing levels

• engagement;

  employee experience

• workload;
• deployment;

workforce

• diversity;
planning
• career development;
• employee experience.

QuestionsA tostrategy Askmay require capabilities that the organisation does not currently possess.

For example:

A company moving aggressively into data analytics may need:

• data scientists

• analysts

• technology specialists

• managers who can interpret data

If those people are unavailable internally, the organisation may need to:

• hire

• train

• acquire

• partner

Staff therefore connects directly to implementation planning.

Key Question

Do we have the people required to execute the strategy?

---

7. Skills

Skills refer to the organisation's distinctive capabilities.

This is broader than asking whether individual employees possess certain abilities.

The question is:

What is the organisation particularly good at?

Examples include:

• product innovation

• logistics

• customer service

• data analytics

• manufacturing

• relationship management

• project management

• brand building

• acquisitions

This is where McKinsey 7S connects directly to VRIO.

VRIO asks:

Can this capability create a competitive advantage?

7S asks:

Does the organisation have enough people?

Are employees in the rightskills roles?

Which roles are criticalrequired to execute the strategy?

Those are related—but different—questions.

---

The Seven Elements Are workloadsConnected

sustainable?

The

Arepower keyof positions7S difficultcomes from the relationships between the elements.

Consider a company pursuing a strategy of digital transformation.

Strategy

Increase digital sales and customer engagement.

Structure

Create a cross-functional digital business unit.

Systems

Implement customer data and digital analytics systems.

Shared Values

Increase emphasis on experimentation and customer experience.

Style

Leaders empower teams to fill?

make

Wherefaster decisions.

Staff

Hire digital specialists.

Skills

Develop data analytics, digital marketing, and technology capabilities.

The strategy is turnoversupported highest?

by

Arechanges employees engaged?

Doesthroughout the workforceorganisation.

reflect

Now imagine changing only the customersstrategy.

and

The communitiesorganisation served?

says:

“We are becoming a digital-first company.”

But everything else remains unchanged.

That is strategic misalignment.

---

The Alignment Test

For each element, ask:

What new roles willdoes the strategy require?

Then ask:

Does the organisation currently have it?

This produces a simple diagnostic:

7S Element	Strategy Requires	Current State	Gap
Strategy	Digital growth	Digital growth identified	Low
Structure	Cross-functional teams	Functional silos	High
Systems	Real-time customer data	Legacy systems	High
Shared Values	Experimentation	Risk avoidance	High
Style	Empowerment	Centralized control	High
Staff	Digital talent	Limited	High
Skills	Data analytics	Moderate	Medium

The purpose of the table is not to score the organisation.

It is to identify where implementation is likely to break down.

---

The Misalignment Test

Look for contradictions between the seven elements.

Strategy vs. Structure

The strategy requires speed.

The structure requires multiple layers of approval.

Misalignment.

Strategy vs. Systems

The strategy requires customer responsiveness.

The systems provide information only once per month.

Misalignment.

Strategy vs. Skills

The strategy requires advanced analytics.

The organisation lacks analytical capabilities.

Misalignment.

Strategy vs. Style

The strategy requires experimentation.

Leadership avoids risk.

Misalignment.

Strategy vs. Shared Values

The strategy requires collaboration.

The culture rewards individual performance.

Misalignment.

These contradictions often reveal the real implementation problem.

---

Deciphering Case Characteristics

McKinsey 7S becomes particularly useful when the case includes:

• implementation challenges

• Can existing

  organisational employeeschange

  transition into those roles?
• What recruitment

  restructuring

  or
retention
• risks

  mergers exist?and acquisitions

• digital transformation

• rapid growth

• culture problems

• leadership changes

• declining employee engagement

• new strategic direction

• capability gaps

• organizational resistance

• failed execution

WarningWatch Signsfor language such as:

• chronic understaffing;

  “The strategy isn't working.”

• high turnover;

  “Employees are resistant.”

• unclear roles;

  “The organisation is struggling to change.”

• excessive dependence

  “Departments onoperate ain fewsilos.”

  individuals;
• change added

  “Decision-making tois alreadyslow.”

  overloaded employees;
• weak succession;

  “The company needs new capabilities.”

• critical hiring

  “The delays;

merger
• employeehas groupsnot excludeddelivered fromexpected planning;
results.”
• insufficient support during implementation.

"Staff"These isare signals that the problem may be organisational alignment, not simply strategic direction.

---

McKinsey 7S and Change

One of the most useful applications of the framework is evaluating a headcountmajor question.change.

It

Imagine concernsa company moving from:

Product-Focused → Customer-Focused

That change may require:

Strategy

Compete through customer experience.

Structure

Create customer-focused teams.

Systems

Introduce customer metrics and feedback systems.

Shared Values

Make customer outcomes central.

Style

Leaders model customer-first behaviour.

Staff

Recruit people with customer experience skills.

Skills

Build customer analytics and relationship-management capabilities.

The change becomes much more realistic when all seven elements are considered.

---

McKinsey 7S and Mergers

Mergers are another strong application.

Two organisations may have:

• different cultures

• different systems

• different structures

• different leadership styles

• different skills

• different compensation models

The financial logic of the merger may be attractive.

But the organisations still need to become operationally aligned.

The 7S framework can help identify where integration problems may arise.

For example:

Company A: decentralized and entrepreneurial

Company B: centralized and process-driven

The merger may create tension around:

• decision rights

• reporting

• risk tolerance

• performance measures

• leadership style

• employee expectations

These are not simply "culture issues."

They can directly affect execution.

---

From 7S Analysis to Implementation

The biggest value of 7S in a case competition is its connection to implementation.

Suppose your recommendation is:

“Launch a new digital service.”

A weak implementation plan might say:

1. Develop the service.

2. Launch it.

3. Market it.

4. Measure results.

A stronger implementation plan asks what organisational changes are required.

Strategy

Clarify the digital growth strategy.

Structure

Create ownership for the new service.

Systems

Build the required technology and reporting systems.

Shared Values

Communicate the importance of experimentation and customer experience.

Style

Empower leaders and teams to make faster decisions.

Staff

Recruit or assign required talent.

Skills

Train employees in digital tools and customer analytics.

Now the recommendation is much more implementable.

---

The 7S Capability Gap

A useful way to apply the framework is to identify capability gaps.

Ask:

What must the organisation be able to do that it cannot currently do?

Then determine which 7S element is causing the gap.

For example:

Cannot respond quickly to customers

→ Structure too centralized

Cannot make data-driven decisions

→ Systems and skills gap

Cannot innovate quickly

→ Style and shared-values gap

Cannot enter a new market

→ Staff and skills gap

This creates a direct path from diagnosis to action.

---

Connecting 7S to the Other Frameworks

7S + VRIO

VRIO identifies strategically valuable capabilities.

7S asks whether the organisation is aligned to deploy those capabilities.

VRIO: What can we do uniquely well?

7S: Are we organised to do it?

---

7S + Value Chain

Value Chain identifies activities that create or destroy value.

7S helps determine whether the organisation has the rightstructure, people,systems, instaff, and skills to improve those activities.

Value Chain: Where is the rightproblem?

roles,

7S: withWhat organisational changes are required to fix it?

---

7S + Business Model Canvas

The Business Model Canvas explains how the capacityorganisation creates, delivers, and supportcaptures value.

7S examines whether the organisation can execute that model.

Business Model Canvas: How does the business work?

7S: Is the organisation aligned to execute.make it work?

---

7S + SWOT

SWOT may identify an internal weakness such as:

“Limited digital capabilities.”

7S helps diagnose that weakness.

7. Skills

Skills areIs the capabilitiesproblem:

and

areas
• of

  Staff?

  expertise

• Skills?

• Systems?

• Structure?

• Style?

The framework turns a broad SWOT observation into a more actionable diagnosis.

---

A Simple 7S Diagnostic

When time is limited, use this sequence:

1. What is the strategy?

What is the organisation trying to accomplish?

2. What must change?

What does successful execution require?

3. Where is the organisation misaligned?

Which of the organisationseven elements creates the biggest obstacle?

4. What must be changed?

Identify the specific organisational intervention.

5. How will we know?

Define the implementation measure.

This gives you:

Strategy → Requirement → Misalignment → Intervention → Measure

---

Worked Example: A Retailer Going Digital

Imagine a traditional retailer decides to compete through a stronger digital customer experience.

Strategy

Develop an integrated online and itsphysical people.shopping Theyexperience.

Structure

Current structure is organized primarily around individual stores.

Potential issue: Digital and physical teams may include:operate independently.

Systems

Current customer data is fragmented.

Potential issue: The organisation cannot see the complete customer journey.

Shared Values

The organisation historically emphasizes store performance.

Potential issue: Employees may view online sales as competing with store sales.

Style

Managers have traditionally operated with centralized decision-making.

Potential issue: Digital teams may lack the speed required to experiment.

Staff

Strong retail expertise but limited digital expertise.

Potential issue: Talent gap.

Skills

Strong merchandising and store operations.

Limited:

• technical skills;

  digital analytics

• analytical skills;

  e-commerce

• customer-service capability;

customer

• salesdata capability;
management
• 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 organisationanalysis dotell 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?

us?

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 ansimply:

absence

of

“The innovativecompany ideas.needs a better website.”

The organisation ismay notrequire aligneda tobroader supporttransformation.

innovation.

Possible Aactions stronger recommendation would address:include:

• decision rights;

  establish cross-functional digital teams

• innovation funding;

  redesign incentives so online and store channels share customer objectives

• pilot criteria;

  integrate customer data

• leadership behaviour;

  recruit digital talent

• employee capacity;

  develop analytics capabilities

• empower faster experimentation

  skills;
• learning systems.

  align leadership messaging around an integrated customer experience

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?

A complete recommendation needs both. For each important alignment gap, determine:

• 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   sponsor;

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:

• an executive sponsor;
• a dedicated pilot leader;
• a cross-functional launch team;
• clear partner-management responsibilities;
• defined decision rights.

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:

1. no accountable cross-functional pilot structure;
2. fragmented systems and performance measures;
3. 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-entrytechnology recommendation into an organisationallyorganisational credibleexecution implementation plan.strategy.

McKinsey

---

7S Is Not

Winning the Recommendation.Room

Do not walk judges through:

CompletingStrategy. aStructure. 7SSystems. analysisShared doesn'tValues. determineStyle. theStaff. organisation's strategy. A complete process is:Skills.

define

Instead, thetell proposed strategy;

determinethem 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.revealed.

MeasuringFor Organisational Changeexample:

“The organisationretailer's 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 thedigital 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 equippeddesigned to execute it. Three gaps matter most: fragmented customer data, store-based incentives that discourage channel integration, and limited digital analytics capabilities. We therefore recommend building a cross-functional digital team, integrating customer data, and aligning performance measures before scaling the digital strategy.”

That is strategic communication.

FocusThe onframework supports the Critical Gapsdiagnosis.

InsteadIt does not become the presentation.

---

Coach's Lens

“If your recommendation requires the organisation to behave differently, tell me exactly what has to change.”

A strong case solver understands that implementation is not simply a timeline.

It is an organisational change problem.

Whenever your recommendation requires:

• new behaviour

• new capabilities

• new technology

• new decision-making

• new incentives

• new leadership behaviours

ask:

Which of explainingthe all7S elements must change?

---

Common Mistakes

1. Treating 7S as seven elementsindependent equally,boxes

identify

The value is in the tworelationships orbetween threethe misalignmentselements.

2. Describing the current organisation without identifying gaps

The purpose is diagnosis.

3. Treating culture as the answer to everything

"Culture" is often used as a vague explanation.

Be specific.

Is the problem:

• leadership behaviour?

• incentives?

• systems?

• structure?

• skills?

• staffing?

4. Ignoring the hard elements

Culture matters, but so do systems, structure, and processes.

5. Ignoring the soft elements

Changing structure and systems without addressing behaviour and values can also undermine implementation.

6. Assuming the organisation can change everything

Implementation requires prioritisation.

Identify the few changes that matter most:most.

7.

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 GapFailing 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 McKinseyconnect 7S to identifythe sevenrecommendation unrelated

The problems.framework Useshould itinfluence what you recommend and how you implement it.

8. Treating the framework as a scorecard

The objective is not to decide that the organisation has "7/10 alignment."

The objective is to identify alignmentspecific organisational gaps and actions.

If

---

your

MAD strategySkills requiresDrill

The Strategy-to-Execution Alignment Test

Take a highlystrategic innovativerecommendation from a case.

Step 1 — State the Strategy

Complete:

“The organisation but:should…”

leadership

Step is2 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,

thenIdentify the strategyRequirements and organisation are misaligned. The solution is not an "innovation workshop." The recommendation

What must address the organisational conditions preventing innovation. I often ask teams what must be true inside the organisation forbe this strategyable to work,do then which of those conditions doesn't exist today. Those two questions turn strategy into implementation.differently?

CommonIdentify Mistakesat least three requirements.

·

Step 3 Treating— Test the Seven Elements

as

For Independent.each Therequirement, elements influence and reinforce one another. Explain the most important connections and misalignments.consider:

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

• ·        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.Structure

• ·Systems

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

• ·Style

  Recommending
Restructuring
• Too

  Staff

  Quickly:
Changing
• reporting

  Skills

  lines
doesn't

automatically

Step solve4 coordination, capability, trust, or leadership problems.— Identify the rootThree causeBiggest ofGaps

misalignment

Do beforenot changingidentify the structure.everything.

·        Using Training asChoose 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:

Step

strategic5 importance;

—

severity;

Design

interdependence;

the

difficulty;

risk of inaction.

Interventions

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 Readinessidentify:

Ask:

What

must
• Ischange?
  Who leadership aligned?
• Do employees understandowns 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:

1. 
   What doesresources theare strategy require from the organisation?
2. Where is the greatest current misalignment?
3. Why does that gap threaten execution?
4. What organisational action should address it?
5. required?
   How will thesuccess organisationbe knowmeasured?

   Step 6 — Build the changeExecution is working?

Story

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

Chapter Summary

The McKinsey 7S Framework helps case teams connect“Our 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 insiderequires the organisation to make______. Today, the strategybiggest possible.barriers are ______. We will address these by ______, which will enable ______.”

Step 7 — Deliver It

Present the diagnosis and implementation plan in 90 seconds.

KeyNo Takeawaysseven-box tour.

✓No framework definition.

Focus on:

Strategy → Misalignment → Change → Execution

---

Chapter Summary

The McKinsey 7S evaluatesframework helps case solvers understand whether an organisation is internally aligned to execute its strategy.

✓ The seven elements areare:

Strategy,

Strategy Structure,→ Systems,Structure → Systems → Shared Values,Values Style,→ Staff,Style → Staff → Skills

The framework is most powerful when used to identify misalignment.

A strategy that requires organisational change must consider:

• how the organisation is structured

• how decisions are made

• how systems operate

• what behaviours are rewarded

• how leaders behave

• whether the right people are available

• whether the required capabilities exist

The framework therefore provides an important bridge between strategy and Skills.implementation.

---

Key Takeaways

• ✓ Strategy, structure,Strategy and systemsexecution are oftendifferent describedproblems.

  as
hard
• elements;

  The sharedseven values,elements style,of staff, and skills7S are soft elements.interconnected.

  ✓

Hard and soft elements are equally important to execution.

• ✓Alignment Organisationalmatters alignmentmore meansthan simply identifying the seven elementselements.

  reinforce
one
• another

  Look for contradictions between strategy and supportorganisational reality.

• Distinguish organisational resources from organisational capabilities.

• Identify 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.

  ✓ Prioritisefew gaps basedthat oncould strategicprevent importance, severity, interdependence, difficulty, and risk of inaction.execution.

  ✓

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

• ✓Translate 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 alignmentorganisational gaps into specific actionsimplementation withactions.

  owners,
resources,
• timing,

  Connect 7S to VRIO, Value Chain, Business Model Canvas, and measures.SWOT.

• ✓Avoid McKinseyvague 7Sconclusions identifiessuch as "the culture needs to change."

• Be specific about what must align;change, changewhy, management explainsand how peoplesuccess will movebe frommeasured.

  the
current
• state

  Use 7S to themake requiredrecommendations state.

  more

  ✓ 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,realistic and people. They also depend on relationships with:implementable.

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

  ---

  Bottom Line

  A strategy creates potential value. Organisational alignment determines whether that value can actually be realised.

  The strongest case solutions do not stop at:

  “This is what the organisation should do.”

  They continue:

  “This is what the organisation must change to make it happen.”

  That is the difference between a strategy that looks good on paper and one that can actually be executed.

  ---

  Looking Ahead to Chapter 16

  We have now examined:

  Where competitive pressure comes from → Porter
  Where value is created and lost → Value Chain
  What the organisation can uniquely do → VRIO
  How the organisation creates, delivers, and captures value → Business Model Canvas
  Whether the organisation is aligned to execute → McKinsey 7S

  But organisations do not operate in isolation.

  Different groups can affect whether a strategy succeeds—and they may have very different interests, levels of influence, and reactions to change.

  The next chapter introducesexamines Stakeholder Analysis, which— helpsUnderstanding teamsWho identifyCan who can influenceInfluence the strategy, who will be affected by it, and how those relationships should shape the recommendation and implementation.Outcome.