Donato BlandolinoWhy restructuring and SAP transformation belong together, and how operational transformation succeeds when processes and the system are managed together.
In most companies we work with, two of the largest initiatives run in parallel and yet separately. On one side, restructuring: processes are reorganised, responsibilities shifted, structures changed. On the other, an SAP programme, often S/4HANA, which transfers precisely these processes into a new system.
Two programmes, two project leads, often two external service providers. That sounds like a clear division of labour. In practice, it is one of the most expensive mistakes a company can make during a transformation.
The artificial separation of organisation and system
There is an understandable logic to the separation. Restructuring is seen as an organisational and leadership matter, SAP as an IT matter. The problem begins the moment both programmes touch the same thing: the company’s operational processes.
Restructuring changes precisely these processes. An SAP programme maps precisely these processes in the system, and in doing so freezes them. What is configured in the system becomes the binding reality.
Why SAP locks in what restructuring is currently changing
SAP reinforces structures, it does not fix them. A system maps what it is given. Give it unclear or outdated processes, and it locks in precisely that lack of clarity and makes it binding for years.
If an SAP programme is based on processes that are being restructured in parallel, the system maps a state that is soon supposed to cease to exist. The company goes to great lengths to configure an organisation that it is in the process of abolishing.
Both programmes can be considered a success on paper, go-live achieved, restructuring formally completed, and operationally, that is precisely where instability begins.
Operations and digitalisation are not two separate disciplines
A production process and its representation in the system are the same thing, just in two forms. Anyone who changes one inevitably changes the other. There is no significant restructuring step that leaves the system untouched, and no significant SAP decision that leaves the organisation untouched.
Operational transformation therefore means treating both as a single whole. Stabilising processes and implementing systems as one coordinated undertaking.
What “from a single source” means in practice
From a single source does not mean that one person does everything alone. It means that both initiatives operate under shared accountability and a common logic.
In practice, this means: We first establish how the company actually works, not how it is documented. We define which processes the restructuring should change and, in the same step, assess how those changes can be reflected in the system. And we manage the SAP programme so that it reflects the target organisation, not the state that the restructuring is in the process of leaving behind.
Getting the timing right: integrate rather than sequence
A common follow-up question is: Should you not simply complete the restructuring first and then implement SAP? Neat in theory, rarely realistic in practice. The answer lies not in doing one after the other, but in integrating the two.
Those who separate restructuring and SAP end up paying twice: once for each programme and a second time to bring the two outcomes into alignment afterwards. Those who approach both through a single source ultimately get what matters: an organisation and a system that speak the same language.
