Data alone does not create operational control.
Financial data such as costs, revenue, invoices and accruals were available in the ERP system. Quotation data sat in the sales and project management system, supplemented by operational data from different functions.
For executive management, however, knowing revenue, result or margin at top level is not enough. As soon as a metric deviates from plan, the real question begins: where did the cause originate?
For this reason, data from different systems were brought together using shared identifiers such as project numbers and presented in Power BI so that financial and operational information could be connected.
A company-level number shows an outcome. Leadership also needs the path back to its cause.
Metrics need to be broken down through the organisation.
The management logic starts at company level and is then progressively broken down.
A weaker company margin can, for example, be traced back to individual customers, projects or cost categories. Within a project, it can then become visible whether additional services, waiting times, changes, labour effort or misallocated overheads were the cause.
A financial deviation thus becomes an operational question that can be investigated directly.
An operational deviation is only fully assessed when its economic impact is visible.
Deviations arise constantly in day-to-day operations. A project changes. Resource requirements increase. Employees wait longer than planned. A customer changes an assignment several times. Material consumption rises or additional services are delivered.
This information matters operationally. For leadership, however, it only becomes fully relevant when its impact on cost, margin, cash flow or result is visible.
Measure not only volumes or movements, but understand the additional cost and its effect on the project.
Allocate time to the relevant project and make its economic significance visible.
Capture subsequent customer requests and process changes as effort and potential additional services.
Allocate consumption to the assignment that caused it wherever possible and identify deviations early.
From the company result down to the individual process, it should be possible to trace where a deviation arises and what it means economically.
Activity is not the same as performance.
Operational metrics in particular can easily be misinterpreted. The number of cases, quotations or movements processed says very little on its own.
One employee may process a high number of small, standardised cases. Another may handle far fewer cases that are considerably more complex, extensive or economically significant.
That is why every metric needs context: How complex was the transaction? How many items and participants were involved? How many changes occurred? How much time was required? And what economic contribution did the transaction ultimately make?
The same applies to physical processes. The time between two scan points can be a useful indicator, but it only becomes meaningful when the actual complexity and effort of the underlying activity are understood.
A metric without context may measure activity – and still lead to the wrong management decision.
A commercially attractive assignment is not automatically good for cash flow.
Connecting different metrics often changes the way customers and projects are assessed.
An assignment can generate an attractive margin while still tying up liquidity if payment terms are long or significant cash outflows occur well before payment is received.
For me, result, margin, payment terms, receivables ageing and cash flow belong together. Only this combination provides a robust economic assessment.
Open invoices and services not yet billed are equally important. Deviations therefore led not only to a look at the dashboard, but to conversations with the responsible employees: Why has this not yet been invoiced? Why is a receivable still outstanding? Is information missing? Has a process not been completed?
Metrics need to reach the level where they can actually be influenced.
As Managing Director, I need to be able to explain to owners and controlling why result, cash flow or other key metrics deviate from plan.
The same principle must extend throughout the organisation. Department and location managers are responsible for their performance indicators. Managers discuss deviations with their teams. Employees receive the metrics they can actually influence through their daily work.
These may include processed cases, documented project time, movements, lead times, billing status or other operational measures.
The important point is not to confuse responsibility with mere control. A metric indicates where an explanation or investigation is required.
Responsibility must extend throughout the entire organisation. Every level needs the metrics it can influence – and must be able to understand, explain and address deviations.
Good metric systems reduce micromanagement.
Executive management cannot investigate every individual deviation itself. That is exactly why leaders and employees need to learn to understand metrics as indicators.
A deviation may be a one-off. It may result from an unusual assignment, a special customer requirement or a short-term bottleneck. If it keeps recurring, however, a structural problem may lie behind it.
At the critical points, an organisation therefore needs people who identify deviations themselves, investigate causes and make an initial assessment before the issue reaches the next management level.
The purpose of a metric system is not for executive management to control more and more. The purpose is for the organisation to identify and address deviations earlier itself.
Future information requirements belong in the process design from the outset.
Anyone digitalising a process today should already consider which metrics will be needed to manage it tomorrow.
If working time, movements, additional services, complaints, material consumption or lead times will later be relevant, that information should ideally be generated as part of the normal process.
Otherwise, additional Excel lists, paper notes or manual side processes will appear later.
Temporary manual data capture can still be useful. If, for example, material consumption increases while billing does not rise accordingly, a simple project-based record can initially help identify the cause.
Once it is clear which information is required permanently, it should wherever possible be integrated into the regular process and system landscape.
Metrics close the loop to continuous improvement.
A good metric system does more than manage results. It reveals where processes have become unnecessarily complicated, error-prone or inefficient for employees.
Metrics should therefore not be understood as an instrument of mistrust. A deviation may equally indicate that a process needs improvement – not that a person is performing poorly.
This is where the loop closes for me with continuous improvement and Kaizen: identify the deviation, understand the cause, change the process and then use the same metric to determine whether the change actually produced an effect.
Without metrics, improvement often remains subjective. With metrics, it becomes possible to test whether a process has actually become faster, safer, simpler or more economical.
Reporting becomes a leadership and improvement system.
The tool may be Power BI or another platform. What matters is the management logic behind it.
Metrics do not lead. Leadership with metrics does.
A company does not become controllable by collecting as much data as possible or building as many dashboards as possible.
What matters is a clear logic: Which metric reveals a deviation? What operational cause lies behind it? Who can influence it? What economic impact does it have? And which decision follows from it?
Good metrics are therefore broken down through the organisational hierarchy. They give managers and employees direction and create accountability without turning into micromanagement.
When deviations are identified where they arise, reporting becomes self-management. When the causes are subsequently addressed and the impact is measured again, the result is continuous improvement.
An initial confidential conversation is enough to assess the starting situation, leadership responsibility and potential assignment scope.