Email stakeholders about a delayed report and what is safe to use

About this exercise

The monthly KPI report will be late because of a data problem. Write a plain-text email to the leadership team under 110 words with a Subject: line, the new delivery time in the first sentence, and two short sections labeled Safe to use: and Do not use yet:. Don't blame a person, and don't promise a time beyond what the notes say.

Common mistakes when you ask AI for this

• Burying the new time. The AI opens with apologies and the story of the incident. Try: Add: "First sentence: ready Wednesday 4:00 pm instead of 9:00 am."
• Not separating the metrics. The AI says 'some numbers may be off' without naming them. Try: Add: "Safe to use: customer counts, churn, uptime. Do not use yet: revenue, ARPU, disputes."
• Naming people or promising more. The AI credits Priyam or promises a Thursday fallback. Try: Add: "Don't name anyone and promise no other time."
• Leaving the format to chance. The AI picks its own length and layout unless told the exact shape. Try: Add: "Plain text, no bold or headings."
• Trusting the AI to count words. AI is bad at counting. Ask for a total word limit and it often lands over it. Try: Cap each part instead, for example "each line under 15 words."

What a strong prompt includes

• Asks for the new time first
• Gives the two labels
• Names the metrics
• Rules out blame and promises
• Fixes the subject line

Practice this now ↑

Related exercises

• Announce a delay to three audiences with different limits (Leadership AI · Communications and PR)
• Announce one feature separately to admins and to end users (Customer Support & Success AI · Customer success managers)
• Annualize recurring revenue without the one-time fee (Data AI · Finance and accounting)
• Answer "we'll build it ourselves" with their own numbers (Sales AI · Sales and customer success)
• Answer "what does a CSM do for us?" in plain spoken words (Customer Support & Success AI · Customer success managers)