Digital culture: why your team does not use what you bought

If you bought a tool and the team still works the same way, the tool is not the problem. Nobody changed the process, the training or what gets rewarded.

Digital culture is not an awareness workshop or a motivational talk. It is people working differently every day, and that is achieved through far more concrete things.

Why does the team not adopt new tools?

Almost always for one of these five reasons, and none of them is “resistance to change”:

Real reason	How it looks	What fixes it
It adds work instead of removing it	”Now I do the old thing and log it too”	Remove the old step, do not add a new one
They do not know how to use it	They use 10% of the features	Training on their case, not a manual
They see no benefit	They use it when supervised	Show them what they personally gain
They are still measured on the old thing	They prioritise what they are judged on	Change the indicator
Nobody uses it at the top	The boss asks for the report on WhatsApp	Have management use it first

The last is decisive. If the manager asks for the numbers through another channel, the new system is dead however many training sessions you run.

Where do you start?

With a small group, one process, and one number.

1. Pick a process that hurts. One where the team already complains about wasted time. That way the tool arrives as relief, not as an imposition.
2. Measure where it stands today. How long it takes, how many errors, how many people it touches.
3. Pilot with three or four people, including at least one sceptic. The sceptic is the one who tells you the truth.
4. Explicitly remove the old step. If both coexist, the old one wins.
5. Show everyone the result, with the before and after numbers.
6. Only then, roll out.

Step four is the most forgotten and the one that kills the most projects.

How do you actually train the team?

Not with a recorded course nobody finishes. What works:

• On each person’s own case, not with generic examples.
• In short, repeated sessions, not an eight-hour day.
• With someone to ask when they get stuck, which is when learning really happens.
• With someone from the team itself as the reference point, not only the vendor.

That internal figure, the person others go to with questions, is worth more than any training plan. Identify them and give them time to do it.

And with artificial intelligence?

Everything above applies, and two things are specific to AI:

Fear of replacement. It is real, and if it is not discussed it turns into quiet sabotage. The honest conversation is about which tasks change, not promises that nothing will.

Shadow usage. Many people are already using AI tools on their own, sometimes pasting company information into personal accounts. Banning it does not stop it, it hides it. Better to provide approved tools and clear rules about what can and cannot be pasted.

How do you know it is working?

Not by attendance at training. By these four signals:

• Usage holds without anyone pushing, three months later.
• Someone proposes an improvement that was not in the plan.
• The old process disappeared, rather than coexisting.
• The number you measured at the start improved.

If after three months usage only holds because someone demands it, adoption did not happen.

Frequently asked questions

What is digital culture in a company? People working differently with the support of digital tools, sustainably. It is not a talk or a workshop: it is measured by whether the process changed and whether the change holds without supervision.

Why does the team not use the CRM we bought? Most commonly because it adds work instead of removing it, because the previous process was never eliminated, or because management still asks for the information through another channel.

How long does it take to change how a team works? A small pilot shows signals in two or three months. Sustained change without pushing usually takes six months to a year.

Do we need to hire someone external? Not always. It helps when experience with this kind of project is missing or when the team is too close to the problem. What never works is delegating adoption to the vendor.

What if someone openly resists? Listen before labelling them. In my experience, someone resisting with arguments is usually seeing a real problem in the process that nobody else voiced.

How do I handle the team using AI on their own? By providing approved tools and clear rules about what information may be used. Banning it does not stop it: it makes it invisible and riskier.

Where do I start if the company is small? With the process where the most time is lost, with two or three people and a number measured before you begin. Never by changing everything at once.