By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres and Petra Wille push back on the hype around the 'product builder' trend, arguing that whether product managers should code or vibe code is the wrong starting question. They suggest first asking whether the activity is enjoyable and whether one has enough experience to do it well. The conversation stresses that organizational setup, not tooling, determines whether AI empowers a team or produces chaos. They also separate three layers of AI's impact (personal productivity, team process, and product strategy) that are often confused, and argue that discovery still requires talking to customers.
01Key takeaways
- Ask whether building is enjoyable and whether you have enough experience before deciding if you should build.
- Treat product building as a tool in the toolbox, letting people opt in based on interest and skill.
- Assess organizational readiness before adopting AI tools, since setup determines whether outcomes are empowering or chaotic.
- Distinguish personal efficiency gains, team process changes, and product strategy impacts, and respond to each separately.
- Watch what teams do with time freed up by AI, since it reveals whether they are output-oriented or outcome-oriented.
- Keep talking to customers in discovery; AI should deepen that work, not replace it.
02Key sections
- Rethinking the coding question
- The hosts argue that asking whether PMs should code is the wrong question. Instead, personal enjoyment and existing skill should guide who on a team takes up building.
- Organizational readiness
- A well-structured org can use AI to strengthen its work, while a poorly set-up one turns the same tools into chaos. This makes readiness a leadership problem rather than a tooling one.
- The design system trap
- AI can make weak decisions look polished on the surface, so executives see the shine while engineers inherit the underlying mess.
- Three layers of AI impact
- Personal productivity, team process change, and product strategy form distinct stacks that need different responses. Mixing them up causes confusion.
- Discovery still matters
- AI can help teams go deeper in research, but it does not replace the fundamentals of discovery, which still require direct conversations with customers.
03From the post
“Listen to this episode on: Spotify | Apple Podcasts Is the "product builder" trend the future of product management—or just the latest thing everyone thinks you should be doing? In this episode, Petra Wille and Teresa Torres push back on the hype. They dig into whether product managers should be”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.