Lesson up front: Customers don’t buy dashboards or features. They buy the story those features tell. If your product narrative doesn’t make the value obvious, even the most powerful system will struggle.
The Problem
I was leading design on a technically brilliant product. On paper, it was unbeatable: it could mitigate massive threats in real time, deliver forensic-level detail, and impress the toughest engineers and infrastructure security pros.
But something didn’t add up. Acquisition was harder than it should have been, and churn was higher than anyone wanted.
The technology was strong. The problem was the story.
The Wrong Narrative
The portal customers used every day was filled with charts, traffic graphs, and packet statistics. To an engineer, it looked like an impressive control room. To a business leader, it looked like gibberish. And it didn’t communicate the immense value of the product.
What they really needed to see was:
- You’re safe right now.
- This is what we’re actively blocking for you.
- Here’s the risk you avoided.
Instead, we gave them raw telemetry. We were presenting ourselves as a monitoring tool when the real value was protection and continuity.
Not Just a UX Problem
The team tried several things to “fix the UX” before I got involved. Fair. At first glance, it seemed like a UX issue: the interface wasn’t surfacing the right information. Throw another chart up there. Or maybe it needed to be prettier, slicker, “more pop”. Nothing was working. The deeper challenge was strategic.
One “almost there” idea was report export. Surely if they could just put the data in the portal in front of executives, they would see the value. But the reports exported the same data the portal showed. And there was a reason the executives and managers didn’t use the portal.
The product was trying to tell a story about technical sophistication and omniscience. Customers needed a story about business protection. We weren’t aligned on the narrative, and the disconnect was costing us.
Leading the Change
Convincing others of this wasn’t easy. Engineers had built the system for other engineers and believed the metrics spoke for themselves. Product managers and sales were used to framing the solution around features, not outcomes.
I started with workshops and meetings across Product, Engineering, and eventually C-levels. We mapped the customer journey, identifying where our current approach failed to communicate value. Seeing it laid out visually made the gap impossible to ignore: customers couldn’t connect technical data to business impact.
This wasn’t about hiding complexity. It was about elevating outcomes.
The Redesign
We rebuilt the experience to tell a different story—one that led with value instead of data.
- Clear protection status front and center.
- Real-time view of active threats being blocked.
- Context around what those threats meant for the business.
- Sampling and visualization strategies that showed the scope of protection without overwhelming users with raw data.
The portal stopped being a wall of charts and became something far more powerful: proof, in real time, that we were protecting customers’ businesses.
The Impact
The change was immediate. Customers finally understood what the product was doing for them. They immediately saw the value in terms that spoke to them. Retention improved, acquisition got easier, and the feedback shifted:
“It’s not just prettier now. I get it. This product is indispensable.”
That pivot, from utility to service narrative, did more than change the interface. It reshaped how the product was perceived in the market and helped set the stage for the company’s next chapter.
The Takeaway
Every product tells a story, whether you intend it or not. If the narrative is buried in metrics, customers won’t connect the dots. But if you make the value explicit, you can unlock growth that pure technical capability alone can’t deliver.