Maria C.M. adjusted her safety goggles, the 107-degree heat of the Nevada testing bay shimmering off the mangled hood of a 2017 test mule. She didn’t look at the wreckage; she looked at the heavy-duty tablet in her hand, her thumb hovering with a kind of weary desperation over a greyed-out button. The crash had been a success. The sensors had captured 47 gigabytes of high-velocity data. The cables had held. The dummy’s neck had snapped at exactly the right millisecond. But now, in the aftermath, the $7,777,747 enterprise resource planning platform Maria was forced to use was refusing to acknowledge that the car existed. To log a single impact report, she had to navigate through 17 distinct screens, most of which were designed by people who had never smelled burnt rubber or seen a windshield shatter into 7,000 pieces of safety glass.

I watched her sigh, a sound that carried more weight than the hydraulic press used to crush the chassis. She looked at me, her eyes reflecting the fluorescent lights of the hangar, and pulled a folded piece of paper from her pocket. It was a printed spreadsheet, hand-inked with 37 rows of manual entries. This was her ‘workaround.’ It was the secret engine that actually kept the safety tests running while the official software sat in a pristine, unusable state on the company’s servers. It’s a scene I’ve seen in 87 different industries, from healthcare to high-speed rail. We buy the dream of efficiency and we receive a digital cage.

The Politics of Bloat

Why does it take 17 clicks to do what used to take 2? The answer is never technical; it’s always political. When a company spends $777,000 on a new suite of tools, they aren’t just buying code. They are buying the appearance of control. They are buying a process that they can show to the board to prove they are ‘digitally transformed.’ But transformation is a painful, messy, human process. It’s not something you can install via a .msi file. The software is designed to enforce a rigid, idealized workflow. It assumes that every car crash happens in a vacuum, that every sensor works perfectly, and that every engineer has 47 minutes of spare time to fill out ‘Mandatory Field B-7.’

Ingenuity Born from Frustration

Maria showed me the back-end of her spreadsheet. It was a masterpiece of human ingenuity born from frustration. It used 7 nested macros to bypass the need for the central server’s approval. She could input a crash result in 7 seconds. The official software required her to select the vehicle type, the test date, the weather conditions (which were already in the system), the tire pressure, the name of the lead technician (her own name, which the system should have known), and finally, a 47-character description of the impact. If she missed a single character, the system cleared the entire form. This isn’t productivity. This is organizational vanity. It is the act of valuing the data’s structure more than the data’s truth.

The Hostile Interface

We see this everywhere. We see it in hospitals where doctors spend 47% of their time clicking boxes instead of looking at patients. We see it in schools where teachers manage 27 different apps to track 7 metrics of student ‘engagement’ while the students themselves are checked out. We are building a world of friction. I think about my accidental ‘like’ again. The interface of social media is designed to make that mistake easy. It’s designed for engagement, not for human dignity. Similarly, enterprise software is designed for the buyer-the CIO who loves the 7-year roadmap-not the user who needs to get home by 5:37 PM to see their kids.

There is a deep, quiet movement happening beneath the surface of these bloated systems. People are migrating to simpler spaces, finding solace in places like 꽁머니 where the noise is dialed down and the utility is dialed up, far from the 17-step authentication rituals of the corporate abyss. It’s a search for the ‘2-click‘ reality. Maria’s spreadsheet is her version of this. It’s a protest in the form of a .xlsx file. She knows that if she uses the official system, the work will die.

The Map vs. The Territory

I once tried to explain this to a Product Manager at a tech conference. He was wearing a shirt that cost $137 and talking about ‘frictionless synergy.’ I told him about Maria. I told him about the 17 clicks. He looked at me with a blank expression and said, ‘But the dashboard looks amazing, right?’ He wasn’t lying. The dashboard was beautiful. It had 7 different types of charts, all animating in real-time. It just didn’t happen to have any real data in it because the people on the ground couldn’t figure out how to feed the beast. We have prioritized the map over the territory. We have decided that the report of the work is more important than the work itself.

These are the artifacts of a workforce that has been abandoned by its own tools. Maria’s hangar was full of these shadows. Every desk had a sticky note with a password; every terminal had a ‘Do Not Use’ sign taped over a feature that didn’t work. The company had spent 7 years trying to eliminate these shadows, not realizing that the shadows were the only thing keeping the lights on.

The Inevitable Crash

I feel a strange kinship with Maria today. We are both trapped by interfaces. She is trapped by a $777,000 platform that doesn’t understand car crashes, and I am trapped by a social media algorithm that won’t let me forget a moment of social awkwardness. We are both fighting against the ‘Default Path.’ The default path is the 17 clicks. The default path is the ‘Like’ button that lives exactly where your thumb rests when you’re being a creep. To do something real, to do something authentic, you have to deviate. You have to build your own spreadsheet. You have to admit that the system is broken.

There was a moment, about 37 minutes into our conversation, where Maria’s tablet finally synced. It made a cheerful ‘ding’ sound, a sound of unearned accomplishment. It had finally accepted the data for the 2017 sedan. Maria didn’t celebrate. She just looked at her spreadsheet to make sure the numbers matched. They didn’t. The software had rounded the impact velocity from 47.7 mph to 48 mph. It seems like a small thing, a rounding error. But in the world of crash testing, that 0.3 mph is the difference between a minor bruise and a fatal internal hemorrhage. The software had traded accuracy for ‘cleanliness.’ It wanted a whole number. It wanted the dashboard to look tidy.

This is where work goes to die. It dies in the rounding errors. It dies in the 17th click. It dies when we stop trusting the person who is standing in the glass and start trusting the person who sold us the license. I realized then that I haven’t apologized for liking that photo yet. Maybe I won’t. Maybe that ‘like’ is the only honest thing I’ve done on that platform in 7 months. It was a mistake, yes, but it was a human one. Maria’s spreadsheet is full of human mistakes, too-smudges of grease, scribbled corrections-but it’s more honest than the $7,777,747 lie sitting on her tablet.

The Path Forward: Digital Humility

We need to start building for the grease. We need to start building for the 107-degree heat and the 17-year veterans who don’t have time for a tutorial. The future of work isn’t ‘Digital Transformation’; it’s ‘Digital Humility.’ It’s the realization that the software should be the servant, not the master.

Until then, Maria will keep her spreadsheet. She will keep her Sharpie and her folded piece of paper. And I will keep my thumb far away from the screen, at least for the next 7 days, or until the next time I feel the need to see a ghost from my past. We are all just trying to navigate the impact, one click at a time, hoping the airbags deploy when the software inevitably crashes.