In partnership with
Your first HR system, implemented right
Rolling out your first HR tool? Get a step-by-step guide to avoid common mistakes, drive adoption, and build a scalable HR foundation.
👋 Hey friends,
Something is shifting in product right now and most people haven’t named it yet.
PMs are designing their own wireframes. Designers are writing code. Engineers are running their own teams of AI agents, setting priorities, writing specs, making product calls that used to belong to you.
The swim lanes we built our careers around are blurring fast.
And I think that’s actually great news. But only if you know how to use it.
The Role Is Expanding, Not Disappearing
There’s a version of this story that sounds scary. If everyone can do your job, what’s your job?
But here’s the reframe.
When the whole team can build, the scarce skill isn’t execution.
It’s judgment.
It’s knowing which problem is worth solving
why it matters right now
and who you’re actually solving it for.
That’s the PM skill. And it’s more valuable than ever.
🧠 Insight: The question is whether you’re leaning into it or still operating like the old swim lanes exist.
What Adjacent Experience Actually Gives You
Most PMs I know came from somewhere else first. CS, support, design, engineering, ops, marketing. And most of them undervalue what that background actually built.
Here’s what it gave you that the role expansion makes critical.
Customer empathy that isn’t theoretical.
If you came from a customer-facing role, you’ve sat with frustrated users. You’ve heard the question behind the question. You know what customers mean, not just what they say. In a world where engineers are making more product decisions independently, someone needs to stay anchored to the customer. That’s not a soft skill. It’s the job.
The ability to translate, not just collect.
You’ve processed feedback from multiple directions, customers, sales, support, leadership, and handed it to a team in a form they could act on. That translation layer is what keeps a fast-moving, blurry-roled team from building the wrong thing confidently. It matters more as teams get more autonomous, not less.
Cross-functional fluency.
If you’ve ever worked in a product-adjacent role, you learned how to work without authority. You figured out how to get engineers, designers, and stakeholders moving in the same direction without being able to tell anyone what to do. That’s not a workaround. That’s leadership. And it scales.
Product depth before you had the title.
The people who know where the product breaks, who’ve lived inside the workarounds and edge cases, walk into a room with context that nobody can manufacture quickly. That depth is a compounding advantage, especially as teams move faster and have less time to slow down and learn.
Like coffee. Just smarter. (And funnier.)
Think of this as a mental power-up.
Morning Brew is the free daily newsletter that helps you make sense of how business news impacts your career, without putting you to sleep. Join over 4 million readers who come for the sharp writing, unexpected humor, and yes, the games… and leave feeling a little smarter about the world they live in.
Overall—Morning Brew gives your business brain the jolt it needs to stay curious, confident, and in the know.
Not convinced? It takes just 15 seconds to sign up, and you can always unsubscribe if you decide you prefer long, dull, dry business takes.
Why 2026 Is the Best Time to Have This Skillset
A few years ago, doing PM work required a PM title. The tooling, the access, the process all funneled through one role.
That’s gone now.
AI tools have collapsed the barrier between having an idea and being able to pressure-test it. You can synthesize customer feedback at scale in minutes. You can prototype without engineering support. You can walk into a roadmap conversation with research, data, and a rough concept that would have taken a team two weeks to pull together two years ago.
The adjacent skills, listening deeply, translating clearly, knowing the customer and the product from the inside, are now multiplied by tools that let you act on them faster than ever.
The PM who came from somewhere else and knows how to use these tools isn’t playing catch-up. They’re pulling ahead.
🎯 Try this: Think about the last big product decision your team made. Could you articulate, in two sentences, what customer insight drove it? If you can, that’s your edge. If you can’t, that’s your work for this week.
The Bottom Line
The role is expanding. The team is getting blurrier and more capable all at once.
In that world, the person who can hold the customer context, translate across functions, and make judgment calls with incomplete information is the most important person in the room.
You’ve been building that person for years.
The title just caught up.
Your challenge this week:
Look at your last three product decisions. For each one, write one sentence that connects it back to a specific customer insight. Not a metric. Not a stakeholder request. A real human problem. If you can do that consistently, you’re already operating at the next level.
See you next Friday,
Stef
💬 Where did you come from before product? Hit reply and tell me. I love hearing the non-linear paths. I read every single one.
P.S. If you’re in a product-adjacent role right now and wondering whether your experience counts, it does. This is exactly what we dig into together on ADPList. Book a free session with me right here: https://adplist.org/mentors/stefanie-brown
📬 Other Newsletters You Might Like
→ The Byte – Fast, punchy tech and AI news
→ Innovate Disrupt or Die – Strategic insights on innovation and disruption
→ Marketing Alec – AI-powered marketing strategies
→ Practical Marketing – No-BS marketing tactics that work
→ Two Dads in Tech – Honest conversations about tech careers and life
→ Cooking Agile – Agile practices made practical
→ Seedradar AI – Startup and AI trends to watch
→ The Centaur – Stay irreplaceable in the age of AI