Write & communicate

Write a decision-ready executive update

Compress progress, evidence, risk, and the needed decision without hiding uncertainty

4 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Facts and progressRisks and uncertaintyDecision or support needed

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Draft a concise executive update using only the information below.

Facts and progress:
[facts]

Risks and uncertainty:
[risks]

Decision or support needed:
[ask]

Write for a busy senior leader. Lead with what changed and why it matters. Use this structure:
- Headline: one sentence
- Progress: up to three bullets with concrete evidence
- Risks: severity, evidence, and mitigation
- Decision needed: owner and latest useful decision date
- Next checkpoint

Keep facts, forecasts, and recommendations visibly distinct. Do not add invented metrics or confidence.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Facts and progress: On April 1, we exposed the new onboarding checklist to 50% of new workspace users. By April 14, 620 users were eligible: 311 saw the checklist and 309 remained in the control group. Seven-day activation was 44% for the exposed group and 38% for control. Eight user interviews were completed; five participants said the sample project helped them understand the first step. Setup-related support tickets fell from 52 in the prior two-week period to 39 across both cohorts in this period.
Risks and uncertainty: The activation difference has not yet been tested for statistical significance. Tracking for the ‘invite a teammate’ action was missing until April 6. A mobile checklist bug affected 23 sessions on April 9–10 and was fixed on April 10. The analyst will rerun the comparison excluding incomplete tracking windows by April 18.
Decision or support needed: VP Product should decide by April 19 whether to increase exposure to 100% on April 22 or keep the 50/50 test running for one more week.

Example output

Headline

The onboarding checklist shows a six-point activation difference, but incomplete tracking and a resolved mobile bug mean the result is not yet ready to support a full rollout.

Progress

Observed fact: From April 1–14, 311 eligible users saw the checklist and 309 were in control; seven-day activation was 44% versus 38%.
Observed fact: Five of eight interview participants said the sample project clarified the first step.
Observed fact: Setup-related tickets fell from 52 in the previous two-week period to 39 in the current period across both cohorts; the data does not attribute that decline to the checklist.

Risks

High: The difference has not been tested for statistical significance, and “invite a teammate” tracking was incomplete through April 6. Mitigation: rerun the comparison without incomplete windows by April 18.
Medium: A mobile bug affected 23 sessions on April 9–10. It was fixed April 10; the rerun should clarify its effect.

Decision needed

Owner: VP Product
Decision: Increase exposure to 100% on April 22 or retain the 50/50 test for one more week.
Latest useful date: April 19
Recommendation: Keep the 50/50 test until the corrected analysis is available. This is a recommendation, not a forecast.