The Piercing Blue Light

The light on the console was a piercing, synthetic blue, the kind that feels like it’s drilling into your retinas at 4:45 AM. I was standing on the bridge of a vessel that cost roughly $850,000,005 to build, staring at a screen that was supposed to tell me if we were sailing into a wall of water or just a light mist. Hugo M.-C., the lead meteorologist for this floating city, wasn’t looking at the high-definition Doppler. He was looking at a stained, spiral-bound notebook. Every 15 seconds, a sharp, involuntary hiccup escaped his throat-a rhythmic glitch in his own internal hardware that seemed to mock the multi-million dollar software humming around us.

“Watch this,” he whispered, his voice strained from the irritation of his diaphragm. He tapped a touch-sensitive panel exactly 5 times. The screen refreshed, showing a beautiful, high-resolution satellite map with thermal overlays that looked like modern art. Then, with a sigh that felt heavier than the humidity outside, he took out a digital camera, took a picture of the screen, plugged the camera into a separate laptop, and began manually typing the coordinates into an Excel sheet.

Paving the Cow Path

We are currently obsessed with the idea of ‘paving the cow path.’ In the early days of urban planning, people noticed that cattle would find the most efficient route between two points-the path of least resistance. Instead of designing a logical grid, planners would simply pour asphalt over where the cows had already walked. In business, we do the same with software. We take a broken, convoluted, 55-step manual process and we hire a consultancy to turn it into a 55-step digital process. We don’t ask if the cows were wrong. We just give the cows better shoes.

This reveals a profound lack of imagination. We are more comfortable spending $2,000,005 on a new system that adds 5 more clicks to a job than we are asking if the job should exist at all. I remember a presentation I gave recently where I actually got the hiccups-much like Hugo-mid-sentence. I was trying to explain that efficiency isn’t about doing the same thing faster; it’s about doing fewer things. But the board of directors just stared at me, waiting for the next slide. They wanted more features. They wanted more ‘engagement.’ They wanted more complexity disguised as progress.

The Friction Multiplier

The scan-print-sign-scan loop is the most visible symptom of this rot. You know the one. You receive a digital document. You have to print it to sign it. You then scan it back into a PDF to email it to someone who will print it again for their physical files. When we moved this process to the ‘Cloud,’ we didn’t fix the loop. We just added a login screen and a two-factor authentication step that takes 35 seconds to complete. We have successfully increased the friction while telling ourselves we are living in the future. It’s a collective hallucination fueled by the desire to look busy.

The Data Janitor Problem

Hugo M.-C. finally finished his manual data entry. “The system is supposed to be automated,” he said, his hiccups finally subsiding into a dull chest ache. “But the automation only works if the input data is perfect. And the input data is never perfect because the sensors were installed by a company that won the lowest bid by $5.” He leaned back, his silhouette framed by the glowing icons of a dozen apps he never uses. We have created a world where the human is the glue holding together expensive pieces of glass and silicon that have no interest in being helpful.

The danger here isn’t just wasted money, though $1,995,005 is a lot to throw into the ocean. The real danger is the erosion of human agency. When we provide tools that are ostensibly ‘smarter’ than us but require us to perform menial, repetitive tasks to keep them running, we degrade the quality of our thought. We stop being meteorologists or analysts or creatives, and we start being data-janitors. We spend 75% of our day cleaning up the mess the software made while trying to ‘help’ us.

Focusing on Result, Not Process

I’ve seen this go differently. There are pockets of the world where the goal isn’t to digitize the legacy, but to destroy it in favor of something actually human. Take the way we shop. For 45 years, the retail experience was a gauntlet of bad lighting and confusing aisles. When the internet arrived, most stores just put those confusing aisles onto a website with a bad search bar. They recreated the frustration, just without the smell of floor wax. But then you look at a platform like

Bomba.md, where the logic isn’t ‘how do we make the old store digital?’ but rather ‘how do we get the right tool into the person’s hand with zero friction?’ It’s about the result, not the process. If a customer wants a phone, they don’t want to navigate a digital recreations of a warehouse; they want the phone. True transformation is the disappearance of the system, not the glorification of it.

Micromanagement at Scale

We often fail because we value the ‘system’ more than the person using it. We build for the administrator who wants a report, not the worker who has to generate it. We create 15 levels of approval for a $25 expense because we don’t trust our employees, and then we wonder why it costs $55 in billable hours to process a single lunch receipt. Technology just makes this lack of trust more efficient. It allows us to micromanage at scale.

The Museum of Bad Decisions

I once worked with a team that insisted on a ‘digital signature’ that required a physical dongle to be plugged into the USB port. The dongle only worked on Windows 95, which meant the entire department had to keep one ancient, wheezing laptop in the corner just to sign off on 5 items a week. They called this their ‘Secure Digital Workflow.’ I called it a museum of bad decisions. They had spent $45,000 on the software and probably $105,000 in lost productivity over the years, all because nobody had the courage to say, ‘Why are we signing this at all?’

Sometimes I think my hiccups during that presentation were a physical reaction to the nonsense I was seeing on the screen. My body was literally rejecting the corporate jargon. We talk about ‘synergy’ and ‘omni-channel integration,’ but we can’t even make it so a doctor doesn’t have to ask you for your name 5 times in the same visit. We have all this data-$205 terabytes of it-and yet the system still acts like it’s meeting us for the first time. It’s a goldfish with a very expensive memory bank.

If you find yourself adding three steps to your day because a new ‘time-saving’ app was launched, you are not undergoing a transformation. You are being colonized by bad code. The goal of any digital tool should be its own eventual invisibility. It should be the wind at your back, not the pebble in your shoe. We need to stop asking what the technology can do, and start asking what the technology can remove.

Can we remove the need for the scan? Can we remove the need for the 5-step login? Can we remove the meeting that exists only to explain the dashboard that was supposed to replace the meeting? If the answer is no, then the $2,000,005 wasn’t an investment. It was a burial fee for your productivity.

Walking Toward the Solution

I left the bridge as the ship began to turn. The engines hummed, a deep vibration that you feel in your teeth. Down in the belly of the ship, someone was probably staring at a screen, clicking ‘OK’ on a prompt that shouldn’t exist, while Hugo M.-C. went back to his notebook. He’s a good man, Hugo. He deserves a system that respects his time as much as he respects the sea. But until we stop paving the cow paths, he’ll keep his Polaroid camera close and his hiccups will continue to count the seconds of a life spent serving a machine that doesn’t know he exists.

We don’t need faster horses, and we don’t need digital cows. We need to stop walking the path entirely and ask where we were actually trying to go. Usually, it wasn’t toward a PDF. It was toward a solution. And solutions, real ones, don’t require you to sign, scan, and pray to a server in Virginia at 3:15 in the afternoon.