top of page

When transformation fails, it is rarely just the technology

Cover: when transformation fails, it is rarely just the technology

The recent reporting on ASX CEO Helen Lofthouse conceding she underestimated the scale of the ASX challenge should be a warning to every board, executive and transformation leader.


Large-scale transformation is often presented as a technology problem. Replace the platform. Upgrade the system. Modernise the infrastructure. Appoint the vendor. Reset the roadmap. Strengthen delivery controls.


All of these matter, but they are rarely enough.


The deeper issue in complex transformation is often not the technology itself. It is the people, governance, decision-making, culture and trust required to make the technology work in a real operating environment.


business presentation stage

The ASX CHESS replacement experience is a powerful example. CHESS is not simply a technology platform. It is critical market infrastructure. It sits within a complex ecosystem of regulators, market participants, brokers, clearing and settlement stakeholders, vendors, internal teams and public confidence. Any change to that system is therefore not just a systems replacement. It is an ecosystem transformation.


That distinction matters because a technology replacement can be managed as a project but an ecosystem transformation must be led as a change in the way people understand risk, make decisions, collaborate, govern, communicate and build confidence.


financial data charts

When leaders underestimate that difference, they often default to the easier narrative: the technology is difficult, the vendor is late, the architecture is complex, the roadmap needs resetting.


These may all be true but they can also distract from the harder questions, such as:


  • Was the organisation culturally ready for the change?

  • Was there genuine alignment across the executive, board, delivery teams, regulators and stakeholders?

  • Were warning signs escalated early enough and acted on with sufficient seriousness?

  • Was governance designed to surface uncomfortable truths, or to reassure?

  • Were stakeholders truly engaged as partners in change, or treated as recipients of a solution?

  • Was there enough humility in the leadership system to recognise that critical infrastructure transformation requires more than confidence, ambition and technical expertise?


The uncomfortable lesson is that transformation failure is often visible long before it becomes undeniable. The signals are usually there. Requirements keep shifting. Stakeholders lose confidence. Risks are softened in reporting. Red flags become amber. Governance forums receive updates rather than insight. Leaders focus on milestones while trust quietly erodes.


This is where cultural change becomes essential. Culture is not a soft side issue, it determines whether people raise risks early, whether executives listen, whether governance forums challenge constructively, whether teams collaborate across silos, and whether stakeholders believe the organisation is being transparent.


In high-stakes transformation, culture is a control system. If the culture rewards optimism, status protection and delivery theatre, the governance system will be weak, regardless of how many committees exist.


If the culture encourages transparency, escalation, learning and challenge, then governance becomes a mechanism for informed decision-making, not a reporting ritual.


This is why transformation leaders need to resist the temptation to treat cultural change as a workstream that sits beneath the “real” program. In reality, cultural change is the condition that allows the program to succeed, where:


  • Technology change asks: what system are we implementing?

  • Cultural change asks: how must we behave differently for this system to deliver value safely and sustainably?

  • Governance change asks: how will we know the truth early enough to act?

  • People change asks: who needs to understand, trust, adopt and operate the change?

  • Strategic change asks: what value are we protecting or creating, and for whom?


The ASX case reinforces a lesson that applies well beyond financial market infrastructure. Whether an organisation is replacing a core platform, implementing AI, restructuring operating models, digitising services, or transforming project delivery capability, the same principle applies.


Do not confuse implementation with transformation. Implementation installs the thing. Transformation changes the system around the thing.


The leaders who succeed are not those who focus only on the technology. They are those who understand that it is a system of people, governance and culture which are not peripheral to delivery, they are part of the delivery.


This requires a different kind of leadership. It requires authentic leadership to create psychological safety for bad news, ensure governance forums test assumptions rather than endorse optimism, involve stakeholders early and meaningfully, and treat cultural readiness as seriously as technical readiness. It also requires boards and executives to ask better questions:


  • What are we not being told?

  • Where is confidence higher than evidence?

  • Which stakeholders do not trust the current approach, and why?

  • What behaviours are preventing honest escalation?

  • What would have to be true for this program to succeed?

  • Where are governance forums adding value, and where are they simply receiving updates?

  • What would an independent assurance review say if it had full access and no pressure to be polite?


These are not comfortable questions. But they are the questions that protect value. The lesson from ASX is not simply that technology transformation is hard. Everyone already knows that. The deeper lesson is that technology transformation becomes far harder when leaders underestimate the cultural, governance and stakeholder change required to make it work.


In complex transformation, the people are not a change management afterthought, they are the strategy, they are the risk control, they are the delivery system and ultimately, they are the difference between a technology project that consumes money and a transformation that creates lasting public value.


If some of these points are ringing true for you, please contact the PMLogic team below to discuss how we can help get your transformation program back on track.


city and technology


📩 Complex transformation needs more than technology—it needs clarity, governance and culture that supports delivery.

Talk to PMLogic about how we can help your organisation deliver with confidence.



PMLogic team

Comments


bottom of page