What good operational data actually looks like

A report can contain plenty of data and still leave a team unsure what to do next. Dashboards proliferate, numbers multiply, exports are emailed each morning; and the team is no closer to knowing what to do next.

Good operational data is quieter than that. It exists to support a small number of recurring decisions, and to make significant exceptions easier to notice.

Three things worth getting right

1. A single source of truth, per concept

For each important record or field, define which source is authoritative: a customer, job, booking, vehicle or product may appear in several systems. Other systems can hold copies, with agreed rules for resolving disagreements. Without that rule, every report is a negotiation.

2. Decisions, not vanity

A useful dashboard answers a question someone will act on. "How many enquiries this week?" is rarely actionable on its own. "Which enquiries have passed our agreed response window?" points towards a follow-up action. The first is a metric; the second is a decision.

3. Exceptions surfaced, normality hidden

Operational data should make the unusual loud and the routine quiet. A well-designed view shows you what needs attention, not everything that happened. The team's time is the scarce resource, not the data.

Things to be sceptical of

• Dashboards that nobody opened last week.
• Reports that always look healthy, regardless of the week.
• Numbers without a definition anyone can recite.
• "More data" as the answer to "why didn't we know?"

If a dashboard exists, someone should be able to name the decision it supports and the person who makes it. If neither answer comes, the dashboard is decoration.

Where to start

Pick one decision that recurs every week. Write down what data would make it obvious. Make that data available to the person who has to make the decision. Do nothing else until that works. That first decision gives the work a concrete purpose before the reporting system expands.

To put this into practice, map one workflow and review the dashboard decisions it needs to support.