There is a point in many transformation journeys when leaders begin to question the strategy.
The priorities appear clear. The destination is compelling. The investment has been approved. Programmes are active. Yet the enterprise is not moving with the coherence, pace or impact that the strategy promised.
At that moment, the natural response is often to revisit the plan: refine the priorities, restate the ambition, commission another diagnostic or apply greater pressure to delivery.
Sometimes that is necessary.
But often, the strategy is not the central problem. The problem is that the enterprise around it was never redesigned to carry it.
The operating model still reflects yesterday's value logic. Structures preserve inherited boundaries. Decisions move through forums built for a slower environment. Capabilities are developed separately from the work they must enable. Transformation programmes sit alongside the organisation instead of changing it. Measures record activity without showing whether the enterprise is becoming more capable of executing the strategy.
That gap is one of the most consequential—and most frequently misdiagnosed—causes of stalled transformation.
Strategy creates a design obligation.
Every material strategy contains an implicit organisational question:
What must the enterprise become for this strategy to be executable?
If the strategy changes where the business will compete, how it will create value, how customers will be served, how technology will be used, how risk will be governed or how work will be performed, it also creates a design obligation.
It may require different accountabilities. New decision rights. Stronger integration across functions. New role families and capabilities. A different workforce shape. Faster governance. New measures. A more explicit relationship between investment, performance and value.
These are not implementation details to be resolved after the strategy has been approved. They are part of the strategy's executable architecture.
PwC's 2026 Global CEO Survey found that organisations moving fastest to reinvent their business and operating models are outperforming less dynamic peers. Yet only one in eight surveyed CEOs reported achieving both revenue growth and cost benefit from AI during the preceding year—the strongest performers were distinguished by the enterprise foundations surrounding the technology.
View the source ↗Deloitte's 2026 Global Human Capital Trends describes a shift from static talent allocation towards orchestration of people, skills, data and technology around outcomes, while traditional functions, change mechanisms and learning models are often too slow or siloed for the environment they support.
View the source ↗A strategic investment does not become an enterprise outcome until the organisation around it is capable of absorbing, coordinating and scaling it.
A broader definition of readiness
Information is not the same as carrying capacity.
“Readiness” is frequently treated as a downstream change-management question: do people understand the strategy, has it been communicated, has training been completed and is the business ready to go live?
These questions matter, but they are not enough. An organisation can be well informed and still be structurally unable to execute. People may understand the destination while remaining trapped inside conflicting accountabilities, duplicated work, slow decisions, fragmented incentives and roles designed for a different model.
Readiness is also a matter of enterprise carrying capacity: whether the operating model, organisation, governance, workforce, capability, execution and value systems can carry the strategic load being placed upon them.
The leadership implication is clear: the organisation cannot be treated as the passive recipient of strategy. It is one of the primary instruments through which strategy succeeds or fails.
03 / Diagnose the gap
Five signs the organisation cannot yet carry the strategy.
The symptoms often look operational. The underlying problem is architectural.
The operating model still reflects the previous value logic
The strategy calls for integrated journeys, platforms or enterprise performance while the organisation continues to optimise individual functions, products, regions or business units.
The issue is not necessarily poor performance. It is misaligned performance.Accountability exists, but work falls between the accountabilities
Ownership is clear within functions, but the interfaces through which decisions, work and value must move have not been designed around enterprise outcomes.
Repeated escalation, duplicated analysis and slow decisions become structural symptoms.A capability problem is being solved without changing the system
New skills are introduced while the roles, work, incentives, governance and decision environment remain designed to reproduce old behaviour.
Learning succeeds as an intervention but struggles to change enterprise performance.Transformation has become a parallel organisation
The programme has its own governance, reporting and language while the operating system of the enterprise remains largely intact.
Programme progress becomes possible without equivalent organisational movement.The business case was approved, but the value system was never built
Milestones and expenditure remain visible, while the connection between organisational change, customer response, financial performance and enterprise value becomes difficult to govern.
Leadership cannot see clearly what to accelerate, stop, redesign or fund next.04 / The enterprise carrying system
Connect the architecture as one system.
Closing the gap requires more than an organisational chart or a new programme plan. No one element can carry the transformation alone. The power lies in their integration.
Strategic intent
Define what must become structurally true—not only what the enterprise wants to achieve. Make explicit the outcomes, value pools, customer experiences, risk positions and capabilities the strategy requires.
Operating model
Translate intent into the system of value creation, authority, integration, information and work. Determine what must be standardised, connected, federated or locally owned.
Organisation and workforce
Design structures, roles, capacity and interfaces around the work of the future state. The objective is not to move boxes, but to make the operating model function in practice.
Governance and performance
Build the decision rights, forums, measures and management information that reinforce the model—so the new strategy is not managed through old governance.
Capability and adoption
Connect skills and behaviour to roles, leadership expectations, work practices, communities, tools and the transition journey—not to a separate intervention.
Execution and value
Create one governed journey from design through mobilisation, transition, adoption and value realisation. Show whether carrying capacity is increasing and what value it produces.
Strategic intent defines what must become true. The operating model translates it into work. Organisation, governance and capability make that work executable. Execution and value connect the future state to measurable enterprise outcomes.
05 / Follow the evidence
When the mandate is too small for the system behind the problem.
Disciplined reframing is not uncontrolled scope expansion. It is the decision to solve the organisational system required for an intervention to perform.
The original brief was too small for the problem the evidence revealed.
The mandate began with a structured learning intervention to develop future-fit marketers. The diagnostic showed that learning was only part of the problem: the federated function carried duplicated activity, inconsistent practices and uneven alignment to the enterprise brand and customer strategy.
New capability could not make the function future-fit while the organisational system around it remained unchanged. The mandate therefore had to connect the operating model, organisation, workforce, capability, execution and value architecture as one transformation journey.
Leadership followed the evidence to the system behind the problem.Major financial-services group
A capability brief became an end-to-end function transformation.
The original mandate focused on future-fit marketers through a structured learning intervention. The diagnostic revealed duplicated activity, inconsistent practices and uneven alignment across a federated function. Learning alone could not solve the system behind the capability problem. GC connected the target operating model, 59 architected roles, workforce transition, a multi-level capability ecosystem, five enterprise programmes and a finance-grade Return on Marketing Investment architecture. Client reporting recorded material cost avoidance and improved advertising effectiveness across the wider journey.
- 59 roles architected
- 5 enterprise programmes
- Multi-year journey
Supporting evidence
Different briefs. The same strategic elevation.
One mandate required an operating model to become an activated organisation. The other required role standardisation to become a system capable of sustaining a future-fit global function.
Leading African bank
A conceptual Risk model became an activated organisation.
The conceptual operating model was already defined. The challenge was turning it into an activated organisation across a 666-position future state. GC connected structure, roles, workforce processes, governance, performance, learning and adoption, while a re-engineered delivery approach recovered 93 days and enabled the programme to land on time and on target.
- 666-position future state
- 93 days recovered
- On time · On target
Global industrial technology group
Role standardisation became a global capability architecture.
A request to standardise global Data roles revealed the need for more than common titles. The mandate became a multidimensional architecture aligned to international professional standards and the enterprise's Human Capital frameworks—connecting roles, technical and behavioural capability, proficiency, career movement and integrated structures.
- Global architecture
- SFIA-aligned
- Multi-country collaboration
The strategic elevationSolve the organisational system required for the intervention to perform—not only the intervention contained in the original brief.
06 / Questions for the executive team
Before restating the strategy or adding more delivery pressure.
The answers reveal whether the enterprise is truly ready—or simply informed about what is coming.
- 01
What must the enterprise be able to do differently for this strategy to succeed?
- 02
Where does the current operating model structurally resist that requirement?
- 03
Which outcomes depend on work crossing functional, regional or business-unit boundaries?
- 04
Are accountability and decision rights designed around those outcomes?
- 05
Do current roles, capacity and capabilities reflect the future work—or the inherited organisation?
- 06
Is adoption designed into the transformation architecture, or treated as support for it?
- 07
Can leadership see how organisational change connects to customer, financial and enterprise value?
- 08
If the programme ended tomorrow, would the business possess the system and capability to continue?
Has the enterprise been designed to make the strategy real?
A sound strategy deserves more than communication, programme activity and executive sponsorship.
It means treating operating model, organisation, governance, workforce, capability, execution and value as one connected transformation architecture. It means resisting the temptation to force a narrow intervention through a system that cannot sustain it. And it means staying with the work long enough for the design to become operational reality—while building the client's ability to continue without dependence.
The question is not only: Is the strategy right?It is also: has the enterprise been designed to make it real?
Discuss the operating-model gap
If the organisation must become structurally different, let's connect the architecture.
GC helps leadership connect operating model, organisation, workforce, capability, execution and value into one executable architecture.
Start a transformation conversation