Product, Design and AI

Marty Cagan and Bob Baxley argue that in the Generative AI era, strong product managers and product designers become more essential, not less, but only when those roles are defined by their specific, demanding skill sets. The product manager is responsible for value and viability, built on product sense spanning customers, data, market, business, and product knowledge. The product designer owns the user experience, grounded in design sense across service design, information architecture, interaction, visual, and industrial design. The authors stress that these roles collaborate closely in product discovery, alongside the engineering tech lead, to determine the right thing to build. Their point is that faster tools only help when paired with strong judgment in both roles.

01Key takeaways

• Treat product management and design as distinct disciplines, each requiring deep specialized knowledge rather than generic skills.
• Judge a PM by their ability to assess value and viability, not by document creation or backlog management, which are comparatively easy.
• Use fast prototyping, including AI-powered live-data prototypes, to discard weak ideas within minutes or hours.
• Test usability and user value separately, since users who can use a product may still choose not to.
• Earn stakeholder trust by walking them through prototypes personally rather than relying on written requirements.
• Avoid feature teams in which the PM role is reduced to project management; the model only works with empowered teams.

02Key sections

The empowered product team

An empowered team pairs a product manager, a product designer, and engineers, with the first three focused on discovery and all engineers on delivery. Feature teams, where the PM is merely a facilitator, do not fit this model.

Product manager responsibilities and product sense

The PM ensures solutions are valuable to customers and viable across business functions. Product sense rests on customer, data, market, business, and product knowledge that few other team members possess.

Product designer responsibilities and design sense

The designer owns the end-to-end user experience, built on five design disciplines. Recognizing good design is far easier than knowing how to create it.

Problem and solution discovery

Leaders set strategy, while the team quickly understands the problem and then uses prototypes to test ideas for usability, value, viability, and feasibility. Many ideas fail once fleshed out, which is the point of prototyping.

True cross-functional collaboration

Each role shapes solutions from a different lens, and the authors argue that empowering a team without these skills sets it up to fail. Triple-threat people are rare and should not be assumed.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.