Product managers should evaluate every initiative as if they were investing their own capital. This shifts focus from a "feature factory" to outcome-driven management, ensuring resources are allocated to the highest-impact work and treating the product like a mini-company with its own P&L.
The Chief Product Officer shouldn't just execute the company vision; they should be a key partner to the CEO in drafting it. Since company strategy is often inextricably linked with product strategy, the CPO is crucial for translating long-term vision into an actionable, product-led plan.
To decline lucrative but strategically misaligned deals, create a "reverse business case." Instead of only arguing against the revenue, quantify the long-term costs of complexity, maintenance, support, and diluted focus. This data-driven approach provides a compelling rationale for saying no.
The trend of combining CPO and CTO roles is driven by the increasing need for deep tech understanding in product (especially AI). Whether to unify the roles depends heavily on the CEO's willingness to manage the inherent conflict between product and tech, and the company's strategic needs.
Product managers often jump to the next new feature without validating past work. Implement "reverse traceability" by systematically reviewing initiatives from 6-9 months prior. This practice ensures teams check if past work delivered its expected results, fostering accountability and learning.
While AI will alter PM-to-engineer ratios, its more profound impact will be blurring traditional boundaries between product, UX, and engineering. Product managers will increasingly use AI to generate designs and prototypes directly, forcing a more integrated model of collaboration.
Assess a candidate's ability to handle ambiguity by asking for real-world examples of a success and a failure. The key is to deeply probe their decision-making process for both—not the outcome—focusing on how they gathered data and made choices when information was scarce.