In every environment I've worked in, there's been pressure to deliver quickly. Ship it, and learn from it once it's in front of people.
So the button goes on the page and we test it works, but we rarely ask whether anyone actually uses it, and almost never whether it's driving the value we expected.
The cause is in the design. Nobody built the data in, so there was never anything to check. In more than twenty years leading data functions, I've seen the same pattern play out everywhere, from a single feature to an entire business. It has five levels: Feature-Focused, Data-Aware, Data-Enabled, Data-Informed and Data-Powered. Most teams sit lower than they'd guess, and most of the climb is a decision made earlier than usual.
Maturity models aren't new. Gartner and CMMI both publish one, and they're worth reading. The difference here is where it starts. Those measure the data function: its governance, process and tooling. This one starts with a single feature, and the decision someone makes while building it.
I've written the framework up in full, and built a two-minute assessment to see where you sit today. It only works if you score where things stand now, not where the roadmap says they'll be.