The left sneaker is still on the floor, upside down, covering the remains of a spider that decided my mid-afternoon coffee was a personal invitation. I didn’t think about it. I didn’t consult a manual. I didn’t check if the shoe was the ‘standard issue’ spider-removal tool according to some IT checklist. I just moved. The impact was immediate, messy, and 100% effective. It’s funny, in a bleak sort of way, how we handle immediate physical threats with an instinctive, singular action, yet we handle the ‘risk’ of a $15 software subscription with a 15-step approval process that costs the company $525 in lost productivity.

Consider the designer. Let’s call her Sarah. Sarah needs a specific font-management tool to finish a project that is already 5 days behind. It costs $15 a month. In a sane world, she’d swipe a card and get back to work. In our world-the world of ‘optimized efficiency’-Sarah opens a ticketing system. This system was designed after one guy in the 1995 era accidentally downloaded a virus, so now every software request must be vetted. Sarah’s request goes to her manager. Then to the department head. Then to Procurement. Then to IT Security. Each of these 5 people has a 45-minute window to look at tickets once a week. 25 days later, Sarah receives an automated email: ‘Denied. Non-standard software. Please use the pre-approved internal font library from 2005.’

We have built cathedrals of process to prevent the ghost of a single mistake. We optimize for the ‘how’ until we completely lose sight of the ‘why.’ When we talk about efficiency, we usually mean control. We want to ensure that nothing goes wrong, forgetting that the most efficient way to ensure nothing goes wrong is to ensure that nothing happens at all. A rock is perfectly efficient at not failing; it’s also perfectly efficient at doing absolutely nothing.

The Certainty of Speed vs. The Comfort of Control

I spend most of my nights as a livestream moderator. My name is Leo E.S., and my job is to keep a chat of 555 people from devolving into a digital version of Lord of the Flies. If I had to follow a 15-step process every time someone typed a slur or started spamming crypto links, the stream would be dead in 15 minutes. In the live environment, you have to trust the moderator’s intuition. You have to allow for the possibility of a mistake in exchange for the certainty of speed. But corporations aren’t live streams. They are slow-motion oil tankers that think they can avoid icebergs by requiring 5 signatures before the captain is allowed to turn the wheel.

The 25-Day Approval Journey

This bureaucratic impulse usually starts with good intentions. A problem occurs-a $575 overage on a cloud bill or a leaked document-and instead of addressing the individual who made the mistake, the organization creates a ‘Process.’ The process is a net designed to catch that specific fish, but the holes are so small that the entire ocean gets stuck in it. We optimize the steps of the process to be as ‘efficient’ as possible-tracking metrics, setting SLAs, creating dashboards-but we never ask if the process itself should exist. We become very good at doing things that shouldn’t be done at all.

Optimizing Human Decision-Making Out of the Loop

I once saw a team spend 75 hours of collective meeting time trying to figure out why their project was 15 weeks behind. The irony was so thick you could have sliced it with a sneaker. They had a process for tracking time, a process for reporting delays, and a process for ‘risk mitigation,’ but the risk they were mitigating was ‘human decision-making.’ They had successfully optimized the humans out of the loop, leaving only a series of check-boxes that no one really understood.

Friction vs. Delay Cost

We often mistake friction for safety. We think that if it’s hard to do something, we are being careful. But friction doesn’t prevent bad decisions; it only delays them. If a decision is bad, making it go through 5 layers of management doesn’t make it good; it just makes it an expensive bad decision. By the time Sarah’s font request was denied, the project was already a disaster. The delay cost more than the font, the virus, and the IT security guy’s salary combined. We focus on the $15 because it’s a line item we can see. We ignore the $525 in wasted time because it’s invisible.

Focusing on Effortlessness

What we really need is a return to the ‘Single Point of Action.’ This is where tools that prioritize outcomes over hurdles become essential. If you want to see how a system can actually facilitate results rather than just managing permissions, looking at something like LMK.today provides a glimpse into a philosophy of effortlessness. It’s the difference between a tool that helps you do the work and a tool that forces you to prove you are allowed to do the work.

I admit, I’ve been part of the problem. As a moderator, I once tried to implement a ‘Three Strike Rule’ for chat members that was so complex I needed a spreadsheet to track it. I thought I was being ‘fair’ and ‘efficient.’ In reality, I was spending 45% of my time looking at the spreadsheet instead of watching the chat. I was missing the actual fire because I was too busy recording the temperature of the smoke. I eventually scrapped it and went back to my gut. People want to be led by humans, not by algorithms disguised as policy.

The Cost of Speed

If we want to be effective, we have to embrace the mess. We have to accept that a designer might occasionally buy a font that doesn’t get used, or that a moderator might accidentally ban someone who was just being sarcastic. These are the costs of doing business at speed. The alternative is a perfectly safe, perfectly efficient graveyard of ideas. We have to stop treating every employee like a potential liability and start treating them like the experts we hired them to be.

The Choice: Process vs. People

I’m looking at the sneaker again. I’ll have to clean the floor now, which is another task, another ‘process.’ But the spider is gone. The threat is neutralized. I didn’t need a committee to tell me that a spider near my coffee was a bad thing. I didn’t need to fill out a ‘Pest Control Requisition Form.’ I just acted. Imagine a company where Sarah could just act. Imagine the amount of work she could get done in those 25 days she spent waiting for a ‘No.’

Optimizing for the Finish Line

We have to stop building 15-step fences and start building 5-lane highways. We need to optimize for the finish line, not for the pit stops. Efficiency is a metric for machines; effectiveness is a metric for people. And last time I checked, we are still a species that uses sneakers to solve problems, even if we’ve forgotten how to do it without a 45-page manual. I’m going to go get a paper towel now. No approval required.