The Double Bill

The slide goes up in a quarterly review. A tiered escalation path: level one to the service desk, level two to the platform team, level three to a single name in a box with a four-hour response window. The sponsor who asked for it leans back. Months of "who do I even call about this" have just been compressed into one clean diagram, and the room can feel it.

Two people in that room are worth watching. The first is the sponsor, who requested the path and just received exactly what they asked for. The second is the name in the level-three box.

I have sat in rooms like this in local government, where the path ran through a permit office and the name in the box belonged to the one analyst who actually knew the system. I have sat in them in private industry, where the box held an integration lead who had been quietly catching failed jobs for two years before anyone drew a diagram around them. I have watched it happen where the instrument was not an escalation path at all: an ownership matrix, shipped after an audit, that turned one architect's informal habit of reviewing changes into a signature requirement on every one of them. The settings change. The slide does not. Someone asks for clarity, someone produces a diagram, and someone's name goes in the box at the top of it.

The request always sounds reasonable, because it is. We need visibility. We need a clear owner. We need to know who to call. No responsible leader hears those sentences and objects to them.

The accounting starts after the applause.

The sponsor received a diagram. It answers their question, closes their action item, and survives every audit that asks whether an escalation path exists. As a purchase, it performed.

The name in the box received an itemized bill.

Line one: nothing came with the box. No staffing. No budget. The formalization arrived as a named responsibility, not a resourced one, and the diagram does not have a column for that difference.

Line two: escalations now route to them officially. Before the slide, people found them because they were useful. After the slide, people find them because a document says to. The same requests, now with a paper trail and a four-hour window attached.

Line three: help they gave freely hardened into obligation. The favor that used to earn gratitude now earns a ticket number. Miss it, and the miss is measurable. What was generosity is now a service level, and service levels do not say thank you.

Line four: ownership in name, none of the authority to change the load. They own the outcomes of a queue they cannot shrink, staffed by a team they cannot grow, fed by upstream decisions they do not get a vote on.

Four line items, and they still were not the expensive part.

The expensive part is that the informal path never closed. The people who used to walk over, message directly, or catch them in the hallway kept doing it, because the informal path was faster and it had always worked. The tickets arrive through the new front door. The favors keep arriving through the old one, usually as a message that opens with "I know there's a ticket in, but."

The official path did not replace the informal one. It joined it.

Two loads. One person. No new hours.

That is the double bill: the organization charged the same person twice for the same clarity, once through the documented path and once through the path the documentation was supposed to retire. Every status review shows the path holding, because every status review can only see the documented copy. The second load runs off the books, which is exactly where it ran before, except now it runs on top of an SLA.

The organization bought a diagram and sent the invoice to a person.

The escalation path is only the instrument this version of the pattern happened to use. The same accounting runs on ownership matrices, RACI charts, intake processes, data contracts, on-call rotations: every artifact an organization ships in the name of clarity. Clarity is a purchase. Someone always pays for it, and the diagram never says who. That question is the spine of this series.

I have made the request too. As a leader, I asked for a formalization: a clear path, a documented owner, the same reasonable sentences. I believed in it. I still believe in the underlying instinct, because building better processes and clearer standards is most of what I think leadership in an operating function is for. I have never wanted a better box. I have wanted processes that need one less often.

What I did not price was where the path would land. The formal route I asked for did not move the work somewhere new. It routed the work into my own organization: the escalations arrived with official standing, the response expectations arrived with them, and my team absorbed both inside the same headcount and the same budget we had the week before the diagram existed. No individual was put in a box by my request. The whole organization I led became the box.

I had asked for clarity and become the payer again, from the other chair this time. The first bill found me as the person whose quiet catching got formalized. The second found the people I was responsible for, on a request I signed.

The cost surfaced the way this cost usually does: in burnout, and eventually in a departure. I will not draw a straight line from my request to that outcome, because organizations are not that legible, and this piece does not get to pretend otherwise. What I can say is that the load was real, the resourcing never arrived, and the people carrying it were mine.

The request had been mine. That is the part I sit with.

There is an honest objection here, and it deserves a straight answer. Should the path have stayed informal? No. Undocumented dependency is worse: it concentrates risk in whoever happens to be catching things, and it walks out the door with them. Formalization is the right instinct. The failure is pricing it at zero.

"We need more visibility" is not a complete decision. Neither is "we need a clear owner." They are the first half of a sentence that most requests never finish.

The complete sentence names four things: what we are formalizing, who will carry it, what resourcing arrives with it, and what gets retired to make room for it. If the request cannot finish that sentence, it is not a decision yet. It is a wish with a diagram attached, and the difference will be paid by whoever's name lands in the box.

And the complete sentence is still only the floor. The box exists to absorb what the process cannot yet handle: every escalation through it is an exception the system produced somewhere upstream. The formalization worth signing pairs the name with the work that shrinks what the name has to catch. Fund the box, then fund the reason the box is loud. A box that never gets quieter is a process failure with a name on it.

It is the standard I hold my own requests to. Before I ask for a path, an owner, or a matrix, I finish the sentence, and if I cannot fund the second half, I do not ship the first half.

There is a simple test for whether an organization is running double bills, and it fits in one question: when the path was formalized, what changed for the name in the box besides the routing? Headcount, budget, authority, retired work: any of those, and the organization paid for its clarity. None of them, and a person did.

This week, pull up the newest escalation path, ownership matrix, or RACI your organization shipped, find the name that carries the top tier, and ask what arrived with the name besides the routing. Then find one that shipped six months ago and ask whether its box is quieter than the day it went live. The first answer tells you who paid for the clarity. The second tells you whether anyone ever stopped paying.