It Was Never a Decision. It Was Someone Else's Budget.

In June of last year, Woody, who oversees support at the company I work for, sent me a Slack message. The technical program manager we had just hired, the person sitting at the line between support, engineering, and sales, was gone. Two months in the seat, and he had resigned. It landed as a surprise. What I remember clearly is not his exact words. It is what came with them: every piece of large-customer onboarding, and the project management for every change those customers needed after, was coming back to me.

I went to reopen the req and found out the freeze had already happened, days before he left. Not a response to his departure. A blanket freeze on backfills, company-wide, requiring approval from the highest level, with no realistic path to that approval. The role was not going to sit open for a while and then quietly get filled again. It was dead before anyone in the building knew it would need to be.

Fourteen months later, I am still in it. I have always sat in the room for enterprise onboarding, the security reviews on our largest accounts, because that is where a CTO's judgment actually belongs. What I did not expect was ending up in deals under a hundred thousand dollars, several a week, month after month, because nobody else owns that layer anymore. Some of the work lands on me. Some of it is scattered across two or three other people who never agreed to carry it either. What is frustrating is not the hours. It is watching our headcount stay frozen while the business grows at double digits, and knowing the freeze was never actually a decision about whether we needed the role at all.

The convenient explanation is that a hiring freeze is just fiscal discipline: careful, temporary, the kind of caution a well-run company exercises when the ground feels uncertain, and the headcount returns once the numbers do. Every technical leader who has watched a freeze quietly eat a role they actually needed has told themselves some version of that story, because the alternative is harder to sit with: admitting the freeze was never a judgment about your team in the first place.

That is not what happened here, and the difference is the whole argument. A freeze approved at the highest level is not a verdict on my team. It is a verdict on whether some other group's numbers held up that quarter, applied uniformly, with no one in the room who understood what a boundary-spanning role like this one was actually doing. Nobody weighed the trade-off. Nobody decided the seat at the line between support, engineering, and sales was not worth the cost. A budget problem somewhere else in the company made that call by proxy, and my team absorbed the consequence as though we had agreed to it.

This is what I call Coordination Debt: the accumulated cost of removing coordination capacity without redesigning where it goes. It compounds invisibly, because the work does not disappear when the role does. It migrates to whoever is standing closest, with no title, no budget line, and no mandate to carry it. Fourteen months of onboarding calls two levels below where my time should sit, at up to ten hours a week, appear on no dashboard anywhere. The company believes it saved a salary. What it actually did was move that cost onto more expensive time, spent at a worse return, and split it thin enough across enough people that no one is positioned to add up the total. The leaders who eventually get a role like this restored do not do it by waiting more patiently for the budget to loosen. They start treating the absorbed cost as a number somebody upstream has never seen.

You cannot unfreeze a req by naming what it costs. What you can do is stop letting that cost stay invisible. Every hour spent two levels below your actual seat is a real number, and pricing it, then putting it in front of whoever owns the freeze, is a different move than absorbing it quietly and hoping the budget comes back on its own. The freeze was never your decision to make. Whether the cost stays silent still is.

Name the last role your organization let go unfilled "for now." Add up how many hours a week someone is spending on that work who never agreed to carry it. Then ask the harder question: does anyone above you actually know that number, or have you been the only one keeping it?

The Edge Case walks through how to map a tension like this as a Structural Bearing precisely enough to act on, what load each side is actually carrying and the structural constraint holding a freeze like this one in place, before it costs you another year: http://TheEdgeCaseBook.com