Work with stakeholders and make decisions by combining quantitative data with qualitative signals.
Making decisions with stakeholders
Data-informed decisions and managing stakeholder pressure
Stakeholders are anyone with an interest in what the product does: executives, sales, customer success, engineering leads, legal, and users themselves. Each stakeholder has a different goal and a different type of influence. Part of a PM's job is to understand what each stakeholder cares about and communicate product priorities in terms they find relevant — a CFO cares about LTV:CAC, a sales lead cares about deal-blocking objections, a support lead cares about ticket volume.
The loudest-voice or HiPPO problem (Highest Paid Person's Opinion) describes a pattern where the person with the most authority — not the most evidence — wins the argument. PMs counter this by bringing data and qualitative discovery signals to every prioritization conversation. "Our data shows X; here is what five customers told us about their experience" is harder to override with gut feel.
Data-informed does not mean data-only. Quantitative metrics tell you what is happening; qualitative signals from discovery tell you why. A drop in activation rate is visible in the funnel — but only user interviews reveal whether that drop is caused by a confusing onboarding flow, a missing integration, or a pricing mismatch. Good PM decisions combine both.
Saying no is a core PM skill. A reasoned no is better than a reluctant yes: explain what evidence you have, which framework you applied, what trade-off you are protecting, and when you could revisit. This turns a rejection into a shared understanding of priorities rather than a power struggle.
Lesson notes
Data-informed decisions and managing stakeholder pressure
Stakeholders are anyone with an interest in what the product does: executives, sales, customer success, engineering leads, legal, and users themselves. Each stakeholder has a different goal and a different type of influence. Part of a PM's job is to understand what each stakeholder cares about and communicate product priorities in terms they find relevant — a CFO cares about LTV:CAC, a sales lead cares about deal-blocking objections, a support lead cares about ticket volume.
The loudest-voice or HiPPO problem (Highest Paid Person's Opinion) describes a pattern where the person with the most authority — not the most evidence — wins the argument. PMs counter this by bringing data and qualitative discovery signals to every prioritization conversation. "Our data shows X; here is what five customers told us about their experience" is harder to override with gut feel.
Data-informed does not mean data-only. Quantitative metrics tell you what is happening; qualitative signals from discovery tell you why. A drop in activation rate is visible in the funnel — but only user interviews reveal whether that drop is caused by a confusing onboarding flow, a missing integration, or a pricing mismatch. Good PM decisions combine both.
Saying no is a core PM skill. A reasoned no is better than a reluctant yes: explain what evidence you have, which framework you applied, what trade-off you are protecting, and when you could revisit. This turns a rejection into a shared understanding of priorities rather than a power struggle.