Digital transformation adds complexity as reliably as it adds capability. Organisations that combine transformational investment with rigorous simplification discipline — deliberately removing unnecessary complexity from processes, systems, and governance structures — consistently achieve competitive positions that capability investment alone cannot create.
The Complexity Accumulation Problem
Every digital transformation programme adds complexity. New platforms introduce new interfaces, new data models, new operational procedures, and new dependencies. New processes create new handoffs, new approval steps, and new exception handling requirements. New governance frameworks layer additional oversight onto organisational structures already burdened with the accumulated oversight of previous frameworks. The net effect, across a decade of transformation investment, is often an organisation that is objectively more capable than it was — with more technology, more data, more governance, and more compliance infrastructure — but also objectively harder to operate, harder to understand, and harder to change.
This is the paradox at the heart of many digital transformation programmes: the investment designed to make the organisation more agile has made it more complex, and complexity is the enemy of agility. The organisations that have the greatest competitive flexibility are not those that have implemented the most technology. They are those that have remained clear about what they are trying to do and have been willing to remove complexity from their operations as deliberately as they add capability.
The discipline of simplification — of deliberately identifying and removing unnecessary complexity from processes, systems, data structures, governance frameworks, and organisational structures — is one of the most valuable and most underinvested capabilities in the Australian enterprise sector. It is underinvested partly because complexity accumulation is slow and gradual while the benefits of simplification are diffuse, and partly because the individuals and teams who own complex systems and processes are rarely incentivised to simplify them.
The provocative framing of the Chief Simplification Officer is, at its core, a way of making the point that simplification requires the same organisational authority and sustained management attention as any other strategic priority — and that, in most organisations, it has neither.
What Complexity Costs the Organisation
The cost of organisational complexity is rarely measured directly, because complexity does not appear as a line item in the budget. It appears as the aggregate overhead of operating environments that require more coordination, more explanation, more training, more exception handling, and more management attention than simpler alternatives would need.
The organisations that consistently out-innovate their competitors are, almost without exception, simpler to operate than those they are out-competing. Complexity is the enemy of agility, and transformation that adds the former while claiming to create the latter is working against itself.
The Platform Trap and the Simplification Imperative
The instinct to solve complexity with another platform is one of the most persistent and most expensive failure modes in enterprise technology. Complex data integration? Buy an integration platform. Complex reporting requirements? Buy a business intelligence platform. Complex workflow management? Buy a workflow automation platform. Each solution addresses a real problem. Each solution also adds to the overall complexity of the technology estate, creates new dependencies, requires new operational capability, and generates new data governance challenges.
The alternative to solving complexity with technology is simplifying the processes and structures that generate the complexity in the first place. This is more demanding work, because it requires examining why processes are complex, whether the complexity is necessary, and what changes to organisational structure, governance, and decision-making authority would allow simpler approaches to be used. Technology solutions are attractive partly because they address the symptom without requiring the organisation to confront the structural conditions that produce it.
The simplification discipline starts with a different question from the one that drives most technology investment decisions. Instead of “what capability do we need to address this complexity?” it asks “why is this complex, and does it need to be?” The second question is harder to answer, requires more organisational authority to act on, and produces more durable value when answered correctly.
The Simplification Mandate and Where It Should Sit
Simplification does not happen organically in large organisations. The structural incentives run in the opposite direction: teams protect their processes, technology owners protect their platforms, governance owners protect their frameworks, and nobody owns the aggregate complexity that results from the combination of all these individually rational protective decisions.
Creating a simplification mandate — explicit organisational authority and accountability for identifying and removing unnecessary complexity — requires placing it at a level that can cut across these structural incentives. This means either creating a dedicated leadership function with the authority to challenge and simplify across business units and technology domains, or embedding the simplification mandate explicitly in the CIO, COO, or CEO role with the governance weight to make it effective.
The simplification mandate should operate across at least three domains: technology estate rationalisation, removing platforms and capabilities that are duplicated, underutilised, or no longer aligned with current requirements; process simplification, eliminating steps, approvals, and handoffs that add cost without adding value; and governance rationalisation, consolidating oversight frameworks that have accumulated layers without proportional risk reduction. In each domain, the mandate requires both the authority to decide and the capability to execute — and in each domain, the capability requirement is often underestimated.
Simplification as the Strategic Complement to Transformation
The argument for a Chief Simplification Officer is not literally an argument for a new executive role. It is an argument for treating simplification with the same organisational seriousness as transformation — for ensuring that the drive to add capability is balanced by an equivalent drive to remove unnecessary complexity, and that the organisation’s leadership structure reflects the strategic importance of both imperatives.
Boards and executive teams that want to assess their organisation’s relationship with complexity should ask: what has the organisation removed from its technology estate, its process portfolio, and its governance structure in the past twelve months? If the answer is very little, the organisation is accumulating complexity faster than it is removing it — and the competitive consequences of that accumulation will eventually exceed the benefits of the capabilities being added.
Digital transformation without simplification discipline is a strategy for building a more capable, more complex, and ultimately less competitive organisation. The organisations that combine transformational capability investment with rigorous simplification discipline will, over time, achieve competitive positions that neither investment alone can create.
What has the organisation removed from its technology estate, its processes, and its governance structure in the past twelve months? If the answer is very little, complexity is accumulating faster than it is being removed — and the consequences will eventually outweigh the benefits of the capabilities being added.