Tripwires and Gradual Drift: Why You Need Pre-Set Triggers to Catch Slow Failure
Slow failure is invisible from the inside, because you compare each month to the one before it and never to the plan. A tripwire compares the number to a line you drew when you were thinking straight.
You started the year with eighteen months of cash and a plan that said you’d be at break-even before it ran low. In January you had sixteen months of runway, slightly behind, nothing to lose sleep over. In April you had thirteen, and you told yourself the pipeline was about to turn. In July you had nine, and you’d grown so used to the number sliding that nine felt like just another step down from ten. Each month you compared the balance to last month’s balance, the gap was small, and a small gap never feels like a reason to do anything. By the time nine months of runway frightened you, the cheap moves were eight months behind you, and the only ones left were the expensive ones.
Nobody got the decision wrong here, because nobody ever sat down to make one. You measured the drop against the wrong thing every single month, and the wrong thing made the drop look survivable right up until it wasn’t.
The evidence
The reason you missed it is not that you stopped watching the number. You watched it every month. The reason is that you compared each reading to the one before it, and against that yardstick every single step was small. Drift is invisible because you judge it against a moving baseline, and a baseline that moves with the thing it’s measuring can never register a trend. This is the same limit that shows up when people try to recall a familiar object from memory: you handle a coin every day and still can’t draw which way the head faces, because continuous exposure registers as sameness, not as information. Your runway feels like your runway. Last month’s number becomes the standard you grade this month against, and the original plan, the only fixed line that would have shown you the slope, drops out of the comparison entirely.
There is a second force pushing the same way, and it sets the price of doing something about the drift. You favour the current course far past what its merits justify, and the pull gets stronger the more committed you already are. This is status quo bias, among the more reliably reproduced findings in decision research. Its practical effect is to make two thresholds wildly unequal. The threshold to keep going is essentially zero: you do nothing, the spend continues, the runway ticks down, and no one has to act. The threshold to change is high: you have to gather the numbers, build the case, tell people the plan you sold them is slipping, cut something you fought to fund, and carry the cost of saying out loud that it isn’t working. So the cheap path is always continuation, regardless of what the cash position deserves, and you lean on it without ever choosing it.
Attention finishes the job. When you’re heads-down running the thing, hitting payroll, closing the next deal, shipping the release, slow changes in the surrounding numbers stop reaching you. People focused hard on a counting task will miss a person in a gorilla suit walking straight through the scene. Your runway is the gorilla. It’s right there on the dashboard, and the task in front of you swallows your attention so completely that the slope never lands.
How it works
Put those together and the trap is structural, not a matter of discipline. You’re grading a falling number against its own recent history, the cost of acting on it is loaded entirely onto the side that breaks the routine, and your attention is spent on the operation rather than the trend. None of that gets fixed by deciding to pay closer attention, because the failure isn’t inattention. You were looking. The failure is that you had no fixed line to look against, so there was nothing for the looking to catch on.
A tripwire works by supplying that missing line and handing the decision to it instead of to you. You set a specific number in advance, and when the balance crosses it the question of whether to re-evaluate is already answered. The comparison stops being this month against last month, which always reads as continuity, and becomes this month against a standard you fixed when you could still see the whole slope. That swap is the entire move. You’re not asking yourself to notice the drift in real time, because the thing that makes drift dangerous is precisely that you can’t.
A tripwire moves the decision off your in-the-moment judgement and onto a line you drew back when you could still see the whole slope.
The specificity is what makes it bite. “Keep an eye on cash and act if it gets tight” is not a trigger, it’s the same wish that let the runway slide in the first place, and it bends to the same rationalisation: this month is unusual, the pipeline’s about to turn, give it one more. Once a line is loose enough to argue with, it stops doing any work at all. “If runway drops below seven months, we stop hiring and rebuild the forecast from scratch” either fired or it didn’t. There’s no reading of the balance that lets you talk your way around a number you already crossed.
How to use it
Set the trigger at the moment you commit, long before you have any reason to worry. The time to write down what a dangerous cash position looks like is when you’re funding the plan, clear-headed and not yet attached to any story about how the quarter will go. Seven months of runway would alarm you today, sitting at eighteen. It will not alarm you in July, after you’ve watched the number step down past it one small move at a time and normalised every step. Writing the line down now is a way of preserving the judgement of the version of you who can still see straight, and arranging for it to arrive at the moment you’ll have lost it.
One number and one date will carry most decisions. The instinct is to build something elaborate, a basket of metrics with weights, runway and burn rate and pipeline coverage all blended into a score. Resist it. A blended condition is harder to read, easier to explain away, and far less likely to be honoured, because a composite always has a soft component you can lean on to argue it hasn’t really triggered. “Cash below seven months” or “burn above ninety thousand for two months running” is checkable in one glance and impossible to negotiate with, and that plainness is exactly what makes it hold.
Setting the trigger is the easy part. The hard part comes later, when it fires in the middle of a good story and you have to honour it anyway. Cash crosses your line in the same week a large deal moves to final stage, and every instinct says the number is about to be wrong, hold off, don’t cut now and look foolish next month. Firing the trigger does not mean you have to stop. It means you have to actually decide, in the open, with the real numbers in front of you, instead of letting the spend roll on because deciding was the harder of two paths. Sometimes the honest read is to continue, with the deal weighted properly and the forecast redone. The trigger’s job is only to take away your ability to continue by default, without ever having looked.
Why it matters
Most of what drains a company is spend that nobody decided to keep spending. The contractor who became permanent in everything but the paperwork. The tool the whole team forgot they were paying for. The project that outlived its case a year ago and kept burning because stopping it never reached the top of anyone’s list. None of it shows up as a crisis. It shows up as a runway that’s shorter than it should be, for reasons no one can fully reconstruct, because each commitment was small the month it started and never got measured against the plan again.
The damage from drift is large and almost impossible to see, because it arrives as a slow misallocation rather than a single bad day. No alarm goes off. There’s no meeting where someone announces the cash position turned. You just find yourself, eventually, with less room than you thought and fewer cheap options than you’d have had if a number had stopped you nine months earlier. A tripwire is a small piece of honesty you commit in advance: you name the exact balance at which you’ll force yourself to look, while you can still pick it without flinching. It won’t make the hard call for you. It only guarantees that when the cash says it’s time, you’re the one who decides, instead of the default deciding for you while your attention was somewhere else.
References
- Heath, C., & Heath, D. (2013). Decisive: How to Make Better Choices in Life and Work. Crown Business.
- Samuelson, W., & Zeckhauser, R. (1988). Status quo bias in decision making. Journal of Risk and Uncertainty, 1(1), 7–59.
- Simons, D. J., & Chabris, C. F. (1999). Gorillas in our midst: Sustained inattentional blindness for dynamic events. Perception, 28(9), 1059–1074.
- Bazerman, M. H., & Watkins, M. D. (2004). Predictable Surprises: The Disasters You Should Have Seen Coming, and How to Prevent Them. Harvard Business School Press.
- Nickerson, R. S., & Adams, M. J. (1979). Long-term memory for a common object. Cognitive Psychology, 11(3), 287–307.
One tool a week
How you think, decide, lead, focus, and stay steady under pressure. A specific way to practice one move before the next seven days are out. Grounded in evidence, not self-help.
One email a week. Leave whenever. Powered by Buttondown.
You're almost in. Check your inbox to confirm your subscription.