Nicole is standing over Marcus’s shoulder, her fingernails tapping a rhythmic, impatient staccato against the mahogany edge of his desk. She needs the quarterly conversion metrics for the Western region, and she needs them before the board meeting starts in exactly 18 minutes. Marcus, meanwhile, is staring at a loading icon-a sleek, minimalist circle that cost the company $2000008 to implement across 48 global offices. It’s the new enterprise resource planning suite, a behemoth of a program designed to unify every data point into a single, ‘truth-bearing’ dashboard. But the dashboard is currently ‘aggregating,’ which is corporate-speak for being hopelessly stuck in a loop of its own complexity.

This is the Great Reversion. It is the silent, widespread rebellion occurring in the shadows of every major digital transformation project. We are spending billions to move away from ‘primitive’ tools, only to find that the people actually doing the work are retreating to the very grids we tried to banish.

“

The problem… is that you’ve built a cathedral when the people just needed a sturdy hammer.

We often frame this as ‘resistance to change.’ We blame the aging workforce or a lack of training. But that is a convenient lie told by the people who sell the cathedrals. The truth is far more structural. The spreadsheet is perhaps the only piece of software in history that was truly designed for the end-user’s autonomy rather than the manager’s oversight. When a committee designs a $2 million system, they design it for reports. They design it for ‘visibility.’ They design it for the people who want to look at the work, not the people who have to perform it.

In Marcus’s spreadsheet, he has built custom macros that handle the weird, edge-case exceptions that the $2000008 system considers ‘errors.’ In his grid, he can account for the fact that the client in Bristol always pays in 58-day cycles regardless of the contract, or that the shipping delay in March was due to a localized strike that the ERP’s rigid logic can’t categorize. The spreadsheet is a living document, a masterpiece of user-centric engineering built by the person who understands the friction of the day-to-day. It is reactive. It is plastic. It is, in every sense, more ‘modern’ than the locked-down cloud platform that takes 48 seconds to load a single row.

The Trap of Feature Bloat

I remember a time when I thought more features meant more value. It’s a common trap. You see a software demo where the presenter clicks a button and a beautiful 3D chart appears, and you think, ‘Yes, that will solve our communication issues.’ But you forget that someone has to clean the data to make that chart. Someone has to navigate 18 nested menus to input a single lead. Eventually, the friction becomes so high that the human brain-seeking the path of least resistance-reverts to the grid.

Olaf W.J. points his spoon at the screen. ‘Look at those columns,’ he says, referring to Marcus’s hidden Excel sheet. ‘Column A8 through L8. That’s a narrative. It’s a story of a business process that evolved over 8 years. You can’t just map that onto a pre-built schema from a Silicon Valley startup and expect it to survive.’ He’s right, of course. We treat data like it’s oil-something to be extracted and refined-but data is actually more like a garden. It’s messy, it grows in strange directions, and it requires a gardener who is close to the soil. The ERP system is a paved parking lot. It’s clean, it’s organized, but nothing actually grows there.

There is a profound organizational hubris in believing that a centralized committee can predict the needs of a specialized worker. This is where companies like Magnus Dream UK find their relevance, by championing engineering that prioritizes the actual, lived experience of the user over the theoretical requirements of a boardroom. When you ignore the ‘how’ of the work in favor of the ‘what’ of the reporting, you create a vacuum. And shadow IT rushes in to fill that vacuum every single time. It’s not just about Excel; it’s about the desire for agency.

The Two-Tiered Reality

In most offices, there is a forbidden folder. It’s usually buried four levels deep in a shared drive, or worse, saved locally on a C-drive where IT can’t audit it. This folder contains the ‘real’ numbers. It’s the infrastructure that keeps the company profitable while the official systems are used for the theater of management. We have created a two-tiered reality: the official digital facade and the underground spreadsheet economy.

Olaf W.J. finishes his ice cream, the brain freeze finally subsiding. He starts talking about a project he worked on for a logistics firm in 2018. They had spent 88 weeks implementing a state-of-the-art tracking system. On the day of the launch, the CEO stood in front of a giant monitor showing real-time ship movements across the globe. It was beautiful. It was impressive. It was also completely fake. The ‘real-time’ data was actually being fed into the system by a team of 18 operators in a back room who were manually typing data from-you guessed it-a master Google Sheet. The expensive software was just a $2 million skin for a free spreadsheet.

Why do we keep doing this? Why do we keep buying the cathedral when we know the hammer works? Part of it is the fear of appearing ‘backward.’ In the modern corporate environment, using a spreadsheet is seen as a sign of technical debt, a vestige of a less sophisticated era. We equate complexity with progress. If a system is difficult to learn and requires a 128-page manual, it must be powerful, right? If it costs $2000008, it must be better than the tool that comes free with your laptop.

The Complexity Tax on Efficiency

But this complexity is a tax. It’s a tax on the time of people like Marcus, who now has to do his job twice: once in the ‘real’ world of his spreadsheet to actually get the answers, and once in the ‘official’ world of the ERP to satisfy the requirements of the system. We are doubling the workload of our most efficient people in the name of modernization.

I’ve made this mistake myself. I once tried to organize my entire personal life-from grocery lists to 8-year financial plans-into a complex productivity app. I spent 48 hours setting up the tags, the folders, and the automated workflows. For the first 8 days, I felt like a god of efficiency. By day 18, I realized I was spending more time managing the app than doing the tasks. I eventually went back to a pocket notebook. There is a tactile feedback in a simple tool that a complex one can never replicate.

We need to stop looking at the Great Reversion as a failure of the users and start looking at it as a failure of the architects. If your team is secretly using spreadsheets, it’s not because they are lazy. It’s because your expensive solution is standing in their way. They are choosing the tool that allows them to think, to iterate, and to solve problems in real-time.

The spreadsheet is the ultimate democratic tool. It doesn’t care about your job title or your permissions level; it just gives you a canvas and asks what you want to build. In an era of increasingly locked-down, ‘guided’ user experiences, that freedom is radical. It is the reason why, 48 years from now, when the current crop of ‘revolutionary’ AI-driven enterprise platforms are nothing but broken links and dead servers, there will still be someone, somewhere, hitting Ctrl+S on a file named REAL_DATA_final_v8.xlsx.

Marcus finally sends the slide. Nicole is happy. She has her numbers. She doesn’t know-and doesn’t want to know-that those numbers came from a ‘primitive’ grid rather than the $2000008 investment she championed. She walks away, the click of her heels fading down the hallway. Marcus exhales, closes the browser tab with the spinning loading icon, and returns to his grid. There are 18 new rows to enter, and for the first time all morning, he actually knows what he’s doing.