The one question we ask before anything else
Most data conversations start in the wrong place.
A CTO calls us. The brief is some version of: we need to choose between Fabric and Snowflake, or we need to replace the warehouse, or the board is asking about AI and we need a plan.
These are all real questions. None of them is the right first question.
Before we open any of those, we ask one thing.
Imagine it's a year from now and things are working exactly how you want. What's different about how you get or use data?
That's it. We ask it on the first call, we ask it again in the kick-off workshop, and we keep coming back to it through every discovery conversation. It is the single question that does the most useful work in a data engagement.
Here's why.
When you answer that question, four other answers fall out of it. We tend to ask them as sub-prompts.
How do you get the information you need for your day-to-day work? The answer tells us what reporting actually has to do. Not what someone said in a steering committee. What it has to do for the people running the business at 8am on a Tuesday.
What is different when you're making decisions? The answer tells us which decisions are currently slow, wrong, or guessed at. Those become the priority use cases. Everything else can wait.
What outcomes can you achieve now that you couldn't before? The answer tells us what good actually looks like. A number on a dashboard is not an outcome. A 30 percent uplift in forecast accuracy is. A board paper that takes two days instead of two weeks is.
Where do you spend more time, or less? The answer tells us where the waste lives. Most data programmes uncover at least one process where a senior person spends a day a week stitching together spreadsheets. That work disappears in a well-designed platform, and the value of the change shows up in their calendar.
Notice what isn't on that list.
We haven't asked which platform you want. We haven't asked which vendor you've shortlisted. We haven't asked whether you're doing AI. Those questions come later, and they get easier once the future state is clear.
The order matters. Choose the platform first and you usually end up bending the business to fit the tooling. Choose the future state first and the platform becomes a much smaller decision: which option best serves the world you've just described.
There's a quieter point in here too. Leaders who answer the year-from-now question well usually need less consulting, not more. They already know what the business is for. We're just helping translate that into a data programme that delivers it. The discoveries that go off the rails are almost always the ones where no one at the top has yet decided what data is meant to be doing for the organisation.
So if you're about to start a data programme, or restart one, the most useful preparation you can do is answer that question. Not in a steering paper. Not in a slide deck. In a conversation with the people who actually work with the data day-to-day.
Imagine it's a year from now and things are working exactly how you want.
What's different?