🧠 TL;DR This Week
Product leaders who've never taken a customer call are building for a customer they've never met
The gap between what a product does and what a customer experiences is always bigger than the roadmap assumes
One afternoon in the queue is worth six months of user research
💬 The Hot Take
If you've never personally handled an angry customer call about the product you built, you don't actually know your product.
📉 Metric of the Week
Companies where product teams regularly engage with customer support data see 2x higher customer satisfaction scores and 30% faster issue resolution times. — Salesforce State of the Connected Customer
Reading support tickets is not the same thing. Sitting in the queue and taking the call is the same thing.
🎙 From the Queue:
I've worked in and around contact centers long enough to spot the tells.
When a product is built by people who've never spoken to a customer, it shows. The IVR menu that makes perfect sense on a whiteboard but is completely baffling at 8pm when someone's flight is cancelled. The escalation path designed for efficiency that creates four extra steps for the agent and three extra minutes of hold time for the customer. The self-serve tool that works great in a demo and falls apart the moment someone has a real problem.
These aren't edge cases. They're the daily reality of every front-line agent handling the fallout from decisions made in rooms they were never invited into.
Here's what actually happens when product leaders take calls:
They hear the language customers actually use.
Not the language on the website. Not the terminology in the help docs. The real words customers use when they're confused, frustrated, or just trying to get something done. That gap alone changes how you write product copy, how you structure help content, and how you design the next flow.
They feel the friction they created.
There is no substitute for personally navigating a process you designed and realizing it takes four steps when it should take one. No amount of user testing data produces that feeling. That feeling is what drives real change.
They build relationships with the people cleaning up their messes.
Your support team knows more about your product's failure modes than anyone in your organization. They've been documenting them in tickets for months. Most product teams have never had a real conversation with them. One afternoon in the queue changes that permanently.
They stop shipping features nobody asked for.
The most common thing a product leader hears on their first day in the queue is a problem they never knew existed. The second most common is a solution that was already requested six months ago and never made it onto the roadmap.
This isn't a new idea. It's just an idea that keeps getting skipped because there's always something more urgent on the calendar.
There isn't. Put it on the calendar.
🛠️ Ops Corner
How to make this actually happen at your organization:
Start with a listen-only session. New product leaders shadow an agent for two hours before they ever handle a call themselves.
Make it recurring. One afternoon per quarter minimum. Not a one-time empathy exercise.
Create a feedback loop. Product leaders who spend time in the queue should be required to submit one actionable observation to the roadmap within two weeks. No observation, no credit.
The contact center is the best product research lab in your organization. Most companies have no idea.
🙋 One Ask
Has a product leader at your organization ever spent time in the queue? What happened?
Reply. The stories in both directions are worth collecting.
