← HR strategy

HRM practice

Organisation design: align work, decisions and structure

Look beyond the organisation chart to the work, relationships and decision rights needed to deliver the strategy.

ADM HR; reading: Armstrong & Taylor · 2023 · Original editorial explanation
Organisation design: align work, decisions and structure — simplified model sketchStrategic need · Work and dependencies · Design choices · Transition and review. Editorial interpretation, after ADM HR; reading: Armstrong & Taylor (2023).Strategicneed01Work anddependencies02Designchoices03Transitionand review04ADM HR · ORIGINAL INTERPRETATIONADM HR; reading: Armstrong & Taylor · 2023
Original ADM HR application sketch. Read the explanation for assumptions and limitations. Download SVG ↗

The core idea

Organisation design concerns how work and responsibility are arranged. Structure is one part: processes, coordination, decision rights and management capacity also matter. Armstrong and Taylor connect organisation, work and job design. A new reporting line rarely resolves a problem caused by conflicting priorities or a poorly designed handover.

Source and attribution [1]

Using it in practice

Define the outcome the organisation must deliver and map the work required. Identify dependencies, decision delays and duplicated effort. Compare design options against agreed criteria such as responsiveness, specialist depth, accountability and employee workload. Test the most uncertain handovers before a broad rollout. Plan the transition and consult on people implications through appropriate processes.

An example, not a reported case

Worked example · illustrative

A growing security business moves all scheduling decisions into a central team. Standardisation improves cover, but site supervisors lose the ability to respond to local incidents. The design is revised so routine allocation remains central while clearly defined urgent decisions sit locally, with shared information and review.

What to watch for

There is no ideal span of control or universal structure. Task complexity, geography, experience and support systems change what is workable. Redesign may involve contractual, consultation or redundancy issues; use current legal guidance for those decisions rather than treating a diagram as authority to act.

Define the problem before proposing a structure

CIPD describes organisation design as aligning the organisation with its strategy, including the processes and practices through which work is done. It is broader than changing reporting lines. Start an original design brief with a concrete problem: for example, routine client decisions wait several days for approval despite all the necessary information being available locally. Define the outcome required and the evidence of the present difficulty. Separate a strategic need from a leader’s preference for a familiar structure. If the sponsor has already chosen the answer, make that constraint explicit before inviting employees to help diagnose the problem.

Trace one piece of work from request to result

Follow a real, appropriately anonymised request across teams. Record what information enters, what each person decides, where it waits and what causes it to return for correction. Include informal work that does not appear in the procedure, such as a trusted colleague checking an exception. Distinguish processing time from waiting time: a five-minute task can take a week to complete when nobody owns the next decision. Ask the people doing the work to correct the map. Do not assume that the written process or senior manager’s account describes what happens on a busy shift.

Agree criteria that reveal genuine trade-offs

Choose a small set of criteria before comparing options. For a multi-site service these might include response time, consistency, access to specialist advice, resilience during absence and manageable supervisory workload. Explain what acceptable performance means for each. A central team may offer specialist depth while creating a queue; local teams may respond quickly while duplicating expertise. Include retaining the present structure with clearer decision rights as a serious option. Record disadvantages as well as benefits. A numerical scoring table can organise the discussion, but its weights express judgement and should not be presented as objective proof.

Make authority and interfaces usable

For an important decision, specify who can decide, whose advice is required, what information is necessary and where an unresolved conflict goes. Distinguish a contributor from an approver. An original test is to give two teams the same realistic scenario and ask them independently who acts next. If their answers differ, the design remains ambiguous. Describe the service at a boundary as well: what a team supplies, in what form and by when. A reporting line does not automatically resolve a disagreement between professional standards, customer urgency and local capacity.

Worked example: central scheduling with local exceptions

Invented case: a security business centralises routine scheduling to improve visibility of available cover. Site supervisors then find they cannot respond promptly when an incident changes local needs. The revised proposal keeps routine allocation central, defines a narrow local authority for urgent adjustments and requires the central record to be updated. Before implementation, the teams rehearse a normal absence, a simultaneous shortage at two sites and an unavailable decision-maker. They discover that the escalation contact needs a deputy and that the central team lacks one item of site information. Testing decisions exposes problems that a tidy chart would conceal.

Check management capacity rather than chasing a standard ratio

There is no useful universal answer to how many people a manager should supervise. Examine the work: task variety, risk, employee experience, shift coverage, geographical spread and the support available. Estimate the time needed for ordinary coordination, development and exceptions, then compare it with other responsibilities. A wider span may be workable with stable tasks and experienced staff but unrealistic where intensive coaching is needed. Ask what will stop or move if managerial responsibility increases. Removing a management layer can transfer work rather than remove it, so assess where that work will land.

Use models to challenge omissions

The linked McKinsey 7-S guide offers a way to ask whether structure is consistent with systems, skills, management style and shared values. The job-characteristics guide helps examine what a proposed role means for the person doing it. Use these as different lenses, not competing recipes. For example, greater local discretion may require clearer information, capability development and a different approach to performance review. The original question for a design meeting is: which other practice must change for this proposal to work? Naming a model does not supply the missing evidence or settle the trade-off.

Separate the proposed design from the transition decision

Describe how essential work will continue while responsibilities change. Identify temporary ownership, access requirements, unfinished cases and the point at which a handover is accepted. Affected people need clarity about what is proposed, what is decided and where they can raise concerns. If roles, employment terms or staffing levels may change, obtain current advice on the relevant process and jurisdiction before acting. This article provides design guidance, not authority to bypass consultation or other requirements. Keep the operational transition plan connected to the people process without treating them as the same document.

Review what the design actually produces

Compare decision delays, rework, escalation frequency and workload with the starting position. Look for apparent gains that shift a burden elsewhere, such as faster local closure followed by more corrections in payroll. Ask employees to explain the new authority arrangements using a real example. Record which assumptions held and which need revision. AIHR’s Transformation Signal Scorecard is further reading on identifying pressures for change; its ratings are a discussion aid rather than validated evidence that restructuring is required. Retain a route for adjusting interfaces after launch instead of declaring the design finished when the chart is published.

Take it into your next conversation

Three useful questions.

  1. Which decision or handover is the proposed design meant to improve?
  2. What important trade-off would each option create?
  3. What must change beyond the reporting lines for the design to work?

Related terms

Go to the evidence

Sources & attribution

Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 17–20. Edition & reading notes ↗

[1] Armstrong & Taylor (2023), 16th edition, chapters 17–20 — reading notes ↗

[2] CIPD, Organisation design (28 February 2025); consulted 29 September 2026 ↗

[3] AIHR member toolkit, The Transformation Signal Scorecard (25 September 2026); consulted 29 September 2026 ↗

The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.

Original ADM HR teaching guide with attributed background reading. Practical guidance expanded on 29 September 2026. The worked cases, diagnostic questions and suggested decision records are original editorial illustrations, not validated assessment instruments or reproductions of member templates. Source links distinguish further reading from the original authorship of models. The overview review date is retained; this expansion does not establish a new legal review date for linked guidance.

Published 2026-09-25 · Reviewed 2026-09-25. Editorial approach

Keep exploring

A little more context.

Culture · diagnosis & change01

McKinsey’s 7-S framework

Check whether strategy, structure, systems and people arrangements support the same direction.

McKinsey6 min
Design the work, not just the reward02

The job characteristics model

Look at the features of a role that make work meaningful, give people responsibility and show them the results.

J. Richard Hackman5 min
Lifecycle practice guide03

Consulting on change and employment terms

Plan a genuine consultation, distinguish proposed changes from agreed terms, and connect decisions with implementation.

ADM HR editorial4 min