Organisation Design That Supports Delivery

A new operating model can look convincing on paper yet fail within months. Decisions still escalate unnecessarily, accountabilities overlap, senior leaders become bottlenecks and teams create workarounds to keep customers or operations moving. Organisation design addresses these practical failures by aligning structure, roles, decision rights and workforce capacity with the work the business needs to deliver.

For senior leaders, this is not principally an exercise in redrawing organisation charts. It is a commercial and operational discipline. Done well, it clarifies where value is created, what must be governed centrally, what can sit closer to the customer or operation, and how roles should fit together. Done poorly, it can add management layers, unsettle capable people and leave the underlying problems untouched.

What organisation design is intended to solve

Organisation design establishes how work is divided, coordinated and led. It considers formal structure, but also the mechanisms that make a structure work: job accountabilities, delegation, governance forums, reporting relationships, management spans, skills and reward arrangements.

The starting point should be a clear business question. An international group may need greater consistency in commercial governance while retaining local market responsiveness. A scaling technology business may need to replace founder-led decisions with clearer functional accountability. A public or mission-led organisation may need to reduce duplication without weakening service quality. The appropriate answer differs in each case.

This is why an organisation chart is an output, not the design itself. Moving boxes around without resolving decision rights, process ownership or capability constraints often produces a cosmetic change. Employees may receive new job titles while continuing to work in precisely the same way.

A well-designed organisation should make four things easier: making decisions at the right level, coordinating work across functions, holding leaders accountable for outcomes, and deploying workforce cost where it creates the greatest value. These objectives can conflict. Greater control may improve consistency but slow local action; flatter structures may reduce hierarchy but leave insufficient leadership capacity. The design needs explicit choices rather than generic principles.

Diagnose before redesigning the organisation

Pressure for restructuring frequently follows a missed target, cost challenge, acquisition, leadership change or employee feedback. Those are valid prompts, but they are not diagnoses. Before proposing a future structure, leaders need evidence about how the current organisation operates.

A focused diagnostic normally examines the strategy and operating model, major value streams, customer and stakeholder requirements, workforce costs, reporting lines, role profiles and decision-making. Interviews and working sessions are valuable, but they should be tested against data. Headcount by layer, management spans, vacancy patterns, contractor use, grade distribution and pay costs can reveal issues that a chart alone conceals.

For example, a narrow span of control is not automatically inefficient. It may be necessary where work carries significant operational risk, technical supervision or people-management demand. Equally, a wide span can be appropriate for experienced, autonomous professionals but problematic where managers are expected to coach, control risk and lead substantial change. The question is whether the span supports the work, not whether it meets a universal benchmark.

The same discipline applies to layers. Additional layers can create useful expertise, risk control and development opportunities. They can also lengthen approval routes and blur accountability. A diagnosis should distinguish necessary complexity from legacy complexity accumulated through growth, acquisitions or temporary fixes.

Find the real points of friction

The most revealing questions tend to be practical. Where do decisions stall? Which work is repeatedly handed between teams? Who is accountable when an outcome crosses functions or countries? Which senior roles have become overloaded because no-one else has the authority to act?

These questions often expose gaps between the formal organisation and the organisation people actually use. Informal networks are not inherently a problem. In complex businesses they can be essential. However, when routine delivery depends on personal escalation and individual relationships, the formal design is unlikely to be sustainable.

Design the operating model, not just the hierarchy

A credible design begins with the work that must be done and the capabilities required to do it. Leaders should identify the few activities that create competitive advantage, protect critical outcomes or require close control. They should then determine the right organisational level for ownership and the interfaces needed between teams.

Centralisation and decentralisation are rarely binary choices. A multinational employer may centralise reward policy, job architecture and core people data while allowing local flexibility in benefits delivery, workforce deployment and selected market practices. A group structure may retain central functional standards but give business units clear commercial authority. The design should set out these boundaries precisely.

Decision rights are particularly important. A responsibility matrix can help, but only if it is rooted in real decisions rather than broad activity statements. It should show who recommends, decides, approves, executes and must be consulted. Where several executives appear accountable for the same outcome, accountability is normally diluted.

Role design follows from this work. Each leadership role needs a defined purpose, scope, key accountabilities and decision authority. This creates a sound basis for job evaluation, grading and reward. It also prevents a common failure of restructuring: changing reporting lines while retaining role profiles that reflect a previous organisation.

Connect organisation design to job architecture and reward

Organisation design has direct consequences for reward governance. New structures often create roles with broader scope, altered accountability or greater market exposure. If these changes are not evaluated consistently, grade drift and pay inequity can follow.

A clear job architecture provides a common language for role levels, career paths and organisational scope. Job evaluation assesses the relative size of roles using a defined methodology, rather than relying on title or incumbent influence. Together, they help ensure that a redesigned structure is supported by defensible grades, pay ranges and incentive eligibility.

This matters particularly during integration, growth or cost transformation. Leaders may need to retain critical capability, introduce new roles or consolidate overlapping positions. Reward decisions should be modelled alongside the structural options, including fixed pay, incentives, benefits, pension implications where relevant and transition costs. Affordability and fairness need to be considered at the point of design, not after announcements have been made.

Model the choices and test the trade-offs

There is seldom one correct structure. Good organisation design presents a small number of viable options, with clear assumptions and consequences. One option may prioritise customer proximity; another may reduce duplicated functional activity; a third may preserve specialist depth in a tightly regulated or technically complex environment.

Modelling should cover more than headcount. It should assess management layers, spans, role populations, location footprint where relevant, cost, implementation risk and likely effects on service or control. Scenario modelling is particularly useful where leaders are balancing a cost objective against growth plans or uncertain demand.

Financial analysis should be rigorous but not simplistic. A structure that removes cost quickly may create additional workload, weaken succession depth or require expensive external capability later. Conversely, retaining capacity without a clear workload case can defer difficult decisions. The most useful model makes these trade-offs visible to executives and the board.

Implement with discipline and transparency

Implementation is where many well-reasoned designs lose credibility. Employees experience a change through their manager, their role, their pay and the decisions that follow. A technically sound target structure is insufficient if leaders cannot explain why it is changing and what will operate differently.

The implementation plan should sequence structural decisions, role mapping, job evaluation, workforce planning, reward treatment, systems changes and communications. The order matters. Announcing a structure before accountabilities, selection principles or grading approaches are sufficiently clear can create avoidable uncertainty.

Governance is equally important. A senior sponsor group should resolve design decisions promptly, while a programme team maintains data integrity, tracks dependencies and manages exceptions. Exceptions are often necessary, especially in international organisations, but each should have a clear rationale and owner. Otherwise, local accommodations can gradually undermine the intended model.

Managers need practical support, not only presentation materials. They must understand the future accountabilities, how decisions will be made, where teams should collaborate and what they can say about role changes. This is particularly important where the organisation is introducing matrix relationships or shifting responsibilities between corporate, regional and local teams.

Measure whether the design is working

Organisation design should be reviewed after implementation against the outcomes it was meant to achieve. Relevant measures may include decision cycle times, customer or operational service measures, management span and layer trends, workforce cost, voluntary turnover in critical populations, internal mobility and employee understanding of accountabilities.

No single measure proves success. A lower management ratio is not meaningful if delivery, control or engagement deteriorates. Equally, positive employee feedback is not enough if major decisions remain unresolved. The evidence should combine operational performance, workforce data and informed feedback from leaders and employees.

Organisation design is most effective when treated as an operating discipline rather than a one-off restructuring event. Clear thinking, robust analysis and practical delivery create structures that can adapt as strategy, markets and workforce needs change.