Crisis Response Product Playbook
Create a comprehensive playbook for handling product crises such as [outages/security breaches/data loss/compliance issues]. Include: 1) Crisis severity classification framework, 2) Detection mechanisms and alerting thresholds, 3) First response checklist by crisis type, 4) Team roles and responsibilities with escalation path, 5) Communication templates for different stakeholders (users, internal teams, executives, press), 6) Decision-making framework during crisis, 7) War room protocols and tools, 8) Recovery process guidelines, 9) Post-mortem framework with blameless approach, and 10) Preventive measures and continuous improvement process.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt produces an operational playbook rather than a theoretical plan by requiring specific checklists, communication templates, and decision frameworks that teams can follow under pressure. The severity classification system ensures proportional responses so a minor bug does not trigger the same response as a data breach. The blameless post-mortem framework turns crises into lasting improvements rather than blame sessions.
When to Use This Prompt
- Before a major product launch when you need incident response procedures in place for the inevitable first-week issues
- After a poorly handled outage or security incident exposed gaps in your team's crisis response process
- When scaling your team and you need documented procedures so new team members know exactly what to do when things break
Tips for Better Results
- List your specific crisis types (API outages, payment failures, data privacy incidents) so the playbook addresses your actual risk profile
- Include your communication channels (Slack, PagerDuty, status page) so the playbook integrates with your existing incident management tools
- Mention your SLA commitments and regulatory requirements so escalation thresholds and response times reflect real contractual obligations