Introducing a new system? Start with what frustrates your team
If you want a new system to stick, start with what frustrates your team. At the kick-off, everyone still nods enthusiastically. Three weeks later, half the team is quietly retyping everything into the old Excel sheet again.
When a new system is launched, almost everyone is positive. That enthusiasm usually disappears in the first few weeks, at the moment people first see the extra work. They have to learn new things, enter data and get used to a different way of working. That takes time, and that time comes out of the normal work that still has to get done. What they get in return, they cannot yet see in those first weeks.
If they don't notice quickly that it delivers something, they fall back on what they know. That isn't unwillingness. It is logical behaviour. The old way works, even if it is cumbersome, and for now the new way only costs effort. As a business owner, you then see a system you have paid for that stays half-filled, with colleagues who still work alongside it.
The usual reaction is to explain once more why it matters. Another presentation, another email listing the benefits. That rarely helps, because the problem isn't understanding. Your team understands perfectly well why you want this. They just don't feel it in their own working day yet. And you need to sort out that feeling within a few weeks, or you lose it.
Your priority is not their priority
Most business owners start with the process that matters most to them. The reporting, the margin overview, the figures for the monthly meeting. Understandable, because that is why you bought the system. But your team notices none of that in the first few weeks. They do the data entry, you get the overview.
Turn it around. Start with what frustrates your team. The process they grumble about every week, where they have to chase colleagues by phone or type the same thing twice. Fix something there and they notice it themselves straight away. That is more convincing than any presentation you could give.
How do you find out where that frustration lies? Not by sending round a survey. That gets you socially desirable answers or nothing at all. Spend an afternoon shadowing someone, or simply ask over coffee: what did you lose the most time on this week that was really about nothing? Often you hear the same answer three times within ten minutes. Searching for the latest version of a document. Phoning round to check whether something has already been ordered. Retyping a customer address from an email. Those are your candidates.
A frustration that has been resolved does more for buy-in than ten good arguments.
Choose one improvement that everyone can see. For example: a signed quote automatically goes back to the delivery team, without anyone having to forward it. Or the weekly status meeting is no longer needed, because everyone can see where things stand on their own screen. One thing that is clearly different works much better than ten small improvements that hardly stand out. Small gains disappear in the noise of a busy week. A meeting that disappears from the calendar gets noticed by everyone.
Do make sure that first improvement is achievable within a few weeks. A frustration that is only resolved after three months and an integration with the accounting system is not a good starting point. Your team would be stuck with the extra work all that time, with no reward yet. Better to choose something smaller that lands quickly, and save the big job for when the system is already in use. At this stage, momentum matters more than perfection.
Without a baseline, it stays a feeling
Before you change anything, measure how things are going now. How long does it take for a signed quote to reach the delivery team? How often per week does someone have to check something with a colleague? How much time goes into retyping from one list to another? It doesn't have to be a study. Keeping a tally on a piece of paper for a week is enough. Without that baseline, you can't show in four weeks' time what has improved, and it stays a feeling that everyone has their own opinion about.
Build less than you want to
The temptation to set everything up properly straight away is strong. Every field you might ever need, every automation that seems handy. But the more you put in at the start, the greater the chance that people drop out. Start simple. Only add something once the basic process is being used. Used, that is, not just set up. You only really see that difference after a few weeks.
The fifteen minutes that make the difference
Then show the progress every week. A short, fixed slot of no more than fifteen minutes. Two questions: what went better, and what still didn't work well? Nothing more is needed. The fixed rhythm keeps the improvement visible, even in the weeks when it's busy and nobody is thinking about the system.
Let colleagues tell it themselves. When someone from the team says "I no longer have to phone round to ask about things", that is far more convincing than yet another chart from management. Colleagues believe each other sooner than they believe their manager. You are there to listen and take notes.
And use what is said in those fifteen minutes. If something doesn't work, adjust it straight away, preferably that same week. That way the team feels it is their system and not something imposed on them. That sense of ownership is ultimately what ensures nobody falls back on the old Excel sheet after two months. A team that sees its complaints lead to something within a week will naturally report more complaints. And every complaint resolved is another reason to use the system.
You don't keep enthusiasm alive with a good kick-off. You do it by showing every week that the work is getting easier. Start with what frustrates your team, measure how things are now, choose one visible improvement, keep the setup simple and take fifteen minutes every week to let the team speak for itself. After a few weeks, you will have no more convincing to do. Your team does it for you.