Write a decision-ready executive update

Autor: AILesson4 Min. EinrichtungszeitGetestet mit:ChatGPTClaudeGeminiGeprüft am: 2026-08-28

Schnelle Antwort

Compress progress, evidence, risk, and the needed decision without hiding uncertainty. Angeben: Facts and progress, Risks and uncertainty, Decision or support needed. Erwartetes Ergebnis: A concise update that tells leaders what changed and what you need.

1

Kontext hinzufügen

Dein Text bleibt in diesem Browser. AILesson Prompts sendet ihn nicht an ein Modell oder einen Server.

2

Dein Prompt

Nicht ausgefüllte Felder bleiben als Platzhalter sichtbar, sodass du den Prompt weiterhin kopieren und bearbeiten kannst.

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.
Im Playground ausprobieren
Standardmäßig privatDer Prompt wird lokal in deinem Browser zusammengestellt. Gib keine vertraulichen Informationen in einen KI-Dienst ein, es sei denn, deine Organisation erlaubt dies.

Von der Eingabe zum Ergebnis

Ein ausgearbeitetes Beispiel

Sieh dir an, wie konkreter Kontext dieses Rezept in ein nutzbares Ergebnis verwandelt.

Tatsächliche Eingabe

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.

Beispielausgabe

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.

Next checkpoint

April 18: review the analyst’s corrected comparison before the rollout decision.

Warum das funktioniert

  1. 1

    It starts with changed information, matching executive reading behavior.

  2. 2

    The explicit ask turns an update into a decision instrument.

Ergebnis prüfen

  • Is the requested decision unmistakable?

  • Are forecasts distinguishable from observed facts?

Sicher nutzen

Häufig gestellte Fragen

Praktische Antworten dazu, wann du dieses Rezept verwenden solltest, was du bereitstellen solltest und wo menschliche Prüfung weiterhin wichtig ist.

What should I prepare before using “Write a decision-ready executive update”?

For “Write a decision-ready executive update,” prepare Facts and progress, Risks and uncertainty, and Decision or support needed. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Write a decision-ready executive update” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A concise update that tells leaders what changed and what you need—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Write a decision-ready executive update”?

The published test record for “Write a decision-ready executive update” lists ChatGPT, Claude, and Gemini as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Bring die Arbeit voran