The AI-Native Product Team: How CPOs Are Rebuilding Their Org Charts

How are Chief Product Officers redesigning their org charts and ways of working to build truly AI-native product teams? In this podcast hosted by Hoda Mehr, Co-founder and CEO of Up My Mojo and a Board Member at Products That Count, Monumental Chief Product Officer Pawan Gaargi will be speaking on building an AI-native product team. As organizations move beyond using AI as a feature-level tool and begin rethinking how products are built, shipped, and managed, product leaders are being asked to reshape processes, decision-making, and collaboration across their teams. Drawing from his experience scaling teams and rebuilding workflows through acquisitions at Monumental and from his early product leadership roots at Zynga, Pawan shares how experimentation, hypothesis-driven thinking, and hands-on leadership are helping teams become AI-native while keeping core product fundamentals like retention, player motivation, and growth metrics firmly in focus.

Join us for new conversations with leading product executives every week. Roll through the highlights of this week’s event below, then head on over to our Events page to see which product leaders will be joining us next week.

Show Notes:

1. Becoming AI-native is less about adopting specific tools and more about rebuilding how teams operate and make decisions.
2. Product leaders today are expected not only to build great products but to rewrite workflows, processes, and org structures for the AI era.
3. Many existing AI playbooks are either too abstract or too narrow; leaders want team-level guidance on how CPOs are changing execution models.
4. AI dramatically reduces the time required to gather insights from sources like community feedback, metrics, and research, allowing PMs to spend more time deciding what to do with insights rather than collecting them.
5. The biggest shift AI creates is freeing capacity for higher-quality decision-making, not replacing product judgment.
6. Strong product teams should approach AI adoption with a hypothesis-driven experimentation mindset, just like product development itself.
7. Product leaders increasingly benefit from getting hands-on with AI tools, even at the executive level, to understand their real capabilities.
8. CPOs are moving closer to IC-style work again—building prototypes, testing ideas, and exploring tools directly—to lead effectively in an AI-accelerated environment.
9. AI expands creative exploration by enabling teams to generate many more viable solution options than before, improving decision quality.
10. AI improves both execution speed and idea diversity, strengthening product discovery and delivery simultaneously.
11. Teams should avoid letting AI “think for them”; instead, AI should accelerate iteration while humans retain ownership of reasoning and judgment.
12. In gaming—and increasingly elsewhere—product success still depends on aligning core loops with user motivations, regardless of AI adoption.
13. AI enables deeper analysis across retention, engagement, and behavioral metrics, allowing teams to identify overlooked opportunities faster, such as new-user retention gaps.
14. Product success metrics themselves have not fundamentally changed because of AI—growth, retention, and lifetime value still anchor strategy.
15. What has changed is the depth and speed at which teams can analyze second- and third-order KPI relationships.
16. Rather than mandating tools, effective leaders create a culture where experimentation spreads organically through shared discoveries across the team.
17. Visible experimentation by leadership helps normalize adoption and signals permission for teams to explore new workflows.
18. Large organizations often struggle with AI adoption because they treat it as a tooling decision instead of a mindset and experimentation challenge.
19. Incentivizing AI usage directly can backfire; success comes from ensuring AI supports core business outcomes rather than becoming a metric itself.
20. The strongest AI-native teams treat adoption as a cultural shift first and a process shift second, allowing capabilities to evolve naturally as tools improve.