PRINCE2 7 Foundation · Study lesson 11
From installation to adoption
Help people use the change so benefits can emerge.
9 minute study lesson · People · Original learning material
What you will understand
- Distinguish product delivery, adoption, outcomes and benefits.
- Identify practical barriers to changing established working habits.
- Separate people-focused change management from control of project baseline changes.
The idea
A product can pass its technical checks and still sit unused. People may lack skills, access, time, confidence or a reason to change their behaviour. Supporting adoption is therefore part of achieving the project’s purpose, not a promotional activity added at the end. Ask what people must do differently, what enables that behaviour and who will sustain it after the temporary project closes.
An output is a product delivered by the project. Using outputs can produce outcomes, meaning changed circumstances or behaviours. Benefits are the measurable improvements valued by stakeholders. These connections require assumptions that should be examined. A new maintenance application might make scheduling possible, but fewer breakdowns depend on people using it, acting on its information and maintaining equipment appropriately.
People-focused change management helps affected groups move from current ways of working to the intended future situation. It can include participation in design, preparation, training, local support and changes to operational arrangements. It is different from deciding whether a request may alter an agreed project baseline. The first concerns human transition and adoption; the second concerns controlled project change through issue management.
Understand the starting position before prescribing a response. A person may know how to use a product yet have no time to use it, or may support the aim but distrust how performance data will be interpreted. Training addresses a knowledge or skill gap; it cannot alone fix conflicting incentives, inaccessible equipment or an unresolved concern about a new responsibility.
Plan change support alongside product delivery. Involve representative users early, test the working arrangements and provide a route for practical feedback. Identify the people who will own the new service, maintain its guidance and support users after handover. Operational readiness may require revised roles, access rights, procedures and measures, not merely a demonstration that the product functions in a test environment.
Monitor whether adoption and intended outcomes are occurring, with an appropriate owner and timing for benefit reviews. Some benefits arise after project closure, so measurement responsibility must survive the temporary team. Where evidence shows low use or unexpected effects, investigate rather than announcing success based on installation figures. A benefit forecast is an expectation to test, not an achievement already earned.
From product to value
| Step | Evidence |
|---|---|
| Output | The appointment application is delivered. |
| Outcome | Staff and patients actually use the new booking process. |
| Benefit | Measured waiting time improves against an agreed baseline. |
| Adoption support | Training and operating arrangements help the outcome happen. |
An original fictional example
A ceramics cooperative introduces kiln scheduling
A cooperative delivers a booking application to reduce wasted kiln cycles. Members attend a demonstration, but many continue leaving paper notes because the workshop has unreliable internet and nobody has agreed who resolves conflicting bookings.
The decision
Address connectivity and booking authority, involve members in a practical trial, prepare usable instructions and assign an operational owner. Measure booking use and kiln utilisation after handover rather than treating launch day as proof of savings.
Why it makes sense
The product exists, but the behaviour required for the intended outcome is not yet supported. Another demonstration alone would not resolve missing access or decision responsibilities.
A common confusion
The mistaken idea: If the product is delivered and training is complete, its benefits have been realised.
The distinction: Adoption, changed working and measured improvements still need evidence and continuing ownership.
Delivered → usable → used → changed result → measured value.
Points to remember
- Training is one possible intervention, not a universal cure for adoption barriers.
- People-focused change and baseline change control have different purposes.
- Benefits may require measurement and ownership after project closure.
Your takeaway
Make the transition workable for affected people and the operating organisation. Delivery is a necessary step, while adoption, outcomes and benefits need their own evidence.
This independently written explanation is supplementary study material. It is not official examination content. Read about our content and its limitations.