The Tyranny of the Spinning Circle

Sarah’s cursor is currently hovering over the ‘Save & Close’ button that hasn’t functioned for the last 49 seconds. She’s staring at the new CRM like it’s a sentient creature designed specifically to ruin her Tuesday afternoon. In the old system-a clunky, gray box of a program that looked like it was coded in 1989-she could log a call, update a lead, and move to the next task in 19 seconds flat. Now? Now she’s navigating seven nested menus, three mandatory fields for ‘Data Governance Compliance,’ and a spinning blue circle that mocks her existence with its relentless, rhythmic rotation.

She reaches for a yellow sticky note. It’s her 19th one today. She’s keeping a paper record of every transaction because she doesn’t trust the cloud. The cloud, in her experience, is where data goes to be forgotten by the people who actually need it and harvested by people who only want to look at graphs. This isn’t just a Sarah problem. It’s a systemic rot. We have entered the era of the ‘Dashboard Fallacy,’ a period where the usability of a tool is sacrificed on the altar of managerial visibility.

I’m writing this while my own browser tab for the company payroll hangs indefinitely. I cleared my browser cache in desperation about 29 minutes ago, hoping it would exorcise the ghosts in the machine, but the ghosts seem to have tenure. It’s a bizarre form of modern torture: we are given ‘faster’ tools that make us work twice as long to achieve the same result.

Building for the Check Signer, Not the Craftsman

Casey C.M., an acoustic engineer I’ve known for 9 years, knows this frustration better than most. […] Last month, his firm upgraded to a new signal processing suite that promised ‘AI-driven optimization.’ Casey, who usually spends 19 minutes calibrating a room’s response, spent 139 minutes trying to override the software’s automated ‘corrections.’ The software thought the room had too much low-end resonance; Casey knew it was the specific character the client paid for.

[The algorithm doesn’t care about the art; it only cares about the average.]

Casey eventually gave up and used his old analog meters. He told me, while we were grabbing a coffee that cost exactly $9, that the problem is that software designers no longer build for the craftsman. They build for the person who signs the check. The person signing the check never has to use the ‘Add New Record’ button. They only ever see the ‘Quarterly Progress’ report that the software generates automatically.

Feature Retention Bias

This creates a perverse incentive structure. If a software feature makes the user’s life harder but makes the manager’s report 9% more detailed, the feature stays. We are systematically destroying institutional knowledge in the name of ‘data integrity.’

Control vs. Capability

When you force an experienced employee to follow a rigid, 29-step workflow designed by someone who has never done the job, you aren’t just slowing them down. You are telling them that their intuition, their ‘shortcuts’-which are actually just highly optimized cognitive pathways developed over decades-are worthless. You are treating them like untrustworthy children who cannot be trusted to put data in the right box without a digital leash.

I’ve seen this happen in 9 out of 10 digital transformations I’ve witnessed. The transformation is rarely about the work; it’s about the control. It’s about the illusion that if we can track every second of an employee’s day through 79 different metrics, we somehow understand the business better. But you don’t. You just understand the data. The business is what happens in the gaps between the data points-the conversations Sarah has with her clients that she can’t log because there isn’t a dropdown menu for ‘Empathy.’

The Friction Multiplier

Wait, I’m getting a notification. The payroll tab finally loaded. It’s asking for a ‘Two-Factor Authentication’ code that was sent to an email address I haven’t used since 2019. This is the friction I’m talking about. It’s the 99 tiny papercuts that eventually bleed a company’s productivity dry.

Enterprise software is the loud noise of the modern office. It masks the sound of creative problem-solving. It masks the sound of genuine collaboration. It replaces the ‘click-clack’ of a focused typist with the ‘click… wait… click… sigh’ of a frustrated one.

I remember a time when a ‘system’ was just a way of doing things, not a digital cage. My grandfather ran a warehouse with a ledger and a pencil. If he needed to know how many pallets of grain were in the back, he walked to the back and counted them. It took him 9 minutes. Now, we have warehouse management systems that require 29 minutes of data entry every time a pallet moves three feet. We know where the grain is in real-time on a screen, but we’re so busy updating the screen that we don’t have time to actually move the grain.

Demanding Better Workflows

Is it possible to go back? Probably not. But we can demand better. We can demand that software be built with a ‘User First’ manifesto. We can refuse to buy systems that treat our staff like telemetry sensors. If a task took two clicks in 2009, there is no technical reason it should take twelve clicks in 2024. The only reason it does is because someone, somewhere, decided that their need for a granular report was more important than your need to actually do your job.

This is where the ‘Yes, and’ philosophy comes in. Yes, management needs visibility. And yes, employees need to work efficiently. These two things are not mutually exclusive, but they are often treated as such. The solution is to build systems that capture data as a byproduct of a good workflow, not as the primary goal of a bad one. If the software is delightful to use, the data will be accurate. If the software is a chore, the data will be manipulated, truncated, or simply ignored.

I’ve spent the last 99 minutes writing this, and in that time, I’ve had to refresh my browser 9 times. Every time I do, I lose a little bit of the ‘flow.’ That’s the real cost of bad software. It’s not just the seconds lost to clicking; it’s the minutes lost to re-focusing. It’s the cognitive load of navigating a hostile interface.

Beyond the Picture

It’s time to stop the ‘spinning blue circle’ of organizational decay. It’s time to build things that actually work, for the people who actually work. Because at the end of the day, a dashboard is just a picture of a business. It’s not the business itself. And if you kill the business to get a better picture of it, what exactly have you accomplished?

I’m going to try and submit this now. I hope the ‘Submit’ button works. If it doesn’t, I’ve got a yellow sticky note and a pen ready. I’ll just write it all down and mail it to you. It might be faster.