Information does not necessarily disappear. It simply often fails to reach the place where it is needed.
The operational team knows that a process is not working. Sales notices that a customer is behaving differently. Procurement knows about a risk involving a partner. A manager knows that capacity is becoming constrained. Finance later sees the economic impact.
Every individual part of the organisation holds information. Yet the organisation as a whole can still make decisions based on an incomplete picture of reality.
This does not necessarily result from a lack of competence or bad intentions. Information exists in conversations, emails, personal experience, routines, spreadsheets, systems or simply in people's heads.
The question is therefore not only: What data do we have? The more important question is: Who needs which information – and when?
The company as a mechanical watch.
The Uhr-Modell is not a second organisational architecture alongside my model of operational control. It translates the same logic into a simple mechanical metaphor: an organisation can only operate reliably when its different functions are connected and relevant information can move between them.
The five parts of the watch therefore do not represent five separate corporate departments. They describe different functions within the same operating system.
What matters is how information is transmitted between these functions. When that transmission works, the organisation operates in synchrony. When it breaks down, the organisation may continue to function on the surface while increasingly making decisions based on an incomplete picture of its own reality.
This is where much of the organisation's real experiential knowledge is created. Employees often identify deviations, customer reactions and process problems first.
It keeps the rhythm. Leadership must absorb information, interpret it, set priorities and translate it into decisions.
It makes performance, results and deviations visible – but only shows what has previously been captured, structured and analysed.
It holds the mechanism together and creates reliable routines. At the same time, it can only transport information for which a path has been designed.
It connects the organisation with its environment. These stakeholders influence requirements, capital, priorities and expectations – while also requiring a reliable picture of what is actually happening inside the company.
The problem is often not the quality of the individual functions. It is the quality of the information transfer between them.
Not everything that matters for a decision exists in a system.
Companies rightly invest in ERP systems, CRM, dashboards and reporting. But no system automatically knows everything that people know from their day-to-day work.
An experienced employee may recognise from the way a customer communicates that something is changing. Someone working directly in operations may know that a process only works because an additional manual step is performed every morning. A salesperson may know about a concrete order opportunity even though it has not yet become a confirmed order in the system.
Such information is real and may be economically decisive. But it is often not formalised.
Orders, bookings, costs, volumes, deadlines and other information that exists in structured form within systems.
Knowledge gained through years of practice, observation and routine that cannot be fully translated into fields and formal processes.
Conversations, assessments, feedback and signals that are known within the organisation but have no formal information path.
The watch often already contains the information it needs. It is simply in the wrong place or in a form the organisation does not use.
A dashboard can be completely accurate – and still fail to show the whole reality.
KPIs and financial control are essential. But they are a condensed representation of what has previously been captured.
If important information never enters a process or system, even the best reporting cannot display it. The display may then be technically correct, while the overall picture remains incomplete.
Operational and financial information therefore need to be continuously reconciled. A revenue or earnings deviation, for example, shows that something has happened. Information from sales, operations, customer interaction or process analysis may be needed to explain why.
In operational leadership roles, I repeatedly compared KPI and Power BI analysis with information from operations, sales and customer interactions. The dashboard showed what had changed. Looking directly at operational reality often revealed whether the underlying issue was related to processes, capacity, data or customers.
An organisation can measure with great precision and still make the wrong decision if what it measures does not represent the full relevant reality.
Leadership is also information infrastructure.
For me, one of the most important responsibilities of leadership is to make relevant information visible and able to move through the organisation.
That requires open conversations, clear escalation paths, KPIs, personal presence and a culture in which negative information can also be raised early.
Leadership should neither possess every piece of information nor control every process. But it must understand where information is created, which information is relevant to decisions and how it can reach the right place without unnecessary filtering.
Employees need to understand which information matters. Responsibilities must be clear. Systems must capture relevant data. And leadership must repeatedly verify whether the picture presented by reporting still matches operational reality.
Right time. Right place. Right quality.
Not every piece of information needs to be available to every person in an organisation. That would create overload rather than improvement.
Relevance is what matters. Information must be available where it can influence an action, a plan or a decision.
The purpose is not more information, but better decisions. This synchronisation connects employees, leadership, systems, processes, economic control and external stakeholders into a functioning mechanism.
When the watch is not running properly, I start with the information flow.
Restructuring, integration, digitalisation and other transformation situations frequently reveal the same pattern: different parts of the organisation each hold part of the truth.
The more locations, functions and interfaces are involved, the greater the risk that these individual perspectives no longer combine into a reliable overall picture.
That is why my analysis does not start with reports and organisation charts alone. Conversations, observation and a direct view of operational processes matter just as much.
The next step is to identify which information is missing, where it originates, where it is lost and who needs it to make a decision.
Understand which information actually exists – including information outside formal systems.
Define which information needs to reach which level and when escalation is required.
Verify whether KPIs, reporting and the management view still match operational reality.
This logic has repeated itself in very different situations: when building and steering a nationwide service model across 13 locations, as well as in an international brand and production environment with suppliers and operational interfaces across Europe and Asia. In each case, the decisive step was to structure operational information in a way that created real management and decision-making capability.
Only then does it make sense to ask whether processes need to be changed, responsibilities redesigned, systems extended or new KPIs introduced.
The answer to an information problem is not automatically more IT. First, it must be clear which information is actually required for which decision.
Operational control emerges when the organisation has a reliable shared picture of its situation.
Not everyone needs to know everything. But relevant information must be available where decisions are made and action is taken.
The watch does not need to become more complicated. It needs to run properly again.
Many companies try to solve information problems with additional reports, meetings or systems. This often creates more information, but not necessarily more clarity.
The central question remains which information an organisation actually needs for its decisions and how that information can reliably reach the right place.
The Uhr-Modell is therefore not an IT model, not a controlling model and not a second organisational model. It is a mechanical metaphor for operational leadership and control.
The gears must be able to work. The balance wheel must maintain the rhythm. The display must show operational and economic reality. The case must enable information flow and execution. And the strap connects the organisation with the environment for which it delivers value and carries responsibility.
When reporting, processes and operational reality no longer provide one coherent picture.
Brueggemann Interim assumes operational leadership responsibility on an interim basis when transparency, information flow and decision-making capability need to be brought back together – inside the organisation, not from a distance.