The Illusion of Visibility

The Director is hovering his cursor over a bright magenta slice of the pie chart, and for a second, the pixelated lag makes it look like the data is bleeding into the background of the Zoom call. He’s talking about ‘granularity’ and ‘real-time visibility,’ words that usually signal someone has stopped looking at the actual work and started looking at the map of the work. My phone buzzes on the mahogany desk-it’s a private Slack message from Ana L.-A., an industrial hygienist who’s been with the firm for 12 years. She’s sitting three rows behind me in the physical office, though we’re both staring at the same glowing rectangle from different cubicles.

I look back at the screen. The Director is now highlighting a bar graph that cost us exactly $2,402,022 to implement across 52 regional offices. It is a masterpiece of modern engineering that nobody knows how to use, designed by people who have never had to stand in a cold warehouse at 22 minutes past midnight trying to log a structural failure. It’s a colossal failure of empathy disguised as progress. We didn’t actually solve the communication bottleneck; we just paved over it with a very expensive, very shiny toll road that everyone is currently driving around by taking the dirt path through the woods. The dirt path, in this case, is a series of interconnected spreadsheets named ‘FINAL_v2_ACTUAL_REAL_Numbers.xlsx.’

The Architect of Friction

I spent 12 minutes this morning googling the lead consultant who sold us this package. I just met him yesterday in the breakroom-he was the one wearing the $802 loafers and carrying a leather portfolio that looked like it had never touched a surface dirtier than a marble countertop. His LinkedIn profile is a curated gallery of ‘disruptive’ buzzwords and ‘thought leadership’ posts about the future of the workplace. He’s 22, maybe 32 if he’s had a very good dermatologist. He has never filled out a compliance form. He’s selling systems that solve the problems executives think they have, while completely ignoring the friction that defines the employee’s actual life.

Ana L.-A. is the person who actually keeps this company from exploding, figuratively and literally. As an industrial hygienist, her job is to identify risks-asbestos, noise levels, chemical vapors-that others ignore. She sees the software as another form of toxicity. To her, a broken UI is just as dangerous as a faulty ventilation system because they both lead to the same result: people taking shortcuts to survive the day. When a piece of software requires 32 clicks to record a 2-minute observation, the observation doesn’t get recorded. The data becomes a lie, and the company starts making decisions based on a fantasy.

The Charade and The Cockroach

[The dashboard is a graveyard of intentions.]

“

I find myself responding to Ana’s Slack while the Director explains the ‘synergistic data lake’ we’ve apparently built. I suspect the ‘lake’ is actually a stagnant pond, but I don’t say that out loud. I’ve made the mistake of being the ‘negative’ person in the room before, and all it gets you is an invite to a 72-minute meeting about ‘mindset shifts.’ Instead, I start digging through my local drive to find the spreadsheet she needs. It’s a file that shouldn’t exist. It’s technically a security risk. But if I don’t send it, the North sector safety reports won’t get filed, and someone might actually get hurt. This is the paradox of modern digital transformation: we spend millions to centralize data, only to force our most competent people into the shadows just so they can keep doing their jobs.

It’s a strange feeling to realize you are participating in a charade. We all nod. We all attend the training sessions. We all pretend that the new CRM is ‘changing the game.’ But the moment the meeting ends, there is a collective, silent exhaling of breath as everyone minimizes the browser and reopens Excel. Excel is the stickroach of the corporate world-not because it’s perfect, but because it is resilient and obedient. It doesn’t tell you that your vendor ID is the wrong length. It just lets you type. It’s a tool, whereas the $2 million software is an ecosystem that demands you live by its rules or starve.

I remember once, about 22 months ago, I tried to point out that the user interface on our previous ‘transformation’ was unintuitive. The project manager looked at me as if I had suggested we go back to using carrier pigeons. He told me it was an ‘adoption issue’ and that we needed more ‘internal champions.’ That’s the industry’s favorite way of saying that the users are the problem, not the product. If you can’t use the hammer, it’s not because the hammer is poorly balanced; it’s because you haven’t been trained enough in the ‘philosophy of the swing.’

Beyond the Enterprise Shell

This lack of user-centricity is everywhere. It’s not just enterprise software. You see it in the way we design cities, the way we handle healthcare, and even in how we approach online entertainment. When systems are designed for the person at the top-the one who wants the report, the one who wants the total-they inevitably fail the person at the bottom who has to provide the input. In the world of online gaming and digital platforms, this is why simplicity often wins. A platform like mawartoto succeeds because it recognizes that the user’s experience and their ability to stay within safe, responsible bounds is more important than a feature-heavy interface that confuses the intent. If a user can’t find the exit or the limit because of ‘revolutionary’ design, the system hasn’t just failed; it’s become predatory. We see the same thing in the office, albeit with less flashing lights. When the ‘save’ button is buried under four layers of menus, the software is essentially gaslighting the employee into thinking their time isn’t valuable.

Ana Slack-pings me again. ‘Found it. Thanks. By the way, the new guy-the consultant-just asked me if I could export my ‘historical data’ into his format. I told him my historical data is in my head and on a clipboard. He looked at me like I was a ghost.’

The Digital Twin’s Blind Spot

I laugh, a sharp, dry sound that I hope the Director thinks is a reaction to his joke about ‘data silos.’ The truth is, people like Ana are the ghosts in the machine. They are the ones who know where the bodies are buried because they are the ones who had to dig the graves. They know that the $2 million software can’t capture the nuance of a disgruntled foreman or the smell of a localized gas leak. The software wants binary inputs-Yes or No, 1 or 0-but the world is mostly made of ‘maybe’ and ‘it depends.’

We are currently obsessed with the ‘Digital Twin’ concept-the idea that we can create a perfect digital replica of a physical system. But we forget that the digital twin doesn’t sweat. It doesn’t get frustrated. It doesn’t have a 52-minute commute that makes it grumpy during the morning data entry. We are building systems for digital humans and then getting angry when real humans find them unusable. It’s a gap that no amount of ‘digital transformation’ can bridge unless we start by admitting that we don’t know what the person on the ground actually does.

I acknowledge my own errors here, too. I’ve sat on committees where I voted for these ‘comprehensive’ solutions because they looked good on a slide deck. I’ve been seduced by the promise of a single source of truth, forgetting that truth is often messy and distributed. I’ve ignored the quiet warnings from the industrial hygienists and the floor managers because I wanted the $2,002,232 project to be the success it was marketed to be. It’s easier to buy a solution than to fix a culture.

The Record of Resistance

As the Zoom call finally winds down, 12 minutes past the scheduled end time, the Director closes with a quote about ‘innovation being the only way forward.’ I close the browser tab. I look at my desktop, cluttered with 32 different versions of the same spreadsheet. I feel a strange sense of loyalty to these files. They are the record of our resistance. They are the proof that we are still working, despite the software, not because of it.

I think about the consultant I googled. I wonder if he ever goes home and feels like he actually built something, or if he just feels like he successfully moved some money from one pile to another. Maybe he doesn’t care. Maybe he thinks the spreadsheets are the problem. But as long as the $2 million dashboard keeps reporting 82 open tickets when there are actually only 42, Ana L.-A. will keep her Excel files. And I will keep sending them to her. We are the guardians of the real numbers, living in the shadow of the ‘transformation’ that never actually happened. We’ll keep the lights on, even if we have to use a tool from 1992 to do it.