The sequence of digital transformation — process design before technology selection — is one of the strongest predictors of outcome. Organisations that begin with technology and expect processes to follow consistently underperform those that design the future-state first and select the technology to enable it.
The Inversion That Predicts Failure
The sequence in which digital transformation is approached is one of the strongest predictors of its success or failure. Organisations that begin with process redesign — with a rigorous examination of how work is currently done and how it should be done differently — consistently achieve better outcomes from their technology investments than those that begin with technology selection and attempt to fit processes to platforms.
The intuition behind starting with technology is understandable. Technology is tangible, demonstrable, and produced by vendors with well-resourced sales organisations that are expert at creating urgency. Process work is abstract, politically difficult, and requires sustained engagement with the operational realities that leaders sometimes prefer not to examine too closely. It also requires accepting that the current state is not optimal — an admission that can feel like organisational criticism and is therefore often resisted by the people who designed and manage the existing processes.
Yet the evidence for process-first is compelling and consistent. Organisations that redesign processes before selecting technology choose platforms that fit their actual requirements rather than adapting requirements to platform capabilities. They avoid the costly customisations that are required when platform assumptions do not align with process needs. They generate adoption because the system supports the way people are expected to work, rather than requiring them to change how they work in order to use the system. And they achieve the business outcomes that justified the investment, rather than discovering at implementation that the technology cannot support the processes that were supposed to generate those outcomes.
The argument is not that technology is unimportant. It is that technology cannot substitute for the hard work of process design, and that attempting to use it as such is one of the most expensive and most common mistakes in enterprise transformation.
What Process Redesign Actually Requires
Genuine process redesign is a demanding discipline that requires more than process mapping. Mapping current-state processes — documenting what actually happens, step by step, in the processes the organisation is trying to improve — is a useful starting point, but it is not the redesign itself. The redesign requires asking why each step exists, what value it adds, whether it is necessary in the desired future state, and what would need to be true of the organisation for it to be done differently or eliminated entirely.
This is challenging work because it inevitably surfaces organisational dysfunctions — approval processes that exist because trust is low, manual reconciliations that exist because systems do not communicate, reviews that exist because accountability is unclear — that people are invested in maintaining or that reflect structural choices that require senior leadership to change. Process redesign that stops short of these structural questions produces incremental improvement rather than transformation.
Process mapping documents what happens. Process redesign asks why it happens, what value each step creates, and what would need to be true of the organisation for it to be done differently. Most organisations stop at mapping and call it redesign.
Effective process redesign also requires an honest assessment of what the process is trying to achieve, not just how it currently operates. Processes that have evolved over time often accumulate steps designed to address problems that no longer exist, accommodate constraints that have since changed, or reflect organisational structures that have been superseded. Cleaning out this accumulated complexity before designing the future-state process — rather than digitising the complexity and calling it transformation — is one of the highest-value activities in the transformation agenda.
The Process Excellence Capability Gap
One reason that organisations default to technology-first transformation is that process redesign requires a capability that many do not have in sufficient depth: the ability to analyse processes objectively, design improvements rigorously, and facilitate the organisational conversations required to align stakeholders around a changed future state.
Process excellence capability — the combination of analytical skills, facilitation skills, and change management skills required for effective process redesign — was more common in Australian enterprises during the lean and six sigma movements of the 1990s and 2000s than it is today. The shift toward technology-led transformation has, in many organisations, atrophied the process design capability that would make that transformation more effective.
Process Design as the Specification for Technology
When process redesign precedes technology selection, the designed future-state processes become the specification that technology must satisfy. This creates a fundamentally different kind of technology evaluation: instead of asking what a platform can do, the organisation asks whether the platform can support the processes that have already been designed. The technology evaluation is constrained by the process design, and that constraint is valuable — it focuses the evaluation on the capabilities that matter and eliminates vendor demonstrations of impressive features that the organisation will never use.
It also changes the implementation. When technology is configured to support a designed process rather than to demonstrate a platform’s capabilities, implementation is faster, configuration is simpler, and the gap between what users expect and what the system delivers is smaller. The training investment is more effective because users are learning a process supported by technology, not learning a technology and then working out what process to run through it.
The organisations that achieve the best return on their technology investments consistently report that the technology implementation was the easier part of the transformation — that the difficult and valuable work was the process redesign that preceded it, and that the technology largely delivered what it was asked to deliver because what it was asked to deliver had been carefully and specifically defined.
The Executive’s Process Responsibility
Process redesign is executive work in a way that technology selection is not. The structural and political barriers to genuine process redesign — the organisational dynamics, the entrenched interests, the cross-functional dependencies — require executive authority to resolve. Technology decisions can be delegated to appropriately qualified teams. The decisions required to change how the organisation works, and to maintain commitment to those changes under the inevitable pressure to revert to familiar patterns, require executive leadership.
Boards and executive teams should assess their organisation’s transformation portfolio against a simple diagnostic: for each major transformation initiative, can leadership articulate the specific process changes that the technology investment is designed to enable? If the answer is unclear — if the initiative is characterised primarily in terms of the technology being deployed rather than the processes being changed — the programme is at risk of being technology investment without transformation.
Can leadership articulate the specific process changes that each technology investment is designed to enable? If the answer is unclear, the programme is technology investment without transformation.