In most of the rollouts I've worked on, the implementation plan finishes at go-live. The gap that opens up next — between the tool being live and your team actually using it every day — is called the adoption gap.
What's sitting in that gap is a people and change management question, not a technology one. The ROI your organisation is expecting only arrives once your team is using the new system, process or tool the way it was designed to be used.
Projects are far more likely to meet their objectives when people are supported to understand, adopt and use the change. Prosci's benchmarking research found that 88% of projects with excellent change management met or exceeded their objectives, compared with 13% where change management was poor — a difference of roughly six to seven times.
Here's what strong adoption looks like in the day-to-day work that follows go-live:
Your rollout gains momentum when you stay connected to your team after go-live — paying attention to their experience of the change.
Indeed's 2026 AU Jobs & Hiring Trends Report found the same pattern nationally: 32% of Australian workers now use AI multiple times a week, and an equal 32% have disengaged from it entirely. That leaves 36% of the workforce still deciding — not locked into either camp, and still open to influence. The Prosci figures above and this split are telling the same story: change management, not the tool itself, decides who ends up using AI well. This course teaches that methodology, mapped out in the framework below — bringing both the 36% still deciding and the 32% who've disengaged into real, daily adoption.
This course teaches you change management — the practical skill that closes the adoption gap between go-live and daily use.
Many AI projects begin with a capable tool, a committed vendor and a clear business case. The results depend on what happens next: how well the organisation helps people understand the change, see its relevance and build it into their work.
MIT research published in 2025 found that 95% of enterprise generative AI pilots delivered no measurable impact on the bottom line. The opportunity sits in how organisations integrate the tools into real work, not simply in making the tools available.
This is where communication, training and day-to-day leadership matter. David Rock's SCARF model describes five social needs people continually look for at work:
- Status — am I still valued here?
- Certainty — can I see what is coming?
- Autonomy — do I have a say in this?
- Relatedness — do I still belong in this team?
- Fairness — is this being handled fairly?
An AI announcement can raise questions across several of these areas before anyone has opened a demo link.
A change to someone's role or way of working may feel highly personal, and that sense of threat can narrow attention and make it harder to take in new information.
The practical leadership task is to create enough clarity, involvement and support for people to stay open to learning — this is good change management.
When you reduce the social threat around a change, you create more capacity for people to engage, practise and adapt.
It isn't resistance — it's status, certainty, autonomy, relatedness or fairness feeling under threat. Address that, and people stay open to the change.
"We've done technology change before — ERP, cloud, remote working tools. We know how this goes."
Usually that would be true. This time the territory is different.
Previous technology change replaced administrative and manual tasks — things people were largely glad to hand off. AI moves into different territory, because it can potentially take on:
- writing first drafts, editing, and refining content
- researching topics and synthesising findings
- analysing data and identifying patterns
- generating advice, options, and recommendations
- building presentations, proposals, and reports
- preparing for meetings and client conversations
- creating ideas and solving problems
- designing training content and learning materials
- reviewing and summarising documents
These are not peripheral tasks. For many people these are the job itself — skills they spent years building, and the thing that defines them professionally and justifies their place in the team.
When AI can do the drafting, what does it mean to be the drafter? What does it mean to be the analyst when AI can run the analysis? That question surfaces in your team whether you name it or not — as silence, resistance, or performative use where people appear to engage while changing nothing.
Here's what the research actually shows: AI is not replacing people — it's changing what people are asked to do. The World Economic Forum's Future of Jobs research projects that AI will create more roles than it displaces. What is happening is a shift in what expertise looks like — and that shift needs managing, not ignoring.
Here's a rollout pattern you've probably seen — or run:
There's a name for this: the tool reveal. It gets the announcement done, and it skips every condition that actually makes adoption happen.
A demo shows people what's possible. It doesn't give them:
- A reason tied to their own workload
- Time to practise on real tasks
- Permission to be clumsy with it at first
Without those three things, watching a tool work is not the same as using it.
- One meeting in the calendar
- A room full of people watching, no one doing
- The assumption that seeing it work means wanting to use it
- A reason tied to their own workload, not a use case in general
- Time to practise on a real task, not a demo script
- Permission to be clumsy with it before they're expected to be fast
We’ll get to those conditions properly in the framework ahead — first, what do you think the core assumption was?
Everything in this course maps to the 5-step change methodology I've built across 20 years of change practice and more than 50 technology projects. It's the framework behind Change Made Simple's free AI tools and consulting, and it runs in sequence — each step creates the conditions for the next. Click each step to see what it involves.
Hold workshops with each executive team member and the project sponsor to find out:
- What they expect from the project
- Their key people to work with
- Their success criteria
Spend time on a deep-dive analysis of:
- The solution design (if applicable), or the proposed technology solution
- The existing processes
- The new, expected processes
- The teams and team members who'll need to take on the new processes
- When each team meets regularly, and who their team leaders are
- What the changes will look like in real life
- The impact of those changes on people — including their psychological safety in this project
This analysis is what makes the next stage — planning — possible.
In this planning phase, you'll need to create plans for the following — depending on how many team members are impacted by the change:
- Change Management Plan — usually a one-page summary of all your proposed activities
- Engagement Plan — usually a list of dates for team meetings, and when you can talk to people in each team, formally or informally. This needs to happen before the communications and training go out
- Communications Plan — usually a list of proposed emails or updates, which teams they go to, and when
- Training Plan — usually a document listing out proposed training modules and contents
- Training Schedule — usually a plan showing training delivery dates and teams
You'll get started on these plans in Module 2, with Change Made Simple's free Project Risks & Actions Report.
Look for your Change Champions and Change Leadership Team among people who:
- Already have informal trust and influence in their team, whether or not they hold a formal title
- Are genuinely using the new way of working, and can talk about it honestly — including what's hard about it
- Have enough credibility that their endorsement would actually change someone's mind
This grassroots layer is what most AI rollouts skip entirely.
Keep supporting the change after go-live, through:
- Regular check-ins with each team — not just a single follow-up once training ends
- Coaching and troubleshooting support, available as people hit real friction in their day-to-day work
- Mini showcases where someone shares a prompt, the first output, and what they changed next — so iterating in front of others feels normal, not risky
- Publicly celebrating early wins, and naming the people behind them
- Adjusting your approach based on what you're actually hearing from teams, not just the original plan
Steps 4 and 5 can run concurrently on larger projects.
Where Does Your Team Stand?
Your five answers, gathered from each section above. Edit them up there — this is a read-only copy for review, saving and printing.