I just hit the corner of a solid oak filing cabinet-the kind of furniture that exists solely to store paper that no one will ever read again-and the pain is a sharp 4 out of 10 that keeps me grounded in a reality I’d rather ignore. I am currently staring at a screen that tells me my expense report for a 24-dollar client lunch was rejected. The reason? I used the wrong internal project code. Not because the code doesn’t exist, but because the code I was given by my manager was for the ‘Alpha’ phase, and apparently, we transitioned to the ‘Beta-14’ phase last Tuesday at 4:04 PM. To get the new code, I have to submit a ticket to a department that doesn’t accept tickets on Fridays.
We live in an era where we have optimized every possible micro-second of our digital lives, yet the actual work remains buried under a landslide of performative hurdles. We use high-speed fiber optics to send 14 emails back and forth about whether a 54-dollar software subscription is ‘strictly necessary’ for a designer whose hourly rate is 144 dollars. The math doesn’t just fail to add up; it actively insults the intelligence of everyone involved. My toe pulses again. It’s a physical manifestation of the institutional friction I deal with every day.
The Unfiltered Law of Physics
Ian R.-M. knows a thing or two about friction, though he calls it resistance. He’s a neon sign technician I met 4 years ago when I was trying to fix a vintage ‘Open’ sign for my uncle’s shop. Ian spends his days bending glass tubes over ribbons of fire, filling them with noble gases, and wiring up transformers that could easily stop a human heart if handled with the wrong kind of casualness. He told me once that neon is the most honest medium in the world. If you have a leak, the gas escapes and the light dies. If your vacuum isn’t perfect, the color is muddy. If your electrodes are dirty, the tube flickers and fails. There is no ‘approval process’ for physics. You either do the work correctly, or the sign stays dark.
In our corporate landscapes, we have managed to decouple the light from the work. We have created systems where the sign stays dark, but we still spend 44 hours a week arguing about the shade of blue we’re not currently producing.
This isn’t just an accident of growth or a side effect of scaling a business. It is a deliberate, albeit often unconscious, strategy. We create and enforce these arcane rules not for efficiency, not for safety, and certainly not for profit. We create them to consolidate power.
The Validation Cost: Gatekeeping vs. Output
When you are the person who holds the ‘code’ or the person who must sign off on the 24th step of a 54-step process, you feel important. You are a gatekeeper. Your existence is validated by the fact that someone else cannot move forward without your nod. This is ‘process-as-an-excuse.’ It’s the ultimate shield against the terrifying possibility that our roles might actually be redundant if the work were allowed to flow naturally. We optimize the tracking of the work, the reporting of the work, and the meta-analysis of the work, but the work itself? That’s just the thing that gets in the way of a good meeting.
I think about the physical cost of this. Every time I have to navigate a 14-page PDF to explain why I bought a specific cable, a little piece of my creative drive withers. It’s a form of learned helplessness. You start to ask yourself why you should bother innovating or moving quickly when the system is designed to trip you at every turn. You stop looking for the most elegant solution and start looking for the path of least resistance-which, ironically, usually involves doing as little as possible so you don’t trigger a new round of approvals.
When you see something that actually works-something built by Lando-you realize that friction isn’t a law of nature; it’s a choice we make every morning when we log in. There is a specific kind of beauty in a process that disappears. It’s like Ian’s neon signs. When they are done right, you don’t see the wires, you don’t see the transformers, and you certainly don’t see the 14 hours he spent sweating over a torch. You just see the glow. You see the intention. You see the result.
We Prioritize Safety of the System Over Success of the Mission
If the project fails but you filled out all 24 forms correctly, you are safe. If the project succeeds but you bypassed the official procurement channel to buy a 4-dollar part that saved the deadline, you are a liability.
Ian R.-M. once showed me a transformer that had shorted out because a spider had crawled into the housing. That one tiny, 8-legged interruption was enough to kill the whole display. Our offices are full of these spiders. They aren’t insects; they are tiny, insignificant rules that have spun webs across our workflows. We’ve become so used to the webs that we’ve started calling them ‘infrastructure.’ We hire ‘Web Removal Specialists’ who just end up spinning more silk to justify their 144,000-dollar salaries.
The Man Who Declines $24
I’m looking at the email from the Accounting department again. It was sent by someone named Marcus. I’ve never met Marcus. I don’t know what Marcus does other than reject expense reports. I wonder if Marcus feels a sense of accomplishment when he clicks ‘Decline.’ Does he feel like he’s protecting the company from my 24-dollar extravagance? Or is he just as trapped in the web as I am, following a script written by someone who left the company 14 years ago?
There’s a specific kind of madness in the way we use technology. We have tools that could automate 94% of these administrative tasks, but we don’t use them for that. Instead, we use them to create more tasks. We use AI to generate reports that no one reads, so that we can use other AI to summarize those reports into bullet points that we then discuss in a 44-minute Zoom call. It’s a closed loop of productivity-themed entertainment.
The Loop of Adaptation
Visualizing the automated, self-justifying cycle.
My toe is finally starting to stop throbbing, or maybe I’m just getting used to the pain. That’s the real danger, isn’t it? Adaptation. We adapt to the friction. We learn how to navigate the 24-step approval process so efficiently that we forget the process shouldn’t exist in the first place. We become experts in the bureaucracy instead of experts in our craft. Ian R.-M. wouldn’t last a week in this environment. He’d probably try to wire the filing cabinet to a 14,004-volt transformer just to see if it would light up.
[The light of the work is buried under the heat of the process.]
I remember a project I worked on about 4 years ago. We had a team of 4 people, and we were building something new. We didn’t have a project manager. We didn’t have a ‘governance framework.’ We just had a goal and a deadline. We communicated in real-time, we made decisions in 4 seconds, and we shipped the product in 44 days. It was the most exhausted I’ve ever been, and the most alive. There was no friction because there was no room for it. We were moving too fast for the spiders to spin their webs.
Growth vs. Optimization: The Cost of Scaling
Time to Ship Product
†
VS
Time for Code Approval
Now, that same company has grown. They have 424 employees and a dedicated ‘Process Optimization Team.’ It now takes 4 months to get a single line of code approved for production. They have optimized the life out of the work. They are profitable, sure, but the neon is muddy. The glow is gone.
We need to stop pretending that more oversight equals better results. It usually just equals more observers. If you trust someone enough to hire them, you should trust them enough to spend 54 dollars without a 4-person committee. If you don’t trust them, why are they there? The friction isn’t a safety net; it’s a shroud. It hides incompetence and stifles brilliance in equal measure.
Clearing the Deck for the Real Work
I’m going to resubmit this expense report. I’m going to find the Beta-14 code, even if it takes me another 24 minutes of digging through archived threads. But I’m not doing it because I believe in the system. I’m doing it because I need to clear the deck so I can actually do the thing I was hired to do. I’m going to finish my work, and then I’m going to go see Ian. I want to stand in his workshop, surrounded by the hum of high voltage and the smell of ozone, and look at something that is either on or off. No approvals. No project codes. Just light.
ON / OFF
The Highest Form of Efficiency
Conclusion: Trust the Craft
The ultimate goal is not process adherence, but mission success, illuminated by clear, direct action.