Your career history isn't holding you back. You are.

That's the AI paradox hiding in your CX stack. Tickets close. Customers leave. And most teams don't see it coming because they're measuring the wrong things.

Efficiency metrics look great on paper. Handle time down. Containment rate up. But customer loyalty? That's a different story — and it's one your current dashboards probably aren't telling you.

Gladly's 2026 Customer Expectations Report surveyed thousands of real consumers to find out exactly where AI-powered service breaks trust, and what separates the platforms that drive retention from the ones that quietly erode it.

If you're architecting the CX stack, this is the data you need to build it right. Not just fast. Not just cheap. Built to last.

See the data

👋 Hey Friends!

I've written about this before.

The idea that your background outside of product isn't a liability. That the 5 years in customer success, the decade in finance, the time spent in marketing or ops or support, aren't things to apologize for. That they're actually the thing.

I still believe all of it.

But something shifted for me on Saturday, and I want to tell you what it was.

I was at the Monday Girl Summit, listening to a panel of women who've completely reinvented their careers. Banking to beauty. Journalism to communications. Twenty years in advertising, then talent management. None of it was planned. Every single story started with circumstances shifting, one small thread of interest, and a choice to keep pulling.

One speaker stopped me cold: "Don't negate your abilities just because they're in a different context. Skills aren't job-specific. You're good at things beyond your particular role."

Another: "Pull those little strings and see where they go."

And another, on what finally made her move: "What's going to happen if you do it vs. if you don't?"

I've said versions of these things in this newsletter before. Hearing them out loud, from women who'd actually lived it, across completely different industries, made me want to say them again more clearly.

This isn't a new topic. It's a reminder that keeps being true.

Product management is fundamentally about understanding what people need and why. If your previous role put you in proximity to customers, whether in CS, sales, support, or operations, you have something most aspiring PMs lack: direct exposure to real problems. Reframe it that way. "I spent 3 years in customer success talking to users about what broke and why" is more powerful than any certification.

If you're not sure what to include: Write down every time in your previous role you had to understand someone's problem before solving it. That's your raw material.

Product managers don't build things. They align people to build things. If your past role required you to work across teams, manage conflicting priorities, or get buy-in without formal authority, you've already done the hardest part of the job.

If you did this in a previous role: Don't just list it. Describe the friction. "I worked with 4 teams who had different goals and helped them reach alignment on X" shows judgment, not just activity.

The best PMs I've seen in fintech came from finance. The best PMs at health companies came from healthcare. The best PMs at B2B tools came from the teams that used those tools. Your domain knowledge isn't a consolation prize. In many cases, it's the reason you're qualified when other candidates aren't.

If you're not sure how to position it: Answer this question: What do I know about this problem or this user that someone without my background wouldn't know? Build your narrative around that answer.

Skills are specific. Behaviors are portable. "I know Salesforce" is a skill. "I know how to learn a new tool fast when the job requires it" is a behavior. Behaviors are what PMs actually hire for. Look through your history for examples of: learning fast, navigating ambiguity, influencing without authority, recovering from failure. Those are the stories worth telling.

One of the summit speakers called this "pull on passion strings and see where they go." You don't need a full reinvention plan. You need one honest next move. A side project. A conversation. A role that's 70% what you've done and 30% closer to where you want to go. The path doesn't have to be linear. It just has to keep moving.

Career reinvention doesn't require a blank slate. It requires a reframe. The skills you built before product are evidence, not baggage. The only thing standing between you and the pivot is how you're presenting what you already know.

You're not starting over. You're translating.

P.S. At the summit on Saturday, someone came up to me and said the newsletter had been genuinely helpful for them. I'd actually met her at the same summit a year ago, when I was just getting started. That moment is kind of what this whole issue is about. You don't need to have it figured out to start. You just have to start.

If you want a thinking partner while you're figuring out how to position your background for a product role, I do that in 1:1 sessions on ADPList. Book a free session here.