Stakeholder comms

Stakeholder Comms

Draft the messages PMs dread sending. The formula for all of them: lead with the news, show your reasoning, preserve the relationship, and make the next step concrete. Never bury the point.

Before drafting

1. Ask who the recipient is and what they care about — the same "no" reads differently to a sales lead protecting a deal versus an engineer protecting quality.
2. Ask what the user's actual position is: is this a firm no, a "not now", a negotiation, or a done decision being communicated? The message must not pretend a decision is open when it's closed (cruelest failure mode) or closed when it's open.
3. Ask the medium: Slack, email, or talking points for a live conversation. Match length and formality.

Message patterns

Pick the pattern; all share the spine news → reasoning → what survives → next step.

Saying no to a request:

1. The decision, first sentence, unhedged. "We're not building X this quarter."
2. The real reason, briefly — the tradeoff, not corporate fog. "It would displace Y, which serves 10× the accounts."
3. Acknowledge what's legitimate in their ask — most requests contain a real problem even when the proposed solution is wrong. Name the problem.
4. What you can offer: a workaround, a revisit trigger ("if two more enterprise accounts raise this"), or the criteria that would change the answer.
5. Keep the door open on the relationship, not the decision.

Announcing a delay / de-scope:

1. The news with the new date/scope, first sentence. No "quick update on timelines :)".
2. Cause, honestly and without blaming individuals or teams.
3. What you're doing so it doesn't recur (or an honest "this was an estimation miss").
4. Impact on the recipient specifically, and what you need from them.
5. Never announce a new date you don't believe. A second slip costs 10× the first.

Escalating a blocker:

1. Frame as a decision request, not a complaint: "I need a decision between A and B by [date]."
2. One paragraph of context — the escalation reader wasn't in the meetings.
3. The two (max three) options with costs, and your recommendation.
4. The default: what happens if no decision arrives by the date.
5. Confirm the person being escalated around saw this framing first, or knows it's coming. Ask the user if unsure — surprise escalations burn bridges.

Pushing back on an executive:

1. Steel-man their position first — show you understood the strategic intent.
2. Present the data or constraint they may not have. New information, not re-argued preference.
3. Offer a middle path where one honestly exists; don't invent fake compromises.
4. End with commitment: "If you still want X knowing this, we'll execute well." Disagree-and-commit stated up front, not extracted later.

Workflow

1. Identify the pattern; confirm the user's true position (firm/negotiable/closed).
2. Draft in the user's voice, matched to medium. Default short: hard messages inflate with anxiety padding — cut it.
3. Strip hedges that blur the news ("just", "sort of", "we're thinking maybe"). Keep softeners that serve the relationship ("I know this lands badly for the Northwind deal").
4. Read it as the recipient: what's the first question they'll fire back? Add a P.S.-level answer or prep the user for it.
5. Offer a 2-line and a full version when medium is ambiguous.

Quality bar — self-check

• News in the first sentence. If the first sentence could open a good-news message, rewrite.
• The decision's openness is represented honestly — no fake consultation, no fake finality.
• A real reason is given. "Bandwidth" and "priorities" are fog; the actual tradeoff is respect.
• Something constructive survives: workaround, revisit trigger, or decision criteria.
• No blame laundering. Systems and tradeoffs, not named individuals or "the eng team".
• Anticipates the recipient's first counter.