04
Project risk management and change management
Projects that are delivered successfully still fail for two reasons: a risk everyone knew about but nobody owned, and a solution nobody wanted to use.
Risk register and change control
Preparing people and the organisation to actually use the new solution, with a risk register reviewed every week.
What you have at the end
- Risk register with owner, date and response plan
- Stakeholder engagement and communication plan
- User readiness plan and post-go-live adoption measures
How we work
How project risk and change management starts
A register that is opened every week.
Every risk is entered with an owner and a date and reviewed at the weekly meeting; no scope change is accepted without an impact assessment. User readiness is planned from the first phase, not the week before go-live. Adoption is measured after go-live as well, against indicators agreed in advance — not by whether the training took place.
The first step is normally a delivery assessment: two to three weeks, fixed scope and fixed price, with written findings. Only then do we agree further work, if any is needed. See Engagement models.
Frequently asked questions about risk and change management
Why do risk registers fail?
Usually because risks have no owner and no date. A risk without a name next to it is an observation, not a risk. The other reason is that the register is written at the start and never reopened, while the risks change with every phase.
What is change management?
Two different things under one name. One is scope change control — who may request a change and how its impact on schedule and cost is measured. The other is preparing the people who will use the new system. We do both, but they are agreed separately: scope change control goes with project delivery (service 01), and preparing the people is this service.
Do you run user training?
We do not run courses. We plan and manage user readiness as part of the project, while the training itself is delivered by your people or the solution supplier — they know the system better than we do.
How long does it take, and what does the engagement look like?
It starts with a two-to-three-week assessment at fixed scope and fixed price: which risks have no owner, which changes went through unassessed and how ready the users are. If we continue, the risk register and user readiness run alongside the project and last as long as it does — through go-live and the adoption measurement after it.
Does your programme look like this? Get in touch or call +381 63 275 615.
Related services
The system is delivered. Who will use it?
The assessment takes two to three weeks at fixed scope and fixed price: which risks have no owner, which changes went through unassessed, and how ready the users are. You receive written findings, with no obligation to continue.