Skip to content
DevOps AI ToolKit
Newsletter
All prompts
Post Mortems with AI Difficulty: Intermediate ClaudeChatGPT

Postmortem Stakeholder Distribution Variants Prompt

Spin one approved postmortem into audience-tailored versions (executives, the engineering team, affected customers, and an internal wiki record) without changing the underlying facts, so each reader gets the right depth and framing.

Target user
Incident managers and communications leads
Difficulty
Intermediate
Tools
Claude, ChatGPT

The prompt

You are an incident manager who repackages a single, approved postmortem for different audiences. The facts stay identical across versions; only depth, framing, and emphasis change.

I will provide:
- The approved internal postmortem (timeline, impact, root cause, action items)
- The audiences I need versions for and any tone or compliance constraints
- What is confidential and must not leave the company

For each requested audience, produce a tailored version:

1. **Executive brief** — under 200 words: what happened, customer/business impact in numbers, current status, and the top commitments with dates. No deep technical detail.
2. **Engineering record** — full technical depth: causal chain, contributing factors, telemetry, and all action items with owners; written blamelessly for the people who will do the work.
3. **Customer-facing summary** — plain language, accountable and empathetic, scoped to what affected them; states remediation without internal jargon, names, or confidential architecture.
4. **Knowledge-base entry** — a searchable record with tags, symptoms, root cause, and the runbook/mitigation, so the next responder finds it fast.

Across all versions:
- Keep every fact consistent; if a number must be rounded or omitted for an audience, note it in a editor's comment, do not alter it.
- Strip individual names and confidential details from any externally shared version.
- Keep all framing blameless and system-focused.

Output each version under a clear heading, then a one-line distribution note (who sends it, to whom, what to redact). Flag anything you could not safely externalize.

Related prompts

Newsletter

Free: the DevOps AI Incident-Triage Cheat Sheet

Subscribe and we’ll send you the one-page cheat sheet — plus weekly AI prompts, automation ideas, and tool reviews for infrastructure engineers. One email a week. No spam, unsubscribe anytime.

  • AI Incident-Triage Cheat Sheet (PDF)
  • Access to 2,104 DevOps AI prompts
  • One practical workflow email per week