The project was delivered on time.<\/p>\n\n\n\n
The budget was under control.<\/p>\n\n\n\n
The new system launched.<\/p>\n\n\n\n
The project plan was complete.<\/p>\n\n\n\n
So why, six months later, is hardly anyone using it properly?<\/p>\n\n\n\n
This is one of the uncomfortable realities of project management:<\/p>\n\n\n\n
Delivering a project doesn’t automatically mean delivering successful change.<\/strong><\/p>\n\n\n\n For project professionals in New Zealand, that’s an increasingly important distinction.<\/p>\n\n\n\n Organisations are introducing new technology, transforming services, changing processes and asking employees to work in different ways.<\/p>\n\n\n\n Project management can get the solution delivered.<\/p>\n\n\n\n But somebody still has to bring the people with it.<\/p>\n\n\n\n That’s where change management becomes critical.<\/p>\n\n\n\n Imagine your organisation is introducing a new digital platform.<\/p>\n\n\n\n The project team does everything expected of them.<\/p>\n\n\n\n Requirements are gathered.<\/p>\n\n\n\n Suppliers are appointed.<\/p>\n\n\n\n Risks are managed.<\/p>\n\n\n\n Testing is completed.<\/p>\n\n\n\n The platform launches on schedule.<\/p>\n\n\n\n From a traditional project delivery perspective, it looks like a success.<\/p>\n\n\n\n Then reality arrives.<\/p>\n\n\n\n Employees don’t understand why the new system was introduced.<\/p>\n\n\n\n Some don’t feel confident using it.<\/p>\n\n\n\n Managers haven’t reinforced the new processes.<\/p>\n\n\n\n Teams create workarounds.<\/p>\n\n\n\n Others quietly return to the old way of doing things.<\/p>\n\n\n\n Three months later, the organisation has delivered the output but isn’t achieving the outcome.<\/p>\n\n\n\n The technology worked.<\/p>\n\n\n\n The change didn’t.<\/p>\n\n\n\n It’s easy to think of organisational change as a process.<\/p>\n\n\n\n Implement the system.<\/p>\n\n\n\n Change the structure.<\/p>\n\n\n\n Introduce the policy.<\/p>\n\n\n\n Launch the service.<\/p>\n\n\n\n But organisations aren’t simply processes and technology.<\/p>\n\n\n\n They’re people.<\/p>\n\n\n\n And people don’t automatically change their behaviour because a project plan says they should.<\/p>\n\n\n\n They ask questions.<\/p>\n\n\n\n “Why are we changing this?<\/strong>“<\/p>\n\n\n\n “What does it mean for my job?<\/strong>“<\/p>\n\n\n\n “Will I be able to do it?<\/strong>“<\/p>\n\n\n\n “Is this actually better than what we had before?<\/strong>“<\/p>\n\n\n\n “What happens if I don’t agree with it?<\/strong>“<\/p>\n\n\n\n If nobody answers those questions effectively, resistance shouldn’t come as a surprise.<\/p>\n\n\n\n That’s why successful change requires more than a good implementation plan.<\/p>\n\n\n\n It requires understanding how people experience change.<\/p>\n\n\n\n Project management and change management are closely connected, but they aren’t the same thing.<\/p>\n\n\n\n Project management focuses on delivering the change.<\/strong><\/p>\n\n\n\n That could mean a new system, process, product, service or organisational structure.<\/p>\n\n\n\n Change management focuses on helping people understand, adopt and sustain that change.<\/strong><\/p>\n\n\n\n A project manager might ask:<\/p>\n\n\n\n Are we on schedule?<\/p>\n<\/blockquote>\n\n\n\n A change manager might ask:<\/p>\n\n\n\n Are people ready?<\/p>\n<\/blockquote>\n\n\n\n A project manager might ask:<\/p>\n\n\n\n Have we delivered the new system?<\/p>\n<\/blockquote>\n\n\n\n A change manager might ask:<\/p>\n\n\n\n Are people actually using it?<\/p>\n<\/blockquote>\n\n\n\n A project manager might ask:<\/p>\n\n\n\n Have we completed the training?<\/p>\n<\/blockquote>\n\n\n\n A change manager might ask:<\/p>\n\n\n\n Has the training changed people’s behaviour?<\/p>\n<\/blockquote>\n\n\n\n Neither discipline replaces the other.<\/p>\n\n\n\n The strongest transformations need both.<\/p>\n\n\n\n You don’t need Change Manager in your job title to benefit from understanding change.<\/p>\n\n\n\n Project managers are often right at the centre of organisational transformation.<\/p>\n\n\n\n They’re communicating with stakeholders.<\/p>\n\n\n\n Managing competing priorities.<\/p>\n\n\n\n Introducing new ways of working.<\/p>\n\n\n\n Dealing with resistance.<\/p>\n\n\n\n Supporting teams through uncertainty.<\/p>\n\n\n\n Trying to turn a business case into an actual benefit.<\/p>\n\n\n\n Those aren’t purely technical project management challenges.<\/p>\n\n\n\n They’re human ones.<\/p>\n\n\n\n Understanding change management can therefore help project professionals see a project through a different lens.<\/p>\n\n\n\n Instead of only asking:<\/p>\n\n\n\n \u201cWhat do we need to deliver?\u201d<\/strong><\/p>\n\n\n\n You start asking:<\/p>\n\n\n\n \u201cWhat needs to happen for people to adopt what we deliver?\u201d<\/strong><\/p>\n\n\n\n That’s a powerful shift.<\/p>\n\n\n\n Some project risks appear neatly on a risk register.<\/p>\n\n\n\n Others show up in conversations, behaviours and silence.<\/p>\n\n\n\n Here are five signs that the people side of your project might need more attention.<\/p>\n\n\n\n Ask five people why the project exists.<\/p>\n\n\n\n Do you get roughly the same answer?<\/p>\n\n\n\n If not, there’s a problem.<\/p>\n\n\n\n People are far more likely to engage with change when they understand the reason behind it, what the future should look like and why remaining where they are isn’t an attractive option.<\/p>\n\n\n\n Communication isn’t the same as information distribution.<\/p>\n\n\n\n A monthly project update might tell people what’s happening.<\/p>\n\n\n\n It doesn’t necessarily create understanding or engagement.<\/p>\n\n\n\n Different stakeholders need different information, delivered in different ways and at different stages of the change.<\/p>\n\n\n\n And communication needs to work both ways.<\/p>\n\n\n\n People need opportunities to ask questions, raise concerns and understand what the change means for them.<\/p>\n\n\n\n Resistance can be frustrating.<\/p>\n\n\n\n But it can also be useful.<\/p>\n\n\n\n Someone resisting a change may have spotted a genuine problem.<\/p>\n\n\n\n They may have experienced a similar failed initiative.<\/p>\n\n\n\n They may be worried about losing expertise, control, status or confidence.<\/p>\n\n\n\n Simply labelling people as \u201cresistant\u201d can mean missing valuable information about why adoption is struggling.<\/p>\n\n\n\n Strong change leaders get curious about resistance.<\/p>\n\n\n\n The system goes live on Monday.<\/p>\n\n\n\n Everyone gets trained on Friday.<\/p>\n\n\n\n Job done?<\/p>\n\n\n\n Not necessarily.<\/p>\n\n\n\n Training is an important part of change, but successful adoption may also require communication, leadership support, opportunities to practise, reinforcement and continued help after implementation.<\/p>\n\n\n\n People rarely transform the way they work after one training session.<\/p>\n\n\n\n This is perhaps the biggest warning sign.<\/p>\n\n\n\n A project team spends months working towards launch day.<\/p>\n\n\n\n Then the solution goes live and everyone celebrates.<\/p>\n\n\n\n But go-live isn’t necessarily success.<\/p>\n\n\n\n The real questions come afterwards.<\/p>\n\n\n\n Are people using the new solution?<\/p>\n\n\n\n Has behaviour changed?<\/p>\n\n\n\n Are the expected benefits appearing?<\/p>\n\n\n\n Has the organisation actually moved from its old state to the new one?<\/p>\n\n\n\n Delivery is a milestone. Adoption is the goal.<\/strong><\/p>\n\n\n\n This becomes particularly important when we talk about digital transformation.<\/p>\n\n\n\n The word digital can make transformation sound primarily technological.<\/p>\n\n\n\n But introducing AI, automation, new software or new digital services often changes much more than technology.<\/p>\n\n\n\n It can change:<\/p>\n\n\n\n That’s why a technically brilliant transformation can still struggle.<\/p>\n\n\n\n The organisation may have invested heavily in the technology while underinvesting in the transition people need to make.<\/p>\n\n\n\n Project professionals who understand both delivery and adoption are therefore extremely valuable.<\/p>\n\n\n\n There’s another misconception worth challenging.<\/p>\n\n\n\n Change management isn’t simply what you do when people complain about a project.<\/p>\n\n\n\n Effective change management begins much earlier.<\/p>\n\n\n\n It considers questions such as:<\/p>\n\n\n\n Who will be affected?<\/p>\n\n\n\n How ready is the organisation for this change?<\/p>\n\n\n\n What does each stakeholder group need?<\/p>\n\n\n\n How should the change be communicated?<\/p>\n\n\n\n What support will people require?<\/p>\n\n\n\n What might create resistance?<\/p>\n\n\n\n How will leaders reinforce the change?<\/p>\n\n\n\n How will we know whether adoption has happened?<\/p>\n\n\n\n These aren’t \u201csoft\u201d questions.<\/p>\n\n\n\n They can determine whether an organisation ever achieves the benefits it invested in the project to create.<\/p>\n\n\n\n Successful change professionals need an interesting combination of skills.<\/p>\n\n\n\n They need to understand the organisation and the change being introduced.<\/p>\n\n\n\n But they also need to understand people.<\/p>\n\n\n\n That means developing capabilities around:<\/p>\n\n\n\n Stakeholder engagement<\/strong> \u2013 identifying who is affected and understanding their needs and influence.<\/p>\n\n\n\n Communication<\/strong> \u2013 creating clear, relevant messages and genuine two-way engagement.<\/p>\n\n\n\n Leadership<\/strong> \u2013 helping create direction and confidence during uncertainty.<\/p>\n\n\n\n Impact assessment<\/strong> \u2013 understanding how a change will affect different parts of the organisation.<\/p>\n\n\n\n Change readiness<\/strong> \u2013 assessing whether individuals, teams and the wider organisation are prepared.<\/p>\n\n\n\n Resistance management<\/strong> \u2013 understanding why people may resist and responding constructively.<\/p>\n\n\n\n Benefits and adoption<\/strong> \u2013 keeping attention on whether the change is actually creating the intended outcome.<\/p>\n\n\n\n For project professionals, these skills can complement traditional capabilities around scope, risk, planning and governance.<\/p>\n\n\n\n Not every project manager needs to become a dedicated change manager.<\/p>\n\n\n\n But if your projects regularly introduce significant changes to how people work, formal change management knowledge can be extremely useful.<\/p>\n\n\n\n A recognised Change Management qualification gives you a structured way to understand the human side of organisational change rather than relying purely on instinct.<\/p>\n\n\n\n Training ByteSize New Zealand offers Change Management Foundation and Practitioner<\/a> training<\/strong>, with learning focused on areas including the impact of change, organisational capability, stakeholder engagement, communication, leadership and aligning change management with project management practices.<\/p>\n\n\n\n Foundation is suitable for professionals looking to develop their understanding of change management principles, while Practitioner develops the ability to apply that knowledge more deeply.<\/p>\n\n\n\n Training ByteSize also offers a combined Foundation and Practitioner<\/a><\/strong> pathway for learners wanting to develop both levels of knowledge.<\/p>\n\n\n\n Project management will always involve deadlines.<\/p>\n\n\n\n Budgets will always matter.<\/p>\n\n\n\n Risk will always matter.<\/p>\n\n\n\n Governance will always matter.<\/p>\n\n\n\n But ultimately, many projects exist because an organisation wants something to be different<\/strong> when the project ends.<\/p>\n\n\n\n A new system should be used.<\/p>\n\n\n\n A new process should become normal.<\/p>\n\n\n\n A transformation should produce benefits.<\/p>\n\n\n\n A new service should improve an outcome.<\/p>\n\n\n\n That’s why understanding change can make you a stronger project professional.<\/p>\n\n\n\n Because the real measure of success isn’t always:<\/p>\n\n\n\n \u201cDid we deliver it?\u201d<\/strong><\/p>\n\n\n\n Sometimes it’s:<\/p>\n\n\n\n \u201cDid anything actually change?\u201d<\/strong><\/p>\n\n\n\n If you’re involved in projects, transformation or organisational change, Training ByteSize New Zealand’s Change Management qualifications<\/a> can help you develop a structured understanding of how to prepare, support and lead people through change.<\/p>\n\n\n\n Choose from Change Management Foundation, Practitioner or combined Foundation and Practitioner training, with flexible online, virtual and blended study options available.<\/p>\n\n\n\nA project can succeed on paper and fail in reality<\/h2>\n\n\n\n
Projects don’t change organisations. People do.<\/h2>\n\n\n\n
Project management vs change management: what’s the difference?<\/h2>\n\n\n\n
\n
\n
\n
\n
\n
\n
Why project managers need change management skills<\/h2>\n\n\n\n
Five warning signs your project has a people problem<\/h2>\n\n\n\n
1. Nobody can explain why the change is happening<\/h3>\n\n\n\n
2. Communication means sending emails<\/h3>\n\n\n\n
3. Resistance is being dismissed as negativity<\/h3>\n\n\n\n
4. Training happens just before launch<\/h3>\n\n\n\n
5. Success ends at go-live<\/h3>\n\n\n\n
The human side of digital transformation<\/h2>\n\n\n\n
\n
Change management isn’t just about managing resistance<\/h2>\n\n\n\n
What skills does a change manager need?<\/h2>\n\n\n\n
Do project managers need a change management qualification?<\/h2>\n\n\n\n
The best project managers don’t just deliver things<\/h2>\n\n\n\n
Develop your change management skills<\/h2>\n\n\n\n