Data Strategy Consulting: What It Is and When You Need It

Data strategy consulting is the work of deciding what data a business actually needs, what it should be measuring, and how that feeds decisions, before anyone talks about rules or clean up. It comes first. Governance and data quality come after, once you know what you are governing and cleaning.

That order gets muddled a lot. Someone reads about data governance, or gets quoted a data quality project, and starts there. Usually the real gap is earlier than that. Nobody has decided what matters yet.

I have sat in a few of these conversations recently, and the pattern repeats more than you would think.

The business that had no dashboard at all

A multi site healthcare group I worked with had no management reporting of any kind. None. To understand how the business was doing, the owner clicked through the booking system himself, site by site and practitioner by practitioner, and worked it out in his head.

Roughly two thirds of the billing came through insurers. Some of those insurers held invoices without telling anyone.

This was not a business that was behind. It was well run and growing. Nobody had ever built a dashboard, because the owner had got good enough at doing it manually that the problem never felt urgent. That is the shape most data problems actually take in a small business. Not bad data. No decision about what to look at in the first place.

When he was asked what he actually wanted to see, he did not ask for everything. New patients, returning patients and utilisation, for every clinician, checked against their own average. With four staff he did that comparison in his head. There are now around thirty.

That is a data strategy, in miniature. Decide what the business is run on, before you decide how to collect it.

What data strategy consulting actually covers

Done properly, this starts with one question, not a list of three. What does this business decide, week to week, that it currently has to guess at or go and find?

For the healthcare group that was utilisation, by clinician. For another business it might be which jobs are actually profitable once you take out the ones that run long. The answer is rarely "everything". It is usually one or two things, sitting in somebody's head or buried in a system nobody has time to click through.

A data strategy consultant is not primarily building reports in the first session. They are working out what the business is actually for, data wise, before anything gets built. The build comes later and is usually the easier part.

How it differs from governance and quality work

This gets conflated constantly, so it is worth being precise.

Data governance consulting is about control. Who is allowed to see what, what the rules are, what happens if something goes wrong. It matters, particularly in regulated sectors, and some access and privacy questions do need settling early rather than waiting. But most of governance still assumes you already know what data you hold and why.

Data quality consulting is about accuracy. Are the numbers right. Are two suppliers quoting the same plant under two different names. Is a diary entry marked as a break actually a break. That work only makes sense once you know which numbers you care about.

Data strategy sits before both, for the most part. It decides what you are even trying to measure. Get that wrong and you can have immaculate governance and perfect data quality on numbers that nobody needed in the first place.

The dashboard that actually gets opened

One thing worth saying plainly: more data is not more insight. The temptation, once someone starts looking seriously at reporting, is to build something comprehensive. Every metric the system can produce, on one screen.

In my experience that kind of dashboard gets opened once, and then not again.

The healthcare group owner did not want top treatments or a breakdown of every chart entry. He wanted a small number of figures that told him whether each clinician's week was normal, delivered without him having to ask. That is the test for a good data strategy. Not completeness. Whether the person it is for would actually look at it on a Monday morning.

There is a catch worth flagging honestly, because it came up in the same conversation. Clinicians were blocking time in the diary as breaks, which could make a diary look fully booked when a clinician was not actually working. If you are going to hold someone to a utilisation figure, you have to agree what counts as booked time first. That is not quite a governance point or a quality point. It is a strategy point: deciding what the word "utilisation" means before you start reporting on it.

When this is worth paying for

The ONS found that the average UK business already using AI uses only 1.6 AI technologies, and only one in ten describes its use as extensive. Adoption is wide. Depth is not. I see the same pattern with data generally. Most small businesses are not short of tools. They are short of a decision about what those tools should be telling them.

DSIT's AI Adoption Research, based on telephone interviews with 3,500 UK businesses, found that the top barrier to AI adoption is not cost or fear. 71% said they had not identified a clear business need for it. I see the same shape with data work. The barrier is rarely the tool. It is deciding what you would actually use it for.

I worked with a professional services firm once where a consultation surfaced thirteen candidate projects. I sent the list back with no prices on it and asked them to pick what mattered most, and in what order. Prices followed afterwards, project by project, so they could buy one at a time rather than being quoted one large number up front. That is a sales method, I will admit, but it is also more honest than a single big figure that usually just gets shelved.

If that sounds like your business, a short piece of data strategy work is worth more than another piece of software. If you already know exactly what you want to measure and the only problem is messy source data, you need data quality work, not strategy. If the problem is who is allowed to see what, that is governance.

I would not take on a strategy engagement for a business that already has a clear, used dashboard and just wants it prettier. That is a design job, not a strategy job, and paying consultancy rates for it is a waste of your money.

What to do before you call anyone

Spend a fortnight writing down, honestly, the decisions you make regularly and where the information for them currently comes from. For a lot of owners that answer is "my head" or "clicking through the system", same as it was for the healthcare group owner before anyone got involved. That list is most of the strategy work done already, for free.

If your main gap is reporting rather than strategy, automated business reporting is the narrower version of this, for businesses that already know what they want to measure and just need it to arrive on its own. If the problem is broader than data, a wider look at digital transformation covers more ground, and AI for small business is a reasonable place to start if you are not sure which of these you need yet.