A company aims to release new product versions every month and discovers that between the idea and the customer there are three approval committees. Another sells a client an integration with its ERP and, when the time comes to deliver it, the integration is not viable. A third bought a company two years ago for the synergies and still has not managed to get their systems talking to each other.
They look like different problems: one of process, one commercial, one of integration. They are the same. In all three, whoever leads issues a mandate and the company does not respond as it should, or responds late and halfway. It is the feeling of pressing the brake and noticing that the car does not behave as expected.
Whoever lives through this usually knows their company better than anyone and has tried everything: one committee fewer, a better-drafted contract, more budget. The situation gets resolved and a few months later the problem reappears somewhere else. Because what is failing is not a single part, and from inside it is very hard to see anything else.
What is missing is not information
What is missing is command: knowing what is really happening in the company and being able to decide with an understanding of the consequences.
It is not about seeing and knowing everything in detail. A board member does not need to know how each integration is programmed. Nor is it a dashboard with more indicators. You can have an impeccable one and still lack command, because indicators measure what someone was able to measure, not what the company needs to know in order to decide.
Many organisations have committees, policies and procedures in the hope of having governance. Yet very few have these mechanisms in a layer that stays hidden and is not taken into account: Technology. Without it, the other layers of the company (Ownership, Business, Structure) believe they are in control, but they lack knowledge of the situation, the limitations, the levers and the mechanisms that decisively shape what the company can actually do.
Where the lack of command comes from
Rugaro bases its intervention on the idea that every company has a Model and a System, even if it has never named them. The Model refers to what the company wants to be, and how: its purpose, its strategy, what it decides to be and what it gives up. The System is what, and who, makes it possible: the people, processes and tools it actually runs on. Both always exist, with greater or lesser maturity or explicit definition. The question is never whether they are there, but whether they sustain each other.
The System is talked about less than the Model, and it comes in more variants than it seems. It may be barely incipient, with the company running on improvisation and on particular people. It may be solid and resistant to change: everything works, but every modification takes months. It may produce good results without anyone really knowing why, and collapse at the first serious crisis, with no clear explanation and to everyone's bewilderment. And a System is not just what works. It has a behaviour of its own: it maintains and stabilises itself, it is configured and used, and it tends to produce what its definition allows, not what those in charge of it wish for. It is not mere inertia, and that is why it cannot be changed by decree. It is designed.
In a good many cases, the point where the System stops responding is Technology, the layer that is named least and that most constrains what the company can do. It does not execute other people's decisions: it imposes limits and opens possibilities nobody has explicitly decided. And one of two things usually happens. Either it is not clear, and nobody knows precisely what there is, in what state and what it depends on. Or it is known but not governed: someone knows it in depth, but that knowledge does not reach where decisions are made, or there are no levers to act on it.
What those who lead decide has to reach the technical level, and what happens at the technical level has to reach those who decide. When either of those two paths is interrupted, the company does not respond. And it is interrupted at a specific point, between technology and the structure that operates it, or between that structure and the business. Locating where it does not flow is the first thing that changes the conversation.
It can only be achieved from within
Command cannot be bought. Nor can it be outsourced or commissioned: nobody can be engaged to produce it, because it is not something that is manufactured, but what appears when the company knows what it has and can decide about it. No consultancy hands it over to you, not even the best one. A diagnosis and a judgement only become command when the company makes them its own.
What can be commissioned is building the governance of Technology, integrating it into the System and aligning it with the Model: determining what needs to be known about Technology, with which indicators, and with which levers to act on it, according to the scenario the company operates in and the circumstances it is going through at that moment.
And this can only be done from within, and until self-sufficiency and sustainability are achieved.
Rugaro comes in with you
Rugaro comes in to understand, decide and transform with you, as you determine and as far as you determine.
Reading with you what is really there: what technology exists, in what state, what it depends on and what risk it carries. That is our diagnosis, and its result is a map the company did not have.
Turning that map into judgement you can stand behind: what is kept, what is changed, what cannot wait and in what sequence.
Carrying out with you what has been decided, as you require: creating the organisational structure, processes and decision channels you need in order to govern, demolishing what does not serve, and leaving in place the governance that makes it sustainable.
Governing better has a price, and it is not always worth paying. Part of the judgement lies in assessing, in each company, how far it is worth going. Which challenge we take on and which we postpone or set aside.
But whatever we do, this is the path: understand what you have, decide what can be changed, and be able to build it so that the company responds to the mandate of those who lead it.
