Structure as a Strategic Choice
Organisational design is not a neutral administrative decision. It determines where decisions are made, how information flows, where accountability sits, and what behaviours the organisation makes easy versus difficult. Leaders who inherit structures without questioning whether they fit their strategy are allowing history to constrain the future.
When Structure Becomes a Growth Constraint
- Decision-making is concentrated at the top, creating bottlenecks as the organization scales
- Functional silos prevent the cross-organizational collaboration that new growth areas require
- Accountability for customer outcomes is fragmented across multiple teams
- Complexity has grown without corresponding increases in coordination capability
- High-potential leaders are leaving because they lack sufficient autonomy and scope
Principles of Growth-Oriented Design
Organisations designed for sustainable growth share common structural characteristics: they push decisions down to the level with the most relevant information, they align accountability with authority, they create clear interfaces between units while allowing genuine autonomy within them, and they build coordination mechanisms that do not require hierarchy to function.
Redesigning Without Losing Momentum
Organizational redesign carries real risk. Done poorly, it creates confusion, erodes trust, and consumes leadership bandwidth that should be directed at growth. Done well, it unlocks capability that was latent in the organization. Leaders who approach redesign with clarity of purpose, transparent communication, genuine stakeholder involvement, and disciplined implementation manage this risk effectively.
Culture and Structure as Partners
Structure and culture are not independent variables. New structures succeed when they are accompanied by the cultural and behavioral changes they require. A decentralized structure without a culture of accountability produces confusion. An accountability culture without the structural authority to match produces frustration. Leaders who align structure and culture—and invest in both simultaneously—build the most scalable organizations.
Common Organisational Design Models
The functional model remains one of the most familiar structural choices, grouping people by discipline — finance, technology, marketing, operations — to build deep expertise and achieve economies of scale within each domain. It works well for organisations with a relatively narrow product range or stable operating environment, but it often struggles when cross-functional collaboration is essential to delivering customer value. The very specialisation that creates efficiency in a functional structure can harden into the silos that constrain growth.
Divisional structures, by contrast, organise around products, geographies, or customer segments, giving each unit end-to-end accountability for its own outcomes. This model trades some resource efficiency for greater responsiveness and clarity of ownership, making it particularly suited to large, diversified organisations operating across distinct markets. Matrix structures attempt to capture the benefits of both approaches by creating dual reporting lines — typically functional and business unit — but they introduce significant coordination overhead and require mature leadership to manage competing accountabilities without dysfunction.
More recent design thinking has moved toward network and team-based models, in which small, cross-functional teams form around specific outcomes and dissolve or reconfigure as priorities shift. Platform organisations take this further, separating enabling shared services from the customer-facing units that consume them, reducing duplication while preserving speed at the edges. No single model is universally superior; the right choice depends on the organisation's strategy, competitive environment, talent model, and appetite for coordination complexity.
Roles and Responsibilities in the Design Process
Effective organisational design is not the exclusive domain of the CEO or a small strategy team. While senior leadership must own the strategic intent and the final decisions, the process itself benefits from structured involvement across multiple levels. HR and people leaders bring critical insight into workforce capability, talent pipelines, and the behavioural implications of structural change. Finance leaders ensure that proposed structures are commercially viable and that resource allocation aligns with the new accountability model.
Line leaders who will operate within the redesigned structure have an essential role that is often underused. Their proximity to operational reality means they can identify where proposed changes will create unworkable hand-offs, duplicate effort, or misalign incentives — problems that are far more expensive to fix after implementation than before. Involving them meaningfully, rather than consulting them superficially, improves both the quality of the design and the pace of adoption when the new structure goes live.
Technology and digital leaders, including CIOs, are increasingly central to organisational design conversations because so many structural decisions now have direct implications for systems, data flows, and automation. A structural change that requires a new operating model for technology delivery, or that creates new data ownership boundaries, needs CIO input at the design stage rather than as an implementation afterthought. Clarifying who holds decision rights, who provides input, and who is simply informed at each stage of the design process prevents the governance confusion that derails many redesign efforts.
Metrics for Evaluating Structural Effectiveness
One of the most common failures in organisational design is treating structure as a one-time decision rather than an ongoing variable to be monitored and adjusted. Establishing clear metrics from the outset gives leaders an objective basis for assessing whether the design is delivering its intended outcomes and for making the case for further refinement when it is not. Without measurement, structural problems tend to surface only when they have already become performance crises.
Decision velocity is one of the most telling indicators of structural health — specifically, how long key decisions take to move from identification to resolution, and how many layers of approval they pass through. Organisations that have successfully decentralised accountability should see this number fall meaningfully. Alongside decision velocity, tracking the quality of cross-unit collaboration through mechanisms such as shared outcome achievement, internal customer satisfaction, and time lost to escalation provides a rounded picture of how well the structure enables coordination.
People metrics are equally important and often underweighted. Span of control data reveals whether managers have enough headcount to justify their role or whether there are unnecessary layers of hierarchy adding cost without adding value. Retention and engagement patterns within specific structural units can expose where accountability and authority are misaligned — high-potential talent typically exits fastest from parts of the organisation where they have responsibility without genuine decision-making power. Reviewing these metrics together, rather than in isolation, allows leaders to distinguish structural problems from leadership or cultural ones.
Technology and Digital Enablement in Organisational Design
Digital capability has fundamentally changed what is structurally possible. Coordination mechanisms that once required hierarchy — because information had to flow up and across through human intermediaries — can now be embedded in platforms, dashboards, and automated workflows. This means that organisations can maintain coherence and governance at scale while pushing operational authority much further toward the front line than earlier structural models allowed. For CIOs and technology leaders, this shift represents both a design opportunity and a responsibility to ensure that technology infrastructure actively supports the intended operating model.
The relationship between organisational design and enterprise architecture deserves more deliberate attention than it typically receives. When business units are redesigned with new boundaries and accountabilities, the systems and data structures that underpin their work rarely change at the same pace. This misalignment between structural intent and technical reality is a common source of operational friction in the months following a redesign. Technology leaders who map system dependencies against proposed structural changes before implementation can identify these risks early and sequence remediation accordingly.
Artificial intelligence and automation are introducing a further layer of complexity into organisational design decisions. As routine coordination, reporting, and decision-support tasks are absorbed by intelligent systems, the human roles that remain need to be redesigned around judgment, relationship management, and contextual reasoning. Leaders who treat automation purely as a headcount reduction tool miss the structural opportunity it presents — namely, the chance to create leaner, higher-capability teams with clearer accountability and more meaningful work. Organisational design must now account for both human and machine agents as active components of the operating model.
Organisational Design for Hybrid and Remote Workforces
The widespread shift to hybrid and remote working has exposed structural assumptions that were invisible when everyone shared the same physical space. Informal coordination mechanisms — the corridor conversation, the spontaneous whiteboard session, the visible cue that a colleague is under pressure — do not translate naturally to distributed environments. Organisations that have simply layered remote working onto structures built for co-location often find that decision-making has slowed, team cohesion has weakened, and accountability has become harder to observe and reinforce. Redesigning for hybrid requires confronting these structural dependencies directly.
Span of control norms, communication protocols, and meeting architectures all need deliberate reconfiguration in a distributed context. Leaders managing large, geographically dispersed teams require more structured feedback loops and more explicit governance of how decisions are documented and shared. Team boundaries may need to be redrawn to reduce the number of cross-time-zone dependencies for time-sensitive decisions, while asynchronous-first communication norms require that roles carry clearer written accountability than was previously necessary. These are structural choices, not simply behavioural preferences.
Hybrid working also affects the equity dimensions of organisational design in ways that have performance consequences. If proximity to leadership — whether physical or digital — determines who gets development opportunities, visibility, or informal input into decisions, then the structure is effectively creating a two-tier workforce. CIOs and technology leaders, who often manage globally distributed teams and who depend on the technology infrastructure that makes hybrid work viable, are well placed to model the structural disciplines that make distributed organisations genuinely equitable and high-performing.