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.
Why did employees resist going paperless?
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 wouldn’t 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.
That fear deserves respect, and I can’t stand leaders who read quiet resistance as laziness or stubbornness. What they’re looking at is a competent person watching the thing that made them competent get taken away.
The intensity is easy to measure: 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 better founded. But the shape is identical: a workforce looking at a new technology and privately asking whether they’re still valuable on the other side of it.
If you’re leading an AI adoption today, you’re running our paper conversion at higher volume, and the resolution we found still applies. I wrote a companion piece on exactly that parallel.
What was the paper underground?
The most instructive resistance was the kind we couldn’t see. When pressure mounted, the paper didn’t disappear; it went underground.
Ledgers maintained “just in case” in bottom drawers. Spreadsheets secretly shadowing the new modules, reconciled after hours by people hedging against the day the system failed, or the day they failed the system. Every one of those parallel records was labor invisible to management, doubled work performed voluntarily by people we’d officially relieved of it.
You can’t demo your way past someone’s worry about their own survival.
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 don’t 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, whatever the rollout plan said.
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 don’t resist new systems. They resist what the systems imply about their jobs.Share on X
What works against paper resistance?
Mandates didn’t dissolve the resistance; they drove it underground, into parallel paper kept “just in case” and systems used reluctantly and badly. Enthusiasm campaigns didn’t touch it either, because the fear wasn’t about the system’s merits. You can’t demo your way past someone’s worry about their own survival. I think mandating adoption is the lazy leader’s move. It feels decisive and looks good in a status report, and it teaches every frightened employee to hide their doubts in a bottom drawer.
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. That means you exist in the new world. Once people knew they would have a job, and knew they could do the job, the resistance didn’t have to be defeated. It evaporated, because the thing it was protecting was no longer threatened.
| Approach | Result | Why |
|---|---|---|
| Mandates | Drove resistance underground into parallel paper and reluctant use | They teach frightened employees to hide doubts in a bottom drawer |
| Enthusiasm campaigns | Did not touch the resistance | The fear was never about the system’s merits |
| Reassurance | Not believed | It is free, and everyone knows it |
| Reading resistance as laziness | Misses what is happening | A competent person is watching their competence get taken away |
| Serious, visible retraining | Resistance evaporated | It costs the company something and shows people they exist in the new world |
My take
Quit treating resistance as stubbornness. The people clinging to their filing cabinets are watching the thing that made them competent get taken away, and they’re scared for their jobs. Mandates push the paper into bottom drawers, where it doubles everyone’s work in secret. Retrain them, seriously and where everyone can see it. The training tells them they have a place in the new world, and the resistance has nothing left to protect.
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’s the only answer they’ll believe, because it costs the company something. Reassurance is free and everyone knows it. A training program is a commitment with a budget attached.
Any executive who led a change like this has a strong chapter sitting in that fight, because every reader leading any change recognizes it. Skipping it to get to the launch cuts the part readers came for. The technology in these stories dates quickly, and the quiet fear in the accounting department shows up again with every new system.
For more from this series, see The Digital Transformation Hub: real transformations, lived from the inside, decades before the term existed.
Frequently Asked Questions
- U.S. Workers Are More Worried Than Hopeful About Future AI Use in the Workplace, Pew Research Center
