7 Things You Should Never Say to Executive Stakeholders
Product managers spend a significant portion of their professional lives communicating with executive stakeholders. These conversations — whether roadmap presentations, strategy reviews, or informal updates — largely determine the PM’s organizational credibility, their ability to advance their priorities, and the degree of autonomy they’re granted to make product decisions.
Some phrases, however well-intentioned, reliably undermine PM credibility with executives. Understanding what these are — and what to say instead — is one of the most practical communication improvements available.
1. “It’s on the Roadmap”
Said to explain why something won’t be addressed immediately, this phrase communicates almost nothing useful. The executive doesn’t know when “on the roadmap” means, whether it’s a commitment or a placeholder, or how to set customer or organizational expectations.
Instead say: “We plan to address this in Q3, which is approximately three months out. I can share more detail about the timing and what we’re prioritizing ahead of it if that would be helpful.”
2. “Engineering Didn’t Build What I Spec’d”
Any sentence that assigns blame for a product problem to another team — especially in front of executives — signals immaturity, not accountability. Product managers own the outcome, including the alignment failure that produced the wrong implementation.
Instead say: “We had an alignment gap between what was specified and what was built. Here’s what I’ve already done to address it, and here’s the plan going forward.”
3. “We Don’t Have Enough Data Yet”
This phrase is often used to defer difficult decisions indefinitely. Executives hear it as “I’m not willing to make a decision” or “I don’t know how to make a decision without perfect information.”
Instead say: “Here’s what the available data tells us, here’s what we’re uncertain about and why, and here’s the decision I’m recommending given this context.” Executives expect decisions to be made under uncertainty; they’re not expecting perfect information.
4. “That’s Not How Agile Works”
Using methodological doctrine to push back against an executive request — even when the request is genuinely problematic — signals rigidity rather than strategic judgment.
Instead say: “Here’s my concern about this request and the trade-offs it would create” — focused on business consequences rather than process violation.
5. “I Don’t Know”
Said alone, without a commitment to find out, this phrase creates anxiety about PM capability without providing any path forward.
Instead say: “I don’t know the answer to that right now. I’ll find out and get back to you by [specific time].” The commitment to follow through transforms an admission of uncertainty into a demonstration of reliability.
6. “Marketing Needs to Communicate This Better”
Any sentence that identifies another function as the reason your product isn’t performing is a credibility problem in an executive conversation. Executives expect PMs to solve problems, not to identify whose fault they are.
Instead say: “We have an opportunity to improve how this capability is communicated to the market, and I’m working with the marketing team on a plan to address it.”
7. “We’re Planning to Release This When It’s Ready”
This phrase communicates no useful information about timeline and signals that the PM hasn’t done the planning required to estimate delivery.
Instead say: “Our current estimate is [specific timeframe]. This could be affected by [known risks]. I’ll update you if that estimate changes significantly.”
Key Takeaways
Executive communication is a PM competency, not just a communication style preference. The phrases to avoid share a common characteristic: they communicate lack of accountability, lack of planning, or lack of business orientation. The replacements share a different characteristic: they demonstrate ownership, specific planning, and awareness of business context. Building this communication discipline consistently is one of the most impactful investments in PM effectiveness.