▸case-01 I messed up today by pushing untested hotfixes directly to our main branch, which took down the app for 40 minutes and ruined a key sales demo. I thought it happened because the team was rushing me, and I've made similar hasty deploys once before. I'd like a structured breakdown of this mistake. Give me an objective autopsy without self-blame, dig past my initial excuse to identify the underlying root cause, outline a concrete rule or trigger to stop it from recurring, write a clean one-line summary takeaway for my lesson log, and evaluate if this is part of a larger pattern. | pass→pass | 16,563 | 15,999 | -3% | 1 | 1 | 0% | 2,161 | 2,220 | +3% | 0 | 0 | — |
▸case-02 I committed to a tight project deadline for a client without reviewing my existing workload, missed the delivery date, and had to give a $1,000 discount. My initial thought was that I simply misestimated the task duration, and I've done this twice in the past six months. Please conduct a post-mortem for me: provide a blame-free analysis of what took place, unearth the core systemic habit behind it, state an actionable prevention rule, compress the key takeaway into a one-line entry, and flag whether this indicates a repeating theme. | pass→pass | 18,041 | 14,554 | -19% | 1 | 1 | 0% | 1,995 | 2,045 | +3% | 0 | 0 | — |
▸case-03 I sent an email campaign to 10,000 subscribers with incorrect pricing details, resulting in 50 angry customer tickets and lost revenue. I told myself I was just distracted, but this is the second time I sent unverified marketing copy this year. Help me turn this failure into a clear lesson. I need an objective breakdown of the event, the real root cause behind the distraction excuse, a specific prevention trigger, a concise one-line museum entry for my records, and an assessment of whether this is a recurring issue. | pass→pass | 19,534 | 15,365 | -21% | 1 | 1 | 0% | 1,814 | 2,496 | +38% | 0 | 0 | — |
▸case-04 I accidentally deleted a production S3 bucket yesterday because I ran a script in the wrong terminal window. I thought it happened because I had too many tabs open. Can you process this through a failure post-mortem? | fail→fail | 24,741 | 15,880 | -36% | 1 | 1 | 0% | 2,542 | 2,182 | -14% | 0 | 0 | — |
▸case-05 I missed a major client presentation this morning, which cost us a $50,000 contract renewal. I have never missed a client meeting before in my 5 years at the company. I want to add this to my lessons. | fail→pass | 20,869 | 11,588 | -44% | 1 | 1 | 0% | 2,190 | 1,761 | -20% | 0 | 0 | — |
▸case-06 I saved production database credentials in a public GitHub repository, resulting in an automated security alert and emergency credential rotation costing 4 hours of DevOps work. My initial thought was that I was tired and sloppy. I've never done this before. Analyze this failure and give me a prevention strategy. I'm thinking my rule should just be 'I will be more careful with secrets in code'. | pass→pass | 20,940 | 12,487 | -40% | 1 | 1 | 0% | 2,463 | 2,447 | -1% | 0 | 0 | — |
▸case-13 I forgot to turn off an idle GPU cloud instance over the weekend, resulting in an unnecessary $1,200 bill. I thought I was just tired on Friday afternoon. I've done this once before. Give me a full failure autopsy and compact museum entry. | fail→pass | 21,840 | 14,596 | -33% | 1 | 1 | 0% | 2,176 | 2,346 | +8% | 0 | 0 | — |
▸case-07 I agreed to verbal contract terms during a Zoom call without documenting them, which cost our agency $3,000 in scope creep when the client demanded extra features. I assumed I would remember everything. This has happened once before. Analyze this and give me a lesson rule. Should my rule be 'Try harder to remember client requests'? | pass→pass | 19,269 | 13,961 | -28% | 1 | 1 | 0% | 1,964 | 2,169 | +10% | 0 | 0 | — |
▸case-08 I completely bombed my keynote address at our industry conference because I started preparing the slides at 2 AM the night before. I lost a major partnership opportunity worth $20k. I'm just an idiot who procrastinates and I have zero discipline. I've done this for every major talk this year. Help me turn this failure into a lesson. | fail→fail | 21,156 | 15,699 | -26% | 1 | 1 | 0% | 2,126 | 2,344 | +10% | 0 | 0 | — |
▸case-09 I published an unencrypted API secret key to a public staging server, which caused a data leakage threat and required $5,000 in security auditing. I told myself I was just distracted by Slack notifications. This is a one-off event. Dig into this mistake for me. | pass→fail | 26,290 | 19,964 | -24% | 1 | 1 | 0% | 2,416 | 2,420 | +0% | 0 | 0 | — |
▸case-10 I double-paid a vendor invoice for $15,000 because I received two copies by email and processed both. Recovering the funds took two weeks of accounting work. I thought I was just in a hurry. This has never happened before. Please analyze this failure. | pass→pass | 22,813 | 18,469 | -19% | 1 | 1 | 0% | 2,634 | 2,032 | -23% | 0 | 0 | — |
▸case-11 I forgot to mute my microphone during an internal review and made a sarcastic comment, which offended a senior executive and required a formal written apology. I thought it happened because I was multitasking. I did the exact same thing on a client Zoom call two months ago and on a team standup last quarter. Analyze this failure. | pass→pass | 25,274 | 27,382 | +8% | 1 | 1 | 0% | 2,568 | 2,126 | -17% | 0 | 0 | — |
▸case-12 I accidentally deleted our team's shared Slack channel history during a workspace permission migration because the admin console interface changed after a major update. Restoring it took 6 hours of enterprise support. I thought it happened because the new UI layout was unfamiliar. I have managed Slack workspaces for 8 years and never made a permission error before. Analyze this incident. | fail→fail | 49,476 | 15,617 | -68% | 1 | 1 | 0% | 2,448 | 2,326 | -5% | 0 | 0 | — |
▸case-14 I gave the wrong pricing deck to a prospective client during a sales pitch, causing confusion and losing a $30,000 deal. I am completely incompetent and lazy. I've made this mistake once before. Turn this into a rule-based post-mortem. | pass→pass | 31,873 | 17,395 | -45% | 1 | 1 | 0% | 2,331 | 2,306 | -1% | 0 | 0 | — |
▸case-15 I approved a pull request without reading the diffs, which introduced a critical bug into production and caused 2 hours of downtime. I thought I was just busy that afternoon. This is the third time this quarter I approved PRs unread. Help me analyze this. | fail→fail | 24,451 | 9,168 | -63% | 1 | 1 | 0% | 2,523 | 2,013 | -20% | 0 | 0 | — |
▸case-16 I entered the wrong shipping addresses for 20 customer orders, leading to delayed deliveries and $400 in reshipment costs. I assumed the spreadsheet was up to date. I've done this once before. Analyze this and give me a rule. I plan to resolve this by paying closer attention when copying address rows. | pass→pass | 21,712 | 19,687 | -9% | 1 | 1 | 0% | 2,131 | 2,188 | +3% | 0 | 0 | — |
▸case-17 Can you help me log a recent failure into my failure museum? | fail→pass | 9,715 | 7,689 | -21% | 1 | 1 | 0% | 1,172 | 1,162 | -1% | 0 | 0 | — |
▸case-18 Our database backup failed for two weeks straight without anyone noticing until a drive failure caused 4 hours of data loss. I thought it happened because I forgot to check the backup logs on Mondays. This has never happened before. Analyze this mistake. | pass→pass | 21,615 | 14,012 | -35% | 1 | 1 | 0% | 2,355 | 1,949 | -17% | 0 | 0 | — |
▸case-19 I showed up 15 minutes late to interview a finalist candidate for our lead developer role because my calendar notifications were muted. The candidate withdrew their application. I'm a terrible manager and a total failure at leadership. I missed another interview last month. Analyze this failure. | fail→pass | 19,478 | 17,554 | -10% | 1 | 1 | 0% | 2,431 | 2,337 | -4% | 0 | 0 | — |
▸case-20 Write a formal incident report document for our enterprise client regarding a database outage yesterday. Include standard corporate sections like Incident Overview, Timeline of Events, Severity Classification, SLA Metrics, and Escalation Contacts. Do not format this as a personal failure museum entry. | pass→pass | 25,672 | 54,441 | +112% | 1 | 1 | 0% | 2,726 | 7,665 | +181% | 0 | 0 | — |
▸case-21 Facilitate a team sprint retrospective outline for a 6-person software engineering team using the 'Start, Stop, Continue' framework to gather team-wide feedback on our last two-week iteration. | pass→pass | 27,456 | 23,847 | -13% | 1 | 1 | 0% | 2,527 | 3,727 | +47% | 0 | 0 | — |
▸case-22 Create a Failure Mode and Effects Analysis (FMEA) table for an electric vehicle battery cooling pump failure, specifying Risk Priority Numbers (RPN), severity, occurrence, and detection ratings according to automotive standards. | pass→pass | 28,961 | 28,596 | -1% | 1 | 1 | 0% | 3,815 | 4,407 | +16% | 0 | 0 | — |