The Reporting Problem Is Usually Not the Report

I keep seeing the same pattern in growing businesses.

The leadership team says, “We need better reports.”

Someone then suggests Power BI, a new ERP module, a dashboard project, a planning tool, or maybe an AI layer because apparently every modern problem needs a chatbot standing nearby with a clipboard.

But quite often, the report is not the real problem.

The real problem is that the business has not agreed what the numbers mean.

Better reports will not fix unclear numbers

Revenue can mean one thing to finance, another thing to sales, and something slightly different to operations.

Customer margin may depend on whether freight is included. Product profitability may change depending on which product hierarchy someone used. Forecast versus actuals only works when the forecast and actuals are built at the same level.

Meanwhile, the board pack still depends on three spreadsheets, two manual adjustments, and one person who “just knows how it works”.

That is not a reporting issue.

That is an operating model issue wearing a reporting hat.

A dashboard can make the confusion more visible

The danger is that businesses often try to solve this by buying or building another reporting layer.

I understand why.

A dashboard feels tangible. You can see it. You can show it in a meeting. It looks like progress.

However, when the underlying definitions, mappings, ownership and checks are weak, the dashboard does not solve the problem. It simply makes the confusion more visible.

The better first question is often much simpler:

“What decisions are we trying to make, and what numbers do we need to trust to make them?”

That question changes the whole conversation.

Start with decisions, not charts

Instead of starting with visuals, start with the decisions the business needs to make.

Which customers are profitable?

Which products are growing but hurting margin?

Which sites are underperforming?

Where is cash being trapped?

Which assumptions are driving the forecast?

Which costs can managers actually control?

Which operational metrics explain the financial result?

Once those questions are clear, the reporting design becomes much easier.

The business can define the measures. It can map the data properly. It can agree who owns each number. It can automate the repetitive work. It can then build dashboards that people actually trust.

Finance teams need a stronger reporting foundation

This is where many finance teams get stuck.

They are expected to produce better insight, but they are still buried in data preparation.

Finance teams spend too much time cleaning exports, fixing mappings, reconciling reports, chasing commentary, and updating packs by hand.

Then people wonder why finance is not being more strategic.

Hard to be strategic when you are manually proving the same number for the fourth time this month.

My view is simple: if a growing business wants better reporting, it should not start with the visual layer.

It should start with the reporting foundation.

What a good reporting foundation looks like

A strong reporting foundation usually includes:

• clear definitions
• clean mappings
• source system traceability
• sensible controls
• agreed ownership
• repeatable data flows
• trusted reconciliations
• decision-ready reporting logic

This does not always require a massive transformation program.

In many cases, the best starting point is a focused reporting layer around the systems already in place.

Keep the ERP doing what it does well. Keep Excel where it is genuinely useful. Use Power BI or another reporting tool where it adds visibility.

But put proper structure around the data, definitions and logic that connect everything together.

That is usually where the value sits.

Not in the prettiest chart.

Not in the newest tool.

Not in another spreadsheet with “final_v7_really_final” in the file name, a naming convention that should probably be reported to the authorities.

Better reporting starts with trusted numbers

The real value is giving leaders numbers they can trust early enough to act.

If your reporting process feels harder than it should, the answer may not be “build more reports”.

It may be time to step back and ask whether the business has the right reporting foundation underneath it.

That is the kind of work Think Numbers helps with: turning messy finance, operational and system data into practical reporting workflows that support better decisions.