Strategy often weakens as it moves through an organisation. A corporate ambition becomes a business-unit plan, then a functional roadmap and finally a list of initiatives whose connection to the original choice is difficult to see.
Nested strategy offers a way to preserve that connection without pretending every level does the same work. Each part of the organisation makes choices appropriate to its context, inside the direction and constraints established above it. The lower layer also returns evidence that may require the higher strategy to change.
It resembles nested dolls only in structure. In practice, information has to move both ways.
What is nested
At corporate level, leaders decide where the organisation will play, how it intends to create value and which constraints or capabilities matter across the whole enterprise.
A business unit interprets those choices for its market, clients, competitors and economics. It does not merely repeat the corporate language. It decides which problems, propositions and capabilities deserve focus locally.
A function such as operations, marketing, technology, people or finance then sets choices that enable one or more business strategies. Teams translate those choices into outcomes, policies, services and work.
Every layer should be able to answer:
- What outcome are we responsible for?
- Which choices have been made and which options rejected?
- What constraints come from the level above?
- Where do we have authority to adapt?
- Which other teams do we depend on?
- What evidence would cause us or the parent strategy to change?
This is more demanding than cascading goals. A target can be handed down. A strategy requires choices and a coherent response to local conditions.
Why it can help
Nested strategy creates traceability. A team can explain how current work supports a unit and corporate outcome. An initiative with no meaningful connection becomes visible and can be challenged.
It also improves resource conversations. Competing requests can be compared against choices already made, rather than being decided by the most senior advocate or the most polished business case.
Coordination improves when sibling strategies expose dependencies and conflicts. Marketing may aim to increase qualified demand while operations is constrained in onboarding capacity. Technology may seek platform consolidation while a business unit requires regulatory separation. The nested view forces the trade-off into the open.
The softer value is participation. People can see the purpose of their decisions and provide evidence from delivery. That can create stronger ownership than a central strategy presented as a finished document.
None of this guarantees execution. Structure is useful only when leaders are willing to stop incoherent work and revise a strategy that evidence contradicts.
Avoid turning it into a hierarchy of instructions
If the board makes every meaningful choice and lower levels only receive tasks, the organisation has a cascade rather than nested strategy. Local leaders need defined authority over choices within their context.
Set decision boundaries. Corporate leaders may reserve risk appetite, capital allocation and market entry. A unit may own service positioning and channel priorities. A function may choose how to build a capability within architecture, policy and budget constraints.
Escalation should be available when local evidence reveals an impossible constraint or conflict. The purpose is not permission-seeking for every adjustment; it is to protect choices with enterprise consequences.
Avoid assigning the same outcome to everybody. Shared contribution is real, though one person or forum still needs accountability for integration and trade-offs.
Start with choices, not a diagram
Write the corporate strategy in a form that a unit can use. It should state the problem or opportunity, chosen direction, sources of advantage, critical capabilities, constraints and measures. A long vision document with no exclusions gives lower layers nothing to interpret.
At each level, run a translation conversation:
- What does the parent choice mean in our context?
- Which local evidence matters?
- What will we prioritise and decline?
- Which capabilities and behaviours must change?
- What do we need from sibling teams?
- Which measures show progress and guard against harm?
- When will we review the choice?
Capture decisions and assumptions, not only objectives. A unit that chooses one client segment should record the opportunity it is giving up and the evidence behind that focus.
Resolve conflicts between siblings
Nested strategies will not align automatically. Two units may compete for the same specialists. A shared platform may satisfy one journey and constrain another. Local optimisation can undermine an enterprise outcome.
Create a portfolio forum with authority to resolve cross-unit trade-offs. Bring options, resource implications and outcome evidence. Avoid forcing every difference into a common score when legal duty, service criticality or strategic option value requires judgement.
Make shared enablers explicit. Data, identity, content, brand and integration may serve several strategies. Give each an owner and funding model so it does not become everybody’s dependency and nobody’s responsibility.
The six Critical Pillars can help Distinction clients examine whether choices across strategy, experience, content, technology, data and operation form a coherent system. They should not be used to fill every box with an initiative.
Use measures to support learning
Each layer needs measures appropriate to its decisions. Corporate outcomes may include sustainable growth, margin, risk or client value. A unit needs more specific market and service evidence. A function needs operational measures and leading indicators.
Link them through a benefit chain without claiming that one functional metric caused the enterprise result. Content quality may contribute to qualified demand; it is not revenue by itself.
Set review points and thresholds for investigation. Evidence should travel upward. If several units cannot execute because a corporate constraint is unrealistic, the corporate strategy may need revision.
Do not use targets to suppress inconvenient local knowledge. A green dashboard can coexist with growing workarounds, client friction or capability loss.
Know when the model is a poor fit
A very small organisation with fluid roles may not need formal layers. A problem-focused strategy and a shared set of choices may be clearer.
An organisation with little delegated authority will produce elaborate documents and few genuine local decisions. Address decision rights before adding nested planning.
A large organisation prone to bureaucracy can turn the model into an annual cascade of templates. Keep the artefacts short, focus on trade-offs and connect strategy review to real allocation and stopping decisions.
The model may also struggle where business units are deliberately autonomous investments with few shared capabilities. Corporate strategy may then concern portfolio ownership rather than operational alignment.
Use the minimum structure that clarifies decisions.
Test whether strategy reaches work
Ask people at several levels to explain the organisation’s important choices, their team’s contribution, what they are declining and which evidence could change the plan. Variation is expected because context differs. Contradiction about purpose, authority or priorities signals a broken connection.
Then inspect the portfolio. Does current spending reflect the stated choices? Are teams measured against outcomes they can influence? Do sibling dependencies have owners? Has anything been stopped because it no longer fits?
Nested strategy is working when local leaders can act without losing the enterprise direction, and senior leaders can learn from delivery without taking every decision back.
Distinction can help review whether strategy, decision rights and active investment connect across the organisation. The useful result may be a nested model, a simpler problem-based approach or a clearer portfolio mechanism. The framework should serve the choices, never become the work itself.
