> ## Content Index > Fetch the complete content index at: https://www.thedailyconstraint.com/llms.txt > Use this file to discover other available public pages before exploring further. # Nobody Raised Their Hand: How AI Finds the Risks Your Rollout Meeting Missed - URL: https://www.thedailyconstraint.com/how-can-operations-managers-use-ai-to-run-a-pre-mortem-before-changing-a-process/ - Published: 2026-08-28T01:43:08.000Z - Updated: 2026-08-28T04:59:34.000Z - Author: Andrea Bullock Picture the usual send-off meeting. Someone presents the rollout plan. The room gets asked, “any concerns?” Crickets. Nobody raises a hand. Not because there's nothing to worry about. Because saying so out loud, in that room, at that moment, feels like being the one person who didn't get the memo. Last time, we built a pilot for the Line 4 sign-off fix, stop condition and all. If you missed how that pilot came together, catch up here. \[LINK: Your Pilot Isn't a Test: How AI Builds One That Actually Proves Something\] Say it clears the threshold. Downtime drops. Nothing downstream got worse. You're ready to roll it out on every line that runs this changeover. One more check first. **Imagine It Already Failed** Cognitive scientist Gary Klein had a fix for this. It's blunt. [Instead of asking what might go wrong](https://hbr.org/2007/09/performing-a-project-premortem?ref=thedailyconstraint.com), assume it already has. Tell the room the rollout failed, a year from now. Ask everyone to explain why. That single reframe changes everything. Predicting failure feels like betting against the team. Explaining a failure that's already “happened” feels like just describing what you saw. It also short-circuits [groupthink](https://www.britannica.com/science/groupthink?ref=thedailyconstraint.com), the well-documented tendency for cohesive groups to prioritize agreement over honest assessment. A pre-mortem makes dissent the assignment instead of the risk. Nobody needs to be the pessimist who's betting against the team. Everyone's just explaining a failure the exercise already assumed. That's a small reframe with an outsized effect on what gets said out loud. **Eight Angles, One Pass Each** ![](https://storage.ghost.io/c/6a/5a/6a5a81c1-c40d-4db0-af99-e0cedc71c0c2/content/images/2026/08/blog-1.png) Don't run one generic “what could go wrong” pass. Attack the plan from eight specific angles, one at a time: ● **Safety:** Could this hurt someone, even under normal operating conditions? ● **Quality:** Could this introduce a new defect mode nobody's watching for yet? ● **Delivery:** Could this slow output or blow a ship date somewhere downstream? ● **Cost:** Could this quietly cost more than it saves, in labor, scrap, or overtime? ● **People:** Could this break trust with the crew, or get quietly worked around instead of followed? ● **Customer:** Could this show up as a complaint before it shows up on any internal dashboard? ● **Downstream constraint:** Could this trigger the exact migration problem we modeled a few articles back? ● **Failure recovery:** If this does go wrong, how long before anyone notices, and how hard is it to reverse? Eight passes, not one. A single “what could go wrong” question always gets the same two or three obvious answers. Eight specific angles get the ones nobody thought to ask about. **Applied to the Full Rollout** The pilot only ran on Line 4\. The rollout touches every line running this changeover. That gap is where most of the real risk hides. ● **Safety:** operators on lines that never saw the pilot improvise their own version of the sign-off step. Nobody trained them on the exact procedure that worked. ● **People:** crews on the other lines hear “we already proved this works.” They quietly resent being handed a mandate instead of a pilot. ● **Downstream constraint:** dock capacity held during a single-line pilot. Three lines speeding up at once is a different math problem entirely. It's the one from a few articles back. None of those three showed up in the pilot data. All three are exactly the kind of thing a pre-mortem is built to catch before they show up on the floor instead. **From Scattered Worries to a Risk Register** A pile of concerns from eight angles is not useful yet. It's just a longer list of worries. Turn it into a [risk register](https://asana.com/resources/risk-register?ref=thedailyconstraint.com): each risk named, its likelihood and impact rated, an owner assigned, and a specific trigger that means it's happening. That last part matters most. A risk with no trigger just sits there being vaguely alarming. A risk with a trigger turns into an early warning system somebody's watching. One row from that register, for the Line 4 rollout, might look like this: ● **Risk:** untrained crews improvising the sign-off step. ● **Likelihood:** medium. ● **Impact:** high, since it undoes the entire fix. ● **Owner:** the shift supervisor on each line. ● **Trigger:** any sign-off logged outside the standard three-minute window. That's a risk you can manage. “People might not follow the new process” is not. **The Prompt: Run the Pre-Mortem** ![](https://storage.ghost.io/c/6a/5a/6a5a81c1-c40d-4db0-af99-e0cedc71c0c2/content/images/2026/08/Blog-2-2.png) Give an AI tool the full rollout plan: what's changing, where, on what timeline, and who's affected. Use one that can hold a structured conversation, not just answer a single question: Claude, ChatGPT with data analysis enabled, or similar. Ask it to run all eight angles before you present anything to leadership. Then adapt this prompt to your situation. This works even before the plan is finished. Running a pre-mortem early enough to still change the plan is the entire point. Running it after everything's locked in is just an expensive way to feel bad later. **1\. Set Up the Prospective Hindsight Frame** ● Explicitly tell it to assume the rollout already failed, a year from now. ● Not that it might fail. That it did. ● Example instruction: “Assume this rollout completely failed. It's a year from now. Work backward and explain, in specific detail, what went wrong.” **2\. Run All Eight Angles Separately** ● Don't let it collapse them into one generic risk list. ● Ask for distinct output for safety, quality, delivery, cost, people, customer, downstream constraint, and failure recovery. **3\. Force Specificity Over Generality** ● Reject any risk phrased as “communication issues” or “resistance to change.” ● Ask what that looks like on your floor, in your own words. **4\. Ask for a Trigger, Not Just a Description** ● Every risk needs a specific, observable sign that it's starting to happen. ● Not just a category it falls under. **5\. Build the Register** ● Have it consolidate everything into a table: risk, likelihood, impact, owner, trigger, response. **6\. Ask What It's Most and Least Confident About** ● Some risks are obvious. Others are speculative. ● Knowing which is which tells you where to spend your own judgment. Run all six, and you'll walk into that rollout meeting with the concerns already named, instead of buried in a room full of nodding heads. **What AI Can't Pre-Mortem for You** AI can generate eight angles of failure faster than any meeting ever could. It cannot sit in the room and notice who went quiet when Cost came up. It cannot read the specific exhaustion on your team's faces after three changes this quarter. It cannot know which risk, on your floor, with your people, is the one everyone's thinking and nobody's saying. It also can't tell you which risks are worth losing sleep over. Or which ones are worth a shrug. A risk register full of everything reads the same as a risk register full of nothing. Not unless a person with real floor experience decides what deserves attention this week. The list is the easy part. Reading the room that built the list is still yours. **The Series, Looking Back** Six pieces ago, Line 4 was just a downtime number climbing on a dashboard. No cause. No lead. Just red ink. A dashboard showed what happened. It never showed what happened together. That's where the interaction effect was hiding. \[LINK: Your Dashboard Missed This: How AI Finds the Relationships It Can't See\] A hypothesis matrix replaced a guess dressed up as a root cause. Multiple suspects, tracked side by side, instead of the first plausible story winning by default. \[LINK: The 5 Whys Are Broken: How AI Helps You Track Multiple Root Causes\] A model caught where the fix would push the strain before it cost a dime. Dock capacity, sitting closer to its limit than anyone had checked. \[LINK: You Didn't Fix the Bottleneck: How AI Predicts Where It Moves Next\] A pilot proved the fix on one line. A stop condition, written down before anyone started. Not argued about after. \[LINK: Your Pilot Isn't a Test: How AI Builds One That Actually Proves Something\] And now, a pre-mortem, before that fix touches every line that runs this changeover. None of those five steps needed a data scientist. Every one of them needed AI to carry the part that used to take more time, more tooling, or another person than you had sitting around. And every one of them still needs you. Your floor knowledge. Your judgment call. Your walk down to Line 4 to see what the numbers couldn't say on their own. That was the bet this whole series made. It's still the bet. Subscribe to The Daily Constraint if you haven't yet. This isn't the last series like this one. Run a pre-mortem this week? Comment below. Tell me what risk showed up that you weren't expecting. Not the ones on everyone's list already. The one somebody almost didn't say out loud.