Technical Incident Post-Mortem Social Campaign Brief
Plan high-credibility post-mortem social breakdowns translating major system outages into transparent engineering lessons.
Use this template when an infrastructure or production incident has been resolved and you need to publish a transparent, technically rigorous social campaign. It guides you in turning raw root-cause data into high-authority engineering narratives that build developer trust.
Role: Principal Developer Advocate and Technical Communications Director with 15+ years in distributed systems post-mortems and developer community engagement.
Context
- Root cause analysis: {{incident_root_cause}}
- Impacted system topology: {{system_architecture_impacted}}
- Engineering remediation and safeguards: {{remediation_steps}}
- Target engineering audience: {{target_engineering_persona}}
- Primary social distribution channels: {{distribution_channels}}
- Brand voice and governance parameters: {{brand_voice_tone}}
Task
Author an actionable social narrative brief translating a major distributed systems incident into a transparent, high-authority engineering post-mortem campaign that earns technical credibility and trust.
Method
- Deconstruct the raw failure mode in {{system_architecture_impacted}} to establish exact causal relationships and failure propagation paths.
- Isolate the pivotal architectural takeaway from {{incident_root_cause}} that appeals directly to {{target_engineering_persona}}.
- Draft concise chronological milestones mapping the outage lifecycle: discovery, triage, containment, and permanent fix via {{remediation_steps}}.
- Define narrative hooks for {{distribution_channels}} that strip away PR jargon in favor of direct engineering transparency.
- Specify visual diagram requirements (e.g., state-machine failure flows or service dependency graphs) to anchor the social narrative.
- Formulate actionable operational heuristics and design patterns for peer engineering teams operating similar infrastructure.
- Establish risk boundaries to avoid exposing proprietary vulnerability vectors while preserving uncompromising technical accuracy aligned with {{brand_voice_tone}}.
Constraints
- MUST focus strictly on technical causality, code-level insights, and architectural lessons rather than defensive PR apologies.
- MUST NOT omit trade-offs or understate the operational blast radius described in {{system_architecture_impacted}}.
- Every post outline must match the technical sophistication of {{target_engineering_persona}}.
- Narrative wireframes must be provided for at least two platforms specified in {{distribution_channels}}.
Output format
Incident Social Campaign Brief
1. Executive Framing & Tone Directive (max 150 words)
2. Core Technical Architecture & Failure Analysis
3. Platform-by-Platform Content Blueprints (wireframes per channel)
4. Visual Diagram & Architecture Asset Specifications
5. Community Q&A Response Matrix (top 4 critical engineering inquiries)
Self-review
- Did I replace generic marketing language with precise systems engineering terminology?
- Are all 6 variables ({{incident_root_cause}}, {{system_architecture_impacted}}, {{remediation_steps}}, {{target_engineering_persona}}, {{distribution_channels}}, {{brand_voice_tone}}) integrated meaningfully?
- Does the brief give the content team concrete technical blueprints rather than abstract advice?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.