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.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Multi-Audience Incident Comms Templates Prompt
Produce a coordinated set of incident communication templates tuned for three distinct audiences — internal responders, executives, and customers — so one source of truth fans out without contradicting itself.
-
Postmortem Sanitize-for-Public-Sharing Prompt
Prepare an internal postmortem for external or cross-customer sharing by finding secrets, PII, customer names, and internal details that must be stripped or redacted — without gutting the technical lesson.
-
Incident Metrics Extractor from a Postmortem Prompt
Extract clean, comparable reliability metrics (MTTD, MTTA, MTTM, MTTR, engagement, and handoff counts) from a finished blameless postmortem so incident data rolls up into trends instead of dying in a single document.
-
Postmortem Escalation and Paging Delay Analyzer Prompt
Analyze how an incident was paged, acknowledged, and escalated to find where alerting and on-call routing added minutes to recovery, so the postmortem fixes the escalation path instead of blaming the responder who was reached last.
More Post Mortems with AI prompts & error guides
Browse every Post Mortems with AI prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.