Self-serve data sounds like a great idea until you actually hand someone a warehouse and a login. Access was never the problem. Comfort was. Every team I've worked with already has more data than anyone's looking at, and most of it goes untouched. It isn't locked away.
I'm not technical. I don't want to be. What I care about is behaviour: why someone uses a product the way they do, in the context they use it in. For most of my career, if I had a hunch about that, I'd write it down, do some user testing, check GA, take it to an analyst, wait, and hope the question I asked was still the one that mattered by the time the answer came back. That gap, between having a hunch and being able to check it, is where good instincts go to die quietly in a backlog.
Databricks is the first tool that's actually closed that gap for me. I can ask a question in plain language and get a query back. I can drop into a notebook someone else built and just read it, no fear of breaking anything. I can build a dashboard I actually understand because I built it, instead of inheriting one where I don't know what half the filters are doing. None of that required me to learn to code. It required the tool to meet me at the level of curiosity I already had, instead of demanding a level of technical fluency I was never going to reach.
That's the actual case for self-serve data, and it's narrower than the hype suggests. It isn't "give everyone a warehouse and productivity will follow." It's: if you want people to actually understand the systems they're designing for, instead of inheriting a version filtered through someone else's dashboard and someone else's assumptions about what's interesting, you have to make asking a question as cheap as having one.
Comfort is the design problem here, which is maybe why this is the tool that got me, of all people, excited about data. I've spent a career arguing that good tools remove the tax between a person's intent and their ability to act on it. Self-serve data is the same argument, applied to curiosity about a system instead of curiosity about a screen. The question isn't whether self-serve data is good, more people understanding the systems they're part of is always good. The question is whether we're building the on-ramp for people like me, who were never going to take a SQL course, or just handing out warehouse keys and calling it done.