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.
Related Insights
Project-based companies operate on a cash flow mindset, accepting any custom work that brings in immediate revenue. A true product company uses an investment mindset, strategically saying 'no' to short-term revenue to invest in building a scalable asset that can win a market long-term.
In ROI-focused cultures like financial services, protect innovation by dedicating a formal budget (e.g., 20% of team bandwidth) to experiments. These initiatives are explicitly exempt from the rigorous ROI calculations applied to the rest of the roadmap, which fosters necessary risk-taking.
Beyond vision and roadmaps, a CPO’s fundamental role is to act as a steward of the company's R&D investment. The primary measure of success is the ability to ensure that every dollar spent on development translates into tangible, measurable enterprise value for the business.
To be truly successful, a product leader cannot just focus on features and users. They must operate as the head of their product's business, with a deep understanding of P&Ls, revenue drivers, and capital allocation. Without this business acumen, they risk fundamentally undercutting their product's potential impact and success.
A one-time meeting with finance is "surface level" advice. To truly build financial acumen, PMs must integrate hard financial targets and business levers directly into their squad's goals. This creates an enduring, operational fluency that informs daily product decisions.
To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.
Product managers often fail to get ideas funded because they speak about user needs and features, while executives focus on business growth and strategic bets. To succeed, PMs must translate user value into financial impact and business outcomes, effectively speaking the language of leadership.
Creating products customers love is only half the battle. Product leaders must also demonstrate and clearly communicate the product's business impact. This ability to speak to financial outcomes is crucial for getting project approval and necessary budget.
A simple but powerful framework for any product initiative requires answering four questions: 1) What is it? 2) Why does it matter (financially)? 3) How much will it cost (including hiring and ops)? 4) When do I get it? This forces teams to think through the full business impact, not just the user value.
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.