Starting digital transformation with platform selection is the most common and most costly sequencing error in enterprise technology investment. The organisations that consistently get more from technology are those that arrive at platform selection having already answered the harder questions about operating model, process design, and capability building.
The Technology Selection Fallacy
The most common mistake in digital transformation is also the most predictable: starting with the technology. Organisations convene platform selection committees, evaluate vendor proposals, attend industry demonstrations, and commission proof-of-concept deployments — all before achieving clarity on the business model they are trying to enable, the processes they are trying to change, or the capabilities they are trying to build. The result is a technology investment that is operationally disconnected from the strategic purpose it was supposed to serve.
This pattern is not irrational from the perspective of the individuals driving it. Technology vendors are well-resourced, highly visible, and expert at creating urgency. Their products are tangible in a way that operating model redesign is not. Platform selection feels like progress because it produces artefacts — evaluation matrices, vendor shortlists, commercial proposals — that can be reported to steering committees as evidence that transformation is underway.
What platform selection does not produce is clarity on the harder questions: What should the organisation be able to do differently? How should work be organised to enable that? What capabilities need to exist in people, not just systems? What does success look like in operational terms, and how will it be measured? These questions require more difficult internal conversations than vendor evaluations do — and they are the questions that determine whether transformation delivers its intended value.
The organisations that consistently get more from their technology investments are those that arrive at platform selection having already answered these questions. For them, technology selection is a constrained decision — constrained by a clear understanding of what they need the technology to do and why — rather than an open exploration of what technology vendors offer.
The Operating Model That Technology Must Serve
Every technology investment is, implicitly, an investment in a particular operating model — a view of how the organisation should work, how decisions should be made, and how value should be created and delivered. When technology selection precedes operating model design, the implicit operating model encoded in the technology shapes the organisation rather than serving it.
Enterprise software vendors build their products around assumptions about how businesses operate. ERP systems assume particular organisational structures and approval hierarchies. CRM platforms assume particular sales process models. Cloud data platforms assume particular data governance models. When these assumptions align with the organisation’s intended operating model, the technology is an accelerant. When they do not, the technology becomes a constraint — one that is expensive to work around and difficult to replace.
When technology selection precedes operating model design, the assumptions baked into the platform shape the organisation rather than serve it.
The discipline of operating model design before technology selection is not new. What is new is the growing recognition among Australian organisations that have completed major technology deployments — and found themselves adapting to the technology rather than the other way around — that the sequence matters enormously. The retrospective cost of misalignment between technology architecture and operating model intent is reliably higher than the prospective cost of doing the operating model design work first.
Process Redesign as a Prerequisite, Not a Workstream
Related to the operating model question is the process design question. In most transformation programmes, process redesign is a workstream — something that runs concurrently with technology selection and is expected to converge with it at some point during implementation. In the most effective transformations, process redesign is a prerequisite — work that is substantially complete before technology selection begins.
The difference matters because processes designed without technology constraints are fundamentally different from processes designed around a selected platform. When process design follows technology selection, the technology becomes the constraint around which processes are organised. This is the reverse of the intended relationship, and it produces processes that are suboptimal by design.
The Capability Question That Precedes All Others
Before selecting a platform, organisations should be able to answer a more fundamental question: what capabilities does this transformation need to create, and who will carry them? Capabilities exist in people and processes. Technology enables them but cannot substitute for them.
The failure to distinguish between deploying a technology and building a capability is one of the most consistent patterns in transformation programmes that underdeliver. A data analytics platform, deployed into an organisation without the data literacy, analytical skills, and decision processes to use it, generates reports that no one acts on. A customer relationship management platform, deployed without the customer management skills, process discipline, and performance culture to operationalise it, becomes an expensive contact database.
Capability building requires investment in people, role design, training, and management systems — none of which appear in technology vendor proposals. Organisations that budget only for the technology component of transformation consistently find themselves with platforms that are underutilised, because the human capabilities that would make the platforms valuable were never developed.
Resequencing the Transformation Agenda
The practical implication for boards and executive teams is that transformation programmes should be structured to answer strategic questions before operational ones, and operational ones before technology ones. The sequence that reliably underdelivers — identify a technology, build a business case around its promised benefits, deploy it, and hope the organisation adapts — should be replaced with a sequence that starts with strategic intent and works toward technology selection as a constrained, well-defined decision.
This requires resisting the pressure that technology vendors create, and that internal programme teams often reinforce, to begin with platform selection. It requires investing in design work — operating model design, process design, capability assessment — that does not produce the visible artefacts that steering committees find reassuring but that creates the conditions for technology investment to actually work.
The organisations that have invested in this sequence consistently report faster implementations, lower costs, higher adoption rates, and more durable outcomes than those that began with the technology. The investment in getting the sequence right is, in every case, smaller than the cost of getting it wrong.
Transformation programmes that start with strategic intent and work toward technology selection as a constrained decision consistently outperform those that start with the platform.