A lot of data strategy work becomes too abstract too quickly. It turns into a list of platforms, future-state ideas, and architecture diagrams that sit a long way from the actual decisions a business is trying to make.
A more useful starting point is usually much simpler.
What are the decisions that matter most? Which numbers are trusted? Where is reporting helping, and where is it creating friction? Where are teams losing time because the basics are not clear enough?
Those questions tend to tell you more about the health of a data environment than a long list of technology ambitions.
A practical data strategy usually includes a few things:
- clarity on the most important business questions
- clearer KPI definitions and ownership
- stronger reporting and decision-support habits
- sensible capability priorities
- tooling decisions that support the business rather than lead it
The point of a data strategy is not to sound impressive. It is to make the organisation clearer on where it is going, what matters, and how data can genuinely help.