It is a product manager's job to understand the company's financial goals. Instead of waiting for leadership to share this information, great PMs take ownership by actively seeking it out. This means building relationships with finance and other departments to understand the metrics that truly matter to the business.
Executives and investors care about lagging business indicators like ARR and churn, not leading product indicators like user engagement. It is the PM's job to connect the dots and clearly articulate how improvements in product metrics will directly result in moving the high-level business needles.
The traditional "business case" for new features is an outdated exercise. Investors today, particularly in PE-backed SaaS companies, care about unit economics. They want to know how quickly every dollar spent on R&D will be recovered as revenue or profitability, a much more rigorous standard.
When a product improvement is meant to benefit another department (e.g., reduce support tickets), don't just ship it and hope for the best. Create a joint, aligned goal with that department's leader. This ensures they are accountable for accruing the benefit (e.g., reallocating saved capacity) and solidifies your impact.
A product team saved $150 million in margin improvement not by building new features, but by decommissioning a long tail of customized, on-prem legacy products. This "unsexy" work eliminated significant operational drain from support and maintenance, directly impacting the bottom line in a way new features rarely can.
Product leaders often feel pressure to keep executive discussions confidential. However, effective leaders break this norm by immediately sharing and translating high-level business goals for their teams. This transparency empowers individual PMs to connect their daily work to what truly matters for the company's success.
Cascading OKRs through multiple layers (company to department to team to individual) often results in "OKR theater" where the connection to business impact is lost. Instead, an individual product manager's goals should be no more than one link away from a core business objective that leadership cares about.