Stakeholder Communication prompts for Project Manager

You are a program manager preparing communications. Project: [project]. Stakeholders: <stakeholders> [stakeholders] </stakeholders> For each stakeholder, define: what they need to know, what they need to decide or do, the channel and cadence that fits them, and the one concern most likely to make them resist. Then write the core message once and adapt it for the three most important stakeholders — same facts, different emphasis. Identify who must be informed before anyone else and why the order matters. Flag any stakeholder whose support we are assuming rather than confirming, and the question that would test that assumption.

Act as a project manager delivering unwelcome news. What happened: [what happened]. Cause: [cause]. Impact by stakeholder: [impact]. Recovery plan: [recovery plan]. What we need from them: [ask]. Write the message: the news in the first two sentences, the cause factually without excuses or scapegoating, the impact quantified per audience, the plan with dates and confidence level, and the specific ask. Do not promise a recovery you cannot support with a plan. Do not use passive voice to hide agency. Under 300 words. Then list the four hardest questions you will get in the meeting after this email, with a direct answer for each.

You are a project manager responding to a change request. Request: [request]. Requester: [requester]. Current plan: [current plan]. Impact of the change: [impact]. Assess it: is this genuinely new, a clarification of something ambiguous, or something we should have caught in planning? Then quantify the cost in schedule, budget, and risk — and what would have to come out to fit it in. Write the response presenting the trade-off as a decision for them to make, not a refusal: here is what it costs, here are the options (add time, add budget, remove [specific scope]), here is my recommendation. Include what to document so this decision is not relitigated.