Product Builder Myth

Show notes

Show Notes:

Why "should product managers code?" is the wrong question
Is it fun for you? Do you have enough experience to do it well? Two better questions to start with
What a well-set-up org looks like vs. one that's headed for chaos
The design system trap: why AI makes bad decisions look good on the surface
Output-oriented muscle memory: what teams do with time freed up by AI reveals where they really are
The three layers of AI's impact: personal productivity, team process, and product strategy — and why they're different stacks
Why discovery still requires talking to your customers (sorry)
The real takeaway on product builders: not everyone has to build, but everyone can if they want to

Key Takeaways:

The product builder trend isn't a mandate — it's a tool. Let enjoyment and skill guide who on your team leans into it.
AI can make unskilled work look polished. That's a feature and a bug — executives see the shine, engineers inherit the mess.
Organizational readiness determines whether AI empowers your team or creates chaos. That's a leadership problem, not a tooling problem.
Don't conflate the three layers: personal efficiency, process change, and product impact require different responses.
Discovery fundamentals haven't changed. AI helps you go deeper, not skip the work.

Quotes:
"Just because I can do it — is it something I enjoy doing? And do I have enough experience to really get into the flow?" — Petra

"It's a tool in our toolbox. We can decide who on our team has fun with it, wants to do it, wants to contribute." — Teresa

Resources & Links:

Mentioned in this episode: