I have read a lot of documents with the words “data strategy” on the cover, and most of them are not strategies at all. They are inventories: a list of platforms to buy, a list of dashboards to build, a list of capabilities to acquire, usually with a roadmap that is really just the same list arranged by quarter. There is nothing in them about what the business is trying to achieve, which is the one thing a strategy is supposed to contain. Strip out the vendor names and you could file most of them under any company in the country.
A genuine strategy makes choices, and choices hurt a little, because to choose one thing is to not do several others. A shopping list avoids that pain by including everything. That is why so many of these documents feel reassuring to write and useless to follow. Nobody has had to decide that the customer-data work matters more this year than the finance-reporting work, so when budgets tighten and something has to give, there is no principle to fall back on. Everything was a priority, which is another way of saying nothing was.
Strategy starts with a decision, not a stack
The first question in any serious data strategy has nothing to do with technology. It is: what decisions does this organisation make badly or slowly today, and which would be worth most to make better? That framing forces a conversation the shopping-list approach skips. It puts the business outcome first and treats data and tooling as means rather than ends. A retailer that cannot tell which products are quietly unprofitable has a different first move from a charity that cannot show funders its impact, even if both buy similar software eventually.
Get that ordering right and everything downstream gets easier. You know what to build first because you know which decision you are trying to improve. You know what data you actually need, which is usually far less than the everything-everywhere approach implies. And you have a way to say no to the inevitable parade of interesting-but-irrelevant ideas, because you can hold each one up against the decisions you said mattered and watch most of them fail the test.
The sequencing problem
Even organisations that get the why right often stumble on the order. There is a strong pull towards the visible and the exciting, the predictive model or the executive dashboard, when the unglamorous foundations underneath are not yet in place. Building the showpiece before the plumbing reliably produces something that demos well in March and is quietly abandoned by September, because it sits on data nobody trusts and processes nobody agreed.
Sequencing is where outside help tends to earn its keep, and it is worth noting how the more disciplined advisers approach it. Transparity, for instance, frames its data strategy work around getting the foundations and the order of operations right before anything flashy is attempted, which is exactly the discipline the shopping-list approach lacks. The value of a good adviser here is less the technology they know and more their willingness to tell you that the thing you are most excited about is the thing you should do third.
Why this is a leadership job
Here is the part that makes data strategy genuinely hard: the important decisions cannot be delegated to the technical team, however capable. Deciding that improving customer retention matters more than optimising the supply chain this year is a business judgement with winners and losers attached. Asking the data function to make that call is asking it to set company strategy by proxy, which is unfair to them and dangerous for you. The technology choices follow the business choices, and the business choices belong to leadership.
This is why the data strategies that work tend to have a senior sponsor who actually engages, rather than one who lends their name to the cover and disappears. Someone has to own the trade-offs, defend them when they become inconvenient, and resist the temptation to quietly turn the strategy back into a shopping list the moment a department lobbies for its pet project. That is leadership work, and it cannot be bought in.
See also: EV Charging Station Business: Complete Guide to Starting a Profitable EV Charging Venture
A simple test
If you want to know whether what you are holding is a strategy or a list, try a small test. Cover the section on tools and platforms and read what remains. If there is still a clear argument about what the organisation is trying to achieve, which decisions it wants to improve, and in what order, you have a strategy. If covering the tools leaves you with almost nothing, you have an expensive shopping list with a strategy-shaped cover.
The good news is that the fix costs little. It is not more software or more dashboards. It is the harder, cheaper discipline of deciding what matters most, saying so plainly, and sequencing the work to match. Organisations that do that find the technology questions become almost easy, because for the first time there is a clear standard against which to answer them. The ones that skip it keep buying tools and keep wondering why the data never delivers what the last strategy promised.
