Technology sits at the centre of many transformation programmes, attracting significant investment, executive attention and delivery effort. Yet the successful implementation of a platform doesn’t automatically translate into operational change.
Key Insights:
- A platform can be implemented perfectly and still fail to deliver value, because benefits realisation depends on the operating model changing alongside it, not the technology alone.
- When operating model questions are left unresolved, they return later as customisation requests that entrench existing practices rather than support future requirements.
- Technology enables new behaviour only when decision rights, accountability and workflows are redesigned before delivery starts, not adjusted afterwards.
Technology is often treated as the centrepiece of transformation. It’s usually where a significant proportion of the budget is spent, so it naturally attracts executive attention and scrutiny. Yet many transformation programmes successfully deliver new technology without producing meaningful operational change, because technology alone doesn’t change how an organisation works.
Decision-making structures, accountability, workflows and service models all shape how work gets done. If those elements remain unchanged, organisations often find themselves adapting new technology to existing ways of working, rather than using it to create new ones.
As a result, the technology changes, but the organisation largely continues operating as it always has.
Why technology rarely changes behaviour on its own
Leaders of transformation programmes are often tempted to assume that once a new platform is implemented, new ways of working will naturally follow. Sometimes that happens; most of the time, it doesn’t.
Technology can enable new behaviours, but it rarely creates them by itself. When there is no deliberate effort to adjust the operating model, organisations will still make decisions through existing governance structures. When that happens, teams continue working within familiar reporting lines because managers reinforce established ways of operating. Performance measures, incentives and accountabilities remain largely unchanged.
Over time, these existing operating conditions exert a powerful influence on how the technology is used.
Instead of changing the organisation to take advantage of the new platform, organisations often begin changing the platform to fit the way they already work. Customisation requests start to accumulate as teams seek to preserve familiar processes, accommodate local preferences or maintain existing ways of operating. Over time, workflows become more complex and standard functionality is reshaped to reflect historical practices rather than future requirements.
Individually, these decisions can appear reasonable. Taken together, however, they can gradually undermine much of the value the transformation was intended to deliver.
This is one of the main reasons technology implementations can be delivered successfully while operational outcomes remain largely unchanged. The platform may be performing exactly as intended, but if the organisation continues to operate in much the same way as before, the transformational benefits are difficult to realise.
Why the operating model needs to be defined before the technology
Many transformation programmes begin with discussions about platforms, functionality and implementation roadmaps. The more difficult questions about how the organisation will operate are often deferred until delivery is already underway.
That sequencing can create significant challenges during implementation and after go-live. Technology decisions inevitably embed assumptions about how work will move through the organisation, where accountability will sit, who owns key decisions and how different functions will interact. If those assumptions have not been considered upfront, delivery teams can find themselves navigating competing expectations about what the technology should achieve and how the organisation should operate once it is in place.
As complexity increases, different stakeholder groups bring different interpretations of the future state. Some see the technology as an opportunity to redesign existing ways of working, while others are focused on preserving them. Without a clear operating model to guide decision-making, delivery teams are frequently left trying to reconcile these competing views through system design and customisation.
How technology becomes a proxy for unresolved organisational design
For leaders, the challenge is recognising that these discussions are about the operating model rather than the technology. Decisions about workflows, accountability, ownership and governance are pushed into technology workstreams because they have not been resolved elsewhere. What begins as a platform implementation quickly becomes a debate about how the organisation should function in the future.
This can create the same planning trap that affects many transformation programmes more broadly. As stakeholders attempt to resolve every uncertainty before moving forward, delivery slows and design cycles expand. Customisation requests increase as different groups seek to embed their preferred ways of working into the technology, adding complexity while gradually reducing the transformational value the platform was intended to deliver.
Before major delivery activity begins, organisations need a clear view of how work is expected to flow through the business, where accountability will sit and what capabilities the future model requires. The objective here is to establish enough operational intent that technology decisions can be evaluated against a coherent vision for how the organisation intends to operate.
Transformation is organisational redesign, not technology delivery
Technology will always play a central role in transformation. Yet technology alone rarely delivers transformation outcomes, which must be realised through the operating model that sits around it: the structures, accountabilities, workflows and governance mechanisms that determine how work gets done.
Organisations that achieve the greatest value from transformation programmes tend to recognise this early. Rather than treating operating model design as a downstream change management activity, it becomes foundational architecture that informs delivery from the outset.
Understanding how work will flow through the business, where accountability will sit, how decisions will be made and which capabilities the future model requires can provide a valuable reference point as delivery progresses. It also creates a framework for evaluating technology decisions against the operating outcomes the transformation is intended to achieve.
A new technology platform can enable change, but it can’t deliver it on its own. Real transformation occurs when organisations redesign the structures, processes and accountabilities surrounding the technology. When those elements move together, the likelihood of achieving meaningful operational improvement increases significantly.
Quay Consulting is a professional services business specialising in the project landscape, transforming strategy into fit-for-purpose delivery. Meet our team or reach out to have a discussion today.