Episode 1, the short cut. Watch the full episode on YouTube.
Every turnaround is won or lost on one decision, and it gets made before a tool hits the field: what work goes in the window. Get it wrong one way and you defer work that needed doing, and the equipment fails on you mid-run. Get it wrong the other way and you open equipment that was running fine, and hand yourself a startup full of problems you built yourself. Most teams never even have the argument. Days in a room, the list comes out five percent smaller, and nobody can defend why.
The teams that win do not minimize the scope and they do not maximize it. They optimize it, on purpose, with a test everyone in the room can see.
Three roads, and two of them lose
Minimize the scope and you look disciplined on paper, right up until a bearing you deferred lets go six weeks after startup and the unit is down at full rate. You did not save that money. You borrowed it, and the interest is a forced outage. Maximize the scope and you feel safe, but every job you add costs money, costs window time, and introduces risk into equipment that did not need you. More is not safer. More is just more. Optimize is the hard road, and the only one that wins, because it means you can say, for every item, exactly why it is in or out.
Why optimize wins: the bathtub curve
This is not a judgment call. It is how equipment fails. The bathtub curve has three regions: infant mortality, where a new or freshly opened asset fails at a high but falling rate; useful life, where the rate is low and steady; and wear-out, where corrosion, fatigue, and erosion drive it back up. Wear-out equipment is what genuinely needs your window.
Here is the part most teams never connect. Do intrusive work on equipment sitting happy in the flat middle, and you do not improve it. You reset it to infant mortality and buy yourself early failures at startup on a machine that was going to run clean. And decades of reliability research found that most equipment, especially instrument and electrical, never reaches a wear-out zone at all. It fails early or it fails at random, and opening it on a schedule does nothing but reset the clock. So minimize leaves the genuine wear-out equipment in the ground until it fails mid-run, and maximize opens up healthy equipment that was never heading for wear-out. Both lose. Optimize is the discipline of telling those two apart, item by item.
The method: the premise gate, then two stages
One gate comes before any scoring: the premise. Every event runs for a reason, and that reason sets what belongs in the window. Anything that does not serve the premise is out before you ever look at its risk. What is left goes to a two-stage challenge. Required work, the regulatory and integrity work, is in by law. Everything else earns its place.
Stage one is a before and after risk screen: score the risk if you do not do the work, then score it if you do. An item comes in on risk only if the unmitigated risk clears your threshold and the work actually reduces it. Stage two is where most of the list lives, items below the risk line that still feel worth doing. Feel is not a basis. The Mitigation Ratio is: how much risk cost does this work remove per dollar it costs in the event? An exchanger bundle that removes three hundred sixty eight thousand dollars of risk for sixty thousand dollars of work scores a six point one, and against a threshold of two, it is in. Once every discretionary item carries that number, the whole list ranks on one scale, and the descope conversation stops being a fight and becomes a decision.
Freeze, and hold the line
Then you freeze, and the bar does not stay level, it rises. A late addition three weeks before the unit comes down has to clear a higher hurdle than the same item six months ago, because late scope costs more than early scope every time. That escalating hurdle is what keeps a frozen list frozen.
That is the standard: every discretionary hour in your window earns its place with a number, or it comes out. It is the discipline behind scope development and challenge, and it is one piece of how we help teams run shutdowns, turnarounds, and outages with confidence. All figures and screens shown are illustrative.