The job of a product manager is, in large part, the job of having uncomfortable conversations on behalf of the product. Some are easy: explaining a launch to a partner team. Some are not. The five conversations below are the ones almost every PM avoids until they have to be had badly. The ones who learn to have them well are the ones who get promoted.

This article distills practical scripts for each conversation, building on Eira Hayward's Mind the Product piece on difficult conversations in product leadership, with the addition of concrete language you can borrow.

The pre-work that makes every difficult conversation easier

Before any of the five conversations, three things matter more than the words you choose:

  • Know the facts cold. Numbers, dates, decisions made and who was in the room. Bring evidence, not opinion.
  • Check your assumptions. What are you bringing to this conversation that may not actually be there? Often, the other person is calmer than you predict.
  • Have a goal beyond "survive the meeting". What does success look like an hour after? A week after? Anchor to the post-meeting state, not the meeting itself.

The more information you can give, the more you can lay out the situation, the better.

Conversation 1: Sunsetting a feature

The hardest internal version: the team built it, customers depend on it, and you are pulling the plug. The hardest external version: customers who built workflows around it have to migrate.

Script anchor

"I want to share a decision we have made and give you the reasoning. We are sunsetting [feature] on [date]. The reason is [specific business decision tied to strategy]. Here is what this means for [you / your team / your customers], here is what we are doing to support the transition, and here is what we are asking from you. I want to acknowledge that this is a loss, and I am open to any questions or concerns you want to raise now."

The key moves: name the decision, give the why, name the impact, offer support, acknowledge the loss. Acknowledging the loss is the step most PMs skip. People grieve when things end. Skipping it makes them grieve harder.

Conversation 2: Telling another team their request will not make the roadmap

The relationship matters as much as the message. The team asking has reasons. Their reasons might be excellent. You still have to say no.

Script anchor

"Thank you for bringing this. I understand why it matters to your team and to [your stakeholders]. We have considered it against the current roadmap and it is not making this quarter. The reason is [strategic priority that is higher OR specific blocker]. Here is what I can offer instead: [smaller version, different timeline, or alternative approach]. If circumstances change, here is what would need to be true for us to reconsider."

The key moves: thank them, acknowledge the validity, name the decision, give the reason, offer a partial path. Never end on a flat no. Always leave a window, even a narrow one.

Conversation 3: Telling leadership they will not like the answer

The temptation is to soften the message until it is meaningless. Leadership noticed the softening and trusts you less the next time.

Script anchor

"I want to give you the honest read on [topic]. The data shows [specific finding]. This is not what we expected when we set the strategy. The implication is [what this changes]. I have three options for how to respond: [option A with tradeoffs], [option B with tradeoffs], [option C with tradeoffs]. I recommend [option] because [reasoning]. I want to be clear that any of these involves a tradeoff. There is no clean answer."

The key moves: deliver the finding directly, name the implication, present options with tradeoffs, recommend, acknowledge the difficulty of the choice. Leaders trust PMs who can hold complexity without flinching.

Conversation 4: Performance or letting someone go

The conversation most PMs delay. The delay is itself harmful: the person you are protecting from a hard message is being kept from the feedback that would let them improve or move on.

Script anchor

"I want to be direct with you about your performance in [area]. The expectation is [specific behavior or outcome]. The pattern I have observed is [specific behavior with examples]. I am sharing this because I want to give you the chance to address it. Here is what I would need to see in the next [timeframe] for us to stay on the same path. I am committed to supporting you with [specific support]. I want to be clear that if the pattern continues, the next conversation will be about [consequence]. What questions do you have?"

The key moves: name the gap, give specific evidence, define what success looks like, commit to support, name the consequence, invite questions. Vague feedback ("you need to step up") is unfair. Specific feedback with evidence and a path forward is professional.

Conversation 5: Telling someone they did not get the promotion they wanted

The risk is the person leaves angry. The bigger risk is they stay and disengage.

Script anchor

"I want to talk about the promotion decision. The decision was [yes/no]. I know you were hoping for [outcome]. The reasoning was [specific factors that drove the decision, focused on what is in their control to change]. Here is what I would want to see for the next cycle: [specific behaviors or outcomes]. I want to be clear that this is not a question of whether you are valued. It is a question of [specific gap]. What questions do you have? And how can I support you between now and the next cycle?"

The key moves: state the decision quickly, acknowledge their hope, give specific reasoning, give a path forward, separate the decision from their value, invite questions, offer support. The conversation goes wrong when the PM avoids specifics out of kindness. The kindness is in the specifics, not in the vagueness.

Common failure modes across all five

  • Cushioning until the message is lost. Bad news delivered through five sentences of context arrives confused. Lead with the message.
  • Apologizing the message away. "I am so sorry to have to say this" makes you feel better. It does not help the other person.
  • Filling silence. After the message, let silence sit. The other person needs time to process. Most PMs talk through that processing time and dilute the conversation.
  • Negotiating in the moment. If pushback comes, do not improvise concessions. "I hear that. Let me think about what you raised and come back to you tomorrow" is professional.

The single biggest mindset shift

Most PMs treat difficult conversations as something to survive. The mindset shift that changes everything: treat them as a service to the other person. The discomfort is real. The alternative (vagueness, delay, silence) is worse for them, not just for you.

The takeaway

Five conversations come up in every PM career: sunsetting features, declining other teams, delivering hard truths to leadership, performance feedback, denied promotions. The scripts above are starting points, not formulas. Run them through your own voice, but keep the structure: name the message clearly, give the reasoning, define what comes next, acknowledge the difficulty, invite questions. Do this well a few times and you become the PM other people seek out for hard conversations, instead of avoiding them.