Your New Software Is Broken on Purpose

Your New Software Is Broken on Purpose

The cursor blinks. Once. Twice. You click the button again, a little harder this time, as if physical pressure can communicate intent through the layers of tempered glass and liquid crystal. Nothing. The button, labeled ‘Submit Expense,’ remains a placid shade of corporate blue, a silent monument to your wasted afternoon. This is the new, streamlined, revolutionary expense portal that has been the subject of 46 separate all-staff emails over the last 6 months. It was supposed to replace the shared Excel file, ‘Expenses_FINAL_v4_USE_THIS_ONE.xlsx’. Instead, it has produced only a low-grade, simmering rage that now fuels the entire accounting department.

This isn’t a bug; it’s a feature.

Not of the software, but of the entire corporate strategy that birthed it. We have entered the age of the Perpetual Beta. Companies, mesmerized by the siren song of ‘Digital Transformation,’ sign contracts for half-baked, barely-functional SaaS platforms because they look good on a shareholder report. They chase buzzwords instead of stability. The sales demo was flawless, a ballet of seamless integrations and one-click reports. But the reality, the version rolled out to 236 employees on a Tuesday morning, is a Frankenstein’s monster of broken APIs and user interfaces designed by people who seem to hold a deep, personal grudge against humanity.

They’ve effectively outsourced their quality assurance department to you. You, the marketing associate, the project manager, the sales lead. Your salary now quietly subsidizes the final 36% of the software’s development cycle. Every support ticket you file into the void, every convoluted workaround you discover and share in a Slack channel, is unpaid labor. You are the final, exhausted line of defense between a disastrous product and a company that has already paid the invoice. The vendor saved $676 per seat on their development budget, and it only costs you the will to live, one frozen loading screen at a time.

36%

of development cycle subsidized by your unpaid labor

The Art of Origami and SynergyHub

My friend Marcus J.-P. teaches corporate teams the art of origami. It’s a wellness initiative, a way to get stressed-out executives to use their hands for something other than typing angry emails. His craft is about precision, order, and the quiet satisfaction of a perfect fold. Last month, his contracting company forced him to start using ‘SynergyHub,’ an all-in-one platform for scheduling, invoicing, and “creative asset management.”

I tried to upload a PDF of folding instructions,” he said. “The upload bar reached 96 percent and then gave me an error message. It was just a picture of a sad computer. Not an error code. Just a drawing.”

This is a man who can turn a flat square of paper into a flapping crane with exactly 16 folds. He understands process. He understands steps. SynergyHub, however, does not. It requires him to log in through three separate authentication screens, and if he gets one wrong, it locks his account for 6 hours. He told me he spends more time trying to submit his invoices than he does actually teaching his workshops.

The Lost Trust

This reminds me of a Wikipedia rabbit hole I fell into last week. I started on the page for ‘Cognitive Dissonance’ and ended up on the history of the ‘Undo’ command. It was developed at Xerox PARC in the 1970s. Think about that. The concept of a digital safety net, the ability to take back a mistake, is nearly half a century old. It was a foundational gesture of trust between the machine and the user. It said, “Experiment. Try something. You can always go back.”

Today’s internal tools have lost that trust.

There is no undo for a submitted form that vanishes into a broken database. There is no going back from a corrupted file saved by a cloud-based word processor that had a momentary glitch. The sad computer drawing is the new reality.

My Own Confession

I’d love to stand on a soapbox and blame the faceless vendors or the uncaring IT departments, but I can’t. Not entirely. Because I was once part of the problem. I was on a committee, 6 years ago, tasked with choosing a new project management tool. We were dazzled by the one with the most features. It had Gantt charts, Kanban boards, resource allocation heatmaps, and 236 other bullet points on its marketing website. We chose it. We inflicted it upon our colleagues.

It was a catastrophe. The features were all there, technically, but they were buried under layers of confusing menus and non-intuitive workflows. It was powerful, but unusable. We had chosen the promise of functionality over the reality of human experience. We spent our days fighting the tool instead of doing our jobs. The adoption rate was catastrophic, and after 16 painful months, we retreated to our old system of shared documents and a very complicated whiteboard. I championed a monster because I was seduced by its list of capabilities, forgetting to ask the simple question: does it actually help anyone?

The Promise

Functionality over experience

VS

The Reality

Fighting the tool, not working

That bloated, feature-heavy platform also promised a “content creation” module. It claimed you could edit videos, format blog posts, and even generate audio for internal communications. Of course, it did all three things with breathtaking incompetence. I remember a colleague from our São Paulo office trying to create a simple Portuguese audio version of a company announcement. The tool’s text-to-speech engine was a mess, and the interface kept crashing. He eventually gave up and used a simple, single-purpose tool he found online. He showed it to me once; he could just paste in his script and converta texto em podcast with a single click. It didn’t try to manage his budget or schedule his meetings. It did one thing, it did it well, and it got out of his way. That’s the difference between a tool and a hindrance.

Learned Helplessness

This constant exposure to bad technology creates a deep-seated organizational disease: learned helplessness. After you’ve been burned by six consecutive “game-changing” software rollouts, you stop believing the next one will be any different. Your expectations plummet. You no longer hope for a tool that will make your job easier, but merely for one that won’t make it actively harder. The announcement of a new platform is met not with excitement, but with a collective, weary sigh. We are being trained to expect failure.

It’s a profound disrespect for the employee’s time and intelligence. When a company provides you with a broken shovel, it’s not just making it harder to dig. It’s sending a clear message that it doesn’t value the hole, the digger, or the time spent digging. It’s a thousand tiny cuts that bleed morale dry, fostering a culture of cynicism that no amount of free pizza or corporate happy hours can fix.

These tools aren’t just failing to work.They are succeeding at making us feel small.

Grateful for Partial Failure

I spoke to Marcus again this morning. He’s abandoned SynergyHub for invoicing and scheduling, retreating to the functional simplicity of email and a calendar. A workaround. A shadow system, like the hundreds that exist in every company that has chosen sizzle over steak. He still has to use the portal for one thing, however: uploading photos of the origami models from his workshops for the company’s internal newsletter.

Does it work?” I asked.

He was quiet for a moment. “The ‘upload’ button works,” he said. “About 86 percent of the time.”

86%

functionality now feels like a roaring success

And that’s the truly insidious part. We’ve become grateful for that. We celebrate the one feature that occasionally functions as advertised. Our standards have been so thoroughly lowered that partial failure now feels like a roaring success. We have adapted to the perpetual beta, molding our workflows around its deficiencies, accepting the friction as a cost of doing business.

A Finished Thing That Simply Worked

Later, he sent me a video. It was just his hands and a single, square sheet of red paper. He made a valley fold, then a mountain fold. A squash fold, a petal fold. There were no pop-up windows, no loading spinners, no cryptic error messages. With 6 final, precise movements, his hands transformed the flat sheet into a perfect crane. It wasn’t a prototype. It wasn’t a minimum viable product. It was a finished thing. It did exactly what it was supposed to do, with a quiet elegance that has become completely alien in our digital world. He had created something that simply worked.

The quiet elegance of something that simply works.