What the Forest Service knows about change that consultants don’t.
In late winter, somewhere on the Coronado National Forest, a crew with drip torches walks a ridgeline. The relative humidity is above forty percent. The wind is backing down the slope. A firebreak was cut yesterday. Pump trucks are staged at three access points. At 10:14 a.m., the burn boss gives the word, and the first mixture of gasoline and diesel drips onto pine needles.
Within an hour, the crew is watching a fire they started.
The U.S. Forest Service runs about 4,500 of these a year. Around seven escape. That is less than one percent.
Change management has been talking about “burning platforms” for three decades. The phrase comes from the 1988 Piper Alpha disaster in the North Sea — workers jumped into freezing water because staying on the rig meant certain death. Daryl Conner formalized the metaphor in his 1992 book Managing at the Speed of Change, and consulting firms imported it to justify manufactured urgency in organizational transformations. The trouble is that a burning platform is a wildfire. A disruption that happens to you. The discipline you actually need is the one those crews practice on the ridgeline: a disruption you choose.
In 1905, Theodore Roosevelt signed the Transfer Act that created the U.S. Forest Service, and the new agency inherited a simple mandate: put out every fire as fast as possible. In 1944, the Smokey Bear campaign launched, building on the 1942 Cooperative Forest Fire Prevention effort; by the 1950s “Only You Can Prevent Forest Fires” had become one of the most effective public-awareness campaigns in American history. The forests seemed safer. The fire numbers fell. The agency had done its job.
Before Roosevelt and before Smokey Bear, people on this continent had been setting fire to these forests for roughly ten thousand years. The Karuk in the mid-Klamath set fire to oak savannas and mixed-conifer stands on cycles that ran roughly three to ten years depending on the resource and the location. These were not pyromaniacs. They were maintenance crews operating at civilizational scale. Low-intensity surface fire cleared undergrowth, encouraged forage species, killed pathogens, and — most importantly — kept the fuel load low enough that when a lightning strike eventually started a fire, it stayed on the ground instead of climbing into the canopy.
Suppression doctrine stopped that maintenance. The forests didn’t become safer. They became dense and choked, stacked with decades of unburned fuel. The number of small fires fell. The size of the fires that did occur grew. The term of art for this is the “fire deficit” — the gap between the acreage that should have burned under a reference regime and what actually burned under suppression.
The deficit is paid back with interest. The 2020 California fire season alone burned more than four million acres. The 2022 New Mexico gigafires, the 2023 Maui fires, the 2025 Los Angeles fires — these are not separate events. They are installments on a bill that has been accruing since 1905.
Suppression doesn’t eliminate fire. It concentrates and defers it.
The “less than one percent” figure is what gets people’s attention. But the real insight is what prescribed fire does over time. A 2024 study in Fire Ecology (Brodie et al., Fire Ecology 20:17) found that combinations of mechanical thinning and prescribed fire were still measurably reducing wildfire severity roughly twenty years after the initial thinning treatment and ten years after the most recent prescribed burn. This is not a one-time intervention. It is a schedule.
The 2022 Black Fire in New Mexico became a gigafire by area — over 131,000 hectares — but only about four percent of that burned at high severity. Researchers attributed the low severity, in large part, to prior fuels-reduction treatments including prescribed fire and previous wildfire footprints. The fire happened. The catastrophic damage didn’t.
Crews don’t pick burn days at random. They work within a narrow envelope defined by temperature, humidity, wind direction, slope, and time of year. The Southeast historically had the most generous burn windows in North America; climate change is now compressing that window as rising temperatures and declining moisture reduce the number of safe burn days. Meanwhile, California has a declared goal of treating about 400,000 acres (~162,000 hectares) of land per year with beneficial fire by 2025 — and has fallen drastically short. The constraint is no longer “can we burn.” It is “can we find enough trained burners, enough weather windows, and enough legal cover to burn at the rate the forest needs.”
Which brings us to the number most worth dwelling on.
A spotfire is what happens when an ember — a single burning fragment lofted by convection or wind — lands outside the burn perimeter and starts a small new fire. Oklahoma State Extension’s NREM-2903 fact sheet, drawing on field data across hundreds of burns, reports that with relative humidity between twenty and eighty percent, the probability of at least one spotfire occurring is 21.2 percent. Roughly one burn in five.
Now read that inside the other number. Spotfires happen on one burn in five. Escapes happen on fewer than one in a hundred. A spotfire, in other words, almost never becomes an escape. The crews expect spotfires. They staff for spotfires. A spare engine idles at the firebreak precisely because the burn boss assumes that sooner or later, today, an ember will skip the line.
The fact sheet also reports something more interesting than the aggregate. Below forty percent relative humidity, spotfire probability jumps to 41.3 percent. Above forty percent, it drops to 3.8 percent. A ten-fold swing across a single threshold. Fire behavior is non-linear, and the crews know exactly where the cliff is. They burn on the safe side of it.
This is the operational insight that most change programs never internalize. Most organizations treat small negative consequences — a team pushback, a confused customer, a missed rollout deadline — as signals to abort. The prescribed-fire discipline treats them as signals that the system is working as designed. The spotfire is not a failure of the burn. It is a prediction the burn made, caught, and contained.
A system that cannot absorb its own routine spotfires is a system forced to choose between stagnation and catastrophe. A system that expects spotfires, staffs for spotfires, and contains spotfires gets something different: routine.
Many things in the fire model have a clean analogue in organizational life, and a few don’t. The rough correspondence looks like this.
Fuel load — the decades of unburned biomass — is the accumulated dysfunction an organization carries. Dead projects nobody will kill. Processes whose original reason nobody remembers. Middle-manager resentments from reorgs that never got closure. Every suppressed decision is a handful of pine needles on the forest floor.
Ignition is the deliberate small-scale change. A pilot. A sandbox team. A time-boxed reorg of one department. A production chaos test. Netflix’s Chaos Monkey is the purest software example: it deliberately kills production services on a schedule precisely so the organization’s response muscle stays conditioned. Google’s SRE error budget is the same discipline — a non-zero tolerance for failure that lets engineers push changes without triggering catastrophic risk-aversion.
Pre-positioned crews, firebreaks, and the humidity window are everything an organization does before the change starts. Rollback plans. Communication scripts drafted a week in advance. An executive sponsor who will provide air cover when the first confused Slack message lands. The budget contingency that means a project can absorb a two-week slip without existential risk. Toyota’s andon cord — any worker’s right to stop the production line — is pre-positioned spotfire containment, elevated to cultural rule.
The spotfire is the unexpected consequence. An employee raises an objection nobody anticipated. A customer segment reacts badly to a feature. The change encounters a dependency nobody mapped. In a suppression culture, this gets treated as evidence the change should be aborted. In a prescribed-fire culture, this gets written down in the after-action review and used to calibrate the next burn.
The wildfire is what happens when all of the above has been deferred too long: forced bankruptcy restructuring, regulator-mandated breakups, mass exodus of senior talent. The fire happens to the organization rather than being conducted by it. Boeing’s 737 MAX cascade, following two decades of cost-driven deferrals of engineering investments and a corporate posture that treated pilot retraining as a commercial constraint rather than a safety question, is a modern case study in organizational fuel accumulation.
And the burning platform — the thirty-year-old metaphor that change consultants sold so hard — is the moment the wildfire arrives. By the time you’re standing on it, your options have collapsed to “jump or die.”
If prescribed fire works, and the evidence for it is decades old and accumulating, why don’t we burn more? A 2024 paper in Frontiers in Ecology and the Environment (Williams et al.) catalogued the obstacles: liability law — a burn boss is personally exposed if an escape causes property damage — air-quality regulations that flag prescribed-burn smoke even while preventing worse smoke from future wildfires, narrow weather windows, public opposition, and a severe shortage of trained burners. Every obstacle is rational on its own. The sum of them is a system that can’t do the thing it knows it should do.
The organizational obstacles map cleanly. Liability and regulatory risk become legal exposure, HR exposure, and the career risk to the executive who sponsors a failed pilot. Smoke — the visible byproduct that neighbors complain about — becomes the external communication failure, the press article about layoffs, the customer who churns during the migration. The trained-burner shortage becomes the most underrated constraint: most organizations have no internal change-craft. Every change initiative gets run by people who are running their first change initiative. The first prescribed burn a new crew conducts is dangerous. The hundredth is routine. Organizations that treat change as a series of one-off projects never get to the hundredth.
Forests are not organizations, and the metaphor breaks in at least three places worth naming.
First, and most severely: forests are slow systems. Fuel accumulates over decades and the window between burns is measured in years. Organizations are fast. A software team ships code every day; a sales team resets every quarter; a company reorganizes every few years. The cadence of “burns” in a healthy organization runs at minimum weekly and probably daily. If you read “prescribed burn” and think “big annual reorg,” you have inverted the prescription. The burn unit, for most of organizational life, is small and frequent.
Second: forests have reference conditions. Ecologists can reconstruct, from tree-ring scars, what the fire regime looked like in the ponderosa pine belt in 1700, and they use those records to calibrate targets. Organizations don’t have reference conditions. There is no objectively correct rate of organizational change against which to measure fuel-load. This is a real limitation; it means the prescribed-fire discipline in organizations has to be grounded in principles — expect spotfires, pre-position containment, practice the craft — rather than calibrated to targets.
Third: the capability gap is larger than it looks. The U.S. Forest Service has been running controlled burns, tracking their outcomes, and training burn crews for generations. Their success rate sits on top of institutional knowledge a company cannot replicate in a quarter. Treating this as a how-to is already a mistake; it is more like a direction of travel.
There is a small mercy in how the analogy breaks, which is that the Forest Service already knows. A 2020 paper from researchers at the Rocky Mountain Research Station, Organizational Learning from Prescribed Fire Escapes (Black, Hayes & Strickland, Current Forestry Reports 6:41–59), applies high-reliability-organization theory — a framework originally developed to study nuclear plants, aircraft carriers, and hospital operating rooms — to understand why those seven-or-so annual escapes happen. The metaphor flows both directions. The fire-ecology community learned change-management theory from us. The least we can do is learn fire-ecology discipline back.
An organization that takes this seriously does a few concrete things.
It defines burn windows deliberately. Not “whenever we feel like it” and not “whenever a crisis demands it.” Post-product-launch. Post-quarter-close. The six weeks after an acquisition closes, before the newly combined teams have set in their new patterns. These are the organizational equivalents of the humidity window. Most companies have natural cadences that would make excellent burn windows if anyone were watching for them.
It pre-positions containment before ignition, not after. Rollback plans, not rollback hope. An executive sponsor briefed on every plausible objection, not an executive sponsor who learns about the change from a complaining Slack thread. A budget line item for the spotfires that will occur, not a scramble when they do.
It reframes unexpected consequences. A pilot team encounters a dependency nobody knew existed. In suppression culture, this is evidence the pilot should be cancelled. In prescribed-fire culture, it is a discovery — the thing we just learned from a spotfire we contained. The after-action review is the central ritual. What did we learn. Where was the windbreak weak. Who needs a drip torch next time.
And it builds a burn association. This is what the Forest Service calls the informal networks of landowners, agencies, and trained burners who pool equipment and expertise across burn seasons. The organizational analogue is a community of practice around change-craft — alumni of past pilots who can be borrowed for new ones, a playbook that accumulates rather than a deck that restarts.
Return to the ridgeline. The burn crew is finishing up. Someone is tamping out a line of smoldering duff at the edge of the firebreak. Someone else is checking that the spotfire they caught an hour ago has been fully worked. The captain is filling out a form that will become, eventually, part of an annual report. Tomorrow they will do this again on a different ridge.
For the Karuk, and for the dozens of other peoples whose fire stewardship shaped the ecosystems we now think of as natural, this is not a change initiative. It is not a transformation. It is just the work — the seasonal, unglamorous, necessary work of keeping a forest a forest. The reason Euro-American management doctrine kept inventing more dramatic metaphors for change — burning platforms, disruption, revolution — is that it had forgotten there was a quieter practice underneath.
Most of what change management wants is already available. It has just been misfiled under transformation when it belongs under maintenance. The companies that figure this out will not win because they ran a heroic reorganization. They will win because they ran a few thousand small burns that nobody wrote a book about.
Seven of those burns escaped. The other four thousand four hundred and ninety-three did exactly what they were supposed to do.
Spotfires aren’t bugs. They’re predictions the burn made.
The essay’s prescription — pre-position containment before ignition, treat unexpected consequences as discoveries to log rather than failures to abort — is exactly what an agent rollout needs. Every agent that ships into production is a small ignition. The question is whether you have firebreaks. Chain of Consciousness is the firebreak: every claim an agent makes — capability, performance, behavior — gets anchored to a public provenance chain, so when a spotfire lands, you can trace it back to which burn started it and contain the perimeter. The after-action review writes itself.
See a live provenance chain · Verify an agent’s rating · pip install chain-of-consciousness