Many companies have dashboards, weekly reports and a growing number of metrics, yet meetings still end with the same question: what should we do now? The problem is not always a shortage of data. More often, data are collected first and the management question is asked later.
A metric is not decoration for a report. It should help the person accountable for a result choose between options, identify an abnormal signal or test whether an action is working. If a number cannot do at least one of these three things, it should not occupy space in an operating report.
Start with the decision, not the dashboard
Before adding a metric, a manager should answer one practical question: if this number changes, what will I do differently? A decline in repeat purchase, for example, is not only a negative figure. It directs sales and operations to examine which customers are leaving, where in the journey they disengage, and whether the cause lies in the offer, price, service or post-purchase support. Once the action question is clear, the required data also become clearer.
The opposite approach, choosing available numbers and placing them in a report, can create a feeling of control while producing little improvement. Revenue, visits, new customers and completion rates may all matter. They become useful only when they are connected to an objective and to someone who can change the outcome.
Example
A retail chain sees sales decline in several stores. If it looks only at total revenue, the team may respond with broad discounting. If it also examines store traffic, conversion, basket value and stock-out rates, it can determine whether the issue concerns traffic, service capacity or inventory. The response can then be grounded: adjust staffing, replenish stock, change merchandising or improve in-store advice.
Distinguish three layers of metrics
The first layer is outcome metrics: revenue, margin, customer retention, delivery time or satisfaction. The second layer is leading metrics, which show conditions that may create the outcome: response within service standards, stock-out rate, the share of customers receiving complete advice, request-processing time or error rate. The third layer is control metrics, which protect quality, compliance and risk from being traded away for short-term results.
When these layers are mixed, meetings become report reading. When they are arranged as a chain of cause and effect, managers can move from an underperforming outcome to the point where intervention is needed. A good dashboard therefore does not need many charts. It needs to show the relationship between the objective, the warning signal and the next action.
Do not assign a metric without assigning authority
A common mistake is to give a function a KPI while the causes of that KPI sit elsewhere. Customer service may be assigned a satisfaction target while having no authority to change return policy, delivery quality or technical resolution time. In that situation, the metric is more likely to create pressure than improvement.
Every operating metric needs three companions: an accountable owner, a decision boundary and a review rhythm. If on-time delivery falls, who can coordinate inventory or logistics partners? If conversion falls, who can change the message, offer or advisory process? When these questions cannot be answered, measurement remains description rather than management.
Build a learning rhythm around data
Metrics do not create value in one meeting. What matters is a learning rhythm: monitor, investigate, test, evaluate and standardize. Each week, a team can select one signal that requires explanation. Each month, it should revisit the assumptions it has tested, identify which responses worked and decide what belongs in the standard process. This rhythm helps organizations avoid two extremes: changing continuously by instinct or keeping the same practices after the data have signaled a problem.
As AI and automation make data available faster, the essential capability is not producing more reports. It is framing a useful question, identifying what must be tested and translating analysis into a decision with a named owner. Tools can summarize quickly, but management quality still depends on how people define the problem and act on it.
Conclusion
Organizations do not need to measure everything. They need to measure what helps them act better. Start with the decision that needs improvement, distinguish outcome, leading and control metrics, then make authority and learning rhythm explicit. When that happens, data stop being a reporting activity and become part of management capability.
Do not turn reporting into a way to postpone decisions
A common misconception is that a more detailed report makes a decision safer. In practice, a report can contain many numbers and still fail to help a manager act. The reason is simple: data may describe the past, whereas a decision must clarify what needs to change now. When sales decline, a dashboard by day, region and product is only a starting point. The management question needs to go further: which customers are leaving, at which touchpoint, for what reason, and which team has the authority to adjust something this week? Until those four questions are answered, adding more metrics often only makes the meeting longer.
I usually encourage teams to separate observation, interpretation and decision. Observation records what is happening. Interpretation identifies plausible causes. Decision selects the change to make, the person accountable and the date for review. These should not be collapsed into one slide. When they are, people can jump from a number to a conclusion without testing an assumption. A useful report is therefore not the one with the most charts; it is the one that makes the distance between the current situation and the required action visible.
Example: lower sales do not automatically call for lower prices
The example shows why a metric must sit in a chain of causes. Revenue is an end result, but it rarely tells a team where to intervene. Looking only at revenue makes a familiar tool such as discounting attractive. Looking at return behaviour, complaints, response time and returns rates supports a better hypothesis. This does not mean every decision requires a long study. It means identifying the signals that are sufficient to test a small change, measure the result and adapt.
Design an operating rhythm instead of waiting for month-end reports
Management decisions are often slow not because data are missing, but because the working rhythm is missing. A useful rhythm can include a short weekly review in which every metric is retained only when it comes with an owner and an action question. For example, late-delivery rate belongs to operations, but the question is not merely “what is the rate?” It is “which bottleneck will we address in the next seven days, and which measure will show whether the intervention worked?” Once the question is standardised, meetings spend less time circling around explanations and more time making priorities explicit.
An operating rhythm must also distinguish urgent from important. An unusual movement in a measure should be visible early, but not every fluctuation requires intervention. Leaders need shared action thresholds: what should be watched, what should be tested, and what requires a higher-level decision. This prevents two opposite errors: overreacting to small changes or waiting too long because the team wants every possible piece of evidence.
Three questions to test the value of a dashboard
Before adding a metric, ask: does it describe an outcome, provide an early warning, or control quality? Who will use it in which work? If it changes, what action can be adjusted? A measure that cannot answer these three questions may still be interesting, but it may not belong in an operating dashboard. Removing such measures does not make management less data-informed. It forces attention onto signals that can lead to action.
Measurement creates value when it shortens the distance between recognition and improvement. Start with the decision that must be made, then select measures that serve that decision. A month later, return to the question: did the measure help change behaviour, allocate resources or improve an outcome? If not, redesign the measure or reset the question. This is how an organisation turns data from a collection of reports into a real management capability.
Make learning visible after the decision
Every decision should leave behind a small learning record. State the original assumption, the change made, the expected result and the review date. This discipline matters because teams can otherwise remember only the final outcome and lose the reasoning that produced it. A useful review asks what the team expected, what happened, what it now understands about the situation and what should be retained or changed next time. Such records are especially valuable when staff change or when a local solution is being considered for wider use.
The practical point is not to create another administrative document. It is to make the decision process inspectable. Managers can then distinguish a poor decision made with reasonable information from a sensible decision that was poorly executed. Over time, this builds a shared language for evidence, judgement and accountability. The dashboard becomes more useful because it supports a continuing cycle of action, review and learning rather than a monthly ritual of reporting.
References
Kaplan, R. S., & Norton, D. P. (1996). The balanced scorecard: Translating strategy into action. Harvard Business School Press.
Parmenter, D. (2020). Key performance indicators: Developing, implementing, and using winning KPIs (4th ed.). Wiley.
Provost, F., & Fawcett, T. (2013). Data science and its relationship to big data and data-driven decision making. Big Data, 1(1), 51-59. https://doi.org/10.1089/big.2013.1508
