Change Management: Getting Your Teams to Adopt Your New ERP

Why ERP projects rarely fail for technical reasons

An ERP changes how almost everyone in the company works, and that is precisely its value: information flows, steps chain together, controls apply. But what is progress for the company can be experienced as a loss by each individual. The warehouse keeper who managed "his" stock from memory becomes traceable; the assistant who mastered complex files sees her expertise become useless; the sales rep must enter quotes in a tool instead of his personal formatting; the chief accountant fears automation will shrink her role. None of these reactions is ill will: they are normal responses to a change that touches habits, status and sometimes the sense of competence.

Ignoring this human dimension always produces the same scenario: surface-level adoption during training, then a gradual return to the old tools at the first difficulty, until the ERP is used for nothing but invoicing. Conversely, companies that succeed in their digital transformation (Digital Transformation for Businesses in Morocco: Where to Begin) treat adoption as a workstream in its own right, on a par with data migration: with an owner, milestones and indicators. The good news: in an SME of ten to a hundred people, this workstream is light — a few well-made decisions are enough to tip the dynamic the right way.

• Resistance to change is a normal reaction, not ill will: it is managed, not decreed away.
• Each role experiences the change differently: lost autonomy here, fear of scrutiny there, fear of demotion elsewhere.
• The symptom of the adoption gap: parallel management — notebooks, unofficial spreadsheets, double entry "just to be safe".
• The cost is double: the ERP paid for and underused, plus the shadow management that keeps consuming time.
• Adoption is managed like data migration: an owner, milestones, indicators.

Involve users from the framing stage, not at training time

The most widespread mistake is choosing and configuring the ERP between the director and the vendor, then "presenting" the tool to the teams once everything is decided. Users then discover a system designed without them, some of whose screens contradict their daily reality — and their first reflex is legitimate: "whoever chose this doesn't know our work". The antidote is simple: involve one champion per domain very early — one for sales, one for stock, one for accounting. These champions attend the demos, test their domain's scenarios, flag the special cases (that customer invoiced in a specific way, that product family managed by weight) and naturally become the project's relays with their colleagues.

This champion role has a second virtue: it turns the people most exposed to the change into actors of the change. The assistant who mastered the Excel files is best placed to validate the data migration; the warehouse keeper who knows every corner of the depot is the best judge of the inventory screen. Their expertise, far from being devalued, is mobilised and recognised. During the framing of a Crystal ERP project (Crystal ERP), the CRYSTAL IT team systematically asks to meet these key users: their upstream remarks cost a few hours; the same remarks after go-live cost weeks of fixes and credibility.

• Appoint one champion per domain (sales, stock, accounting) as soon as the solution is chosen.
• Have real business scenarios tested during configuration, not after go-live.
• Collect the special cases early: they are what blocks adoption if discovered at go-live.
• Value the experts of the old system by entrusting them with the validation of the data migration.
• Communicate the why of the project to everyone, not just the schedule: what each person concretely gains.

Train usefully: by role, on real data, at the right time

The "everyone in a room for a day watching every function" training is a guaranteed recipe for forgetting: each person uses only 20% of the tool, but not the same 20%. Effective training is split by role: the sales rep learns quotes, orders and balance lookups; the warehouse keeper learns receipts, issues and stock counts; the accountant learns entries, reconciliations and returns. Each session is short — two to three hours —, focused on the daily gestures of the role, and run on the company's real data: finding "your" customer, redoing an invoice actually issued last week. Immediate recognition ("this is our catalogue, these are our customers") removes half the apprehension.

The calendar matters as much as the content: training three weeks before go-live evaporates; the ideal is to train each group a few days before its module goes live, then to schedule a consolidation session two to three weeks after, when the real questions have emerged. Finally, skill gaps must be accepted: in most Moroccan SMEs, some employees are very comfortable with digital tools and others have never used anything but a phone. Simple materials — one-page sheets per business gesture, in French and if needed in Arabic — and the ability to practise risk-free in a test environment do more for adoption than a two-hundred-page manual.

• Train by role and by module, in short sessions focused on the role's daily gestures.
• Use the company's real data: real customers, real products, real invoices.
• Schedule each training just before the module goes live, not weeks in advance.
• Plan a consolidation session two to three weeks after go-live, when the real questions exist.
• Provide one-page sheets per business gesture and a test environment where mistakes have no consequences.

Support after go-live: the six decisive weeks

Adoption is decided in the six weeks following go-live. That is when each user encounters their first unforeseen case, their first data-entry mistake, their first doubt — and it is the answer they receive at that moment that determines whether they persevere or return to their old tool. Three simple mechanisms make the difference. First, a single, responsive question channel: an internal chat group or a reachable champion, with the rule that every question gets an answer the same day. Second, a short weekly review between champions and management: what difficulties, what recurring questions, what configuration adjustments. Third, the fast correction of irritants: a mistranslated label, an unjustified mandatory field, a document template to fix — every irritant corrected within forty-eight hours signals that the tool adapts to the teams, not the other way round.

Measurement is also needed. Adoption is judged not by the mood but by a few simple indicators: number of quotes created in the ERP per sales rep, stock count discrepancies, delay between delivery and invoicing, share of automatically generated entries. If a department disengages — no entries for a week — the indicator shows it before parallel management sets in. A SaaS ERP like Crystal ERP makes this monitoring easy: CRYSTAL IA dashboards show activity by module in real time, and the Chat IA assistant lowers the learning load — asking a question in natural language is simpler than memorising a menu path (Crystal IA: artificial intelligence serving Moroccan businesses).

The director's role: leading by example, not by speech

In an SME, ERP adoption is the exact reflection of the director's behaviour. If the director asks for figures "like before" — an Excel table by email — the whole company understands that the ERP is optional. If the director opens the dashboard in meetings, asks "why isn't this order in the system?", refuses any figure that does not come from the tool, adoption becomes the norm within weeks. This exemplarity does not require the director to become an expert: consulting the dashboard and the outstanding balances is enough. It requires consistency, including — especially — in tense moments when the reflex of the old system resurfaces.

Three leadership mistakes doom otherwise well-run projects: officially tolerating dual management ("enter it in the ERP when you have time"), indefinitely postponing the shutdown of the old tools, and never mentioning the project after go-live — as if going live were the end of the story. Conversely, marking the milestones (first monthly close in the ERP, first stock count without significant discrepancy, first VAT return produced in an hour) sustains the momentum and makes progress visible. A deployment supported by a local vendor, available in French and Arabic and reachable in Rabat, secures the whole journey: one of the strengths of a partner like CRYSTAL IT compared with remotely deployed solutions (How to choose an ERP in Morocco: criteria, cost and mistakes to avoid).

• The director only accepts figures from the ERP: the most powerful signal of the whole project.
• Officially retire the old tools on an announced date — tolerated dual management kills adoption.
• Track a few usage indicators per department to detect disengagement before it takes hold.
• Celebrate the milestones: first close, first accurate stock count, first VAT return produced in an hour.
• Rely on a reachable local vendor, in French and Arabic, throughout the ramp-up.