Giving managers data and KPIs they can actually use

Give managers reliable information that leads to clearer decisions and action.

7 questions answered

Questions answered on this page

01Why doesn’t better data automatically create better decisions?
02What information should a branch manager see every day?
03What information should an MD see every week?
04How many KPIs are too many?
05How do I stop managers drowning in reports?
06Why does nobody trust the numbers?
07How do I improve data accuracy across branches?

Why doesn’t better data automatically create better decisions?

Data only improves decisions when it is trusted, understood, timely and connected to an action someone can take. A larger dashboard may describe performance without explaining what changed or who owns the response. Managers can also interpret the same figure differently if definitions, targets or time periods are unclear. In a merchant business, sales, margin, stock, credit, service and people measures need context: compared with what, driven by which customers or products, and within whose control? Discuss the decision each measure should support before adding it to a report. Then make ownership and review frequency explicit. Better decisions come from useful information combined with judgement, authority and follow-through, not from increasing the volume of data available.

What information should a branch manager see every day?

Daily information should help the branch manager protect service and control the immediate operation. The exact view varies, but it may include sales and gross profit movement, orders or quotes requiring attention, cash or credit exceptions, stock availability issues, deliveries, staffing and any safety or customer problem that needs action. Keep the daily view short and focused on exceptions and decisions rather than a miniature monthly report. Measures that move slowly or require careful interpretation belong in a weekly or monthly review. Make definitions consistent and show the manager where more detail can be found when needed. A useful daily view helps the manager decide what requires attention now without encouraging them to chase normal variation or ignore the branch floor.

What information should an MD see every week?

An MD needs a concise view of performance, risk and execution across the business. This may include sales and gross profit against an appropriate comparison, cash and debtor movement, stock and availability exceptions, service or operational disruption, people capacity and progress on the few priorities that matter. The view should highlight material variation by branch, customer or product group without forcing the MD to search through every transaction. Include leading indicators where they influence action, not only results that arrive after the opportunity has passed. Weekly information should prompt decisions, questions or support at the right level. It should not turn the MD into the branch manager for every site or encourage intervention in routine local activity.

How many KPIs are too many?

There are too many KPIs when managers cannot explain why each one matters, which action it supports or which measures take priority when they conflict. A branch may monitor many operational details, but its regular management view should focus on a small balanced set covering customers, commercial performance, stock and operations, cash or credit, and people. The right number depends on the role and review frequency. Daily, weekly and monthly views should not repeat the same long list. Remove measures that are interesting but do not lead to a decision, and keep diagnostic detail available beneath the headline rather than on the front page. A focused set creates attention; an overcrowded set allows every manager to choose the number that supports their preferred story.

How do I stop managers drowning in reports?

Begin by identifying the decisions each report is meant to support. Remove duplicated measures, separate immediate exceptions from longer-term trends and tailor the level of detail to the role. A branch manager needs a different view from an MD, finance leader or regional manager. Use consistent definitions and one recognised source so people do not spend meetings reconciling versions. Present the few important movements first, with detail available when a question needs investigation. Managers also need permission to stop producing reports that no longer serve a purpose; otherwise new requests simply accumulate. Reducing reports is not about hiding information. It is about making the route from evidence to ownership and action clearer.

Why does nobody trust the numbers?

Trust falls when systems produce different answers, definitions vary between branches, corrections arrive late or people know that important transactions are missing. It also weakens when reports are used mainly to judge rather than understand, because teams may challenge every figure before discussing performance. Identify the measures where disagreement changes decisions and trace them back to their source, owner, timing and definition. Make adjustments visible rather than quietly overwriting history. Agree one recognised version for each regular review and explain known limitations. Do not promise perfect data before using any information, but distinguish an acceptable estimate from a control failure. Trust grows through consistent definitions, transparent correction and evidence that the business acts on the data it asks people to maintain.

How do I improve data accuracy across branches?

Improve accuracy by linking each important field to a clear business process and owner. Determine where the data is first created, what validation should happen there and how errors are detected before they spread into branch and central reports. Standardise definitions for measures such as sales, gross profit, stock, overdue debt, service and staffing, then train people using real examples. Compare exceptions between branches to find process weaknesses rather than simply instructing teams to be more careful. Remove duplicate entry and unnecessary local spreadsheets where practical. Review recurring corrections and assign action to the process owner. Accuracy improves when people understand why the information matters, systems make the right behaviour easier and repeated errors lead to process correction rather than another reminder.

What you may be seeing

Managers receive several reports but still ask which figure is correct.
Meetings spend more time reconciling data than deciding what to do.
Branch teams focus on sales while margin, stock, debtors or capacity problems surface later.
Different management levels receive the same report regardless of the decisions they own.
New KPIs are added after every problem, but old measures are rarely removed.

What good looks like

A well-informed merchant business gives each management level a focused, reliable view of the decisions it owns. Daily information highlights immediate exceptions, weekly reviews show material movement and execution, and monthly information supports deeper performance understanding. Measures use agreed definitions and one recognised source, with limitations and corrections made visible. Managers can explain what changed, investigate the driver and identify the next action without drowning in detail. Supporting information remains available beneath the headline measures. The business removes reports that no longer serve a purpose and treats recurring inaccuracies as process problems to correct, not simply reasons to distrust every number.

What may be happening underneath

Purpose: Reports were built around available data rather than the decisions managers need to make.
Definitions: Branches or systems calculate important measures using different rules, periods or adjustments.
Ownership: Nobody clearly owns the source process, correction or action prompted by the measure.
Timing: Information arrives after the manager could reasonably influence the outcome.
Capability: Managers receive numbers without enough commercial or operational context to interpret them well.

Questions worth asking

01Which decision is each regular report or KPI intended to support?
02What must a branch manager act on daily, weekly and monthly?
03Where do different systems or branches produce competing versions of the same measure?
04Which measures create action, and which are reported only because they always have been?
05Who owns the source process when an important number is repeatedly inaccurate?

Where to go next

Start with the controls that need attention. The Business Control Score uses twenty short statements across five control areas and takes around four to five minutes. It provides a personalised report showing where time, profit and control may be slipping before deeper work begins.

Complete the Business Control Score Explore Business Systems toolkits