D://LEAD40Change Management
The system landed.
Did anyone use it?
Change management is the work that decides whether a technology change is adopted: communication, training, support, and the follow-through after go-live. It is for organisations rolling out something that requires people to work differently.
THE PROBLEM
Adoption is the only measure that matters, and it is the one most projects stop measuring on the day they go live.
The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.
Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.
- 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
- 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
- 03Only handled when it breaksAttention arrives after the disruption rather than before it.
WHAT YOU GET
What the engagement covers
Scoped before it starts, so you know what is included and what is not.
- 01
Impact assessment
Who is affected, how their day changes, and where the resistance will legitimately come from. Some of it will be well founded, and that is useful information rather than an obstacle.
- 02
Communication plan
What is said, when, and by whom. Where it matters, that means your leaders rather than the IT team.
- 03
Training
Delivered by role against the tasks people actually do, rather than as a tour of the software features.
- 04
Post-launch support
Floor-walking and follow-up in the weeks after go-live, which is when the old habit is strongest and the new system is most likely to be abandoned.
HOW WE WORK
Discover, design, deliver, embed
Four stages with a written output at each one. You always know which stage you are in and what comes next.
- 01Weeks 1 – 2
Discover
We map how the work happens now, including the workarounds people are slightly embarrassed to mention.
- 02Weeks 3 – 4
Design
Options costed against benefit, so the choice is a decision rather than a preference.
- 03Per stage
Deliver
Built in slices that reach production and get used, each with a success measure agreed before it starts.
- 04Post-delivery
Embed
Training, documentation, and a check-in once the novelty has worn off. Adoption is the only measure that counts.
WHAT CHANGES
What you should expect
- Someone other than you owns it, with that written down.
- The current state is documented and stays documented.
- Cost is planned ahead rather than discovered at renewal.
- Decisions are made against evidence rather than assumption.
FAQ
Questions we get asked
01What is change management?
Change management is the work that decides whether a technology change is adopted: communication, training, support, and the follow-through after go-live. It is for organisations rolling out something that requires people to work differently.
02Why do staff resist new systems even when the old one is worse?
Because the old one is known, and competence is comfortable. Someone who was fast and respected at the old way becomes a beginner again, in public, in front of colleagues. That is a real cost to them and it is rarely acknowledged. Naming it, and giving people a way to become competent quickly and privately, does more than any amount of enthusiasm about features.
03How much of a project budget should go on change management?
More than most organisations allocate. Where the change requires people to work differently, treating adoption as a line item rather than an afterthought is what separates the systems that get used from the ones that get paid for. The cheapest possible version of this, involving the people doing the work during design, costs almost nothing and prevents most of the problem.
04How do you measure whether a change has actually been adopted?
With usage data against a target agreed before go-live, not with a satisfaction survey. Who is using the new system, for what, and how often. Where the old process still exists, whether people have drifted back to it. Adoption that is not measured tends to be assumed, and it is usually assumed generously.
05What is the single most common reason rollouts fail?
Leaders who sponsored the change in the planning meeting and were absent from the communication. If the message about why this matters comes from IT, it reads as an IT project. If it comes from the person whose opinion actually affects someone’s working life, it reads as a business decision. That difference is most of the outcome.
06How much does change management cost in New Zealand?
We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.
07How long does it take to get started with change management?
A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.
08Can you deliver change management alongside our existing IT team or provider?
Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.
09Do we have to be an existing Atlas client to start a project?
No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.
10Do you deliver projects outside Auckland?
Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.
11Who from Atlas will be on the engagement?
Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.
12What happens when the engagement ends?
You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.
Start with a conversation.
Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.
← All services