The argument about who paid for the Watering Hole took four meetings, and it was the first time in this whole story that nobody was confused about anything.

That is what made it different. Every previous fight had been a misunderstanding at heart. This one was not. Every animal in the room understood the question perfectly, understood what the other animals wanted, and understood exactly why they wanted it. They just disagreed, in the ordinary way, about who should carry a cost that all of them benefited from.

The Mandrill made the strongest case. He pointed out that his territory had been the first to adopt, that early adoption had subsidized the platform’s development for everyone else, and that charging him now on consumption would penalize him for having taken the risk while the cautious territories waited.

This was completely true. It was also, and he knew it, entirely beside the point, because the same argument would be equally available to him next year and the year after. The Hyena, from her branch, described it as the finest piece of reasoning she had ever heard deployed in service of not paying for something.

The Sloth arrived at the fourth meeting with a framework. It was a good framework. It would have been extremely useful at the first meeting, roughly six weeks earlier, which the Sloth acknowledged without any evident distress.

“The destination,” he said, “was always correct.”

This is not a technical problem

I want to be blunt about this because I have watched a lot of organizations get it wrong in the same way. Allocation is not a tooling problem, it is not a data problem, and it will not be solved by buying something.

It is a question about how your organization distributes the cost of a shared good among parties who all want it to exist and all prefer someone else to fund it. That is a political economy question. It has been a political economy question for as long as organizations have had shared services, and the fact that this particular shared service involves inference does not change its nature at all.

Which means the answer has to be decided, announced, and defended. It cannot be discovered in a dashboard.

Three models, and what they actually do

Central absorption. The platform sits on a central budget and is free at the point of use. Adoption is fast, because nothing is easier to adopt than something free. Consumption discipline is precisely zero, because there is no reason for it to exist. And by the second year the central line has grown large enough that somebody senior asks what it is, at which point it is politically indefensible, because nobody can attribute a single unit of it to a single business outcome.

Showback. Costs are attributed and reported to consuming territories but not actually charged. Behavior changes, genuinely, but modestly. People do respond to seeing their own number even when nothing happens as a result of it. This is the right starting position for almost every organization and it is treated as a waypoint when it should be treated as a destination for at least a year.

Chargeback. Costs move to the consuming budget. Discipline becomes real, immediately and unmistakably. So do the perverse incentives, which arrive in the same week and which almost nobody plans for.

What chargeback does to behavior

Chargeback is not wrong. It is the correct end state for a mature platform. But it changes what people optimize for, and the changes are worth naming before you switch it on rather than discovering them afterwards.

• Local optimization beats global. A territory will happily take an action that reduces its own charge and increases total organizational cost, because the first number is on its report card and the second one is not.
• Avoidance of the sanctioned path. If using the platform incurs a charge and using something else does not, some proportion of your organization will use something else. You have just recreated the conditions that produced the Tortoise’s list two lessons ago.
• Under-investment in the commons. Nobody volunteers to fund an improvement to a shared component that mostly benefits other territories, so shared components stop getting improved.
• Experimentation stops. This is the one that costs the most and shows up the least. Exploration is cheap in absolute terms and highly visible on a chargeback line, so it is the first thing a territory cuts when it wants its number down.

The shared component problem

Underneath the political argument sits a real structural one that pure consumption splitting cannot handle.

Some things in the Watering Hole serve everybody and are attributable to nobody. The retrieval index. The evaluation harness. The guardrails. The gateway. These exist so that any capability can be built at all, and their cost has almost nothing to do with how much any particular territory consumes.

Split those on consumption and you get an absurd outcome, which is that the first territory to adopt pays for digging the hole and every subsequent one drinks from it at marginal cost. This is not a hypothetical. It is exactly what the Mandrill was complaining about, which is why his argument was annoying rather than wrong.

The Crocodile, who has watched this pattern play out with every shared platform of the last twenty years, offered the observation that ended the fourth meeting. “You are trying to solve two problems with one rule,” he said. “Stop.”

The shape that works

Two mechanisms, not one.

A fixed floor, funded centrally, covering the shared foundation. The gateway, the retrieval infrastructure, the evaluation capability, the guardrails, the people who keep it running. This is infrastructure. You do not consumption-split the electrical system.

A variable band above it, tracking actual consumption, shown back initially and charged back once the numbers are trusted. This is the part that should respond to behavior, because it is the part behavior actually drives.

And a published rule defining which is which. Here the rule matters considerably more than where the line falls. Almost any defensible boundary will work if it is written down, explained, and applied consistently. No boundary will work if it is discovered by territories one invoice at a time.

Tagging is the precondition

None of this functions on untagged traffic, which is why the Field Kit item back in Lesson 1 was request level instrumentation and why I have kept returning to it.

If you cannot say which team, which use case and which business purpose generated a given unit of consumption, you cannot allocate. You can estimate, and estimates get disputed, and disputed allocations produce meetings about attribution methodology instead of meetings about decisions.

The unglamorous truth is that the organization that did three weeks of tagging work early can have this entire conversation, and the one that did not cannot, regardless of how sophisticated its thinking about allocation models happens to be.

The maturity path

Absorb, then show back, then charge back. In that order, and do not skip.

The skip is tempting because chargeback is obviously the mature answer and absorption is obviously the immature one, so why spend a year in the middle. The reason is trust. Chargeback introduced before anyone believes the numbers converts every review into a dispute about attribution accuracy. You will spend a year arguing about the data instead of a year making decisions with it, and at the end of that year the credibility of the whole exercise will be lower than when you started.

Showback is where the numbers get argued into shape at low stakes. That is not a delay. That is the work.

Three ways this goes wrong

Chargeback before trust. Real money moving on numbers nobody believes. Every meeting becomes a methodology seminar.

The free lunch that ends abruptly. Central absorption in year one, sudden chargeback in year two, adoption falls off a cliff, and the drop gets reported upward as evidence that the business was not really interested after all.

Precision theater. Enormous effort spent allocating the last few percent accurately while the entire shared foundation sits in an unexamined central bucket that nobody has looked at in three quarters.

The Field Kit

Concrete things to do this week.

If you sit in the Crow’s chair, publish the allocation rule before you publish the first allocated number. People can accept or reject a rule. They cannot do either retroactively, and if the rule arrives after the invoice it will be read as a justification rather than a policy.

If you sit in the Crocodile’s chair, make the tag mandatory at the gateway. Untagged traffic gets rejected, not absorbed. This will be genuinely unpopular for about two weeks and it settles the question for about two years.

If you sit in the Mandrill’s chair, have the argument about the model now, loudly, while it is still abstract. Once the numbers exist, every argument you make about the model will be heard as an argument about your own bill, and you will lose it on those grounds regardless of whether you are right.

For everyone: name the shared components explicitly, in a list, and decide who funds them separately from the consumption question. Two problems, two mechanisms.

Jungle Lesson 7

Everybody wants the watering hole and nobody wants it on their books. Decide who pays for the shared foundation before you decide how to split the water, because a consumption split with no floor makes the first animal to drink pay for digging the hole.

Next time: the Fox presents a benefits case with a very large number in it. The Crow does not challenge the number. She asks one question about where the hours actually went, and the room goes quiet for long enough that everyone understands what has just happened. Lesson 8 is about quantifying productivity without lying, and it is the one I would most like people to read.

The Sloth’s framework, incidentally, was good. It arrived late because nobody asked him until the situation was already unpleasant. There is usually a Sloth, and there is usually a framework, and the delay is more often a demand problem than a supply one.