Organisation design: align work, decisions and structure

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.

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.

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.

Clarify the decision, not just the box

For an important decision, identify who proposes, who contributes, who decides and who implements. Avoid making every stakeholder an approver. Check whether the accountable person has the information and authority needed to exercise judgement.

Examine lateral coordination

Work crosses functions even when charts do not. Agree service expectations, escalation routes and joint review points. A matrix can share expertise but can also create competing instructions; explain how priorities will be resolved.

Evaluate the lived design

After implementation, examine delay, rework, workload and employee understanding of responsibilities. Gather examples of difficult handovers. A cleaner chart is not enough if decisions have become slower or accountability less clear.

Start with the work and its dependencies

Before drawing a new structure, identify what must be delivered, which decisions matter and where coordination fails. A delay may come from unclear authority or incompatible systems rather than the number of management layers. Trace a customer or employee request across teams and note repeated approvals, missing information and unresolved conflicts. This provides a practical basis for design choices and prevents an organisation chart becoming a substitute for understanding the operating problem.

Compare designs against explicit criteria

A centralised specialist team may improve consistency but increase distance from local needs. A distributed model may respond quickly while duplicating work or weakening standards. Define the criteria that matter, such as quality, responsiveness, cost, resilience and employee workload, then compare plausible options. Specify decision rights and interfaces as well as reporting lines. Include the capability required to make the chosen design work; structural change cannot supply skills or trust automatically.

Test the transition, not only the destination

Identify what work must continue while roles, systems and relationships change. Plan handovers, temporary accountabilities and support for affected people. Current consultation and employment obligations need separate checking for the proposal and jurisdiction. After implementation, look for new bottlenecks and informal workarounds. A design should be judged by how decisions and work improve, not by whether the new chart has been issued or whether every role has been placed in a box.

Related terms