The transition to a public company drastically changes a PM's role. Every initiative, including experiments, must be backed by data and tied to a clear return on investment. The "build for fun" or "hackathon project" mindset disappears, replaced by rigorous financial justification and frugality.
Public company constraints don't kill innovation; they change its nature. Instead of building solutions from scratch, PMs must prioritize reusing existing internal capabilities and tech stacks from other products within the company. This "plugin" approach maintains velocity while managing resources under public scrutiny.
To avoid getting lost in data, PMs should first define the decision they need to make (e.g., improve ROI, increase usability). This goal then dictates which data to gather and from whom. Patterns should be grouped by desired user outcomes, not feature requests, creating a more strategic path to delivery.
Beyond just using AI tools, the fundamental process of product management is evolving. For every new initiative, PMs must now consider the appropriate level of AI, automation, or customization. This question is now as critical as "what problem are we solving?" and addresses rising customer expectations for adaptive products.
AI initiatives often require significant learning and iteration, which can derail a roadmap. To combat this, PMs should dedicate a fixed percentage of development bandwidth (e.g., 5-10%) specifically for iteration on high-priority AI projects. This creates a structured buffer for discovery without compromising the entire plan.
Mentoring is not just altruistic; it's a powerful tool for self-improvement. When mentees apply a senior PM's frameworks and encounter challenges, it forces the mentor to refine their models, plug gaps, and confirm which patterns are truly repeatable. It's a feedback loop for your own expertise.