『AI Tools Don’t Make You a Better Product Manager』のカバーアート

AI Tools Don’t Make You a Better Product Manager

AI Tools Don’t Make You a Better Product Manager

無料で聴く

ポッドキャストの詳細を見る
Does knowing how to use AI make you better at product management, or just better at using another tool? In this episode, Joe Ghali, Ryan Cantwell, and Todd Blaquiere dig into what AI competency should really look like for product managers. They talk about why completing training or knowing your way around ChatGPT, Claude, Figma, GitHub, or SQL is not the same as having sound product judgment. The real test is whether those tools help you make better decisions, create clearer outcomes, and focus on problems worth solving. The group also gets practical about how deep PMs should go with technical tools, why AI has made ideas cheap, and why leaders should measure impact instead of usage. More prompts and more tokens do not automatically mean more value. Good judgment still matters. So does knowing when to use the tool, when not to, and how to tell whether the output is any good. If your team is racing to prove it is “AI ready,” pull up a chair on the porch, rethink the scorecard, and listen for what still separates strong product work from shiny tool use. Introduction and Episode Setup [00:00] AI math - Todd argues that AI hasn’t changed how teams define and measure value. [00:31] Depth question - Joe introduces how deeply product managers should understand AI and technical tools. [01:15] Tooling debate - A conversation with a colleague sparks the episode’s central question. Tools Don’t Make the Product Manager [01:52] Jira test - Writing user stories in Jira doesn’t make someone a product owner. [02:13] Roadmap test - Knowing Aha! doesn’t automatically make someone a strong product manager. [02:40] AI extension - Joe asks whether using Claude to create product artifacts changes the answer. [04:01] Tools as enablers - Ryan explains why knowing the job matters more than owning the tool. [05:52] Stethoscope analogy - Todd shows why access to professional tools doesn’t create professional judgment. Measuring Real AI Competency [06:16] Competency challenge - Organizations want AI-literate PMs but struggle to define or measure proficiency. [06:54] Checkbox training - Course completion can create the appearance of competency without proving practical skill. [08:17] Experience matters - Todd argues that real capability comes from using tools on real work. [09:07] Learning the edges - Video editing teaches Todd how practice reveals a tool’s limits. [10:14] Two kinds of knowing - Watching training and building through experience produce very different capability. Outcomes, Discernment, and ROI [11:14] Evaluator problem - Leaders with limited AI knowledge may still be responsible for judging its use. [12:24] Vanity metrics - Counting tokens or tool activity says little about whether better work happened. [12:48] Pivot-table magic - Ryan recalls how basic Excel knowledge once looked like wizardry to executives. [13:28] Confident outputs - Polished AI answers can mislead leaders who don’t know how to challenge them. [14:31] Discernment skill - Product people must learn to evaluate AI output, not simply generate it. [15:07] Same equation - Teams should define the objective, apply AI, and measure whether results improve. [17:42] Tool business case - AI software should face the same cost and ROI questions as any other tool. AI, Strategy, and Product Focus [19:44] Product replacement debate - Ryan rejects the idea that AI can simply turn engineers into product managers. [20:13] Build everything - Todd imagines removing product oversight and letting every function create its own tools. [21:38] Strategy means focus - Ryan explains why unrestricted building is the opposite of a strategy. [22:17] Output isn’t growth - More products and features don’t guarantee revenue, adoption, or customer value. [23:18] Do less to grow - The group argues that focus often creates more growth than added activity. [24:13] Ideas are cheap - AI makes concepts and prototypes plentiful, but worthwhile problems remain scarce. [25:27] Making the diamond - Product judgment applies focus and pressure to problems worth solving. [26:29] Building isn’t enough - Successful bets still need marketing, sales, and operational support. [27:40] Roles versus titles - Todd defines the accountabilities a product organization needs regardless of job titles. Depth Check: How Deep Should PMs Go? [29:14] Depth Check begins - Joe asks how deeply PMs should understand specific technical tools and concepts. [30:04] GitHub knowledge - The hosts debate whether PMs need branching and merge-conflict experience. [31:19] Conceptual fluency - PMs should understand GitHub workflows without necessarily managing repositories themselves. [35:25] Figma prototypes - PMs can go deeper in prototyping because visuals help stakeholders react to ideas. [36:41] Design boundaries - Designers still protect design systems and consistency while PMs create early concepts. [37:19] SQL depth - AI can write queries, but PMs still need enough knowledge to assess requests ...
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません