▸case-02 Can you conduct a pre-mortem evaluation on our cloud database migration strategy? Treat the project as if it has completely collapsed six months post-deployment. Give me a medium-sized list of plausible ways things went wrong with narrative descriptions for each risk, and sort the list from most plausible to least plausible. | fail→fail | 23,711 | 35,598 | +50% | 1 | 1 | 0% | 2,565 | 4,819 | +88% | 0 | 0 | — |
▸case-01 We're preparing to launch our new automated customer support platform next month. Here is our rollout plan [attaches document]. I want you to run a pre-mortem analysis assuming we've already failed spectacularly. Please provide a detailed breakdown of possible failure scenarios accompanied by narrative explanations for each, and rank them in order of how likely they are to happen so we can prioritize our mitigation efforts. | fail→fail | 28,898 | 37,982 | +31% | 1 | 1 | 0% | 3,426 | 5,219 | +52% | 0 | 0 | — |
▸case-03 I'd like a formal pre-mortem breakdown for our Q3 marketing campaign proposal attached below. Imagine we are looking back from a year in the future after a disastrous execution. Generate a comprehensive set of narrative failure stories detailing how the initiative collapsed, and order the results based on how likely each scenario is. | fail→fail | 20,683 | 31,859 | +54% | 1 | 1 | 0% | 3,046 | 4,206 | +38% | 0 | 0 | — |
▸case-04 Our production database suffered a severe 4-hour downtime incident yesterday due to an unindexed migration query. Here is the post-mortem incident log. Please analyze the root causes of the outage that already happened and list actions for our post-incident cleanup. | pass→pass | 14,565 | 60,708 | +317% | 1 | 1 | 0% | 2,326 | 3,571 | +54% | 0 | 0 | — |
▸case-05 We are evaluating a strategic expansion of our retail banking services into Western Europe. Please prepare a standard SWOT matrix outlining our internal Strengths, Weaknesses, external Opportunities, and Threats for the board meeting. | pass→pass | 24,446 | 62,034 | +154% | 1 | 1 | 0% | 2,518 | 6,260 | +149% | 0 | 0 | — |
▸case-06 Our Android app checkout flow build failed during compilation with dynamic linkage error ERR_LINK_77. Please perform a 5 Whys root cause analysis on this build error log to find why the compiler failed. | pass→pass | 18,775 | 18,054 | -4% | 1 | 1 | 0% | 2,215 | 3,168 | +43% | 0 | 0 | — |
▸case-07 We need a quick, low-overhead pre-mortem for our fintech payment gateway API integration specification. We only have time to review a brief set of high-priority risks. Please run the failure analysis assuming the integration failed post-launch. | fail→fail | 21,012 | 21,580 | +3% | 1 | 1 | 0% | 2,411 | 3,385 | +40% | 0 | 0 | — |
▸case-08 Our hospital network is undergoing an enterprise EHR data migration across 14 facilities. We need an exhaustive, deep-dive pre-mortem exercise generating an extensive list of failure paths narrative stories. Please run this analysis assuming total project failure. | fail→fail | 49,280 | 51,937 | +5% | 1 | 1 | 0% | 6,860 | 7,782 | +13% | 0 | 0 | — |
▸case-09 Here is our bill-of-materials and vendor procurement schedule for the next-gen IoT hardware sensor. Perform a pre-mortem assume-failure analysis, ensuring you classify this input document appropriately so the evaluation uses hardware supply chain prompts. | fail→fail | 27,664 | 27,035 | -2% | 1 | 1 | 0% | 3,205 | 3,478 | +9% | 0 | 0 | — |
▸case-10 We are updating our mobile banking app authentication system next month. We want to evaluate risks, but team members are prone to optimistic bias and keep saying 'this won't happen to us'. Run a Gary Klein pre-mortem protocol where the key premise is that failure has ALREADY occurred in the future. | fail→fail | 25,533 | 43,789 | +71% | 1 | 1 | 0% | 2,968 | 4,907 | +65% | 0 | 0 | — |
▸case-11 Our e-commerce portal is launching a single-click checkout flow. Run a pre-mortem exercise assuming total launch collapse. Generate narrative scenarios explaining how it failed, and make sure the primary sorting mechanism orders these scenarios from most likely to least likely. | pass→pass | 29,341 | 37,474 | +28% | 1 | 1 | 0% | 3,128 | 4,840 | +55% | 0 | 0 | — |
▸case-12 We are releasing an autonomous drone delivery control platform. I want to run a pre-mortem analysis on our rollout strategy. Explain why we isolate the execution context in a subagent when running this protocol rather than running it in our main discussion thread, and execute the analysis accordingly. | fail→fail | 37,511 | 27,092 | -28% | 1 | 1 | 0% | 2,950 | 3,596 | +22% | 0 | 0 | — |
▸case-13 Our company is deploying a SAP ERP system replacement next quarter. Here is the implementation roadmap. Run a pre-mortem failure exercise to generate detailed story-like failure pathways for what went wrong. | fail→fail | 29,069 | 82,930 | +185% | 1 | 1 | 0% | 3,399 | 3,735 | +10% | 0 | 0 | — |
▸case-14 We are presenting our Series A pitch deck to investors next week. Here is the deck content. Conduct a brief pre-mortem analysis assuming investors rejected us completely, using a small budget scenario limit. | fail→pass | 18,192 | 30,333 | +67% | 1 | 1 | 0% | 1,912 | 4,078 | +113% | 0 | 0 | — |
▸case-15 Our ML engineering team is deploying a 70B parameter LLM into customer service workflows. Here is our deployment architecture document. Perform an in-depth pre-mortem evaluation with a large scenario budget assuming post-deployment system failure. | fail→fail | 52,517 | 35,103 | -33% | 1 | 1 | 0% | 7,305 | 5,673 | -22% | 0 | 0 | — |
▸case-16 We have attached our Kubernetes multi-cluster mesh network topology diagram and spec sheet. Please run a pre-mortem assume-failure analysis on this infrastructure plan, making sure the tool classifies the artifact type as a technical infrastructure architecture document. | fail→fail | 24,665 | 35,216 | +43% | 1 | 1 | 0% | 3,146 | 5,645 | +79% | 0 | 0 | — |
▸case-17 Our enterprise is transitioning 5,000 employees to a hybrid-remote policy next quarter. Here is the policy draft. Run a Gary Klein protocol pre-mortem assuming this policy causes massive employee attrition and operational disruption six months from now. | fail→fail | 23,486 | 46,702 | +99% | 1 | 1 | 0% | 2,613 | 4,881 | +87% | 0 | 0 | — |
▸case-18 We are installing 500MW battery energy storage across our regional power grid. Here is our project timeline. Run a pre-mortem analysis using prospective hindsight to describe how our deployment failed. | fail→fail | 25,896 | 33,220 | +28% | 1 | 1 | 0% | 2,920 | 4,034 | +38% | 0 | 0 | — |
▸case-19 Our aerospace team is pushing a software update to low-Earth orbit satellite telemetry nodes next month. Here is the update manifest. Execute a pre-mortem protocol assuming mission failure and prioritize the results strictly by how plausible each scenario is. | fail→fail | 18,256 | 33,365 | +83% | 1 | 1 | 0% | 2,663 | 4,319 | +62% | 0 | 0 | — |
▸case-20 We are starting Phase II clinical trials for a new oncology therapeutic. Here is the protocol document. Conduct a pre-mortem protocol assuming the trial failed to meet primary endpoints or safety milestones. | fail→fail | 12,317 | 25,411 | +106% | 1 | 1 | 0% | 1,849 | 4,158 | +125% | 0 | 0 | — |
▸case-21 Our company is merging with a major competitor in 90 days. Here is the operational integration plan. We need a pre-mortem failure exercise, but our leadership team is heavily biased towards success. Run the analysis in an isolated subagent context to avoid optimism contamination. | fail→fail | 14,762 | 42,972 | +191% | 1 | 1 | 0% | 1,516 | 5,051 | +233% | 0 | 0 | — |
▸case-22 Our city public works department is upgrading the municipal water filtration plant. Here is the engineering schedule. Perform a pre-mortem failure exercise assuming total system contamination occurred post-commissioning. | fail→fail | 22,237 | 27,075 | +22% | 1 | 1 | 0% | 2,874 | 4,306 | +50% | 0 | 0 | — |