Leading organisational change
Why delivering the project's products isn't the finish line, and how to help people adopt the change so the benefits arrive.
Scene 1
Leading organisational change
Why delivering the project's products isn't the finish line, and how to help people adopt the change so the benefits arrive.
Caption 1 of 3
Explain the link between organisational change and benefits
Read all scene text
- Explain the link between organisational change and benefits
- Describe how to prepare people for the transition to business as usual
- Recognise and respond to resistance to change
Scenes animate with GSAP. Use pause or replay at any time.
In this session
- Explain the link between organisational change and benefits
- Describe how to prepare people for the transition to business as usual
- Recognise and respond to resistance to change
It's time to think about what happens when the project hands over its products.
Let's say the pre-order app goes live. It works perfectly. But after a month, only 20 customers use it. The Leeds counter staff still take phone orders on paper, because "it's quicker".
Why isn't the app delivering its benefits?
Select the arrow to learn more
1 of 4
The output exists
The app is built, tested and live. The project delivered exactly what was asked for.
From outputs to benefits
You'll meet these terms properly in the Business case module, but here's the chain in short. A project delivers outputs, like the app. When people use them, you get outcomes, like customers ordering ahead. Those outcomes lead to benefits, like shorter queues and more sales.
The weak link is almost always people. If nobody changes how they work, the chain breaks before any benefit appears.
Preparing for the transition
Moving from the project to normal day-to-day running is called the transition to business as usual. It needs planning, just like the build:
- Readiness: are people trained, and are processes and support in place?
- Timing: when is the least disruptive moment to switch? Not the week before Christmas
- Support: who helps people in the first weeks, and how do they ask for help?
- Ownership: who in the business owns the new way of working after the project closes?
Understanding resistance
People rarely resist change because they're difficult. They resist because they're worried: about losing skills, status or control, about extra work, or about the unknown.
The best response is to understand the worry, involve people early and show them what's in it for them. The counter staff came round when they saw the app meant no more scribbled phone orders at 6am.
Who leads the change
The project can prepare people, but lasting change has to be led by the business. In PRINCE2, the people who'll use the products are represented on the project board by the senior user, who is responsible for making sure the products are used and the benefits realised.
For York, Priya leads the bakery staff through their new routines. For the app, Jo leads the counter team. Sam supports both, but the change belongs to the business.
Key points to remember
- Benefits come from people using the outputs, not from the outputs alone.
- Plan the transition to business as usual: readiness, timing, support and ownership.
- Resistance usually comes from worry; involve people early and show the benefits.
- The business, represented by the senior user, leads lasting change.
Knowledge check
Choose one answer
People
What usually lies behind resistance to change?
Sign in to save your result. Knowledge checks can be retried any time.
PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.