Why Performance Data Isn’t Driving Better Decision Making

The original intent behind the performance data

In most organisations, performance packs are designed with a clear and sensible intent. They exist to provide a consistent view of what has happened within a defined period of time, using agreed measures that can be tracked and compared. They typically bring together information on output levels, service performance, quality indicators, compliance measures, and other key metrics that reflect how the work has been carried out.

In doing so, they create a shared reference point that enables different parts of the organisation to see the same picture. As a reporting tool, this structure is effective. It provides visibility, supports governance, and enables a common understanding of activity. The difficulty does not arise because the pack is poorly designed. It arises because the context in which it is being used has shifted.

A shift from performance reporting to decision making

What changes, often gradually and without being formally defined, is the purpose of the meeting in which the pack is reviewed. The conversation increasingly moves away from describing what has happened, and towards deciding what to do next. That shift sounds relatively minor, but it introduces a fundamentally different requirement.

A reporting conversation is concerned with accuracy and completeness. A decision-making conversation is concerned with judgement, prioritisation, and consequence.
In practical terms, this means that the meeting is no longer primarily asking, “what happened?”, but instead asking questions such as:

• What should we focus on next, given the pressures we are currently facing?
• Where do we need to intervene, and what is the likely impact of doing so?
• How do we balance competing priorities when resources are constrained?
• What would justify changing course, or maintaining it, under scrutiny?

These are not questions that can be answered through reporting alone. They require interpretation, context, and an understanding of what the data does and does not represent.
The performance pack continues to describe past activity, but the meeting now requires performance data that can support decision making, not just description.

Why performance data doesn’t support decision making in practice

As this shift takes hold, people begin to adapt their behaviour in ways that are entirely logical, even if they are not explicitly acknowledged.

The first adaptation is that additional sources of insight are brought into the conversation to compensate for what the data cannot provide. Individuals will refer to recent issues that have not yet shown up in the numbers, feedback from customers, operational pressures that are emerging, or their own observations of how the work is flowing. These contributions are valuable, and in many cases essential, but they sit outside the formal structure of the pack. The result is that the centre of the conversation begins to move away from the data, even though the data is still being presented.

A second adaptation relates to confidence. When data is used to inform decisions, it needs to be understood well enough to be trusted. If a number is queried and the underlying definition, source, or construction is not clear to the group, the discussion tends to lose momentum. Rather than resolving the uncertainty, the group will often move on to a more tractable topic. Over time, this creates a pattern in which the data is acknowledged, but not relied upon. It is seen, but not used as the basis for decisions.

From the outside, this can look like disengagement. In practice, it is more accurately a reflection that the data, in its current form, is not sufficient for the level of judgement that is required.

The role has already started to change

Alongside these changes in the meeting, there is a corresponding shift in the expectations placed on individuals within the organisation.

People who may previously have been responsible for compiling, presenting, or contributing to the performance pack find that they are now being asked to go further. They are expected to explain what the data means, to identify where attention should be focused, and to support decisions that have tangible operational consequences. This introduces a different type of responsibility, one that sits somewhere between reporting and leadership. It requires the ability to connect data to context, to challenge assumptions where necessary, and to articulate reasoning in a way that others can understand and trust.

In many cases, individuals are already operating in this space. They are asking more thoughtful questions, noticing where the data does not quite align with the reality of the work, and attempting to improve how decisions are made. However, they are often doing so without a shared framework or a consistent approach.

This is the point at which their role has effectively expanded, even if it has not been formally redefined.

Why changing the pack rarely solves the problem

A common organisational response to this situation is to focus on improving the artefact itself. Dashboards are redesigned, new measures are introduced, and the layout of the pack is refined with the intention of making it more useful.

While these changes can improve clarity and accessibility, they do not address the underlying shift that has taken place. The issue is not simply how information is presented, it is how that information is used, and the capability required to use it well. Unless that underlying capability is developed, even a better-designed pack will tend to follow the same pattern. It will be reviewed, acknowledged, and then set aside as the conversation moves towards more immediate or intuitive sources of insight.

Reframing how performance data supports decision making

A more effective approach is to begin not with the pack, but with the decisions themselves. Rather than asking whether the performance pack is adequate, it is more useful to ask what the organisation is actually trying to decide when that pack is reviewed.

Once those decisions are made explicit, it becomes possible to consider what information would genuinely support them. This often involves questioning whether existing measures reflect what matters most, identifying where additional context is needed, and exploring how the data connects to the reality of the work. In doing so, the focus shifts from producing a comprehensive report to enabling confident and defensible decisions.

This is where performance data becomes useful for decision making, rather than simply reporting what has already happened.

A marker of change, rather than a failure

Seen from this perspective, the moment at which the performance pack “stops working” is not simply a problem to be fixed. It is a marker that the nature of the work has changed.
The organisation is no longer only concerned with understanding what has happened. It is increasingly concerned with making decisions that influence what happens next, and doing so in a way that can be justified and sustained over time.

The numbers remain important, but their role in supporting decision making is different. They are no longer the end point of the conversation, they are the starting point for a deeper discussion about what matters, why it matters, and what should be done in response. And that discussion depends far less on the pack itself, and far more on the capability of the people interpreting and using it.