Somebody finally counted the pilots.

It had not occurred to anyone to do this, because each one had been approved separately, by a different animal, at a different time, for a defensible reason. The count came out at a hundred and eighty something. The precise number was disputed for a while, on the grounds that several of them might not technically still be running, which turned out to be a question nobody could answer.

The Hyena found this genuinely funny for about four minutes, which is a long time for a hyena.

The Fox went through the list looking for the ones that had produced something. He found eleven. Of those eleven, four had been quietly switched off after the demonstration, two had become the departmental builds on the Tortoise’s list from the previous season, and the remaining five were still running as pilots, funded quarter to quarter, eighteen months after proving whatever they had been set up to prove.

“So what happened to the other hundred and seventy?” asked the Crow.

“Mostly nothing,” said the Fox. “They ran, they showed something, everyone was pleased, and then the person who cared moved on to something else.”

The Crocodile opened one eye.

“You didn’t buy a capability,” he said. “You bought a hobby, a hundred and eighty times.”

The arithmetic nobody does

Here is the calculation that nobody performs, because each pilot is approved in isolation and isolation is where this problem hides.

Every pilot carries a fixed cost that has nothing to do with its scope. Getting access sorted. Wiring up to a data source. Standing up somewhere to run it. Building enough evaluation to know whether it worked. A security review. A privacy review. The meetings, which are not free, and which involve expensive animals. Somebody writing a summary at the end.

That fixed cost does not shrink because the pilot is small. A two week experiment and a two month one pay roughly the same setup tax. Which means the true cost of a pilot is somewhere between two and five times what appears on its approval, and almost all of it is invisible because it is spread across other people’s time.

Now multiply by a hundred and eighty.

The number that comes out of that is almost always larger than whatever line item the organization is currently anxious about. In the jungle’s case it was substantially larger than the inference bill that had started this whole conversation four posts ago, and it had never once been discussed as a single number, because it had never once existed as a single number.

Why nothing compounds

The arithmetic is bad. The structural problem underneath it is worse.

In a healthy system, the fortieth thing you build is cheaper than the fourth, because the fourth left something behind. Some infrastructure, some patterns, some hard-won knowledge about what breaks. That is what makes a platform a platform.

Pilots leave nothing behind. Each one builds its own retrieval, its own evaluation, its own prompt scaffolding, its own access pattern, its own little arrangement with whoever owns the data. When it ends, all of that goes with it. The team disbands, the environment gets reclaimed, and the summary document goes into a folder that will be reorganized next year.

So pilot forty costs the same as pilot four. There is no curve. There is a straight line with a bad slope, extending as far as anyone is willing to keep funding it, and the organization experiences this as a series of individually reasonable decisions.

This is the thing to understand about the pilot trap. It is not that the pilots are bad. Several of them were excellent. It is that a hundred and eighty of them, run this way, produce exactly as much accumulated capability as one of them does, which is none.

The graduation problem

The five survivors on the Fox’s list deserve their own attention, because they illustrate a failure that is somehow both obvious and universal.

A pilot is funded to prove something. When it proves it, the funding logic has been satisfied, and the thing that made the money flow no longer applies. There is usually no defined path from proof to production, no budget line waiting, and no team whose job it is to receive it.

So the successful pilot ends up in exactly the same position as the failures. Still running, still on temporary funding, still argued about every quarter, and slowly starved by an organization that has moved on to approving the next batch.

I have watched genuinely good capabilities die of this. Not rejected. Not found wanting. Simply never picked up, because success was not something anybody had designed for. The Mandrill put it well when he finally understood what he was looking at: “We’ve built a system that can start things and cannot finish them, and we call the starting part innovation.”

The portfolio inversion

What good looks like is roughly the inverse of what most organizations have.

A small number of capabilities. A large number of use cases running on them. Not many initiatives each carrying its own complete stack, but a handful of well-built things that many parts of the business consume.

Almost every enterprise I have seen has this exactly backwards. Dozens or hundreds of initiatives, each with its own everything, and no shared foundation underneath any of it. Then somebody proposes consolidation, and the resistance is immediate, because every one of those initiatives has an owner who experiences consolidation as losing control of their thing.

The economics are not subtle. In the capability model, the fixed cost is paid once and amortized across everything that uses it. The marginal cost of the next use case falls as the platform matures. The cost curve bends. In the pilot model, the fixed cost is paid every single time, and the curve does not bend, ever, because there is nothing for it to bend around.

What this sets up

I am deliberately not going to resolve this here, because the resolution takes a whole act and doing it badly in three paragraphs is how this subject usually gets ruined.

What a capability actually is, how it gets funded when your organization’s entire financial machinery is built around things that end, who owns it, and what has to be traded to make it politically survivable, all of that is Act IV. It is the part of the series I expect to be most argued with.

For now the useful thing is to have the number. Count your pilots, multiply by an honest fixed cost, and look at the total. That single figure changes more conversations than any framework I could give you, because it converts a hundred and eighty reasonable individual decisions into one unreasonable aggregate one, which is what it was all along.

Three ways this goes wrong

Innovation theater by volume. The number of pilots becomes the metric that gets reported upward. Once that happens the incentive is to start things, not to finish them and certainly not to kill them, and the count grows because the count is the point.

The graduation cliff. No funding path from proof to production, so success is fatal. The tell is that your longest running pilots are also your best ones, which should be alarming and is usually described as pragmatism.

Capability in name only. A platform team is created, everyone agrees consolidation is the right idea, and then each territory carries on building its own stack on top of the shared one. You now pay the duplicated fixed costs and a governance layer, which is worse than where you started, and it is very common.

The Field Kit

Concrete things to do this week.

If you sit in the Crow’s chair, get the count and multiply it by your honest fully loaded fixed cost per pilot. Include the meetings and the reviews. Bring the total to your next steering meeting as a single number with no commentary attached and let the room react to it.

If you sit in the Crocodile’s chair, list what every pilot has rebuilt from scratch. Retrieval, evaluation, access, deployment, monitoring. That list is not a complaint. It is the specification for your platform, written for you, by evidence.

If you sit in the Mandrill’s chair, stop starting things. Pick the three use cases in your territory that genuinely matter and kill the rest publicly, so that people believe the change is real. Quiet cancellation teaches nobody anything.

For everyone: ask what happens to a pilot that succeeds. If nobody can answer, you do not have a pipeline. You have a graveyard with excellent intentions and a quarterly approval process.

Jungle Lesson 5

Pilots are cheap individually and ruinous collectively, because each one pays the setup cost again and none of them make the next one easier. A hundred experiments is not a strategy with good coverage. It is the same experiment, funded a hundred times, by people who have not met.

That closes the first act. Five lessons in, the jungle now knows that its bill is shaped differently from anything it has managed before, that three groups have been arguing in three currencies, that the layer everyone budgeted for is not the layer that hurts, that the most interesting demand signal in the building was sitting on a compliance officer’s desk, and that a hundred and eighty reasonable decisions can add up to one unreasonable one.

What it still cannot do is answer the Crow’s original question. Are we getting enough for what we are paying? That requires learning to count, which is the second act, and it starts with the least glamorous and most consequential decision in the whole discipline: choosing what to divide by. Lesson 6 is about picking a denominator, and why choosing turns out to be considerably harder than complaining about not having chosen.

If you have never counted your pilots, the count is usually a bad afternoon and a very good quarter. I have yet to see an organization regret doing it, and I have yet to see one where the number was smaller than expected.