AI Prompt to Write Nightmare Scenario Risk Assessments
Most risk assessments are polite documents. They smooth the edges, water down the consequences, and quietly skip the ugly “and then what?” that leadership actually needs to hear. The result is predictable: small issues compound, and by the time anyone reacts, the system has already chosen the worst path.
This nightmare scenario risk assessments prompt is built for Operations leaders stress-testing critical workflows before a rollout, Product managers trying to pressure-test a new feature with real-world dependencies, and consultants who need a sharp worst-case storyline to break stakeholder complacency. The output is a single “doomsday path” narrative with at least six labeled breakdown points, second- and third-order impacts, three first-person stakeholder mini-stories, and clear prevention takeaways (not a generic risk register).
What Does This AI Prompt Do and When to Use It?
| What This Prompt Does | When to Use This Prompt | What You’ll Get |
|---|---|---|
|
|
|
The Full AI Prompt: Doomsday Path Nightmare Scenario Analysis
Fill in the fields below to personalize this prompt for your needs.
| Variable | What to Enter | Customise the prompt |
|---|---|---|
[CONTEXT] |
Provide a detailed description of the situation or system being analyzed, including its purpose, structure, and current state. For example: "A national power grid relying on aging infrastructure and vulnerable to cyberattacks, serving 50 million people across urban and rural areas."
|
|
[TARGET_AUDIENCE] |
Specify the group most affected by the analysis, including relevant characteristics such as their role, needs, or vulnerabilities. For example: "Small business owners relying on uninterrupted electricity to run their operations, with limited financial buffer for disruptions."
|
|
[INDUSTRY] |
Indicate the industry or domain relevant to the situation or system being analyzed. Include any specific subfields if applicable. For example: "Energy sector, with a focus on renewable energy integration and grid security."
|
|
[TIMEFRAME] |
State the period over which the nightmare scenario is expected to unfold, ranging from hours to years. For example: "Over the course of 18 months, starting with minor system failures and escalating to widespread outages."
|
|
[PRODUCT_DESCRIPTION] |
Describe any relevant constraints, dependencies, or technologies involved in the situation or system. Be specific and detailed. For example: "The system depends on outdated SCADA software with limited cybersecurity features, and it requires manual intervention for critical operations."
|
|
[PRIMARY_GOAL] |
Specify any particular angle or focus for the analysis, such as a stakeholder perspective or specific risk type. For example: "Highlight the economic impacts on small businesses and the cascading effects on local economies."
|
Pro Tips for Better AI Prompt Results
- Describe the system like an investigator, not a marketer. Include dependencies, handoffs, vendors, and incentives (who benefits from speed, who pays for failure). For example: “Payments are processed by Vendor X; chargebacks are handled manually by two agents; alerts go to a shared inbox that is checked twice daily.”
- Give it a concrete ignition point option. If you don’t, the model may pick an overly generic trigger. Try: “Start the ignition point with a realistic human error in the on-call handoff,” or “Make the ignition point a subtle configuration drift after a routine update.”
- Ask for named breakdown labels that match your org. Labels like “Approval bypass in change management” or “Vendor SLA ambiguity” make the chain easier to socialize. A good follow-up is: “Rename each breakdown point using our internal language (SRE, RevOps, Legal, Finance) and keep the logic unchanged.”
- Iterate on severity and realism, not length. After the first run, push it to tighten cause-and-effect: “Rewrite steps 3–6 so each one explicitly states what new capability the attacker/system gains, and why detection fails at that moment.” Then ask: “Now shorten by 20% without removing any breakdown points.”
- Use the stakeholder triptych strategically. Pick lenses that create friction: a frontline operator, an executive accountable to the board, and an external party (regulator, key customer, community). If the prompt chooses the wrong people, steer it: “Use these stakeholders instead: Head of Compliance, On-call Engineer, and a top enterprise customer’s procurement lead.”
Common Questions
COOs and Heads of Operations use it to pressure-test cross-team dependencies before a change turns into a cascading outage. Security leaders (CISO, SecOps managers) apply it to translate “theoretically possible” vulnerabilities into a concrete chain that drives prioritization. Product leaders lean on the stakeholder triptych to see how incentives and UX edge cases amplify harm after launch. Consultants and internal auditors use the labeled breakdown points as a clean way to surface control gaps without writing a full audit report.
Fintech and payments teams use it to model how a small reconciliation error or fraud-control tweak can cascade into chargeback spirals, regulatory scrutiny, and partner de-risking. Healthcare providers and health tech apply it to patient-safety and privacy failures where second-order impacts include staffing breakdowns, legal exposure, and delayed care. Manufacturing and logistics get value when a minor supplier slip or system outage creates inventory distortion, missed SLAs, and safety incidents. SaaS and cloud platforms use it to connect a single misconfiguration to customer churn, contract disputes, and irreversible trust damage.
A typical prompt like “Write me a worst-case risk assessment for my project” fails because it: lacks explicit assumptions, so the story floats away from your real system; provides no required structure (ignition point, labeled breakdown chain, end-state), so it becomes a loose list; ignores second- and third-order impacts, so consequences stop at “reputation damage”; produces generic stakeholders instead of first-person lenses tied to control and incentives; and misses the prevention takeaways that identify the earliest interruption points.
Yes. You customize it by changing the system description you paste in, the constraints you specify (regulated vs unregulated, online vs physical operations), and the stakeholder lenses you want in the triptych. If you have missing details, let the prompt ask its up to three clarification questions, then answer them in-line and rerun. A practical follow-up request is: “Keep the same breakdown points, but rewrite the chain assuming Vendor A fails first instead of internal operations, and update the stakeholder accounts accordingly.”
The biggest mistake is providing a vague system description—instead of “our app handles customer data,” use “a B2B SaaS app with SSO, an external data warehouse, and support agents who can impersonate users.” Another common error is leaving dependencies out (bad: “we use cloud hosting”; good: “AWS + managed Redis + a third-party email provider with API rate limits”). People also forget incentives and constraints (bad: “teams collaborate”; good: “on-call is rotated weekly, incident comms must go through Comms, and approvals are often bypassed during launches”). Finally, many users accept generic stakeholders; you will get a stronger triptych if you specify roles like “on-call engineer,” “General Counsel,” and “top customer admin.”
This prompt isn’t ideal for lightweight decisions where you just need a quick checklist, or for situations where your team will not tolerate worst-case framing. It’s also not a fit if you need a probability estimate, a balanced tradeoff doc, or a full mitigation plan, because it intentionally focuses on a single maximally destructive storyline. If that’s you, start with a standard risk register format and then use this prompt later as a deeper pre-mortem once the basics are agreed.
Worst-case thinking is uncomfortable, but it’s cheaper than denial. Paste the prompt into your AI tool, feed it a real system description, and use the breakdown labels to start the hard conversations before reality forces them.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
