ERP Training: Building Role-Based Adoption That Actually Sticks

Why ERP Training Decides Whether Your Project Succeeds

Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, with low end-user adoption cited as a key risk factor. Industry analyses echo this: only about 23% of ERP implementations are considered successful, and roughly 56% of companies face user adoption resistance tied to inadequate training and communication.

The budget tells the story. Research summarized by ERP Focus found that 95% of companies whose ERP failed had dedicated less than 10% of total budget to education, training, and change management. Best practice pushes in the opposite direction: allocate roughly 15-20% of project budget to training and change management. Training and change are also a recurring TCO line item, not a one-time kickoff cost—underfunding them is one of the most reliable predictors of a stalled rollout.

The lever is real. Companies with continuous ERP training programs observe adoption rates around 73%, versus 34% for those doing only initial training. Training is not a line item to trim at the end of a project; it is the mechanism that converts a working system into business value. For SMEs on Dynamics 365 or Odoo, where IT teams are small and every end user matters, this is even more decisive.

Start With Role-Based Training, Not Generic Feature Tours

Role-based ERP training aligns system instruction with specific job responsibilities, decision rights, and accountability structures rather than generic functional overviews. It begins with role mapping: who owns which transaction, where segregation of duties applies, and what the upstream and downstream impacts of each role's work happen to be. Map daily job tasks to system paths first; only then write classroom content, job aids, and sandbox exercises.

Both platforms we implement are built around this idea, which makes role-based training natural rather than forced. Dynamics 365 Business Central uses Role Centers as the user's home page, tailored to each profile. Profiles (called Roles in the client UI) assign a Role Center; defaults include Business Manager, Accountant, Sales Order Processor, Purchasing Agent, and Warehouse WMS. Dynamics 365 Finance & Operations replaces the single Role Center with multiple activity-focused Workspaces layered on role-based security (Security Roles → Duties → Privileges → Permissions). Odoo's integrated suite lets users live in the same apps they sell, buy, and stock through—so training can focus on each team's workflow rather than re-teaching navigation per module.

The practical pattern: map your real roles to platform profiles, then build a curriculum per profile. An Accounts Payable clerk, a Warehouse WMS user, and a Sales Order Processor each get a different learning path, different sandbox exercises, and different success metrics. Generic everyone-learns-everything sessions are the single biggest waste of training budget and the fastest route to low adoption. Use a role matrix so every learner knows which transactions they own, which practice scenarios prove readiness, and which super user backs them on the floor.

Training Alone Fails Under Pressure: Redesign Daily Habits

Classroom skill is not the same as behavior under load. Panorama Consulting's behavioral change work puts it bluntly: the biggest barrier to ERP adoption is habit. Under pressure, users default to what they already know—spreadsheets, paper travelers, shadow systems—even when they passed every sandbox exercise. Most post-go-live failures come down to habit, not missing clicks. Lasting change rewires routines; it does not stop at webinars.

Treat old habits as structural risk during design, not as a soft people issue after go-live. Map the daily behaviors that must shift (for example, grabbing a handheld scanner instead of a clipboard, or approving inside the ERP instead of emailing a PDF). Anchor new habits in triggers: Monday dashboard prompts, manager floor-walk checklists, decommissioned legacy shortcuts, and embedded job aids at the moment of work. Disrupt the old loop, replace it with a simpler or more rewarding path, and reinforce until the new path is the default.

This is why super users and floor-walking matter more than another slide deck. Super users sit inside the habit loop: they coach at the elbow when stress spikes, intercept workarounds before they become permanent, and turn every ticket into a coaching moment. Pair habit design with your ERP change management plan and hypercare window so training, reinforcement, and support are one system—not three disconnected workstreams.

• →Document critical habits (not only critical processes) in process design workshops before content build.
• →Install cues in the daily routine: role-home dashboards, approval queues, barcode first-scan steps, close checklists.
• →Remove easy exits to legacy tools on a planned schedule so the new path is the path of least resistance.
• →Measure behavioral progress: % of transactions on intended digital flows vs workarounds, not login counts alone.

Apply the 70/20/10 Model to ERP Learning

The 70/20/10 model, originated by Morgan McCall, Michael Lombardo, and Robert Eichinger at the Center for Creative Leadership in the 1980s and referenced in The Career Architect Development Planner (1996), describes development as roughly 70% challenging on-the-job experiences, 20% developmental relationships, and 10% coursework and training. CCL is explicit that this is a heuristic guideline, not a strict empirical ratio.

For ERP, that ratio is useful precisely because it warns against over-investing in slides. Applied to a Dynamics 365 or Odoo rollout: formal courses (Microsoft Learn, Odoo Learn, partner workshops) are the 10% foundation; super-user coaching, peer floor support, and community are the 20%; sandbox and live transaction practice are the 70% that builds true proficiency.

Because the model holds that roughly 70% of professional development occurs through challenging on-the-job experience, a sandbox and a strong super-user network will reliably beat another day of classroom time. The 10% formal layer is the foundation, not the building.

• →10% formal foundation: structured courses, certifications, and live instruction. For Dynamics 365, Microsoft Learn is the free, self-paced backbone, organized by product (Business Central, Finance, Supply Chain Management), role, and level, aligned to certifications such as Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate. For Odoo, Odoo Learn (odoo.com/slides) is the free official hub with timed, structured courses per functional area.
• →20% social and coaching: peer support, mentoring, super-user shadowing, and community. The Dynamics 365 Community (community.dynamics.com) and Odoo's partner and user networks are the platform-native layers here.
• →70% experiential: hands-on practice in a sandbox or copy of production. The same principle holds across D365 and Odoo; the majority of real proficiency is built by doing real transactions in a safe environment.

Choose Delivery Methods That Match SME Reality

There is no single right delivery method; there is the right mix for your teams, geography, and budget. The common options for ERP training are online training (virtual classrooms, LMS, simulations), in-person workshops, on-the-job and floor training, and custom role-based modules aligned to specific workflows.

Instructor-led training (ILT) is effective for complex topics, hands-on practice, and competency verification, but it has low scalability and high cost. Virtual instructor-led training (VILT) delivers live instruction via web conferencing for distributed teams at lower cost. Microlearning delivers short, task-focused, bite-sized modules that enable on-demand access, immediate application, and higher retention through repetition. Floor training and at-the-elbow coaching convert remote theory into muscle memory during UAT and hypercare.

Hybrid delivery wins on outcomes. Organizations using progressive, role-adapted ERP training models (spread over 8-12 weeks in sessions of at most two hours) have observed roughly a 35% reduction in post-training support requests and a 28% improvement in user performance indicators at six months. Hybrid methods have also achieved about 89% completion rates, versus 67% for face-to-face only. Industry guidance for 2026 also stresses continuous learning after go-live—role-based refreshers, in-module help, and champion networks—not a single pre-launch event. For a Canadian or UK SME rolling out Business Central across a small finance team and a distributed sales team, a hybrid of VILT plus on-demand microlearning plus sandbox practice plus super-user floor walks is usually the right starting mix.

Build a Train-the-Trainer and Super-User Program

External consultants leave. Internal capability has to stay. A train-the-trainer (TTT) approach designates and deeply trains key internal personnel (often one per team or function) who then train and support end users, providing ongoing internal knowledge transfer after external resources depart.

An ERP super user (sometimes called a power or key user) is a business-side expert who acts as mentor, first-line support, liaison to IT, and trainer for peers within their functional area. Subject matter experts (SMEs) are involved throughout the project: providing deep process knowledge during design and configuration, supporting testing and training material accuracy, delivering end-user training, and serving as ongoing resources for their teams. Panorama's super-user guidance is consistent with what works in the field: designate one per functional area, host peer workshops, train super users before they train others, document their insights, and publicly reward the role so it is not invisible unpaid overtime.

Two practical notes on selection. First, power users in TTT programs receive significantly more intensive training than end users, covering advanced features, system architecture, and troubleshooting, plus adult learning principles, facilitation, and documentation. Second, not every technically strong person makes an effective trainer; selection should weigh patience, empathy, and communication as heavily as system skill.

Scale matters. More than 70% of SAP-running companies create a formal super-user program. Recommended ratios start at roughly 1 super user per 20-40 end users right after go-live, mature to 1:40-60, and eventually reach 1:60-100 as users rely more on self-help. 2026 implementation guidance also stresses department champions who receive advanced training and provide peer support—practitioners often report material reductions in helpdesk volume when champions are real, named, and time-protected. For an SME, even a single strong super user per function (finance, warehouse, sales) is the difference between a self-sustaining system and one that calls the partner for every question.

• →Map every affected function to at least one named super user before go-live.
• →Give super users 2-3x the training depth of end users, including configuration rationale, not just clicks.
• →Protect a percentage of their time post-go-live for support, floor-walking, and material updates.
• →Measure super-user effectiveness by their team's adoption and ticket volume, not by their own activity.

Budget Training as a Real TCO Line Item

Most ERP cost models count licenses and SI hours and undercount the cost of taking people offline to learn. Training TCO is not only partner invoices. It is partner delivery + internal super-user time + end-user hours away from the desk + material build + post-go-live refreshers + new-hire onboarding for every turnover year after year.

A practical planning formula SMEs can put in the business case: (end-user headcount × role-hours of formal training × fully loaded hourly rate) + (super-user headcount × enablement hours × rate) + partner training fees + content/LMS build. Industry ranges vary by scope, but training and change management commonly land at about 10-20% of implementation budget when done properly, with external training programs often quoted in broad bands from a few thousand dollars for tiny teams to tens of thousands for company-wide role-based enablement. Per-employee practical training packages are frequently estimated in the hundreds to low thousands of dollars when you include role-based sessions, documentation, and ongoing support—not just a one-day webinar.

Two budget mistakes to avoid. First, treating training as optional contingency that gets cut when data migration overruns. Second, forgetting productivity dip after go-live: almost every ERP sees a temporary slowdown, and the recovery curve is steeper when role practice and super-user coverage were funded. Put the hours × rate × headcount line next to software and services so sponsors see training as value protection, not nice-to-have.

Get the Timeline Right: Build Early, Deliver Late

A common mistake is to treat training as a go-live-week activity. Comprehensive ERP training content development typically spans months before go-live, because good content depends on finalized processes, configured systems, and tested scenarios. Hands-on workshops are often most effective when delivered in the final 4-6 weeks before deployment so users build confidence close to real work, while super users should be enabled earlier so they can support UAT and peer delivery.

Actual end-user classroom intensity should stay close to go-live—commonly within about three weeks for the final role-based waves—to maximize retention, while still leaving enough runway for practice pass rates and access readiness checks. Layered on top is the post-go-live stabilization curve. Industry guidance is that almost every ERP implementation experiences a temporary but significant productivity decline immediately after go-live, with slower order processing and longer financial closes, and that with the right support most businesses return to baseline within roughly 60-90 days. Academic research on ERP firm-performance effects (Nicolaou, 2004) documents that the payoff is not immediate: short-term performance effects around implementation can be neutral or negative, with positive returns materializing only as users gain proficiency.

Sequence against UAT and go-live: certify super users before UAT; use UAT as live practice for end users; run final role waves after configuration freezes; staff hypercare with the same people who trained the floor. A 30/60/90 change plan works well here—role mapping and materials in the first month, delivery and readiness checks in the second, go-live coaching and adoption dashboards in the third.

That post-go-live window is detailed in our ERP hypercare guide, but from a training perspective the key point is that hypercare and training are the same activity viewed from two angles: every ticket is a coaching opportunity, and every coaching session prevents future tickets.

1. 01
   Months 1-3: Process design and role mapping

   Finalize to-be processes, confirm role list, draft role-based learning objectives, and map critical habits to redesign. SMEs and super users are named here.

2. 02
   Months 4-5: Content build and super-user enablement

   Build role-based materials, sandbox exercises, and quick-reference guides. Certify super users with deeper training before they train peers or coach UAT.

3. 03
   UAT window: Practice under real scenarios

   Treat UAT as graded practice, not only defect hunting. Confirm access, credentials, and practice pass rates by role before go-live waves.

4. 04
   Final 3-6 weeks: End-user delivery

   Run role-based sessions as close to go-live as possible. Prioritize hands-on practice over slides; cap sessions at two hours; schedule floor coverage for cutover.

5. 05
   Days 1-30: Stabilization coaching

   Daily triage, on-floor super-user presence, and just-in-time microlearning on the issues actually surfacing in tickets.

6. 06
   Days 31-90: Optimization and habit formation

   Process walkthroughs, role-specific refreshers, and adoption measurement. Most teams return to baseline productivity in this window when habits stick.

Measure Adoption With the Kirkpatrick Model

Without measurement, training is an article of faith. The Kirkpatrick Model, popularized by Donald Kirkpatrick from his 1959 articles, is the world's most widely used framework for evaluating training impact across four levels: Reaction, Learning, Behavior, and Results.

Level 1 (Reaction) measures whether participants find training favorable, engaging, and relevant. Level 2 (Learning) measures the knowledge, skills, and confidence acquired. Level 3 (Behavior) measures on-the-job application, commonly assessed two to four weeks to three to six months after training. Level 4 (Results) measures targeted outcomes such as productivity, quality, costs, and error reduction. Most ERP programs stop at Level 1; the value is in Levels 3 and 4.

For ERP specifically, login frequency alone can be misleading. More meaningful adoption indicators focus on correct and efficient usage, transaction success rates, error rates per transaction, time saved per task, and the number of manual, correcting, or exception transactions. Helpdesk and support ticket volumes in the first 90 days post-go-live, measured per user and by theme, are key indicators of training and adoption gaps; high ticket volumes often signal competency issues rather than technical bugs. Add behavioral signals from habit redesign: share of work completed on intended digital flows versus legacy workarounds.

Pair Kirkpatrick with the ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement), which Prosci applies explicitly to ERP implementations, and which we cover in depth in our ERP change management guide. Prosci's research indicates projects with excellent change management are up to 7x more likely to achieve change success, which is why training and change management are inseparable rather than parallel workstreams.

Dynamics 365 and Odoo: Platform-Specific Training Playbooks

Because we implement both platforms and stay neutral, here is how the same principles land on each.

• →Dynamics 365: Use Microsoft Learn as the official content backbone, organized by product, role, and level, and align certifications to roles (for example, Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate). Reinforce training with in-product Role Centers and Profiles in Business Central, and Workspaces plus role-based security in Finance & Operations. Plan for bi-annual release waves: interface and feature changes need material updates; pure performance fixes usually do not. The role-tailored UI itself becomes the 70% experiential layer when users practice in a sandbox with their real permissions—not admin access.
• →Odoo: Use Odoo Learn (odoo.com/slides) as the free, structured content backbone per functional area (Getting Started, CRM, Accounting, Inventory, MRP). Layer in the built-in Odoo eLearning app to create internal, company-specific courses with videos, quizzes, prerequisites, and certifications. Certify key users via versioned Odoo Functional Certification (e.g., Odoo 19 Functional Certification) as your SME and super-user mechanism, and use in-person Odoo Academy events for hands-on depth where geography allows.
• →Cross-platform: Whichever platform you choose, the curriculum skeleton is the same: role map, build role-based paths, run hybrid delivery close to go-live, certify super users, redesign habits under pressure, and measure to Level 3 and 4. The difference is which free official content and which certification you anchor to.

Frequently asked questions