Tying a PM's success to getting their project approved creates perverse incentives. Instead, frame discovery as a team effort to find the right opportunities. This encourages rigorous, unbiased investigation and celebrates killing bad ideas, not just launching new ones.

As AI tools automate coding and prototyping, the product manager's core function is no longer detailed specification writing. Instead, their value multiplies in judging, facilitating, and making the right strategic decisions quickly. The emphasis moves from the 'how' of building to the 'what' and 'why,' making decision-making the critical skill.

The eight elements of reasoning—purpose, question, information, assumptions, inferences, concepts, implications, and point of view—from Paul and Elder's model directly map to core product management responsibilities, offering a structured approach to critical thinking.

The core job of a Product Manager is not writing specs or talking to press; it's a leadership role. Success means getting a product to market that wins. This requires influencing engineering, marketing, and sales without any formal authority, making it the ultimate training ground for real leadership.

As AI automates routine tasks like writing specs and managing backlogs, the core responsibility of a PM will shift entirely to exercising judgment. This involves evaluating a high volume of potential product changes for their strategic fit, brand impact, and long-term sustainability.

A product manager's primary role is not just managing roadmaps but injecting courage into the team. This means making unpopular decisions, like scrapping a project after months of work, to ensure the team is always building the right thing, even when it's difficult or requires challenging leadership.

While engineers focus on what's feasible, a PM's job is to be the dreamer, pushing for the ideal user experience even when told it's too hard. This 'unreasonable' conviction forces the team to find creative solutions and prevents settling for mediocrity.

Beyond speaking the same language as developers, an engineering background provides three critical PM skills: understanding architectural trade-offs to build trust, applying systems thinking to break down complex problems into achievable parts, and using root-cause analysis to look beyond user symptoms.

Unvalidated product ideas often originate from executive leadership or adjacent departments. A product manager's critical role is to use disciplined stakeholder management and clear communication to maintain focus on solving validated user problems, rather than simply executing on top-down directives.