The number on the Fox’s slide was very large, and he had checked it three times.

Six hundred and eighty animals were using the capability. Survey responses indicated an average of twenty two minutes saved per animal per day. Multiply that out across a working year, apply a loaded hourly rate, and you arrive at a figure with a great many digits in it, sitting in a box, in bold, next to a modest and considerably smaller number representing what the whole thing cost.

It was, by the standards of these presentations, a good one. The arithmetic was correct. The survey was real. The adoption numbers were not inflated. I have seen a hundred versions of this slide and this was among the more honest ones.

The Crow looked at it for a while.

She did not challenge the twenty two minutes. She did not question the adoption figure or ask about the survey methodology, which is what the Fox had prepared for and which would have been a conversation he could win.

“Where did the time go?” she asked.

The Fox said that it went back to the animals.

“Yes,” said the Crow. “And then what?”

The room was quiet for long enough that everybody in it understood what had just happened, including the Fox, who to his considerable credit did not attempt to fill the silence with anything.

The Hyena, for once, was not laughing. “That’s the whole thing, isn’t it,” she said. “You’ve proved they have more time. You haven’t proved you have anything.”

Why twenty minutes is not twenty minutes

Here is the fallacy, stated plainly, because it is the single most successful piece of fiction in modern enterprise reporting and it is almost never named directly.

Twenty two minutes saved by each of six hundred and eighty animals is not roughly two hundred and fifty person days of recovered capacity. It is six hundred and eighty animals with slightly better afternoons.

Those are not the same thing and they are not close to the same thing. The first is a resource the organization can deploy. The second is a genuinely nice outcome that produces no line in any ledger, ever, under any circumstances.

Time saved becomes money only when it is aggregated into something the organization can either redeploy or avoid paying for. Twenty two minutes, distributed across six hundred and eighty people, in fragments, throughout a day, aggregates into nothing at all. It is real. Every one of those animals genuinely got the time back. It simply does not add up into a unit anybody can spend.

The three conversion paths

There are exactly three ways time turns into money, and I would rank them by how well they survive scrutiny.

Cost avoidance. A role you did not need to backfill. A contractor whose renewal you did not sign. Overtime you did not pay. Seasonal capacity you did not bring in. This is the strongest by a wide margin, because it is verifiable in the ledger by someone who was not involved in the project. If you can point at a requisition that was cancelled, you have a benefit, and nobody can argue with you.

Capacity redeployment. The same people producing measurably more of something the organization values. Not more availability. More output. This is real and it is the most common genuine benefit, but it requires an output metric rather than an input one. “The team has more time for strategic work” is not this. “The team closed forty percent more cases” is.

Quality and cycle time. Faster resolution, fewer errors, better retention, higher conversion. Frequently the largest of the three in absolute terms, and the hardest to trace, because it needs a chain of evidence running from the capability all the way to something financial. Worth doing. Not worth pretending is easy.

And then the part people find uncomfortable. Anything that does not land in one of those three is not a benefit. It is a nice thing.

Nice things matter. Less frustrating work, less time on tasks people hate, better morale, lower attrition risk. I am not dismissing any of it and some of it is genuinely valuable. But it should be reported as what it is, in its own section, under its own heading, rather than converted into currency by multiplication and placed next to the cost line as though the two numbers were the same kind of object.

The fragmentation threshold

Underneath all of this sits a threshold effect that I think deserves more attention than it gets.

Below some proportion of a role’s time, savings do not aggregate at all. They dissipate. The person absorbs the time into the general texture of their day and nothing further happens, because there is no mechanism by which fifteen scattered minutes become a deployable resource.

Above some proportion, savings become visible enough that the work can be restructured, and restructuring is what actually converts time into capacity or cost. A role that gets thirty percent of its time back can be redesigned. A role that gets four percent back cannot.

Where exactly that threshold sits depends on the work, and I would be suspicious of anyone quoting you a universal number. But the existence of the threshold is the important part, because it explains something that otherwise looks like a paradox: why broad shallow deployments produce enormous claimed benefits and almost no realized ones, while narrow deep deployments produce modest claimed benefits that actually show up.

If your deployment strategy is a small saving for a very large number of people, you have chosen the shape that maximizes the claimable number and minimizes the realizable one. That may still be the right choice. It should be a conscious one.

Self-reported savings, and what happens to them

Two things about survey data, since it is the evidence almost everyone uses.

First, people overestimate time saved, consistently and without any intent to mislead. Asking someone how much time a tool saves them is asking them to compare their current experience against a remembered version of a process they have stopped doing. Memory is generous about this in a fairly reliable direction.

Second, and more usefully, reported savings decay. Measure at week two and you get a peak, because the contrast with the old way is vivid and the novelty is real. Measure the same population at month six and the number will be materially lower. Measure at month twelve and lower again, as the improved process becomes the baseline against which nothing feels saved.

This is not people becoming disillusioned. It is the reference point moving, which is exactly what you wanted to happen. But it means an organization that measures once, at week two, and then funds a permanent capability on that number, has funded on a peak that will never recur.

The honest format

What I would put on the slide instead, and what the Fox put on the next version of his.

State the gross number. Twenty two minutes, six hundred and eighty animals, here is what that multiplies to. Do not hide it, it is real and it is the reason anyone is interested.

Then state the conversion path for each portion of it. This much lands as cost avoidance, here is the specific requisition. This much lands as redeployment, here is the output metric that will show it. This much has no conversion path and is reported as a nice thing.

Then state the realized number, which will be dramatically smaller. And then show the gap between the two, explicitly, as its own line.

That gap is not a weakness in your case. Showing it is the single thing that makes everything else in the presentation believable, because it demonstrates that you understand the difference between the two numbers, which is the exact thing the Crow was testing for when she asked her question.

The Crow is not the enemy

One more thing, aimed at anyone who reads this and feels defensive on the Fox’s behalf.

A benefits case that survives scrutiny gets funded again next year. A benefits case that does not survive scrutiny does not merely fail, it takes the credibility of the whole program with it, and the next request from the same team starts from a worse position than the first one did.

The Crow was not trying to kill the capability. She was trying to find out whether she could defend it to somebody more senior than her, six months from now, in a room the Fox will not be in. The question she asked is the question she will be asked. She was doing him a favor and it took him about a week to work that out.

Three ways this goes wrong

Loaded rate multiplication. Hours times salary, no conversion path, presented with total confidence. This works exactly once, on an audience that has not seen it before.

Double counting. The same saved hours claimed by the platform team, the use case owner, and the enterprise transformation program, none of whom are aware the others are claiming them. In a large organization this is startlingly common and it only surfaces when somebody adds up all the claimed benefits and finds they exceed the total cost base of the function.

The benefit with no owner. Claimed in the case, never assigned to anybody, therefore never realized, and nobody notices because nobody was watching for it. This is the most common of the three and the quietest.

The Field Kit

Concrete things to do this week.

If you sit in the Crow’s chair, ask two questions of every claimed benefit. Which of the three conversion paths does this use, and who owns realizing it. Thirty seconds, and it will do more for the quality of your portfolio than any amount of process.

If you sit in the Crocodile’s chair, give the business the usage and acceptance data they need to make an honest case. Withholding it does not protect the program. It guarantees the case gets built on survey data instead, which is weaker, and which will fail later at higher cost.

If you sit in the Mandrill’s chair, commit to a realized number rather than a gross one, and accept that it will be a fraction of the headline. A smaller number you hit is worth considerably more to your standing than a large one you miss, and it is the only version that gets you funded a third time.

For everyone: stop reporting hours saved as a headline figure. Report the conversion. If there is no conversion, report it as a nice thing, in its own box, honestly labeled.

Jungle Lesson 8

Time saved is not money saved until somebody does something specific with the time. Twenty minutes back for six hundred animals is not two hundred days of capacity, it is six hundred slightly better afternoons, and you cannot put an afternoon in the ledger.

Next time: the Owl finally has his moment. It turns out he has been quietly holding a control group for two seasons because nobody ever told him to stop, which makes him the only animal in the jungle who can prove anything at all. Lesson 9 is about baselines, counterfactuals and holdouts, and how to demonstrate value when you cannot run a clean experiment.

If you are about to present a benefits case built on survey data and a loaded hourly rate, the question at the top of this piece is the one you will be asked. It is worth having an answer before somebody else has the silence.