The question comes before the chart

Who needs to act today? Where has a request stalled? Which step requires the most corrections? These questions help define what to measure. A useful number needs a meaning the team shares and a clear connection to the decision it is meant to support.

We map where data originates, how it is recorded and which definitions differ across reports. We also identify information that does not yet exist. When a source is incomplete, organizing data capture is part of the work before building the dashboard.

From the source to the management routine

The scope combines information organization, collection and presentation. Everyone should be able to understand what a metric represents, where it came from and when it was updated.

Defined metrics
A dictionary of names, formulas, sources, frequencies and owners. Shared criteria for comparing numbers and discussing the same process.
Connected data
Collection from operational tools, with consistency checks and processing of the information required by the scope.
Dashboards built around decisions
Views for leadership, operations or sales, with filters and alerts linked to what each role needs to monitor.

Monitoring includes knowing how to act

The delivery includes the metrics dictionary, the agreed dashboard and the review routine. We define who checks the data, when the team reviews results and which decisions that review can support. Automatic updates depend on the available sources and integrations.

When the goal is to assess an improvement, we record the starting point and comparison criteria. This helps distinguish a change in the process from a change in how it is measured. The dashboard should make its coverage and update limitations easy to understand.

An example in practice

Fictional scenario, not a client case: a school records attendance in one system and contact with parents or guardians in another. The proposed dashboard brings together absences and contact attempts so the coordination team can organize its weekly review. The list highlights situations that need attention; decisions about each student remain with the team.

The work includes defining what counts as an absence, a completed contact and a resolved issue. Without these definitions, different people could look at the same dashboard and make decisions based on incompatible interpretations.