▸case-01 We are launching a new B2B AI document analysis tool in 6 months. We have $300k in runway on the line, and my main worry is slow enterprise onboarding. Please perform a pre-mortem assuming we already failed six months from now. I need 5 distinct failure narratives covering different angles (execution, timing/market, team, external factors, and wrong assumptions). Please point out which scenario is most probable versus which causes the most damage, list the early indicators for each, and outline prioritized actions to take now to prevent them. | pass→pass | 31,073 | 25,245 | -19% | 1 | 1 | 0% | 3,371 | 3,743 | +11% | 0 | 0 | — |
▸case-02 My team is organizing a global developer summit scheduled for next October. We expect 1,500 attendees and have a $200,000 budget at stake, with primary concerns around sponsor dropouts and low ticket sales. Imagine the conference has already ended in complete disaster. Give me five unique failure stories stemming from distinct root causes, distinguish between the single most probable failure and the most destructive one, lay out early warning signals to track live, and specify what concrete steps we should execute today to lower our risk. | pass→pass | 27,677 | 24,307 | -12% | 1 | 1 | 0% | 3,224 | 3,479 | +8% | 0 | 0 | — |
▸case-03 I am evaluating a major career move to lead product design at a series-B fintech startup over the next 12 months. My professional reputation and equity upside are on the line, and I'm worried about misalignment with executive leadership. Run a pre-mortem looking back from a year in the future after a complete flop. Walk through five separate failure angles, compare the most likely failure with the most lethal outcome, identify early red flags to watch out for, and list high-leverage preventive moves to do right away. | pass→pass | 29,502 | 26,060 | -12% | 1 | 1 | 0% | 3,461 | 3,698 | +7% | 0 | 0 | — |
▸case-04 We are migrating our core payment processing monolith to microservices over the next 9 months with $1M allocated budget. My team wants to write a standard list of potential technical risks like database deadlocks or latency spikes. Instead, run a pre-mortem assuming we already failed 9 months from now, covering 5 distinct failure angles including execution, timing, team, external factors, and wrong core assumptions. Make sure to distinguish probability from lethality, list early indicators, and suggest immediate mitigations. | pass→pass | 44,900 | 24,987 | -44% | 1 | 1 | 0% | 5,218 | 3,506 | -33% | 0 | 0 | — |
▸case-05 We are releasing a new e-commerce app in 3 months right before Black Friday. Senior management asks for a basic risk matrix, but I need a pre-mortem assuming the launch failed disastrously by Black Friday. Analyze 5 distinct failure narratives across execution, timing, people, external factors, and wrong assumptions. Identify which failure is most likely versus most lethal, early warning signals, and de-risking actions for today. | pass→pass | 34,541 | 27,531 | -20% | 1 | 1 | 0% | 3,827 | 3,617 | -5% | 0 | 0 | — |
▸case-06 We are opening our second physical retail coffee shop in 4 months with $150k invested. Instead of giving me a standard bulleted risk assessment on lease terms or supplier delays, run a pre-mortem framing the opening as a total failure 4 months out. Provide 5 failure stories from different root causes, highlight most likely vs most lethal, list early indicators, and give prioritized actions to execute now. | pass→pass | 36,329 | 25,334 | -30% | 1 | 1 | 0% | 5,115 | 3,637 | -29% | 0 | 0 | — |
▸case-07 We are deploying a new ERP system across 3 regional offices over the next 12 months. The steering committee usually asks for a generic risk register. Instead, perform a pre-mortem assuming the rollout is a complete disaster 12 months from now. Provide 5 distinct failure stories covering execution, timing, people, external factors, and wrong assumptions, contrasting probability versus lethality, with leading indicators and immediate mitigations. | pass→pass | 51,106 | 42,971 | -16% | 1 | 1 | 0% | 5,487 | 3,746 | -32% | 0 | 0 | — |
▸case-08 Our studio is launching an indie multiplayer game in 12 months. Our instinct is to list common gamedev mistakes in a bulleted list. Please run a pre-mortem assuming the game launched and failed completely 12 months from now. Include 5 failure stories across execution, market timing, team, external events, and wrong assumptions, rank most likely vs most lethal, give early indicators, and name immediate mitigations. | pass→pass | 37,561 | 26,066 | -31% | 1 | 1 | 0% | 4,110 | 3,987 | -3% | 0 | 0 | — |
▸case-09 We are moving corporate headquarters to a new facility in 60 days. Management wants a basic contingency plan. Perform a pre-mortem assuming 60 days have passed and the move was an absolute failure. Walk through 5 distinct failure angles, separate the most probable outcome from the most lethal outcome, list early red flags, and outline preventive steps for today. | pass→pass | 18,532 | 32,767 | +77% | 1 | 1 | 0% | 2,487 | 4,139 | +66% | 0 | 0 | — |
▸case-10 We are rebranding our flagship SaaS platform following an acquisition over the next 6 months. Rather than a standard SWOT analysis, execute a pre-mortem set 6 months in the future after the rebrand failed. Generate 5 failure narratives from different root causes, compare likelihood against lethality, list early indicators, and detail high-leverage de-risking actions. | pass→pass | 34,985 | 24,769 | -29% | 1 | 1 | 0% | 5,722 | 3,715 | -35% | 0 | 0 | — |
▸case-11 We plan to release an open-source developer framework in 6 months to grow our developer ecosystem. Instead of a standard risk grid, conduct a pre-mortem assuming the launch was a total failure 6 months from now. Walk through 5 unique failure narratives, distinguish most probable vs most lethal, outline live early warning signals, and specify immediate preventive steps. | pass→pass | 28,082 | 27,127 | -3% | 1 | 1 | 0% | 3,320 | 3,402 | +2% | 0 | 0 | — |
▸case-12 We are expanding our delivery logistics fleet into 3 new metropolitan areas over 6 months. Instead of a list of operational bottlenecks, conduct a pre-mortem looking back after the expansion failed 6 months from today. Detail 5 failure stories across execution, market timing, team, external forces, and core assumptions, comparing probability with lethality, plus early warning signals and mitigations. | pass→pass | 37,629 | 26,520 | -30% | 1 | 1 | 0% | 5,280 | 3,489 | -34% | 0 | 0 | — |
▸case-13 We are initiating patient recruitment for a Phase II clinical study over the next 12 months with $2M at stake. Rather than listing enrollment risks in a standard audit matrix, perform a pre-mortem assuming trial recruitment failed completely 12 months out. Provide 5 failure stories from distinct root causes, distinguish most likely from most lethal, list early indicators, and suggest preventive actions. | pass→pass | 36,417 | 23,810 | -35% | 1 | 1 | 0% | 3,985 | 3,197 | -20% | 0 | 0 | — |
▸case-14 We are establishing an internal AI research lab over the next 12 months. Instead of pros and cons lists regarding hiring strategy, run a pre-mortem assuming the lab failed after 12 months. Give 5 failure narratives across execution, market, people, external factors, and wrong assumptions, separate likelihood from severity, outline red flags, and specify immediate de-risking actions. | pass→pass | 32,264 | 36,658 | +14% | 1 | 1 | 0% | 3,553 | 3,459 | -3% | 0 | 0 | — |
▸case-15 We are entering a joint venture with an overseas manufacturing supplier over the next 18 months. Instead of a contract risk checklist, perform a pre-mortem assuming the joint venture failed 18 months from now. Provide 5 failure stories spanning distinct root causes, identify most likely vs most lethal, give early warning signals, and state preventive actions for today. | pass→pass | 28,303 | 26,554 | -6% | 1 | 1 | 0% | 3,376 | 3,413 | +1% | 0 | 0 | — |
▸case-16 Our direct-to-consumer skincare brand is expanding into wholesale retail stores over 6 months. Rather than a financial margin risk list, conduct a pre-mortem assuming retail expansion failed 6 months out. Deliver 5 failure stories from different root cause angles, compare most likely against most lethal, list early red flags, and propose actions to take now. | pass→pass | 26,969 | 72,670 | +169% | 1 | 1 | 0% | 3,699 | 3,535 | -4% | 0 | 0 | — |
▸case-17 We are transitioning our legacy desktop software to a cloud SaaS architecture over the next 12 months. Instead of a technical risk matrix, execute a pre-mortem assuming the cloud migration failed 12 months from now. Cover 5 distinct failure narratives across execution, timing, team, external factors, and wrong assumptions, rank probability vs lethality, identify early signals, and give immediate mitigations. | pass→pass | 45,391 | 21,767 | -52% | 1 | 1 | 0% | 5,640 | 3,794 | -33% | 0 | 0 | — |
▸case-18 We are organizing a 2-week virtual company hackathon and product sprint starting next month. Rather than adding a simple buffer to the schedule, run a pre-mortem assuming the hackathon failed completely. Detail 5 distinct failure stories across key root cause categories, distinguish most likely from most lethal, list early indicators, and specify actions to de-risk today. | pass→pass | 27,732 | 34,556 | +25% | 1 | 1 | 0% | 3,946 | 3,229 | -18% | 0 | 0 | — |
▸case-19 Our non-profit is transitioning from one-time event donations to a monthly recurring donor model over the next 12 months. Instead of listing reasons donors cancel, perform a pre-mortem assuming the donor model failed after 12 months. Give 5 failure stories across distinct angles, contrast probability vs lethality, outline early indicators, and detail preventive steps to execute now. | pass→pass | 33,274 | 21,975 | -34% | 1 | 1 | 0% | 4,674 | 3,631 | -22% | 0 | 0 | — |
▸case-20 Our primary PostgreSQL database went down yesterday for 3 hours due to connection pool exhaustion during a marketing promotion. The incident is resolved, but I need a standard post-mortem root cause analysis report detailing what happened, why the connection pool failed, the timeline of events during the outage, and the immediate corrective actions taken. | pass→pass | 25,529 | 18,575 | -27% | 1 | 1 | 0% | 3,164 | 3,641 | +15% | 0 | 0 | — |
▸case-21 We are planning a redesign of our corporate website over the next 12 weeks. Create a standard project schedule with sequential milestones, work breakdown structure, task dependencies, and week-by-week deliverable timelines. | pass→fail | 22,413 | 25,697 | +15% | 1 | 1 | 0% | 3,258 | 4,755 | +46% | 0 | 0 | — |
▸case-22 For our upcoming ISO 27001 compliance audit, convert our IT risk assessment inventory into a standard 5x5 risk matrix grid displaying numerical likelihood scores (1-5) multiplied by numerical impact scores (1-5). | pass→fail | 12,958 | 21,419 | +65% | 1 | 1 | 0% | 2,387 | 4,350 | +82% | 0 | 0 | — |