Why Your Project Is "On Time" But Still Failing

By Shane Tyrrell | Head of Advisory and Capability Enablement, Prosci ANZ

There is a moment most project managers know all too well. The go-live date arrives, the system is live, the milestones are ticked and the steering committee gets its green status report. And then quietly nothing really changes.

The technology is deployed. The process is documented. The training was delivered. And yet months later people are working around this new system and the business is asking uncomfortable questions about where the value went.

This is not a project management failure in the traditional sense. The project was delivered on time, on budget and within scope but the organisation is failing to realise the benefits it invested in. In today's environment where the pressure to do more with less is relentless and where AI enabled transformation is accelerating the pace of change the cost of re-working a project can be catastrophic. The gap between delivery and adoption is no longer a soft issue, it is a commercial risk management issue.

This Gap has a name - Adoption

Prosci's research across more than 7,000 organsations consistently shows that projects with excellent change management are six times more likely to meet or exceed their objectives. Six times! That is not a marginal improvement, that is the difference between a transformation and a very expensive iteration.

The gap between a successful deployment and a successful outcome is adoption. And adoption is not something that happens to people, it is something that has to be actively designed, led and managed with the same level of rigour and discipline that project managers bring to scope, schedule and budget.

For most project managers this is not new information. What is new are the stakes.

The modern context has changed the calculation

We are operating in an environment where the velocity and complexity of change has fundamentally shifted. AI is not coming it is here and organisations are under pressure to integrate it rapidly. Digital transformation programs are running concurrently with operational change, cultural evolution and workforce restructures. The assumption that people will simply adapt because the technology is good enough is not a strategy it is a risk where the cost of getting it wrong has never been higher. When adoption fails organisations do not just miss benefits they absorb re-work costs, re-scoping exercises and the significant cost of doing it all again. In a world where boards, CEO’s and CFOs are scrutinising every dollar of investment that is a conversation no project leader wants to be having.

What I experienced at one of the Australia’s largest mining and resources organisation

A little while back I worked with a major mining and resources company on a large scale mine automation program. On paper the project was tracking well, the technology was sophisticated the engineering was sound the implementation timeline and budget was being managed very tightly. As the go-live date drew closer and we looked more closely at the change side of the program a different picture emerged.

The operators who would be working alongside the automation had not been sufficiently prepared to work in fundamentally different ways. The new operating model, roles, workflows, decision rights and the day to day rhythms that would be needed to shift had not yet been adopted in parallel with the technical build. And as the go-live pressure mounted project sponsor visibility dropped off leaving no single accountable voice driving the people side of this transformation.

With hindsight being the exact science that it is the result was predictable, adoption was limited or non existent. Productivity targets were not met and the program had to absorb a significant amount of re-work to address what the original scope had not adequately accounted for the human side of the change.

The technology was not the problem. The change was.

What this means for how you manage projects

I am not suggesting that project managers need to become change managers. But I am saying that the most effective project managers I work with today treat change management as a core discipline within their program structure and not just a workstream to be bolted on and not as something to be handed off to HR or communications.

Specifically, this means three things.

1. Scope the people change from the beginning. Understand who is impacted, how deeply and what will need to shift in their awareness, desire, knowledge, ability and reinforcement of the project, the ADKAR framework gives you a clear model and guide for this. Do not wait until the system is built to ask these questions.
2. Keep sponsors accountable and visible through the entire lifecycle of the project and not just at project kick-off and at go-live. Prosci's research identifies active and visible sponsorship as the single most important factor in change success. When sponsors disengage mid program adoption suffers. Build sponsor engagement into your governance cadence and treat it with the same attention you give milestone reviews.
3. Redefine what the end looks like. A project is not complete when the system is live. It is complete when the people who need to use it are actually using it, using it correctly and realising the outcomes the business invested in. Shift your definition of success from deployment to adoption.

The pressure is real, and so is the opportunity

Project managers are under enormous pressure. Timelines are tight and getting tighter, resources are constrained and the complexity of modern programs continues to grow. I understand the temptation to treat change management as a luxury, something for the big programs with big budgets.

But the organisations that are winning right now are the ones that have understood a simple truth, adoption is not the soft side of a transformation it is the whole point! Every dollar invested in getting people ready, willing and able to change is a dollar that protects the return on every dollar invested in the technology, the process and the project itself.

Your project being on time is a starting point. Whether it succeeds is a different question entirely and the answer lives in the adoption and change.