He'd spent months telling his developers to write their own specs with Claude. It had never once occurred to him to write code himself. When it finally clicked — when he realized this wasn't about getting his team to use AI, it was about what he could now build himself — I watched him light up.

Back up a step.

A product leader who worked for me years ago asked to go for a walk last week. He thought he had a job problem. He actually had a time problem ... and not the kind he thought.

His situation will sound familiar. Seasoned PM, good company. His role has quietly shrunk in scope, and the work in front of him isn't the kind he loves. He keeps trying to get his dev team to experiment - to build a few agents for their customers - but they're buried under the roadmap they already owe. They're using AI plenty; just to deliver the existing list faster, not to make something new and different. So he's landed on the same conclusion a lot of smart people are reaching: I need a new job. This one's too limiting. I can't grow here.

I've now heard a version of this story from dozens of product people — first-hand, second-hand, in DMs, over lunch. So if it's you, keep reading. This is the advice I gave him, and I haven't been this excited about anything I've said in a while. This is your moment. I really don't want you to blow it.

It's the most common sentence I hear right now. And here's my honest answer: some of it is real. But most of it is avoidance wearing the respectable mask of being busy.

Staying heads-down feels responsible. It's also exactly how you get stuck in your old reality. When every hour is spoken for, you never get the quiet, unstructured time where you'd realize that the thing you assumed was impossible isn't.

So the first move is uncomfortable but simple: if you make the time, you've just created a competitive edge. Almost no one around you is making it.

Maybe your team doesn't look like his. Maybe your engineers aren't buried at all — they're already building with AI without you. Either way, the move is the same, and if they're ahead, the stakes are only higher: don't be the one off to the side, prioritizing, while everyone else builds. Jump in and find your own expansion.

So here's the reframe: roles and capabilities are collapsing. As a PM, you've spent your career learning to prioritize, to influence, to decide what not to build. That expertise is what will ultimately set you apart — but you already have it.

What you don't have yet is the building muscle. And for the first time, building is actually available to you. You don't only prioritize and influence anymore. You can vibe-code something end-to-end. You can put a working thing in front of your dev team and get them excited to deliver it — and to build more.

That's a different person than the one who shapes, pushes, aligns — and then waits and waits and waits for it to be built.

This is the part that got me really excited - because he's sharp, and watching his blind spots dissolve in real time told me how widespread this is.

One: It had never occurred to him that he could feed the dev onboarding guide straight to Claude and let it do much of the setup itself — getting his local environment up and running. He still had it in his head that he needed a developer's help. He doesn't — and neither do you.

This is what stops most people before they even start: not the building, the setup. The environment, the tooling, the quiet assumption that you need someone technical to get you over the first hill. You don't. And setup isn't the skill you're here to learn — you don't need to master it, you need to get past it. Let AI handle (most of) that part so your energy goes to the building and experimenting that actually matter. Use AI to use AI.

Two: He'd been pushing his developers to write their own specs with Claude — essentially automating his own old job — and never once contemplated doing dev himself. The asymmetry is wild when you say it out loud. He was comfortable letting AI replace the PM. He just hadn't imagined AI expanding the PM.

Three: He actually had the time. The role had gotten easy. And all that slack — the time he could've spent learning — he'd been pouring into a job search. He was using his competitive edge to run away instead of toward.

So here's the prescription I gave him, and it's the same one I'd give you.

Stop the job search for now and redirect that exact energy into getting AI-pilled. And don't just use AI — invent with it. Build one thing, end-to-end, that genuinely excites you: something for your customers that wasn't possible a year ago. Then show your dev team and watch them light up. Use AI to learn AI — let Claude walk you through the parts you don't know yet.

And document everything as you go. What's the same and what's different — in how you approach the work, which skills you actually lean on, where your constraints move and how you get around them. What you're unlearning. What surprises you. What's suddenly possible that you never imagined. All of that becomes your story — the one that earns you the next job, the internal move, or a bigger mandate right where you are. Far more compelling than another bullet about stakeholder alignment.

Give it real chunks of time. A couple hours a day. Three months. You will surprise yourself with what you can accomplish.

What was really limiting him wasn't his job. It was that he couldn't see what was possible from inside his busy, productive, head-down reality. That's the trap. The people breaking through right now aren't the ones with more time. They're the ones reallocating the time they swore they didn't have.

If you've been telling yourself you need to leave to grow ... pause. Your best bet is to build your story right here, right now ... and then see where that takes you.

So here's my love letter, plainly: I've watched you do hard things for years. This is the most exciting moment our field has ever handed you, and it will not wait around. Stop running. Go build something. Then come tell me what surprised you.

Prepared by Amy Wilson, former tech executive and current product strategy advisor. For more insights on leadership and the future of work, subscribe to The Meg and Amy Show.