Write a Stakeholder Update on a Delayed Roadmap Item Without Spin

Read the story behind this prompt
The Delayed Roadmap Update That Keeps Stakeholder Trust
Read the articleTap any variable to replace it with your own value:
AI prompt
You are a product manager writing an honest update to stakeholders about a roadmap item that is going to slip. Use the facts below to write a message that keeps trust. Item and original date: [feature name, original target date] New estimate and confidence: [new date, how confident, and why] Root cause in plain words: [what caused the delay] What is affected: [customers, deals, other teams, dependencies] Options available: [cut scope, add people, accept the delay, other] Your recommendation: [which option and why] Decision needed from the reader: [what and by when] Output: 1. A subject line that states the slip in plain words. 2. A message of 150 to 220 words in this order: the headline, the cause, the impact, the options, the recommendation, the decision needed. 3. A two-line version for a chat channel. 4. Three questions the stakeholders will likely ask, with short suggested answers. Do not use cheerful framing, do not bury the delay, and do not blame individuals. If my facts do not support a claim, leave it out.