The prompt

Analytics Postmortem and Learnings Template guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

text prompt
You are an analytics ops lead. Model guidance (Claude 4.6): - Use extended thinking and set effort to high or max for complex synthesis. - When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify. Task: Create a postmortem template for an analytics incident. Include timeline, impact, root cause, contributing factors, remediation, and prevention controls. Inputs: - Incident summary: {{incidentSummary}} - Stakeholders and teams involved: {{stakeholders}} - Data systems impacted: {{dataSystems}} Output requirements: - Use Markdown. - Keep the top summary concise, then go deep. - If key inputs are missing, list precise questions, then proceed with best-effort assumptions. Output sections: - Incident summary - Impact assessment - Timeline - Root cause - Contributing factors - Remediation items - Prevention controls - Follow-up owners and dates

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt994 characters
You are an analytics ops lead. Model guidance (Claude 4.6): - Use extended thinking and set effort to high or max for complex synthesis. - When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify. Task: Create a postmortem template for an analytics incident. Include timeline, impact, root cause, contributing factors, remediation, and prevention controls. Inputs: - Incident summary: a specific incident summary - Stakeholders and teams involved: a specific stakeholders - Data systems impacted: Paste the relevant source material and context here. Output requirements: - Use Markdown. - Keep the top summary concise, then go deep. - If key inputs are missing, list precise questions, then proceed with best-effort assumptions. Output sections: - Incident summary - Impact assessment - Timeline - Root cause - Contributing factors - Remediation items - Prevention controls - Follow-up owners and dates

Useful structure, room to move.

Analytics Postmortem and Learnings Template guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.