29 May 2026 Data Strategy Business Analysis

Nobody Wants Data Quality

Quick answer

Nobody Wants Data Quality explains what the change means for UK SMEs and how to turn it into a practical next step. The process is to identify the business decision, connect the data, then automate only the parts that improve speed or reliability.

Think about how a builder sells a house extension.

The customer buys a bigger kitchen. Somewhere to put the island, the bifold doors, the space the family actually lives in. That's the thing they can see, the thing they got excited about, the thing they're paying for.

The builder knows the real work is somewhere else entirely. Foundations. Drainage. Steelwork. Electrics. Load calculations. None of it ends up in the photos. The customer never asks for foundations. They've never lain awake wishing for better drainage.

But the foundations are what make the extension possible. Get them wrong and the kitchen cracks, floods, or falls down. The customer didn't want foundations, but they absolutely wanted everything foundations make possible.

Data is exactly the same.

The mistake data people keep making

A lot of data people try to sell data quality.

They walk into a room and talk about completeness, accuracy, lineage, governance, golden records, master data. All real, all important, all completely invisible to the person holding the budget.

Nobody wants data quality. I mean that literally. No operations director has ever woken up wanting cleaner item master records for their own sake.

What they actually want is:

  • Faster service
  • Better decisions
  • Lower inventory
  • Less downtime
  • Higher sales
  • Better forecasting
  • Successful AI
  • Reliable reporting

Data quality is simply the mechanism. It's the foundations. It's the thing nobody asks for that makes everything they do ask for possible.

Why this matters more than it sounds

This isn't just a framing trick to get projects signed off. Getting the framing right changes what you actually build.

When you sell data quality as the goal, the project drifts toward perfection for its own sake. You clean everything. You build governance no one uses. You produce a beautifully accurate dataset that doesn't move a single number on the P&L. Months later someone asks what the return was, and you don't have a good answer.

When you start from the outcome, the work organises itself. "We want to cut inventory by 10%" tells you exactly which data has to be trusted, to what standard, and where you can leave well enough alone. You fix the foundations that hold up the kitchen, not every foundation on the street.

The builder doesn't pour concrete under the whole garden. They pour it where the extension is going.

How to actually have the conversation

Stop leading with the mechanism. Lead with the outcome, then earn the right to talk about foundations.

Instead of "your data quality is poor," try "your forecasts are wrong about a third of the time, and here's what that's costing you." Now the room is interested, because you're talking about their problem in their language.

Then you trace it back. The forecast is wrong because demand history is unreliable. The history is unreliable because returns aren't recorded consistently. The returns aren't recorded consistently because of how the process runs on the floor. That's your foundation work, and now it's attached to a number everyone cares about.

Same work. Completely different reception.

The uncomfortable bit

Here's the part data people don't always like: if you've done the foundations well, nobody notices them. The extension just works. The reporting is just reliable. The forecast is just right more often.

Builders live with this too. The best foundations are the ones no one ever thinks about again. You don't get applause for drainage. You get a kitchen that doesn't flood, and a customer who's happy without quite knowing why.

If you want recognition for data quality itself, you'll be disappointed. If you want to be the person whose work quietly makes the whole business run better, that's the job. Sell the kitchen. Build the foundations. Let the results do the talking.

If you're the one buying data work rather than doing it, I wrote this for you: Why Your Data Project Stalled (And What to Ask For Instead).

Need help framing your data project?

I help UK SMEs turn messy data into clear outcomes: faster reporting, better forecasts, and dashboards that actually get used.

See Power BI consultancy