TECHNOLOGY · 2 HOURS
Running a Technology Rollout
Running a Technology Rollout teaches project leads and operations managers to introduce a new tool in stages, from a small first group to the whole organisation. You finish with a rollout sheet that sets out the behaviour you expect, an owner and date for each group, and the sign that the tool has stuck.
About this course
A technology rollout is the work of moving people from the way they do a task now to the way a new tool expects, such as a booking system, a shared drive, a sign-in process or a reporting tool. The tool has usually been chosen and the contract signed before a project lead is asked to run the rollout, and success is often defined as a go-live date and a training count, which says nothing about whether anyone now works differently. This course teaches project leads and managers to run a rollout that changes the work and lasts, with no project management qualification needed.
You define success as a behaviour that can be seen in the work, put the groups in an order that lets each one learn from the last, give every group an owner, a helper and three dates, plan a support window followed by a visible stop to the old way, and decide in advance the evidence that the change has held. You finish with a signed one-page rollout sheet for one real tool that each group owner can read and act on without asking you.
What you will take away
- You will be able to write success as a behaviour you can see, saying who does what, when, and what will have disappeared, and tell it apart from an activity such as holding training sessions.
- You will be able to put a rollout in five steps that learn from each other, starting with a small first group that does the task every day and has a manager who wants the change.
- You will be able to give each group an owner inside the group, a named helper with a way to reach them, and calendar dates for the start, the stop and the check.
- You will be able to plan a support window with a back-up and a place for problems, followed by a visible stop to the old way that is announced at the start, and choose a sign it stuck rather than a sign it launched.
- You will leave with a signed one-page rollout sheet in five sections: the behaviour, the order of groups, who and when, support then stop, and the sign it stuck.
Who this course is for
- Project leads who have been asked to introduce a tool that someone else has already chosen and paid for.
- Operations managers rolling out a system across several sites or teams who want to avoid finding every problem on the same Monday.
- Team leaders who will be the owner of the change in their own group and want to know what that role involves.
- Managers who have seen a previous rollout declared finished at go-live while staff carried on with the paper book or the old spreadsheet.
What you will do
Each lesson teaches one part of the method, works through a realistic example, and ends with a check on a case you have not seen. The course closes with an assessment and then the piece of work you sign.
- 5lessons with a worked example and a check
- 8scenario questions in the course assessment
- Signedthe rollout sheet, with a record anyone can verify
- 2 hoursat your own pace, with progress saved
- 01
Lesson
The behaviour
This lesson sets the definition of success for the whole rollout as a behaviour you can see in the work, rather than a go-live date or training count. You choose between success statements and mark sentences as a behaviour or only an activity.
- What a rollout is for
- A behaviour you can see
- Only an activity
- The mistake people usually make
You mark 4 statements from a realistic case and receive an explanation for each one.
- 02
Lesson
The order of a rollout
This lesson explains why going everywhere at once finds every problem at once, and sets out five steps in which each group learns from the one before. You put the steps of a rollout in the order the lesson teaches.
- Everywhere at once finds every problem at once
- The five steps
- Why each step is where it is
- What the order is not
You put 5 steps in the order that holds up in practice, with feedback on the sequence.
- 03
Lesson
Who and when
This lesson shows why each group needs an owner inside the group, a named helper who is a person rather than a service desk, and three calendar dates. You mark group lines as ready to run or not ready and choose the complete one.
- Three things against every group
- The owner is in the group
- The helper is a person
- Three dates, not one
You compare two versions of the same piece of work, choose the stronger one, and see the reasoning behind the answer.
- 04
Lesson
Support, then stop
This lesson plans the fixed support window for each group and the visible stop to the old way that follows it, announced from the first day. You edit a plan so that it names a helper, dates, a back-up, a place for problems and the stop.
- The support window
- The stop
- Why the order is support, then stop
- Announce the stop at the start
You repair a flawed draft so it meets the standard the lesson sets, and your revision is checked against it.
- 05
Lesson
The sign it stuck
This lesson explains how to tell evidence that a rollout stuck from evidence that it merely launched, and why the check should come weeks after the stop. You mark measures such as login counts and sampled work as one kind or the other.
- A sign it stuck
- A sign it launched
- Decide the sign before you begin
- Make the check independent
You mark 4 statements from a realistic case and receive an explanation for each one.
- 06
Course assessment
The rollout assessment
This course assessment brings the four modules together and shows the common pattern in which easily reported parts are detailed and decisive parts are vague. You then apply the method to eight situations you have not met in the course.
- The method in one place
- Where rollouts usually go wrong
- How the assessment works
You judge 8 new workplace situations, with feedback on every option, and need 6 correct to pass.
- 07
Final work and signed record
Your rollout sheet
In this final lesson you write a one-page rollout sheet in five sections for a real tool you are rolling out now or soon. Each section is checked to see whether an owner could act on it as it stands, and then you sign it.
- Choose one real tool
- The five sections
- How the sheet is checked
You write the rollout sheet for your own work, part by part, and sign it as your record.
GOOD WORK.THE ROLLOUT SHEET, SIGNED.
WHAT CHANGES
What the course changes for you and your organisation.
- 01
Problems found in one team first
Starting with a small first group means problems such as a jammed badge printer or a missing field are met at one site, while there is time to fix them. Later groups receive a tool that already works on real work.
- 02
No second system left running
The course pairs a fixed support window with a stop to the old way that people can see, such as a spreadsheet made read-only. The organisation avoids data split between two systems and a new tool that only ever receives the easy cases.
- 03
Evidence the change has held
You decide before the rollout begins what you will check in the work, and when, weeks after the support has ended. The strongest check compares the tool with an independent record, such as the dispatch log or the work schedule, rather than a login count.
- 04
Rollouts that actually stick
Gartner's 2025 research found that only 32% of business leaders said their last change achieved healthy adoption by employees. Project leads who stage a rollout with clear owners, dates and a sign of adoption give employers a better chance of a tool being used as intended.
QUESTIONS
Questions about Running a Technology Rollout
- What is Running a Technology Rollout about?
- A technology rollout is the work of moving people from the way they do a task now to the way a new tool expects, such as a booking system, a shared drive, a sign-in process or a reporting tool. The tool has usually been chosen and the contract signed before a project lead is asked to run the rollout, and success is often defined as a go-live date and a training count, which says nothing about whether anyone now works differently. This course teaches project leads and managers to run a rollout that changes the work and lasts, with no project management qualification needed. You define success as a behaviour that can be seen in the work, put the groups in an order that lets each one learn from the last, give every group an owner, a helper and three dates, plan a support window followed by a visible stop to the old way, and decide in advance the evidence that the change has held. You finish with a signed one-page rollout sheet for one real tool that each group owner can read and act on without asking you.
- Who is Running a Technology Rollout for?
- Project leads who have been asked to introduce a tool that someone else has already chosen and paid for. Operations managers rolling out a system across several sites or teams who want to avoid finding every problem on the same Monday. Team leaders who will be the owner of the change in their own group and want to know what that role involves. Managers who have seen a previous rollout declared finished at go-live while staff carried on with the paper book or the old spreadsheet. No specialist background is assumed, and every term is explained before it is used.
- What will I be able to do after Running a Technology Rollout?
- You will be able to write success as a behaviour you can see, saying who does what, when, and what will have disappeared, and tell it apart from an activity such as holding training sessions. You will be able to put a rollout in five steps that learn from each other, starting with a small first group that does the task every day and has a manager who wants the change. You will be able to give each group an owner inside the group, a named helper with a way to reach them, and calendar dates for the start, the stop and the check. You will be able to plan a support window with a back-up and a place for problems, followed by a visible stop to the old way that is announced at the start, and choose a sign it stuck rather than a sign it launched. You will leave with a signed one-page rollout sheet in five sections: the behaviour, the order of groups, who and when, support then stop, and the sign it stuck.
- How long does the course take, and how is it taught?
- The course takes about 2 hours and is studied online at your own pace. It has 5 lessons, each with a worked example, a practice exercise, and a check on a new case, followed by a course assessment of 8 scenario questions in which you need 6 correct to pass. Your progress is saved to your account.
- Do I get a certificate?
- Yes. When you pass, you sign a record that names you, the course, and the rollout sheet. Anyone you share it with can verify it online and download it as a PDF. The record confirms what you completed and does not claim compliance with any regulation.
- How much does it cost, and when can I start?
- The course costs £129, paid once by card through Stripe. Access begins as soon as payment is confirmed, and you can save a sign-in to return to the course from any device.
- Can my organisation train a whole team?
- Yes. Individuals can buy any self-paced course online, and organisations can book trainer-led courses for teams, in person or online, through the Experrt Academy.
More technology courses are listed on the self-paced technology courses for non-technical teams page.
THERE IS A NEXT CHAPTER.
Start today, and finish with
the rollout sheet your organisation can use.
Checkout takes an email address and a card, and access begins as soon as payment is confirmed. When you finish, you sign a record that names you and the rollout sheet, which anyone you choose can verify online. The record confirms what you completed and does not claim compliance with any regulation.