Most reporting problems don’t begin with data quality.

They begin at the last mile, where information is supposed to influence a decision.

It’s common to see technically sound dashboards that still fail to change behaviour. Not because the numbers are wrong, but because the report doesn’t align with how decisions are actually made.


Where Things Break Down

Last-mile failures usually look like this:

The output exists.

But the purpose is vague.


Reporting Isn’t the Same as Insight

Insight requires context:

Without that framing, reporting becomes passive.

People look at it, nod, and move on.


Designing for Decisions

The most effective reporting starts with questions, not data:

When those answers are clear, the data requirements often become simpler, not more complex.

Clarity reduces noise.


Reporting That Works

Good reporting doesn’t get talked about much.

It gets used.

When decisions happen without debate over the numbers, that’s usually a sign the last mile has been designed deliberately.

Because reporting doesn’t succeed when it looks impressive.

It succeeds when it changes behaviour.

Related posts

The Natural Enemy of the Database

Most splinter spreadsheets do not begin with bad intentions. They begin with urgency. Over time, unofficial tracking files quietly fracture operational truth across the business.

Read →

Clarity Is a Design Choice

Confusion is rarely accidental. It’s often the result of deferred decisions, vague ownership, and flexible definitions. Clarity doesn’t emerge by chance; it is deliberately designed.

Read →