📊 Stakeholder Updates

Draft a Delay Announcement That Maintains Trust

Writes a delay announcement that acknowledges the slip honestly, explains the cause, and commits to a new date. Built for PMs who need to communicate bad news without destroying stakeholder trust.

This prompt drafts a delay announcement following a 4-part structure: acknowledge the slip, explain the root cause, commit to a new date, and list what we are doing differently. It avoids defensive hedging that erodes trust.

When to use this prompt

Use this when a committed date will slip and you need to tell stakeholders before they find out another way. You will need the original commitment, the new expected date, the root cause, and the mitigation plan. The prompt forces honest language; defensive or vague announcements damage trust more than the delay itself. It is most useful when you are telling execs or customers about a public commitment that will slip. For internal-only delays with no external visibility, a Slack message is usually enough; reserve the full structure for higher-stakes situations.

The Prompt

Role: Product Manager Variables: {{original_commitment}}, {{new_date}}, {{root_cause}}, {{mitigation}}, {{audience}}, {{promises}}

You are a product manager drafting a delay announcement. The message must acknowledge the slip honestly, explain the cause, commit to a new date, and describe what you are doing to reduce the chance of recurrence.

Original commitment: {{original_commitment}}
New expected date: {{new_date}}
Root cause: {{root_cause}}
Mitigation: {{mitigation}}
Audience: {{audience}}
What customers or stakeholders were promised: {{promises}}

Produce the announcement in this exact structure:

1. ACKNOWLEDGE (1-2 sentences) — State the delay plainly. Name the original date and the slip. No softening language like "we wanted to update you on timing."

2. ROOT CAUSE (3-4 sentences) — Explain what actually happened. Include the specific cause (technical, resourcing, scope change, dependency). Avoid blame. Do not use phrases like "unforeseen circumstances" or "unexpected challenges."

3. NEW COMMITMENT (1-2 sentences) — State the new date. Be specific. If you need a range, give it ("between May 15 and May 22"). Do not say "as soon as possible."

4. WHAT WE ARE DOING DIFFERENTLY (2-3 bullets) — Specific actions to reduce the chance of another slip. Not vague commitments; concrete things the team is doing.

5. WHAT YOU CAN DO (if applicable) — If there is anything the audience can do to help (approve a tradeoff, unblock a dependency, provide feedback), state it clearly.

6. QUESTIONS — Invite follow-up with a specific contact.

Tone rules:
- No corporate euphemism.
- No blaming individuals or teams.
- No overcommitting to recover time.
- Do not pad with apology; 1 honest acknowledgment is enough.
- If the delay was caused by a PM mistake, own it in the root cause. The trust hit from hiding is worse than the trust hit from owning.

Example Output

Subject: Update on Invoice Export Delivery Timing

Team,

**Delivery slip: Invoice export is moving from April 30 to May 14.**

Root cause: During beta testing we found that exports over 50,000 rows hit memory limits in our PDF generation library. The fix requires switching to a streaming approach rather than building the whole PDF in memory, which adds two weeks of work. We caught this because three beta customers have datasets large enough to trigger the issue; without beta we would have shipped a broken feature to all customers.

New commitment: We will deliver to general availability on May 14. Beta customers will get a patched streaming build on May 7.

What we are doing differently:
- We added a "large dataset" test case to our release gate for all export features.
- We brought in the SRE team early to review memory patterns for any new PDF generation work.
- We are extending beta to one more customer with a 200k row dataset to stress-test the streaming path.

What you can do: If you have customers pushing for the April 30 date, feel free to share this update directly. We can also join a customer call if needed.

Questions: Reply to this thread or message me directly. I will respond within 4 hours during business hours.

— [Name]

Recommended Tools

Google Workspace (Gmail or Docs) is the right delivery channel when the delay affects executives or customers. Notion projects keeps a permanent record of the delay announcement for future reference and post-mortems. Linear tracks the updated commitment so the team stays aligned. Use all three: Google Workspace to announce, Notion to log, and Linear to re-plan.

Google Workspace73/100 Notion Projects76/100 Linear74/100

Frequently Asked Questions

When should I use this prompt?

Use it as soon as you know a committed date will slip by more than a few days, and before the audience notices on their own. Delayed communication compounds trust damage. For small slips (less than a week), a shorter message is usually sufficient. Use the full structure for delays that will be visible externally, that affect customer commitments, or that involve executives who approved the original date. The shorter the time between the decision to slip and the announcement, the less trust damage the delay causes.

What if the root cause is embarrassing?

Own it clearly but without self-flagellation. A single honest sentence about the mistake is more credible than paragraphs of defensive framing. For example, 'We underestimated the scope during planning' is better than 'unforeseen technical complexity emerged.' If the cause was a PM error, say so; if it was an engineering miss, be specific without naming individuals. Stakeholders respect ownership. The trust hit from hiding or softening is always worse than the hit from owning; anyone who has been around long enough to matter has seen their own share of slips.