Table of Contents
TL;DR
The paper departments did not resist the computers. They resisted what the computers implied about their jobs. When we moved accounting, HR, and payroll off paper at a major national retailer, the pushback was persistent and quiet: people wanted their spreadsheets, their Word documents, their filing cabinets. Underneath the preference was a fear, and naming it correctly was the beginning of solving it.
You can imagine how it went. We were taking a major national retailer’s accounting, human resources, and payroll off paper and onto a new computer system, and the people who ran those departments wanted to stay on paper. Not loudly. Nobody stood on a desk. The resistance was quieter and more durable than protest: a steady preference for the Excel spreadsheet over the module that replaced it, the Word document over the form, the cabinet over the database. Just getting people to buy in was, oh my lord, a project of its own.
What the resistance actually was
It took me a while to hear what the resistance was saying, because it never said it directly. The people fighting for paper were worried, at some level, that the system was coming for their jobs, or that they would not be able to do their jobs in the new world. Their competence lived in the paper. They knew where everything was, how every process ran, what every exception meant. The computer erased that map and made twenty-year veterans into beginners.
I want to be precise about the intensity, because I have now watched this movie twice. The fear back then was a back-of-the-mind thing, a murmur, nothing like the fear people carry today about AI. Today’s version is louder and, frankly, better founded. But the shape is identical: a workforce looking at a new technology and quietly asking whether they are still valuable on the other side of it. If you are leading an AI adoption today, you are running our paper conversion at higher volume, and the resolution we found still applies, which is why I wrote a companion piece on exactly that parallel.
The underground
The most instructive resistance was the kind we could not see. When pressure mounted, the paper did not disappear; it went underground. Ledgers maintained “just in case” in bottom drawers. Spreadsheets quietly shadowing the new modules, reconciled after hours by people hedging against the day the system failed or, more honestly, the day they failed the system. Every one of those parallel records was labor invisible to management, doubled work performed voluntarily by people we had officially relieved of it.
I learned to read the underground correctly: not as sabotage but as a trust measurement. People maintain a parallel system exactly as long as they do not trust either the new system or their own place in it, and the drawer ledgers retired on their own schedule, which was the schedule of confidence, not the schedule of the rollout plan. You can decree a cutover date for software. Belief cuts over one person at a time, and the retraining was what moved that date more than anything we mandated.
People do not resist new systems. They resist what the systems imply about their jobs.Share on X
What did not work, and what did
Mandates did not dissolve the resistance; they drove it underground, into parallel paper kept “just in case” and systems used reluctantly and badly. Enthusiasm campaigns did not touch it either, because the fear was not about the system’s merits. You cannot demo your way past someone’s worry about their own survival.
What worked was retraining. We trained the paper people into the new system, seriously and visibly, and the effect went beyond the skills transferred. The training itself was the message: the company is investing in you operating the new world, which means you exist in the new world. Once people knew they would have a job, and knew they could do the job, the resistance did not have to be defeated. It evaporated, because the thing it was protecting was no longer threatened.
The lesson under the lesson
Every transformation plan has a line item for training, treated as skills logistics. That framing misses what training does. Retraining is the answer to the question your workforce is silently asking, and it is the only answer they will believe, because it costs the company something. Reassurance is free and everyone knows it. A training program is a commitment with a budget attached.
The executives I ghostwrite for often lived a version of this fight, and it is reliably the strongest chapter in their book, because every reader leading any change recognizes it. The technology in these stories dates. The quiet fear in the accounting department never does.
For more from this series, see the The Digital Transformation Hub: real transformations, lived from the inside, decades before the term existed.
The Guides That Get Your Book Written, Published, and Sold
Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.
We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.