Framework
The Hidden Subsidy You're Providing Your Employer
Your competence is the load-bearing wall holding up a broken structure. The organization has no idea it is standing on you.
The Hidden Subsidy You're Providing Your Employer
I was lying on the floor of my home office, half-listening to a video call where six people watched someone type into an Excel spreadsheet. We were co-creating a governance document. It would take three more meetings to finish.
Later that night, I took the half-built file and finished it in forty minutes. Better structure. Cleaner logic. Ten times the quality in a fraction of the time.
I felt the familiar surge. So I kept going. Another document. Another framework. Another piece of infrastructure the organization needed but could not seem to produce on its own.
It was 11 PM before I stopped. And somewhere in that quiet, a question surfaced I had been avoiding for months: Who actually benefits from my ability to produce at this volume?
The answer was uncomfortable.
I had discovered leverage and immediately poured it back into the organization. Not strategically. Not with boundaries. Automatically. Because producing felt good. Because I could. Because high performers are trained to interpret capability as obligation.
This is the hidden subsidy. It is not in your job description. It is not compensated. It is not acknowledged. It is the gap between what the role formally requires and what you actually provide — absorbed silently, expected quietly, invisible until you stop.
The construction industry has a term for this in project accounting: unrecovered overhead. Work that gets done but never gets charged. It shows up as profit on someone else's ledger while draining your own.
With knowledge work, the unrecovered overhead is not just time. It is capability. The institutional knowledge you carry. The relationships you maintain. The dysfunction you quietly route around so that things keep working.
And here is what makes it insidious: the better you are, the more you subsidize. Your competence becomes the load-bearing wall that keeps a broken structure standing.
I started paying attention to where I was absorbing dysfunction without being asked.
Coordination that had no owner? I stepped in. Decisions that leadership would not make? I made them anyway. Gaps between what was formally someone's job and what actually needed to happen? I filled them. Automatically. Without negotiation. Without even naming what I was doing.
When you are good at your job and care about outcomes, this absorption feels like leadership. It feels like being a team player. It feels like what makes you valuable.
But there is a game theory principle that reframes it: a threat is credible only when it is costly to carry out — but costlier not to. The flip side is also true. A subsidy is invisible until it is withdrawn. And if you have been providing one for years, the organization has built its assumptions around its perpetual availability.
You have not been leading. You have been load-bearing. And the structure has no idea it is standing on you.
Strategic withdrawal is not disengagement. It is not quiet quitting. It is not burnout management dressed up in professional language.
It is the deliberate, disciplined removal of contributions that were never formally yours to give.
Sloppy withdrawal looks like checking out — missed deadlines, dropped balls, visible decline. It damages your reputation and gives others a story about your commitment.
Precise withdrawal looks like clarity. You deliver fully within your defined scope. You stop delivering outside of it. When gaps emerge, you ask one question: Who owns this decision and budget?
Then you stop talking.
You are not refusing to help. You are declining to provide free coordination that masks structural dysfunction. You are allowing small failures to surface at low cost but high visibility — not engineering them, just not preventing them.
When someone says you usually handle this, the response is simple: I have in the past, but that is not a sustainable model.
No elaboration. No justification. No apology.
What happens next is revealing.
Either the organization names the gap and assigns ownership — which means the dysfunction was real and is now being addressed — or it does not, which tells you something equally valuable about what was never going to change.
Both outcomes are useful. One creates space for your role to be properly defined. The other clarifies that you were subsidizing a system that had no intention of reciprocating.
The goal is not to punish or prove a point. It is to stop being the invisible infrastructure that allows misalignment to persist.