QubicQubıc
Training · Distribution

Second implementation attempt — this time adoption at 94%.

60 employees · Split · 4 months

A distributor had already invested in a CRM that half the team wasn't using. The second attempt — with an approach focused on preparing people before rollout — delivered 94% active users in 4 months.

+100%

47%94%

Active users

Context

A distribution company from Split with 60 employees — distributing food products to the HoReCa sector (hotels, restaurants, catering). A year earlier they had invested significant funds in a new CRM that was meant to replace the Excel sheets and email that order processing had traditionally relied on.

After 6 months the situation was disappointing — only 47% of the team was using the system. The rest had reverted to the old way. The head of sales spent every week reminding colleagues about the importance of the system, but people kept going back to Excel.

The problem wasn't the system — it was well chosen, and half the team actually liked using it. The problem was how it had been introduced. During the first implementation cycle, training was the typical "demo + slides" format. On top of that: the team leads weren't involved in choosing the system — leadership made the decision and presented it to the team as a fait accompli.

What didn't work first

The first attempt — a year earlier, with another partner — was the classic playbook: system demo, slides, "here's how it works", mandatory training. Six months later half the team was back in Excel. The problem wasn't the system — it was that people hadn't been part of the choice and had no reason to trust it was for them.

Approach

We led with Training & Adaptation as the primary service, and Business Process Improvement as the secondary — combining two disciplines that usually run in parallel.

Pre-investment conversations — we started with one-on-one conversations with all 60 employees (run by a small team, focused conversations). Questions: what matters to you in your daily work, where do you lose the most time, what would upset you most if it changed. From those conversations we identified the real pain points and fears — without that, "training" is up in the air.

Training through real situations — instead of a system demo, we ran workshops around concrete clients from the HoReCa sector. "Here's a hotel ordering on Wednesday for the weekend — how does that flow through the system?" People learned through their real clients, not hypothetical scenarios.

Phased rollout — we didn't switch everything at once. We started with the 3 key order types that account for 70% of volume. Those went into the system in week one, the rest stayed in the old format. Only after 4 weeks, once people had mastered the basics, did we add the other types.

Local "ambassadors" — we identified 4 people who picked the system up faster and were happy to help colleagues. We reinforced them with extra training — they became the first point of contact for questions inside the team, faster than formal support.

Delivered

  • One-on-one conversations with the entire team to identify pain points and fears.
  • Workshops with concrete clients from the HoReCa sector, not demo presentations.
  • Phased rollout by order type — 70% of volume in the first month.
  • Internal "ambassador" network for peer support.
  • Adjustments to 2 system configurations based on real usage.

Result

  • 94% active users in 4 months — up from the previous 47%. Growth that didn't come through "forcing it", but through the system actually starting to serve people.
  • Order processing time dropped 65% — a consequence of the system being used correctly, plus a few smaller process tweaks we ran in parallel.
  • The most important outcome isn't a number: there was no resistance. People had a hand in the preparation and felt the system was tuned to their real work.
  • The head of sales no longer has to remind people every week to use the system — it's just not a topic of conversation anymore.

At a glance

  • 94%

    Active users (from 47%)

  • −65%

    Order processing time

  • 0

    Resistance at rollout

The first time, I thought the problem was the people. The second attempt convinced me it wasn't — it was how we rolled it out.
— Owner, distribution company

INTERFACE EXAMPLE

Training that sticks has structure, measurement, and adaptation — here's the LMS a team uses every week.

PLATFORM ILLUSTRATION · ANONYMIZED

What we learned

Adoption doesn't succeed because the tool is good. It succeeds because people consent — and consent comes from feeling they had a say in the choice and that the system is tuned to their real work. Technology is 20%, people 80%.

Client identity anonymized per contractual discretion. Numbers and context are accurate.