The Ritual of Export
Sarah clicks 'Export to CSV' for the seventh time this afternoon, the rhythmic mechanical tap of her mouse echoing in the quiet of the open-plan office. She doesn't look at the screen anymore; she knows exactly where the loading bar will stall for 13 seconds before the file finally drops into her downloads folder. The new multi-million dollar 'Project Hub'-the one the C-suite called the 'backbone of our digital transformation'-glares back at her with its clean, minimalist interface and perfectly rounded corners. It is a beautiful, expensive graveyard of data.
She opens the file in Excel, and suddenly, the air in her lungs feels a little less stale. Her fingers fly across the keys, building the pivot tables and nested VLOOKUPs that the new system simply cannot produce. She saves the file as 'Campaign_Report_FINAL_v9_use_this_one.xlsx'.
Time spent circumventing the $2M investment.
The Quiet Mutiny
We spent $2,000,003 on a solution that everyone in this building secretly hates. I watched the invoice get signed. I saw the celebratory champagne in the 43rd-floor lounge. And yet, if you walk through the cubicles after 5:03 PM, you won't see anyone using the 'Hub' for actual analysis. You'll see the green glow of spreadsheets. It's an open secret, a quiet mutiny carried out in rows and columns.
The path of least resistance (Excel).
Cannot fit through the back alleys.
We bought a Ferrari and everyone is still riding their old, rusty bicycles through the back alleys because the Ferrari won't fit through the streets where the actual work happens.
The Streetlight Effect: Where Progress Hides
I fell into a Wikipedia rabbit hole the other night, reading about the 'Streetlight Effect.' It's a type of observational bias where people only look for what they're searching for where the light is brightest. Our new system is the brightest light in the company. It generates beautiful charts and real-time dashboards that look incredible in a boardroom presentation.
But the actual work-the gritty, complex, context-heavy problem solving-is happening in the dark, in the 'Shadow IT' of spreadsheets and unsanctioned Slack channels. We are measuring the light while the real progress is happening in the shadows.
[The map is not the territory, but we keep trying to live inside the map.]
Translation and Agency
This gap between the prescribed process and the messy reality is where the most brilliant human ingenuity resides. When Sarah builds that spreadsheet, she isn't just being difficult. She is performing an act of translation. She is taking the rigid, sanitized data from the $2,000,003 system and turning it into something that actually means something to her team.
System Output
Sanitized & RigidThe Workbook
Act of TranslationActionable Insight
Living DocumentThe Irony of Belief
I realize the irony here. I'm the one who advocated for the 'Hub' in the first place. I stood in front of the board and talked about 'one source of truth' and 'seamless integration.' I was a believer. But I was wrong.
The 'Shadow IT' isn't a bug; it's a feature of a resilient organization. It's how people survive the imposition of systems that don't understand their day-to-day pain. If you want to know how a tool should actually function, don't look at the sales deck. Look at the shortcuts the employees have invented for themselves. You can find more wisdom in a single insight than in a thousand pages of software documentation because the former understands that the human element is the only thing that actually matters in the end.
Trading Agility for Legibility
We often mistake standardization for efficiency. We think that if everyone does things the exact same way, we will move faster. But efficiency is about output, not adherence. If Sarah can finish her report in 13 minutes using a 'Final_v9' spreadsheet, but it takes her 43 minutes to struggle through the official 'Hub' workflow, which one is actually more efficient?
We've traded the agility of the individual for the legibility of the collective.
The managers can now 'see' everything, but the workers can 'do' less.
Agency: Canvas vs. Coloring Book
We need to stop asking how we can make people use the software and start asking why the software makes it so hard for people to work. The resistance isn't about being 'old-fashioned' or 'afraid of change.' It's about the fundamental human need for agency.
Blank Canvas
Extension of thought process.
Coloring Book
Cage for thought process.
A spreadsheet is a blank canvas; a corporate system is a pre-filled coloring book where you aren't allowed to go outside the lines. And work, real work, is almost always outside the lines.
The Burden of Being Everything
I think about the history of the Antikythera mechanism-that ancient Greek analogue computer used to predict astronomical positions. It was a marvel of engineering, a complex system of gears and dials. But it didn't change the stars. It just gave people a way to track them. Our modern systems often forget that. They try to be the stars, the gears, and the observer all at once. They try to be everything, and in doing so, they become a burden to the very people they were meant to serve.
Sarah is closing her laptop now. It's 5:33 PM. She's sent her 'v9' report to the team, and they've already started making decisions based on it. The 'Project Hub' remains untouched, its dashboard showing a 'Pending' status for a task that was actually completed two days ago in a private chat. The system is silent, expensive, and perfectly organized. But the pulse of the company is beating somewhere else, in the flickering cells of a spreadsheet that technically doesn't exist.
Does the tool serve the person, or does the person serve the tool? If you find yourself exporting data just to do your job, you already know the answer.
Will change that fact.