After go-live.Make the use stick.

We check the change has landed, and fix what has not.

You may be here if

Pick the line that sounds like your project.

  • Spreadsheets and paper are back beside the new system.
  • Support has no end date, and the project team still runs it by hand.
  • Nobody is checking whether the system is used, or by whom.

What we do

After go-live

Five jobs, done against what your people actually do.

  • Measure real useUsage against baseline at 30, 60 and 90 days, by role.
  • Close the workaroundsA register of spreadsheets and paper fallbacks, each with a fix, owner and date.
  • Fix the learningWe update guides and refreshers from what we find.
  • Cover new startersAn onboarding path and release briefings, with an owner.
  • Prove the benefitsA report for your benefits owner and your post-implementation review.

What you receive

Plain English, with no technical jargon. Everything is handed over to a named owner in your business.

  • Usage against baseline at 30, 60 and 90 days, by role
  • A register of workarounds, each with a fix, owner and date
  • Updated guides and refreshers
  • An onboarding path and release briefings for new starters
  • A report for your benefits owner and your post-implementation review
  • Everything handed to a named owner in your business

What we delivered

An NHS mental health trust: SystmOne

Problem

Clinical psychologists were refusing to complete outcome appointments in SystmOne.

What we did

Ran the full cycle from analysis to evaluation. Used communication psychology to diagnose the resistance, found five root causes backed by eight regulatory sources, built e-learning with the clinical lead checking accuracy, and kept scope under a three-tier change control process.

Result

Clinical psychology stakeholders endorsed the method, and a second phase was commissioned on the results.

More detail

A plan, the questions buyers ask, and the method behind it. Open what you need.

An illustrative plan
30, 60 and 90 daysUsage against baseline, by role.
As we find themA register of spreadsheets and paper fallbacks, each with a fix, an owner and a date.
At handoverAn onboarding path and release briefings for new starters, with an owner, and a report for your benefits owner and post-implementation review.

What you get

  • Usage against baseline, by role.
  • A register of workarounds, each with a fix, owner and date.
  • Updated guides and refreshers.
  • A report for your benefits owner.

What we need from you

  • Access to usage data, or to the live system.
  • Two or three people per role who do the real job.
  • A sponsor with the authority to act on what we find.
  • A named owner for each workaround.

What it is not

We do not configure or fix your systems. We log what we find and hand it to the owner. Whether it gets fixed is your programme’s decision.

What a programme lead asks

Isn’t this already in my implementation partner’s scope?

It may be, and we do not duplicate it. Partner work tends to cover the system as designed. We check whether your people can do their jobs in the system as configured, independently of whoever built it.

Do you configure or fix the systems?

No. We log configuration gaps and hand them to the owner. Our work follows the configuration you have.

Who does the work?

A small team of qualified practitioners with a named lead, who stays the same from the first check to handover. The lead has over 20 years across regulated UK sectors.

How is it priced?

Fixed price or time-based, quoted against your scope. The figure is agreed before work starts.

What if the date moves?

We re-plan with you. The plan follows your go-live date, not ours.

The method behind it

Two published models, used together. We say why we chose each over its alternatives, and where the choice is our own judgement.

How we sequence the work: ADDIE

Analysis, Design, Development, Implementation, Evaluation. Florida State University’s Center for Educational Technology developed it in 1975, working with the US military. Source: Wikipedia: ADDIE model

Alternatives. Dick and Carey, the Kemp model, rapid prototyping.

Why ADDIE. Each phase ends in a deliverable that a named owner in your business can sign off. Programme boards ask for that.

The cost. The original model finishes each phase before the next starts, which is slower than rapid prototyping. That is the price of a sign-off at every phase.

How we sequence the change for people: ADKAR

Awareness, Desire, Knowledge, Ability, Reinforcement. Jeff Hiatt of Prosci developed it from research between 1994 and 2002 across more than 700 organisations. It is a model for individual-level change. Source: Knowledge Train: the ADKAR model

Alternatives. Lewin, Kotter, Kübler-Ross, Satir and Senge. Kotter’s model works at organisation level.

Why ADKAR. It names Reinforcement as its own step, which is the work that keeps a change in place after go-live.

What is our judgement, not a finding

Using the two together is our judgement. We have not tested the pairing against outcomes, or against the alternatives. Treat it as a hypothesis. What we can show is what we delivered.

Sources

Start here

Three ways to buy. Each starts with a scoped proposal.

Talk to us directly

Tell us what is going live and when. Start with a fixed-scope readiness check, or go straight to the full programme.

Tell us what is going live

Buy through G-Cloud 15

Experienced Training Ltd is a G-Cloud 15 supplier (Lot 3). Our G-Cloud 15 service is Microsoft 365 Copilot training and adoption. For other work, contract with us directly.

For bid evaluators
  1. You tell us what is going live and when.
  2. We send a scoped proposal.
  3. You decide. Nothing starts until the scope is agreed in writing.

What is going live?

Tell us the system, the date and what is in the way. Get a scoped proposal. UK-wide and remote.

Email

chrisw@experiencedtraining.co.uk

Phone

Based in

Barnsley, South Yorkshire

Where is the programme?

How we use your details: Privacy policy.