The Wednesday Field Guide. Monday's essay split the level of words from the level of facts. This entry takes one word that sits on the fault line.
Kuwait, 2003. We staged for the push into Iraq and drew a mission to secure an airfield. The intel imagery showed debris across the field. Cars, set in places too deliberate to be random. We read them the only responsible way. Vehicles staged like that get wired. We planned the clearance on that assumption and treated every car as a live charge.
We reached the field. The cars sat where the imagery showed them. No mines, explosives, or anything wired.
Here is what has been in my mind ever since. The debris was in place, and there were no explosives. We prepared for what could have happened. I will never know whether we prevented a mass-casualty event or whether there was never a bomb to prevent. The disaster that does not arrive cannot tell you whether it was coming. If there was something there, we never found it.
That is the trouble with the word “prevented.” It carries two claims, and they are not the same.
One claim says I lowered the odds. You can check that. The other claim says without me, the bad thing happens. You really can not check that, because the event that never occurred leaves nothing to measure. Most arguments about prevention are two people holding different halves of the same word. If we want to discuss the same thing, we need to ask each other more questions.
Put the index back
Monday’s essay drew Hayakawa’s split between the level of words and the level of facts. “Prevented” is where that split shows up inside a single word. Hayakawa taught a second tool for exactly this: the indexing rule. Chair-1 is not chair-2. Two things wearing the same word are never identical. The word hides the difference until you add the number.
Prevention-1 is a single averted event. The airfield. One day, one field, one charge that may or may not have been real.
Prevention-2 is a lowered rate of events across many cases. Insurance lives there. So do vaccines, seatbelts, and rehearsed procedure. You cannot prove the policy saved you this month. You can prove, across thousands of policyholders, that the pooled prevention is real and priced to the dollar.
The word “prevented” drops the index. Dropping it is where problems arrive.
Prevention-2 from the same war
We ran convoys in Iraq. Before we rolled, we drilled what would break. A vehicle breakdown. A truck separated from the column. Hostile fire. A tire change under load. An overheated engine. An improvised explosion. A vehicle lost from the convoy entirely. We set rally points along every route and ran the procedure for each failure until the procedure was reflex.
On one movement, a vehicle got separated. The crew did what we had practiced. They returned to the last rally point and held. We found them. Their truck had broken down, the exact failure we had rehearsed.
The event happened. It stayed small. It stayed small because we had run the repair hundreds of times before the day we needed it.
You cannot replay one convoy to test one drill. The countable claim runs across reps and units: rehearsed repair contains escalation. Run the repair enough times and the escalation rate drops, and the drop is something you can measure. The repetition was the infrastructure. The practice lowered the threshold for catching the failure before it spread. This is measurable across time and events.
Why the word gets abused
When the only thing you can point at is nothing-happened, you cannot tell the person who prevented the problem from the person who says they did. Both point at the same empty field.
A writer I read closely, Arimitsu, mapped this extremely clearly. Arimitsu works front-of-house in hospitality and writes from the floor. In a recent essay, they laid out why prevented work resists scoring. You cannot separate “you fixed it” from “it was never going to fail.” Put a reward on invisible work, and the first thing you summon is people who fake invisible work. That is a correct observation. The single averted event resists proof, and the faker hides in that gap.
The essay lives entirely in prevention-1. Prevention-2 is different, and it is where the measurement waits. Index up, and the seeing becomes ordinary. Actuaries do it every day. So do the people who price your car insurance and the units that drill rally points before they need them. His conclusion, that any system trying to credit prevention ends up believing what it cannot see, holds at the level of the single case. It dissolves one index higher.
Pin it in this room, today
Prevention-1 — a single averted event. You are owed a probability, not a proof. Unprovable case by case.
Prevention-2 — a lowered rate of events across many cases. Measurable, falsifiable, priced.
Includes: a drill that turns a breakdown into a delay; a policy that lowers a population’s loss rate; a rehearsed procedure that contains a real failure.
Excludes: “I stopped the disaster” when no disaster arrived, and no rate was measured. That is a sequence cosplaying as a cause.
Example: the convoy. The breakdown came. The repair held. The escalation rate dropped, and you can count it across events.
Non-example: the airfield, claimed as a save. We acted. Nothing happened. Honest reporting stops at “we prepared.” The causal claim stays unearned. We did not prevent anything, and nothing happened.
The one-minute script
When you hear “I prevented that,” or catch yourself saying it, ask which prevention is on the table.
For the single case: “What would have happened, and how do you know?” If the answer is a story about a future that never arrived, the speaker is owed a probability, not a medal.
For the rate: “Across how many times, and what changed?” If the answer is a count and a measured drop, that is the real thing, and it deserves the credit.
Then write it down where the next person will see it. Prevention-2 leaves a record only if someone makes one. The convoy drill held because someone logged the rally points before the truck broke down. The repair was written before it was needed.
Back to the field
I think about the airfield more than the convoy. The convoy I can defend with a count. The airfield I cannot. We geared up for a threat that never happened, and I will go to my grave not knowing if we prevented anything. That is OK.
That uncertainty is honest. It is also the exact spot where the word “prevented” gets worked, because the person who wants credit for the empty field sounds identical to the person who earned it. The only way to tell them apart is to ask which prevention they mean. The answer tells you whether they are owed proof or owed a probability.
Ask the question. The word will not ask it for you.
If this landed, the work goes deeper.
Every essay here draws from an active advisory practice. I work with learning and development directors, workforce administrators, and education leaders on the same problem from the other side: not the analysis, but the repair. Diagnostics, workshops, and standing advisory engagements through jerrywwashington.com. A 30-minute call costs nothing.
Jerry W. Washington, Ed.D., is a Marine combat engineer veteran, independent researcher, and instructor at UCI Division of Continuing Education. He writes What Time Binds on Substack.
Sources
Hayakawa, S.I. (1949). Language in Thought and Action. The indexing rule and the report–inference–evaluation distinction.
Arimitsu (2026). The Office of Being Disbelieved and earlier writing on the invisibility of preventive work. Published on note (Japan).
Washington, J.W. (June 29, 2026). At the Level of Words, At the Level of Facts. Part 1 of three. What Time Binds.
Jerry, this split between Prevention-1 and Prevention-2 is a sharp indexing move to add to the conversation for sure. The part that hits based on some of our previous conversations is smooth because it doesn't argue with observations, feedback, and/or critique of the work, it just moves it a level up.
What I'd add from my own work, and from a conversation I've been in with both of you about this, is a trigger question that sits underneath the index. Both prevention types you describe assume the intervention precedes any visible signal. But some repair work enters after the signal is already present: a diagnosed condition, not a forecasted one. The drift, the gap between what an organization says it values and how it actually operates, is already visible and legible before the repair begins. The doctor doesn't prescribe specific vitamins before running blood work and assessment. That's a different claim than either prevention-1 or prevention-2, and it's a stronger evidentiary position because you're not pointing at an empty field, you're pointing at a before-and-after on a diagnosed condition.
The airfield ending brings it home. "We prepared" is honest. Most people would have taken the medal. The fact that you leave it on the table is what gives the rest of the piece its credibility.
To me, the 2003 airfield still feels like prevention. Even if no one will ever know whether there was a real threat, clearing what could have become a catastrophe still mattered. Maybe it prevented direct harm, maybe it didn't — but removing the uncertainty itself did something certain. The people who came after could move forward without carrying that fear. That peace of mind has value in its own right.
I've been turning the same problem over for a while, and I ended up somewhere close to your move: change the order. Explain the risk and the intended action beforehand. If nothing happens, the note becomes a record — instead of inferring an invisible problem afterward, you compare what was said with what followed.
And I think your prevention-2 is where my "score sheet" was trying to go. Once could be luck; over enough rounds you see whose read consistently lands, and that record is much harder to fake. The difference, maybe, is who gets enough rounds — an insurer or a unit has the repetitions to form a rate, while one person on a floor usually doesn't.