SPT Consulting
Guides

When does your organisation need an organisational design review?.

7 min read

Structure quietly shapes everything: who decides, how fast work moves, and where accountability sits. When the structure stops fitting the strategy, the symptoms show up as duplication, stalled decisions and friction — but the root cause is often invisible until someone maps it. This guide helps you judge whether it is time for an organisational design review.

The warning signs

A few recurring patterns suggest the structure, rather than the people, is the problem:

  • A new strategy, mandate or merger has arrived, but the structure still reflects the old one.
  • Roles overlap, decisions stall, and no one is quite sure who owns what.
  • Headcount has grown organically, leaving duplicated functions and unclear reporting lines.
  • The operating model no longer fits the strategy — or the budget.
  • Auditors, the board or organised labour are questioning how the organisation is structured.

Why “just move the boxes” rarely works

Redrawing an organogram in isolation tends to move the problem rather than solve it. A sound review starts from strategy and works down: what the organisation needs to deliver, which functions deliver it, and how much work each function actually carries.

That is why function analysis, workload studies and span-of-control checks matter. They turn a structural debate into an evidence-based one — and they make the result defensible when you have to explain it to a board, a union or an auditor.

What a review should put in front of you

The following is an illustrative example of the deliverables a costed structure review typically hands over. The exact scope is tailored to your organisation.

  • A current-state diagnostic that flags duplicated roles and span-of-control issues.
  • A proposed macro and micro structure mapped directly to strategic objectives.
  • Role profiles and decision rights (a RACI) for each new or changed position.
  • A costed establishment comparing current and proposed personnel budgets.
  • A phased implementation and placement plan with owners and milestones.

Illustrative example: a division finds that two teams both believe they own supplier management, while contract renewals keep falling through the gap between them. A review makes the overlap explicit, assigns the accountability to one role, and shows the cost impact of the change. This example is illustrative; your findings will reflect your own organisation.

Public-sector and compliance considerations

Public entities have to align structures with DPSA and PFMA requirements, and to run proper consultation before changes take effect. A review built with these rules in mind produces a structure you can take through formal processes without reworking it later.

Designing for implementation, not just a report

The hardest part of organisational design is not the design — it is making it real. A review worth commissioning plans for placement, migration and the change management needed for the new structure to take hold, and transfers skills to your team along the way so you are not dependent on consultants afterwards.

Key takeaways

  • Treat structural friction — duplication, stalled decisions, unclear ownership — as a signal, not background noise.
  • A sound review starts from strategy and uses function and workload evidence, not just a redrawn chart.
  • Expect a costed structure, decision rights and an implementation plan — not only a diagnosis.
  • Public-sector structures should be DPSA/PFMA-aligned and ready for consultation.

Related service

Organisational Design & Development

Ready to discuss your situation? Read how we deliver Organisational Design & Development, or book a free 30-minute consultation and get clear next steps — no obligation.

Book a free 30-minute consultation