Individual change
Use ADKAR to understand the move from knowing why a change is happening to being able to work differently.

Deliver / Change
We run change management for technology and information programs, built on the ADKAR model of how individuals move through change.
The challenge
A launch is a milestone, not evidence of adoption. Change work connects the reason for the program to the people affected, then supports understanding, willingness, skills and sustained practice.
Most technology programs do not fail on the technology.
They fail because the people who were meant to work differently did not.
There is a launch email and a training session, and six months later everyone is back to the old workaround.
A technology program changes how people work.
Training alone has not translated into adoption.
Sponsors need a clear view of readiness and resistance.
From need to outcome
Understand the starting point. Do the work that matters. Give your team something practical to carry forward.
Understand
Do the work
Carry it forward
Scope of work
Change management built on ADKAR, so new ways of working actually stick. The scope reflects your priorities, the operating environment and what needs to be achieved.
Use ADKAR to understand the move from knowing why a change is happening to being able to work differently.
Bring communication, sponsor activity and training into the technical delivery sequence, rather than leaving them until launch.
Agree adoption measures and reinforce the new practices after go-live, including the points where old habits can return.
Our approach
The method follows the work, not a generic playbook. Each stage connects to the decisions, capability or delivery your organisation needs.
Our approach / stage 1
Explain the reason for change and the effect on the people involved.
Your operating environment
Governance, obligations and delivery constraints differ. The engagement is shaped around the organisation you run, not an assumed environment.
Agencies running system rollouts and recordkeeping uplift.
Enterprises rolling out new systems and ways of working.
Intended outcomes
Specialist expertise. Practical application.

Start with the right conversation
We begin with what needs to change and the decisions or work your team needs to support. These are useful starting points for a conversation about change.
The scope, people involved and expected outputs are agreed around your organisation’s needs.
Book a conversationQuestions
Yes. It is most effective when it runs with the technical program from the start.
Adoption measures agreed up front, not just a survey at the end.
No. It scales to the size of the change.
Connected expertise
Let's move the work forward
Tell us what needs to change, what is at stake and where you need support. We will discuss the advice, delivery or specialist capability the work calls for.