Skip to content
Blogs Best-practices

Excel resistance is expertise, not stubbornness: how to win them over

Excel resistance is expertise, not stubbornness: how to win them over

Excel resistance is not stubbornness but expertise. If you fail to see that, you lose your best people before the first training session has even started. You have bought a new system and the demo looked good. Yet your most experienced employee sits in the kick-off with his arms folded, while the file on his screen has kept the business running for 15 years.

Does this sound familiar? A business owner with a team of 10 to 30 people decides it is time for a proper system. Planning, stock or quotes move over, and with them goes the Excel file in which one colleague has tracked everything for years. That same colleague then suddenly becomes reluctant. He asks a lot of questions, sees objections everywhere and keeps putting the switch off. The conclusion seems obvious: he simply does not want to change. But that conclusion is almost never right.

Look at what that file actually is. He often built it himself, perhaps 10 or even 15 years ago. Every column, every formula and every colour code went in to solve a problem he came across in practice. He knows exactly how it works and which parts are best left alone. The file gives him control. It also makes him the person colleagues go to when something does not add up.

Take that file away and to him it feels as if you are taking away his knowledge, and with it his place in the business. The resistance you see is therefore a logical reaction to what he stands to lose. Handle it badly and it becomes a struggle that lasts for months. Handle it well and this very employee becomes your best ambassador. To do that, though, you have to start differently from most implementations.

Start with his knowledge, not with the system

The usual approach goes like this: you choose a supplier, set up the system, plan a training session and only then bring the people in. That puts the experienced employee at the back of the queue. He is presented with something that was designed without him and that he then has to get used to. That is how you lose exactly the person who knows the work best. Turn it around. Start with a conversation in which he explains how the work really runs, before anyone shows a single screen of the new system.

Ask about the steps, the exceptions and the pitfalls. What happens if a customer changes their order halfway through the month? Why is that one column red? Which customer always gets a different price, and why? None of this is in any manual, and he knows it better than anyone. Write it down, preferably in his own words. That list later becomes your checklist when setting up the system.

See his Excel file as a blueprint for the new system. Everything in it was needed at some point. A supplier who sets things up in the standard way misses half of those rules. Someone who has worked with the file for 15 years sees in a few minutes what is missing. So involve him in the conversations with the supplier as well, and not just as a listener. Let him ask the questions you cannot think of. That shifts his role. He loses nothing, he helps build.

Then show him what it gives him. What the business gains from it interests him less. Think of fewer colleagues standing at his desk with questions all day, no more retyping, and finally being able to go on holiday without being phoned. For someone who has carried everything for years, that is often the strongest argument there is.

Five places where it still goes wrong

Even if the first conversation goes well, an implementation can still run aground along the way. We see five recurring failure points. They can all be prevented, but only if you know them in advance. Use them as a checklist before you set a start date. Each point comes down to the same question: does the experienced employee keep the feeling that this is his work, or does it become something that happens to him? A switch usually takes a few months, and that feeling determines how the rest of the process goes.

1. An unfamiliar system instead of his own work

Take his file as the starting point. Use the same columns and the same terms, and put his own data in before he logs in for the first time. If his file calls something "delivery time", do not call it "lead time" in the system. Then the new system feels like his own work in a new place, with the customer names and figures he has known for years.

2. Showing everything at once

The temptation to show all the automations in the first training session is strong. Do not do it. Start with the basics, let him do it himself with an example of his own and repeat where needed. Too much too quickly is the fastest way to make someone give up. Train at his pace, even if that takes a few weeks longer than the supplier's schedule.

The two agreements you make in advance

The third failure point is more subtle. You give him a role as the expert, and that is good. But do not let the whole change rest on his shoulders. Otherwise your new system still runs on one person and you have rebuilt exactly the problem of the old Excel file. Make sure at least one other colleague also really knows how it works, so that questions do not end up with the same person again.

The fourth and fifth failure points belong together: there is no stop date and the old file stays open. Agree on a clear moment when the old file stops. Keep it as an archive, but no longer work in it. If you do not fix that date, you will still have two systems side by side after six months, and then Excel almost always wins, because it feels familiar. Put the date in the calendar as soon as the basics are in place.

If you see an Excel file as something that has to go, you turn your most experienced employee into an opponent. If you see it as recorded knowledge, you get a builder in return. So you do not take their Excel away. You put their knowledge in a place where the whole business benefits from it. Facing a switch like this? Lead Innovation helps business owners start with that knowledge instead of with the system.

Want to know more about monday.com?

The Lead Innovation team at work