Every product ships a feature. Fewer ship the data behind it.
That gap is usually invisible until someone asks a simple question — "is this actually working?" — and nobody can answer it with anything better than a guess. Not because the team is careless, but because data was never designed in. It was left to happen, if it happened at all.
The curve below is a way of naming where a team, a product, or a whole function actually sits today — not where it would like to be. Five levels, each one a genuine step up from the last, not just more tooling. Click through them.
Don't just deliver a feature — deliver a data asset. Thinking about data on day one, at Level 1, is a small cost. Going back for it six months after launch is a large one. Plan for Levels 1 and 2 as part of the build itself, and Levels 3 and 4 stop being aspirational.
Nothing here requires a platform rebuild to start climbing. Most of the jump between levels is a decision, made earlier than usual — before the build starts, not after it ships.
It's a cultural change, not a tooling purchase. No platform decision moves a team up this curve on its own — what moves it is changing what "done" actually means, and holding that line when it's inconvenient.
Whatever you build data on has to survive the systems underneath it changing — because they will. A layer that only works while the source stays still isn't a foundation, it's a liability with a delay on it.
And honestly — most organisations can't actually see where most of their own domains sit on this curve today. That's not a failure, it's just the starting point. You can't climb what you haven't measured.
Data isn't a competing function. It's the missing half of product.
Want to see where your own team actually sits, across five dimensions rather than one guess?
Try the assessment →