Email Deliverability Post-Mortem: Root Cause to Prevention

Role: You are an Email Manager tasked with fixing a deliverability problem.

Context: Our emails are not reaching inboxes like they used to. We need a clear plan to understand why and prevent it from happening again. Think about what we learned from the problem and how to make things better.

Task: Create a simple action plan from a recent email deliverability issue. Don't write the incident report itself, but focus on what we should *do* next. Assume you have basic details about the problem.

Problem Overview: `{{problem_description}}` (e.g., "Emails stopped landing in inboxes last week, a 25% drop for 2 days.")

What We Saw: `{{what_we_noticed}}` (e.g., "Our sender score went down, and we sent a new type of email right before the drop.")

Constraints:
*   Organize your plan into four sections: Key Metrics, Monitoring Dashboard, Team Meetings, and Action List.
*   Key Metrics should list important numbers to watch.
*   Monitoring Dashboard should suggest what to show.
*   Team Meetings should say how often to meet and who should be there.
*   Action List needs at least three specific steps to improve deliverability, with a rough idea of how hard they are.
*   Keep the language straightforward and practical.

Output Format: Use these four headings:
1.  **Key Metrics**
2.  **Monitoring Dashboard**
3.  **Team Meetings**
4.  **Action List**

Role: Act as an expert Email Operations Lead and Incident Analyst.

Context: A significant deliverability incident has occurred, leading to a sudden and sustained drop in inbox placement for our email program. We need a structured approach to not only understand what happened but also to establish enduring preventative measures. The goal is to move beyond mere reporting to a proactive system that integrates post-mortem learnings into our operational framework.

Task: Develop a comprehensive set of operational artifacts based on a thorough deliverability incident post-mortem. Your output should *not* be the post-mortem report itself, but rather the *derived actions and frameworks* that result from it. Assume a detailed post-mortem has been completed, providing the necessary data points. You will use this assumed post-mortem to construct the required output components.

Incident Summary: `{{incident_summary}}` (e.g., "On [Date], a 30% drop in inbox placement was observed across all major ISPs, affecting marketing and transactional emails. The issue persisted for 48 hours before partial recovery.")

Initial Observations: `{{initial_observations}}` (e.g., "IP reputation degraded, increased spam trap hits, new email campaign launched shortly before the drop, no changes to sending infrastructure.")

Constraints:
*   Output must be structured into four distinct sections: KPI Framework, Dashboard Specification, Review Cadence, and Optimization Backlog.
*   The KPI Framework must include both leading and lagging indicators relevant to deliverability, with a clear definition for each.
*   The Dashboard Specification should outline key metrics, visualization types, and suggested data sources for a real-time monitoring dashboard.
*   Review Cadence must specify frequency, attendees, and agenda points for operational reviews related to deliverability.
*   The Optimization Backlog should contain at least five concrete, prioritized actions derived from potential root causes (e.g., IP warming, segmentation refinement, content testing), with estimated effort and impact.
*   Maintain a measured, decision-oriented tone.
*   Focus on actionable outputs rather than descriptive incident summaries.

Output Format: Provide the response as four distinct sections, clearly labeled:
1.  **KPI Framework**
2.  **Dashboard Specification**
3.  **Review Cadence**
4.  **Optimization Backlog**

As an Email Operations Lead, develop an actionable framework following a deliverability incident. Given a brief `{{incident_summary}}` (e.g., "Sudden 30% inbox placement drop on [Date], lasted 48 hours") and `{{initial_observations}}` (e.g., "IP reputation degraded, new campaign launched"), provide four structured outputs: a KPI Framework with leading/lagging indicators, a Dashboard Specification detailing metrics and visualizations, a Review Cadence outlining meeting frequency and agenda, and an Optimization Backlog with at least five prioritized actions, effort, and impact. Focus on concrete, preventative measures and actionable items derived from the post-mortem.

Role: You are a Senior Email Operations Director and Compliance Officer.

Context: A critical deliverability incident has impacted our email infrastructure, leading to significant inbox placement degradation and potential compliance risks. We require a strategic response that not only addresses technical remediation but also reinforces governance, stakeholder communication, and long-term risk mitigation. The objective is to translate post-mortem findings into a robust, auditable operational framework.

Task: From a completed deliverability incident post-mortem, synthesize and construct an enterprise-grade set of operational and governance artifacts. The output must focus on systemic improvements, compliance adherence, and strategic oversight, rather than merely reporting the incident.

Incident Executive Brief: `{{incident_executive_brief}}` (e.g., "On [Date], a severe, multi-ISP inbox placement decline of 35% occurred, impacting critical customer communications and raising regulatory concerns.")

Detailed Findings & Risk Assessment: `{{detailed_findings_and_risk_assessment}}` (e.g., "Identified an unauthorized list import, lack of pre-send validation, and insufficient real-time monitoring. High compliance risk flagged due to potential PII exposure.")

Constraints:
*   Output must be structured into four sections: Strategic KPI & Compliance Framework, Enterprise Dashboard Specification, Governance & Review Cadence, and Strategic Optimization & Risk Mitigation Backlog.
*   The KPI Framework must integrate compliance metrics, audit trails, and both leading/lagging indicators.
*   The Dashboard Specification should include real-time alerts, cross-departmental data feeds, and executive-level visualizations.
*   Governance & Review Cadence must define multi-tier review structures, stakeholder communication protocols, and escalation paths.
*   The Optimization Backlog must feature at least seven prioritized initiatives, including policy updates, technology investments, and training programs, with detailed risk mitigation strategies.
*   Maintain a formal, strategic, and compliance-aware tone.

Output Format: Provide the response as four distinct sections, clearly labeled:
1.  **Strategic KPI & Compliance Framework**
2.  **Enterprise Dashboard Specification**
3.  **Governance & Review Cadence**
4.  **Strategic Optimization & Risk Mitigation Backlog**