Skip to content

Change, adoption and training

Go-lives changes the technology,
Only Adoption changed the business.

Nothing is broken. The data loaded, the reports run, and yet the spreadsheet is still open, the approval still arrives by email and two sites are running two different processes. That gap between going live and actually working differently is where most of the value of a project is won or quietly lost.

How this works

Dynamics 365, Business Central and Power Platform, for the people who have to use them.

Sound familiar?

Nobody says they are refusing to use it.

They just keep doing the bit that matters somewhere else. None of this means people are difficult. It usually means the new way is harder than the old one, or nobody explained why it changed.

Before calling users resistant, it is worth asking whether the process actually works, whether the data can be trusted, and whether anybody told them the reason.

  • The spreadsheet never went away

    People finish the job outside the system because that is still the quicker route.

  • Everyone was trained. Nobody feels ready

    A session two weeks before go-live, on a process that changed again afterwards.

  • One team is flying, another has stalled

    Same rollout, same material, completely different working day.

  • Managers are still asking for the old report

    If leaders do not use the new controls, nobody below them will either.

  • Nobody agrees what the process now is

    So each site quietly invented its own version of it.

  • Support keeps answering the same question

    That is not a ticket problem. It is a knowledge gap with a queue in front of it.

How this works

Start when the process is designed, not two weeks before go-live.

The sequence matters more than the material. People need to know what is changing, have a say in it, practise it, and then find help close by in the first week of real work.

  1. Work out what actually changes: Process by process, role by role. Not a slide saying everything is changing.
  2. Get leaders and process owners committed: Before anyone asks users to work differently. Users notice what leaders tolerate.
  3. Involve real users early: At design playback and process validation, not for the first time at training.
  4. Train on the job, not the menus: Real scenarios for their role, including the day it goes wrong.
  5. Let people practise: A safe environment with realistic data, so first attempts are not made on live work.
  6. Check readiness honestly: Business readiness is a separate question from whether the software can be deployed.
  7. Stay close in week one: Help near the work, correcting the process while habits are still forming.
  8. Watch the process, then act: Workarounds and support demand tell you what to fix, retrain or redesign.

Evidence

Customers describing their own projects.

The strongest evidence of how we work comes from the organisations we work with.

80%

of our business comes from existing customers and referrals.

All customer stories

The best I’ve ever experienced in over 20 years of collaboration.

Programme Manager, Hill & Smith Plc

RAPID Learning Portal

Training should create capability, not attendance.

Go-live does not prove adoption. Implementation training should not consist only of workshops delivered before go-live, so we provide a structured learning environment users can return to, while giving appropriate management stakeholders visibility of learning progress and assessment information.

Learning does not end at go-live.

One structured journey, in two phases.

1

Implementation

  1. Learn
  2. Workshop
  3. Practise
  4. Assess
  5. Reinforce
  6. Readiness
2

Live service

  1. Self-learning
  2. Refresher learning
  3. New starters
  4. Support knowledge
  5. Continued assessment

Management visibility of learning progress and assessment information, across both phases where the portal supports it.

  1. Training
  2. Capability
  3. Adoption
  4. Continued learning
Explore RAPID Learning Portal

Across the methodology

Learning runs through delivery, not beside it.

Where the portal is used, it operates across the stages of our hybrid implementation methodology rather than appearing as a training week near the end.

  1. Understand

    Early process learning, before design decisions harden.

  2. Design and playback

    Users build an understanding of the future processes.

  3. CRP

    Learning against representative end-to-end processes.

  4. Prepare

    Structured role and process learning for the people who will work in the system.

  5. Assess

    Check understanding rather than record attendance.

  6. Go live

    Learning available at the point of need, while real work is happening.

  7. Stabilise

    Reinforce the areas where difficulty is actually showing.

  8. Support

    Continued self-learning and refresher content.

Four honest checks

Readiness is a decision, not a percentage.

At four points we stop and ask whether the organisation is genuinely ready for the next step. Each one has an outcome that includes slowing down, because that is sometimes the right answer.

What is changing, and who owns it
Gate 1Before capability work begins

What is changing, and who owns it

You cannot prepare people until it is clear which processes change and who makes the decisions when two areas disagree.

Confirmed at this gate

  • The outcome wanted, and the behaviour it depends on
  • Which processes change, and how materially
  • Affected roles, sites, shifts and working patterns
  • A named sponsor and named process owners
  • What happens to the old routes

Decision

  • Proceed
  • Clarify process
  • Resolve ownership
  • Re-scope

Swipe, drag or use the arrow keys to move between decisions.

Where do you stand?

Two minutes, and an honest view of what to do first.

Answer a few questions about your situation and we will tell you whether this looks like training, process, platform or something that needs a harder conversation.

Question 1 of 5

0 of 5 answered

1. What is the current situation?

Select one option.

Before you call

The questions leaders ask us first.

A conversation, not a pitch

Tell us what people are still doing the old way.

The team still in spreadsheets, the approval that never left email, the site running its own version of the process. Start there and we will tell you what we would look at first.

See customer stories