Why Data Product Management Is Nothing Like Software Product Management

And the five competencies you need to succeed

Photo by Damir Omerović on Unsplash

After watching my carefully built analytics platform sit unused because it didn’t actually solve user problems, I knew I needed to change my approach. But I wasn’t sure what that meant in practice.

I understood software product management. Talk to users, define requirements, prioritize features, work with engineering, ship products, measure outcomes. That playbook had served me well in previous roles.

But data products felt different in ways I couldn’t quite articulate. The technical conversations were more complex. The stakeholders spoke different languages. The success metrics were harder to define. And my usual frameworks kept hitting unexpected obstacles.

Image by Author.

I remember sitting in a planning meeting discussing our rebuilt analytics platform. My engineering lead asked what seemed like a simple question: “What’s the acceptable data latency for this use case?”

I had no idea. Was an hour okay? A day? Real-time? I didn’t even know what questions to ask to figure it out.