The real reason new software doesn't get adopted (it's not training)

When a new system doesn't get used, the default diagnosis is almost always "we need more training." Sometimes that's true. More often, the team understood the software perfectly well and simply found it slower or more awkward than what they were already doing — and reverted, quietly, back to the old way.

Why training rarely fixes adoption

Training addresses whether people know how to use a system. It doesn't address whether using it is actually easier than the alternative they already have. If the old spreadsheet or the old WhatsApp habit is genuinely faster for a given task, more training on the new system won't change that calculation — people will keep choosing the faster option, regardless of which one they were told to use.

What actually drives adoption

The new way has to be faster or clearly better for the person doing the task, not just better for the business overall in the abstract. A system that makes reporting easier for management but harder for the person entering data will struggle, because the person bearing the extra effort isn't the one getting the benefit.

A more useful question than "did we train enough"

Ask the team directly: is this actually quicker than what you were doing before, for the specific task you do most often? If the honest answer is no, that's the adoption problem — and no amount of additional training resolves a system that's genuinely slower for the person using it daily.