TrenchOps 🐎 
You Bought a Racehorse and Rented a Treadmill
The strangest math in enterprise hiring: paying sports-car money for output you then throttle by hand
A while back I sat in a coffee shop with someone from a very large, very admired technology company. Nine-figure revenue per quarter, the kind of place that puts "we hire only the top 1%" in its recruiting deck without irony.
He told me his last quarter honestly. Two weeks of real engineering. Ten weeks of alignment.
His compensation, fully loaded, was roughly the price of a mid-range sports car per year. So the company paid sports-car money and received, in terms of the thing they actually hired him for, a used scooter. Not because he was lazy. Because 80% of his calendar was owned by people whose job was to make sure nobody did anything surprising.
I hear a version of this story from nearly everyone I talk to who works inside the big names. It is consistent enough that it stopped being anecdote and started being physics.
The idiot index of a knowledge worker
There is a useful little instrument from manufacturing: take the cost of a finished part and divide it by the cost of its raw materials. A machined bracket that costs 200 euros but contains 8 euros of aluminum tells you something. Not that aluminum is expensive. That your process is stupid.
Apply that to a senior engineer.
Raw input: one very expensive brain, capable of shipping things that make money.
Finished output: three slide decks, one Jira epic groomed into a fine powder, and a fix that shipped six weeks after it was written because it needed sign-off from a governance board that meets fortnightly.
The ratio is grotesque. And like the bracket, it does not indict the aluminum. Nobody in these companies has a talent problem. They have a process problem wearing a talent problem's clothes, because "we need to hire better people" is a budget request and "our approval chain destroys value" is a resignation letter.
Why the screws tighten exactly when they shouldn't
Here is the part that genuinely puzzled me for years.
Every time the horizon darkens - a bad quarter, a funding chill, "macroeconomic outlooks"- leadership reaches for control. Hiring freeze, travel freeze, headcount review, mandatory return to office, a new weekly reporting cadence, a "focus" initiative that adds three dashboards. They reduce the heat to save fuel. But the fuel bill is identical, because the salaries are already committed. All they cut was output.
You are still burning the same wood. You just closed the flue.
Why does an intelligent executive do this? Because control is legible and output is not. A vice president can walk into a board meeting and prove, with artifacts, that governance was increased. Nobody can prove what the unshipped feature would have earned. Downside risk of tightening: invisible and deferred. Downside risk of trusting an engineer: has your name on it if it goes wrong.
That is not stupidity. That is an incentive working perfectly. Show me the incentive and I will show you the org chart.
Then there is the second mechanism, and it is the more brutal one. Jerry Pournelle observed that any bureaucracy eventually splits into people who serve its mission and people who serve the bureaucracy itself - and the second group reliably ends up in charge of promotions, because they are the ones present at the meetings where promotions are decided. Crisis is their harvest season. Crisis is when "we need more oversight" sounds like wisdom instead of empire-building.
The power horses 🐎 are elsewhere. Debugging. Missing the meeting where their autonomy got reallocated.
The commodification trick
Watch the language shift over a talent's first two years.
Year one, in the offer stage: "We want someone who can own this space end to end. You'll have real influence."
Year two, in the performance review: "We need to make sure your work is repeatable and not dependent on individuals."
Both sentences are honest. They come from different parts of the organism. Recruiting is optimizing for acquisition. Operations is optimizing for interchangeability, because interchangeability is how you survive attrition, audits and org charts. The company genuinely wants exceptional people and genuinely wants nobody to be exceptional. It buys a racehorse and then, quite rationally, installs guardrails so that any horse could run the same lap.
The tragedy is that the guardrails work. Output does become uniform. It converges downward, to the level of the least capable person the process was designed to survive.
And then a small company opens down the road, hires four of these people, gives them access and a budget and nobody to ask, ships in eight weeks what the giant scheduled for three quarters - and the cycle begins again. That small company will be a giant in eleven years and will install its own governance board. This is not cynicism. It is entropy with a payroll.
For leadership: how to stop paying for horsepower you then bleed off
👉 Measure the ratio, not the headcount. For one senior person, one quarter: hours spent producing the thing customers pay for, versus hours spent producing evidence that work happened. If the second number is bigger, you do not have a productivity problem, you have an overhead problem, and hiring more people will scale it.
👉 Improve by removal first. Before adding a process, kill one. Every handoff, approval and status sync leaks energy that never reaches the customer. Most transformation programs are additive, which is why they cost so much and change so little. But do check why the fence exists before you tear it down - some approval gates are load-bearing and were paid for in blood, usually a regulatory fine.
👉 Give access, not encouragement. Autonomy is not a value on a wall poster, it is a permission set. Production access, a budget threshold they can spend without asking, the right to say no to a meeting. If your top performer needs three signatures to buy a 200 euro tool, they are not autonomous, they are on parole.
👉 Tighten differently in a crisis. Cut theater, not throughput. Kill the reporting layer before the tooling budget. If your instinct in a downturn is to increase oversight of the people who make the product, invert it: ask how you would guarantee terrible output on purpose, and then count how many of those items you just approved.
👉 Protect asymmetric people from uniform processes. One person delivering four times the median is not a staffing anomaly to be normalized. It is your margin. Design a lane for them or watch a competitor design one.
For the talent: how to tell whether you are already in the wheel
Four signals, in order of how late they arrive.
👉 Your calendar. If more than half of your week is other people's agendas and you cannot name what shipped because of you last month, you are being consumed rather than employed.
👉 Your escalation path. Ask yourself how long it takes you to get a decision. In healthy places, hours. In the wheel, "let me take that to the working group."
👉 Your last honest technical argument. In a functioning organization, you lose some of them on the merits. In a converged one, you lose all of them on hierarchy, and you have quietly stopped starting them. That silence is the real symptom, and it precedes burnout by about six months.
👉 Your market temperature. Not "could I get a job" - could you get this job again today, at this salary, with what you have actually built in the last eighteen months? If your recent portfolio is coordination rather than creation, your value is decaying while your title improves. That is the most expensive trade in tech and almost nobody notices it happening.
What to do about it, in ascending order of courage: reclaim one day a week and defend it like a border. Reframe your autonomy ask in the language of risk reduction, because most executives move on framing rather than logic - "this removes a bottleneck on me" travels much further than "I want to be trusted." Find the overlooked, unglamorous domain nobody is bidding for, where competence is scarce and permission is cheap. And if none of that moves - leave before the cynicism sets in, because cynicism is the one injury that follows you to the next employer.
One caveat, because I am not selling romance: some structure is not oppression. Guardrails exist because unconstrained brilliance also produced the undocumented system nobody can maintain and the vendor contract legal is still unwinding. The goal is not zero process. The goal is that the amount of process is proportional to the actual risk, not to somebody's discomfort with not knowing what you are doing right now.
The best talent is not a resource you acquire. It is a reaction you either catalyze or quench - and quenching costs exactly the same per year.
👇 What is your current ratio - real output hours versus evidence-production hours? Guess honestly, then check your calendar.
This article is also available in German.
0 comment(s)
No comments yet. Be the first to comment.
Leave a comment