KiOR and the Iceberg We Failed to See: Reading the Ocean in FOAK Projects

by Jim Lane (Biofuels Digest) ... And yet, the critique has never quite felt complete. Because each explanation treated KiOR as if it existed on its own—like a machine that either worked or didn’t. Based on public reporting, industry accounts, and our prior coverage of the KiOR story, a clearer pattern emerges in hindsight.

But KiOR wasn’t just a machine. It was a ship. And it wasn’t sailing in a spreadsheet. It was sailing in an ocean.

The Software Ghost in the Industrial Machine

The tragedy of KiOR began with a fundamental mismatch of cultures. Backed early on by Silicon Valley investors, the project was managed (by others, an experienced management team) with what was an impressive velocity, a “blitzscaling”, that brought to mind the rhythms we know at the Digest from our software developments and daily publishing. The company pushed for fast innovation cycles—why not? Many do — but there was a fatal arrhythmia when applied to the multi-year steel-and-concrete of a biorefinery, using the tools of the time.

Software could iterate in a vacuum, even then. First of a Kind (FOAK) plants struggle with this, even now. Then, inside KiOR, the signals we might recognize now, were there, early. Pilot results didn’t match the story. Internal voices argued for a different path—baseline the system, split the reactions, slow down, learn.

Instead, the project accelerated. The story pointed one way. The data pointed another.

That gap has a shape. Later, we’ll call it Symbolic Compression Divergence (SCD)—the moment where the narrative of a drop-in fuel becomes physically decoupled from the oxygen-laden acidic reality of the output.

The Refinery Wall

The promise was refinery-ready fuel. The reality was a bio-oil with roughly 17% oxygen.

KiOR hit what the industry now calls the Refinery Wall. Partners like Catchlight Energy (Chevron/Weyerhaeuser) and ExxonMobil could not process the product. It wasn’t “drop-in.” It was drop-kick.

Instead of aligning with partners and their experience, as we related in our long narrative look back at the KiOR story, the company continued along its original development path. They spent another $90 million bolting on a hydrotreater and hydrogen plant to make their product usable.

That’s something, but it is not partner alignment. In the end, it strikes us as adding weight to a boat already pointed the wrong way.

When KiOR slipped from 67 to 22, it didn’t just miss a target. It crossed a threshold—where uncertainty was being generated faster than capital markets could absorb it.

At that point, the plant isn’t producing fuel. It’s producing doubt—and doubt is the one thing capital markets price instantly.

When adaptive capacity is constrained, the system begins to degrade from the inside.

The tragedy is that a Turbine actually existed for the company to escape its fateful ‘iceberg encounter’. A “Stealth Team”

The FOAK Fragility Index

If you were standing on the Columbus site in the early 2010s, here’s what you would have been measuring—without knowing it:

Seen this way, KiOR didn’t fail because of one thing. It failed because the ship and the ocean were out of sync.

TEA can tell you whether the boat should float. TRL can tell you whether it’s been built before. But neither tells you whether you’re launching into a rising tide, a rip current, or a storm. Or an iceberg.

Coda: If We Could Have Read the KiOR Ocean

Our goal today is not to revisit a painful episode for no reason. Let’s ask, what would it have looked like to navigate using a FOAK Fragility Index in real time? KiOR failed gradually—then suddenly. A framework like FOAK Fragility would have changed the signals management acted on.

Fast Forward to Now: Reading Today’s Ocean

The ocean doesn’t care about your model. It only cares whether your structure can stay coherent under pressure. You don’t avoid failure by building a bigger ship—or even a better one.