Culture eats strategy for breakfast. It is true. It is also incomplete. Because something else eats culture. Organisational design. Function follows form. The way an organisation structures reporting lines, decision rights, team boundaries, information flows, incentives and technology governance is not simply an expression of its culture. It is the container that shapes that culture. Change the shape and behaviour changes. Leave the shape untouched and no number of values workshops, town halls or inspirational posters will make much difference.
I have watched organisations struggle to absorb AI, digital transformation and market disruption, not because they lacked technology, talent or ambition, but because their structure made adaptation almost impossible.
Organisational design is strategy
Again and again, the deeper constraint was structural. Decisions were routed upwards instead of towards the people with the best information. Data remained trapped inside functions. Teams were rewarded for protecting budgets rather than sharing capabilities. Signals from customers and markets moved slowly through layers of management before reaching anyone authorised to respond.
The organisational structure was not supporting the strategy. It was overriding it. An organisation does not fail to see change because signals are absent. It fails because its design prevents those signals from travelling, being interpreted and reaching someone with the authority to act. That makes organisational design the machinery of sensemaking.
The old boundaries no longer fit the work
Particulalry, AI exposes the weakness of traditional functional boundaries. Consider the separation between the Chief Technology Officer and the Chief Human Resources Officer. AI changes what work people do, which skills matter, how teams are formed, how knowledge flows, how performance is assessed and how decisions are divided between people and machines.Those are simultaneously technology decisions and people decisions.
Yet most organisations route them through different leaders, different teams, different budgets and different strategies. Without shared ownership, the result is fragmentation. The CHRO manages talent. The CTO manages systems. Nobody owns the intersection where human capability meets machine capability.
That intersection is where the future of the organisation is being built.
From shadow IT to shadow development
The same structural problem is appearing outside the C-suite. Shadow IT once meant employees buying software without approval. It was inconvenient, occasionally risky and usually containable. Shadow development is different. Employees can now use low-code platforms and AI coding tools to build applications, automate workflows and connect systems without waiting for the technology function.
Shared technology creation
The assumption that technology creation belongs exclusively inside a specialist department no longer holds. Tightening control will slow innovation and drive capable people around the system. Removing control entirely will create security, compliance and operational chaos. The answer is not more gatekeeping. It is better guardrails. Technology creation must become a distributed organisational capability supported by shared standards, visibility, skills and accountability. The CIO’s role therefore shifts from hero to architect—from personally controlling technology delivery to designing the conditions in which others can build safely.
Orchestration intelligence
This requires a capability I call orchestration intelligence. Orchestration intelligence is the ability to coordinate human judgement, machine agency, data and decision rights without creating either centralised paralysis or distributed chaos. Modern organisations are becoming complex ensembles of human teams, AI agents, data platforms, automated workflows, suppliers and external partners. Each operates at a different speed, with different information and different levels of autonomy.
Organisational coherence
The leadership task is no longer to control every action. It is to create coherent performance across the system. That means treating organisational design as an information architecture rather than merely a reporting hierarchy. Who needs to know what? How quickly can a market signal reach the team capable of acting? How many handoffs does a decision require? Which approvals improve quality, and which simply add delay? Every unnecessary handoff is a tax on responsiveness. Every silo is a barrier that signals bounce off rather than pass through. Every approval layer maintained for political rather than operational reasons slows the organisation’s ability to sense and respond.
Create the right shape
Leadership teams should ask five uncomfortable questions:
- How quickly does a market signal reach someone who can act on it?
- What happens when one function needs data controlled by another?
- Who owns the intersection between technology and talent?
- How much technology creation is already happening outside the technology function?
- Do incentives reward collaboration—or the protection of functional territory?
Operating system
Organisational design determines what the organisation can notice, who is allowed to interpret it, how quickly a decision can be made and whether action follows. That makes design more than structure. It is the operating system through which strategy, culture, technology, data and talent become organisational behaviour.
Your organisational design may be the most important strategic choice your leadership team makes this decade.
