Anonymised · Multi-sector group · Saudi Arabia · Group-level mandate
A Saudi group operating in real estate, construction, healthcare and industrial sectors needed one technology direction across subsidiaries that had each solved their own problems separately.
The shared layer
Common to the group
- Financial definitions
- Governance
- Security posture
- Group reporting
Different by design
Real estateConstructionHealthcareIndustrial
Each on the operating systems its work actually needs.
The situation
Four sectors, several subsidiaries, and a technology estate that had grown by local decision. Each business had made defensible choices for itself. Collectively they produced a group that could not answer basic questions about itself without a manual exercise.
The tempting answer
One platform. One process. One way of working across every business, and an end to the reconciliation. It is a coherent programme, it presents well, and wanting it was not naïve.
It was still the wrong answer here, and not for ideological reasons. The businesses are genuinely different. A healthcare operation and a construction contractor do not want the same system and should not be forced into one for the sake of tidiness.
What actually had to be common
The real question is not how to standardise everything but which small number of things must be standard for the group to function — and then to defend the rest as legitimate variation.
Four things carried group accountability: financial definitions, governance, security posture and reporting. Those we standardised, and nothing else was allowed into that layer because it would have been convenient there.
The group did not need one way of working. It needed one language for the questions it asked itself.
What we deliberately did not standardise
The operating systems each business runs on. A single-platform consolidation would have pulled those in as well. That is a less impressive-sounding programme without them, and a considerably more successful one.
The processes underneath them. Where the work itself is different, a shared process is not alignment; it is one business being asked to operate as though it were another.
Leaving the rest alone is harder politically than mandating uniformity. Mandating uniformity looks like leadership, and it is announced once. Defending variation has to be argued again each time someone reasonable asks why the group does not simply pick one.
The system that followed
A multi-year roadmap covering enterprise systems unification at the group layer, cloud migration, analytics and reporting, and business-process automation. The IT governance structure was redesigned and ITIL service management practices introduced. Information security was brought to a certifiable standard, and the organisation achieved ISO 27001 certification. HR and finance processes were digitalised and a CRM deployed.
Built on
Enterprise resource planning, cloud infrastructure, business intelligence and reporting, HRMS, CRM, and an ISO 27001-aligned security management system.
What changed
The group gained a single reporting language across four sectors, a governance structure that made technology decisions traceable, and a certified security posture. Security incidents fell and manual processing across the organisation reduced materially.
Percentage improvements recorded internally are not published here pending independent evidence.
What I would watch next
A model like this does not fail loudly. If I were asked whether it is still healthy, these are the four signals I would look at.
Whether the definitions still mean the same thing. A shared definition erodes one reasonable exception at a time, and nobody announces the moment it stops being shared.
Whether the centre has started reviewing what it does not need to review. Creeping centralisation rarely arrives as a power grab. It arrives as helpfulness.
Whether variation is still being defended or has quietly become fragmentation. They look identical from the outside. The difference is whether anyone can still say why a given difference exists.
Whether group reporting is still a report. If it has turned back into a reconciliation exercise with a deadline attached, the common layer has stopped holding.
The principle
Standardisation is a tool, not a virtue. The valuable discipline is deciding precisely which layer must be common — and then having the confidence to leave the rest alone, which is harder politically than mandating uniformity.
The advisory work this belongs to is set out under advisory.