The cursor was frozen, a perfect, mocking circle spinning against a background of corporate beige. Sarah had attempted the simple task seven times. Submit expense report. Total value: $48. She was currently on the third nested menu, trying to locate the specific GL code for ‘Client Refreshments (Non-Alcoholic, Quarterly).’ If she failed this attempt, the system would time out, erasing everything, forcing her to restart the data entry process-a process that involved manually typing 8 digits of a receipt number she could have sworn was just 6 digits last week.

This is not a story about a technical bug. This is a story about a technical ideology, one where complexity is mistaken for competence, and where every layer of unnecessary friction communicates a singular, profound message: We do not respect the people who do the work.

Resistance to Stupidity

I’ve heard the argument countless times from middle management and the software sales teams that collect exorbitant commissions. “Employees are just resistant to change,” they insist, often with a slight, patronizing sigh. They believe the grumbling is a psychological failing of the workforce-a fear of the new, an attachment to the old, inefficient ways. This is, quite frankly, a lazy and self-serving deception.

Nobody resists efficient, well-designed tools. People do not resist change; they resist stupidity. They resist the new, expensive system that takes 17 clicks to perform a function that required two clicks in the dusty, old, supposedly outdated platform.

When a system imposes an illogical workflow, it doesn’t just waste time; it imposes a cognitive tax. Every extra click, every redundant verification step, every unnecessary scroll or pop-up notification requires the user to expend a tiny fraction of mental energy. Multiplied across a team of hundreds, performing these actions 238 times a day, the cost shifts from milliseconds lost to hours of psychological depletion.

Complexity Theater

This is the problem of the ‘solution looking for a problem.’ We build systems that are architecturally pristine, satisfying the needs of the audit committee or the C-suite’s desire for ‘robustness,’ without ever observing the person actually performing the labor. We elevate theoretical purity over practical utility.

Confession: I Was the Architect of Friction

And I’m not standing here on a pedestal, criticizing from some high ground. In a past life, attempting to project expertise, I personally insisted on a new reporting architecture that required 8 mandatory data fields-fields no one in the field organization actually used-just to generate a simple weekly activity report.

I fought for it, and the company acquired a specific module… It was a failure. It taught the sales team one thing: click the ‘N/A’ checkbox 8 times and move on. I was part of the problem. I prioritized theoretical future potential over immediate, practical flow.

The Antidote: Disappearing Systems

When we force someone through 17 unnecessary steps, we are saying, “We value the abstract idea of control more than your actual contribution.” This leads directly to learned helplessness. The system becomes a digital straitjacket, punishing initiative.

The antidote to this kind of digital absurdity often involves simplifying the decision-making process by returning to what is physical and tangible. Consider businesses that truly understand this inherent human need for immediate clarity and low friction.

“

They bypass the digital friction entirely and focus on providing a clear, contextualized, high-trust experience where the decision is simple because the environment is controlled, curated, and relevant.

– Business Model Observed

The team at Flooring Store doesn’t ask you to click through six online portfolios and read 12 PDFs before making a choice. They bypass the digital friction entirely and focus on providing a clear, contextualized, high-trust experience where the decision is simple because the environment is controlled, curated, and relevant.

The Final Indictment

The best system is the one that disappears, leaving the user alone with the task they need to complete. The system should facilitate, not dictate. It should observe the natural rhythm of the human workflow and fit itself around that reality, rather than forcing the human to contort themselves to meet the system’s arbitrary demands.

Every day, we pay thousands of dollars for systems designed by people who never have to use them… The greatest indictment of modern enterprise software isn’t that it’s complicated; it’s that it feels cruel. It’s the digital equivalent of requiring someone to walk 8 extra miles just to reach the mailbox.