What CMS Product Managers Should Care About
Admin panels don't tell you if customers are winning. They tell you if customers are clicking.
At Quantive, we had this gorgeous admin dashboard. It tracked everything you’d expect: seat utilisation, login frequency, feature adoption, and configuration completeness. All of it. And for months, we’d celebrate when those numbers ticked up. More logins. More configured OKRs. More teams onboarded. We felt smart about it.
Then we’d lose a customer who looked perfect on paper.
The Thing Everyone’s Measuring
There’s a comfort in admin metrics. They’re clean. They’re immediate. They’re measurable. When a VP asks “How’s the product doing?” you can point to a chart that goes up and to the right. Everyone nods. Meeting adjourned.
This isn’t new. Every CMS, every enterprise platform, every B2B SaaS product has some version of this dashboard. And they all make the same mistake: they measure the admin experience as if it’s the actual value.
It isn’t.
The admin panel is theatre. It’s the green room, not the stage. Success doesn’t happen there. Success happens when your customer’s business does something different, something better, because they’re using your product.
But here’s what nobody’s saying: most product teams don’t actually know what that “something different” looks like. They’ve never asked. They’ve certainly never measured it.
What Successful Companies Actually Do
I started noticing a pattern with our highest-retention customers. They weren’t necessarily the ones with the highest login counts. Some of them barely touched the admin panel. But they had something else going on.
They’d built rituals around OKRs. Monday morning reviews. Quarterly planning sessions where OKRs were the starting point, not an afterthought. They’d connected their strategic objectives to specific revenue metrics and could show you the line between an OKR shift and a business outcome. One customer showed us how a single objective around customer retention had directly influenced their support team’s workflow redesign, which dropped churn by 8% over two quarters.
That’s not an admin metric. That’s a business outcome that happened to involve our product.
The real indicators of success were: Are they implementing OKRs effectively? Are those OKRs driving measurable improvements in their business? Can we see a connection between strategic objectives and revenue impact?
The companies that renewed and expanded weren’t just using Quantive. They were using it to win in their market. And the way they did it was surprisingly consistent. They integrated OKRs into existing workflows rather than creating a separate “OKR process”. They trained teams on the discipline, not just the tool. They made OKRs visible (literally, in some cases, with dashboards in common areas). They argued about them. They changed them when they weren’t working.
Actually, that last bit is important. The best customers changed their OKRs mid-quarter when reality shifted. The worst ones set them once and never looked back. One was adaptive; the other was performative. Same product, wildly different approaches.
And here’s something else: these successful companies almost always had dedicated Customer Success support. We’d assign a CSM who’d spend weeks, sometimes months, helping them build the discipline. The product alone didn’t create that OKR culture. It took someone who understood both the tool and the methodology to help teams navigate the awkward early phases, challenge their assumptions, and model what good looked like. Success wasn’t product-driven. It was product-enabled and people-guided.
The Metrics We Weren’t Tracking
Net Revenue Retention told us which customers would stay. But it took us too long to realise what predicted NRR. It wasn’t feature adoption. It wasn’t login frequency. It was whether the customer had operationalised the OKR discipline internally.
Could we see evidence that OKRs were influencing decisions? Were they referenced in Slack conversations? Did teams adjust roadmaps based on objective progress? Was there a feedback loop between strategic intent and tactical execution?
These weren’t metrics we had dashboards for. We had to dig. We had to talk to customers. We had to ask different questions.
This reminds me of a conversation I had with a customer success lead at a large consultancy. They’d bought Quantive for about 200 users. On paper, adoption was terrible. Maybe 30% of seats were active monthly. But when you looked closer, those 30% were the strategic planning team and executive layer. They were using it religiously to set direction for 10,000 people. The other 170 seats were team leads who logged in quarterly to review objectives and update progress.
Was that bad adoption? Or was that exactly what success looked like for their structure?
We’d been measuring the wrong thing.
Wrap up
Here’s the thing about CMS products, or OKR platforms, or any enterprise tool really: they don’t succeed in isolation. They succeed when they help a customer navigate three interconnected realities.
First, the product itself. How do successful customers configure it? What features do they actually use versus ignore? What integrations matter?
Second, their market. How are they using the product to compete? What advantage does it give them? If they’re in retail, are they using it to coordinate seasonal campaigns? If they’re in enterprise sales, are they using it to align account teams with strategic bets?
Third, their internal dynamics. Who owns the process? How do teams collaborate around it? What governance exists? What rituals have formed?
Most product teams only look at the first dimension. The best ones (or the ones who accidentally stumble into this) look at all three. Because that’s where the patterns are.
A SaaS company and a manufacturing company might both be “successful customers”, but their success patterns will look completely different. The SaaS company might update OKRs monthly and tie them to product velocity metrics. The manufacturing company might update them quarterly and tie them to supply chain efficiency. Both are winning. Both are high NRR. Both use the product differently.
If you only measure admin activity, you’d miss this entirely.
What This Reveals About How We Build Products
The shift here isn’t just about metrics. It’s about what you think your job is as a product manager.
If your job is to increase feature adoption, you’ll build features that encourage logins. You’ll gamify. You’ll send notifications. You’ll add dashboards to the dashboards.
If your job is to help customers win in their market, you’ll build features that connect your product to their reality. You’ll study how successful customers operate. You’ll identify what they do that others don’t. You’ll codify those behaviours into guidance, templates, workflows, or (if you’re ambitious) predictive nudges that help other customers follow similar paths.
This is uncomfortable because it requires you to care about things outside your product. You have to understand your customer’s business model. You have to know their competitive landscape. You have to recognise that your product is a means, not an end.
Part of me still struggles with this. It feels like overreach. Like I’m supposed to be building product features, not studying market dynamics or organisational behaviour. But the customers who succeed don’t separate these things. Why should I?
The Unresolved Tension
Here’s what I’m still figuring out: how do you measure this at scale and in different industries?
It’s one thing to have deep relationships with 20 customers and understand their success patterns intimately. It’s another thing to operationalise that insight across 2,000 customers. You can’t manually study every company’s market positioning and internal rituals. And you certainly can’t assign a dedicated CSM to every account, no matter how much that accelerates success.
But maybe you don’t have to. Maybe you can instrument the patterns. Track the behaviours that correlate with business outcomes. Build feedback loops that surface early indicators of success or failure. Not “Did they log in?” but “Are they exhibiting the patterns we’ve seen in companies that thrive?”
I haven’t cracked this. Neither has anyone else I’ve spoken to. But the companies that figure it out first are going to have a ridiculous advantage. Because they’ll stop optimising for admin engagement and start optimising for customer success in the real world.
Which, honestly, is what we should’ve been doing all along.