The Roads of Reinvention
ESSAY
Thinking
Dewald Pieterse 4 November 2026
The Roads of Reinvention
In ‘Transcending the Loop’, I argued that seeing the copilot model of AI as the desired end state is a fallacy, and that the transformative value of AI lies in automating tasks rather than in assisting people in doing it faster. This essay is intended to turn from why to how. There are many roads to reinvention, but the principles that should guide the journey are mostly universal.
Naturally, AI transformation is about putting a transformative technology to work properly. But, perhaps counterintuitively, the more important part of any real AI transformation is organisational redesign around the new technology, more so than the new technology itself. The technological solutions a company requires must be engineered, and engineered well, but the harder part is to redesign the company’s functions around a new reality that none of them was built for, namely that intelligence is now abundant and no longer a limiting factor.
Designed for Scarcity
Every business function acquired its current form under conditions in which intelligence was scarce. Attention was expensive, so work was batched and made to wait in queues. No one person could hold the entirety of a complex task in mind at once, so projects were divided into stages and handed from one person to the next. People tire and make mistakes, so their work was reviewed in layers. And because those doing the work could not see (nor had the time to see) what everyone else was doing, a layer of managers grew up to carry information up and instructions down. In ‘From Hierarchy to Intelligence’, for example, Jack Dorsey and Roelof Botha have argued that this routing of information is the principal reason corporate hierarchy exists, and that AI now makes much of it redundant.
None of the above arrangements represent some eternal aspect of organised work. Each was a rational solution to a constraint that is now busy lifting. Fundamentally, this is why AI transformation is as much a matter of organisational design as of technical engineering, and usually more so. A business function designed around scarcity of intelligence simply cannot capture the value of abundant intelligence just by having AI perform its existing steps. It has to be redesigned from the ground up.
This is not the first time such an argument has been made. In 1990, Michael Hammer urged companies to stop using computers to mechanise old ways of working and to redesign their processes from scratch, an approach that became known as business process re-engineering (BPR). Hammer was right that work should be organised around outcomes rather than tasks, and that much of the time a piece of work spends inside a company is spent waiting rather than being worked on. One insurer he cited estimated that an application spent twenty-two days in process but was actually worked on for only seventeen minutes. Re-engineering nonetheless became associated with mass lay-offs and failed programmes, and Hammer later conceded that he had been ‘insufficiently appreciative of the human dimension’.
The lessons from the BPR movement are worth keeping in mind. Redesign imposed in a single upheaval, aimed chiefly at cutting costs and indifferent to the people who do the work, always tends to fail. What is different now, however, is that AI can perform judgement-laden work itself. The redesign therefore reaches beyond the process alone to the roles, authority and verification around it, and a redesigned function can now keep improving as it learns from being corrected by its human overseers.
The Business Function as the Unit of Reinvention
A company’s work can be divided and understood at several levels of analysis. At the first level of division are departments, such as ‘finance’ or ‘operations’, which are administrative containers of related functions. By a ‘function’, I mean a distinct but coherent piece of work the business must perform to achieve a specific end, such as onboarding a client, invoicing or procuring trading stock. Each function consists of one or more workflows, by which I mean processes aimed at transforming certain inputs into a desired output, and each workflow is carried out through individual tasks. A job, finally, is the bundle of tasks assigned to one person, sometimes drawn from several workflows and functions.
Of these levels, the correct conceptual unit of reinvention is the business function. The concept of a department is itself a product of scarcity. Because no one person could master more than a narrow field, people had to be organised into groups of specialists, so that accountants sat with accountants and marketers with marketers. AI, which draws on many specialisations at once, removes much of the reason for that grouping, and a function redesigned around it need not respect departmental lines. A job is too disparate a bundle of tasks to be the most sensible unit of automation, and automating a single task in isolation leaves the workflow around it as it was.
Nor is the workflow the right unit on its own: a function may consist of a single workflow, or of several that must be reinvented together, and reinventing the function in the face of AI sometimes makes some of the workflows that once formed part of it unnecessary altogether. The relevant distinction is one of means and ends. The function is concerned with the end the business seeks to achieve, and its workflows are merely the current means of achieving it. Reinvention therefore begins by identifying the end, and then reconsiders the means. The function, together with its constituent workflows, is the correct level at which a company’s work can be rebuilt systematically.
Reconsidering the means follows Musk’s sequence set out in my previous essay: one must question every requirement, delete what is unnecessary, simplify what remains, and only then automate. Of each, one should ask who required it and why. Was it the client, an internal check, a regulator, an insurer, or simply a developed habit? One would be surprised how many steps survive only because no one has thought to question their existence.
Reinventing the workflow in the face of AI therefore involves breaking it down into the units of work, or tasks, that must be performed to transform the inputs into the output. Each unit should be small enough to be verifiable on its own but not so small that the context needed to do it well is lost in passing it from one unit to the next. Each unit is then assigned to the mechanism best suited to it. Work that can be reduced to deterministic rules can be done by conventional software, which is inexpensive and predictable. Work that calls for reading, interpretation and judgement goes to AI. Work that carries serious consequence, or that the law requires a person to do, stays with a human, who receives it with the evidence required for verification already assembled.
Human review is placed where it does the most good. Ideally it comes at the end of a workflow, where a person approves the outcome and answers for it. But where a wrong turn early in a workflow would corrupt everything that follows, review may be required early, before the error spreads. The point at which one workflow feeds into another is also usually a sensible checkpoint for verification. In each case, the principle is that review belongs wherever an error is cheapest to catch, relative to the damage it would otherwise do.
None of this works unless the AI system knows what the company knows. A company’s method, its precedents, its standards and its house style exist mostly in the heads of its senior people. Making that knowledge explicit, in a form the machine can use, is among the most demanding parts of any reinvention, and among the most valuable, because it is what turns a general intelligence into the company’s own individuated solution. For the same reason, that knowledge should remain under the company’s control, held in a form that can move between AI providers rather than being locked into any one of them.
Where to Begin
The greatest leverage lies in automating a company’s innermost loop, or core value-creating flywheel, which is to say the work its clients pay for. Consider a law firm. Automating client intake, timekeeping or invoicing is valuable, but is categorically different from automatic its ability to do quality legal work. An AI system that researches the authorities for an argument, drafts the particulars of claim or writes an opinion in the firm’s house style, with a lawyer steering it and reviewing the result, can collapse days of work into hours, and multiply the productive capacity of the firm. While there are still many skeptics of this proposition, I have seen it happen with my own eyes many times over, and would therefore advise you to suspend such skepticism as you may have.
This does not mean that every AI transformation must necessarily begin with the innermost loop. For a company still cautious about AI, the back office is a sensible training ground. A function such as onboarding or timekeeping carries comparatively little risk, its results are easy to measure, and success there builds the confidence and foundations that later work in the innermost loop will need. Beginning in the back office is far better than not beginning at all.
In deciding where to begin, a company should consider both which of its existing functions to reinvent and which functions that once lay outside it can now sensibly be brought inside. Much of what a company buys in from outside, it buys because the work once required specialists it could not afford to employ, and that, too, is an arrangement born of scarcity. A law firm, for example, might now bring much of its marketing in-house and design it around AI from the outset, although higher-stakes work may, for now, still go to specialists.
What Changes in the Organisation
When functions are redesigned in this way, the organisation around them changes too. Which roles exist, and what each role consists of, are necessarily reshaped. Much of what a junior lawyer does today is performed by the machine, and what remains of the role tilts towards judgement, review and contact with clients. The routing layer of middle management, which existed to carry information between those who decide and those who do, largely falls away, although the work of developing people and holding them to account remains in different forms. Decision rights move closer to the people who answer for outcomes, and even the way work is priced may have to change, since a fee built on billable hours is logically inconsistent with work which takes little human time.
No company is served by pretending that none of this will affect its people. Those who do the work today hold much of the knowledge a redesign needs, and they will share it fully only if they are told candidly what is changing and where they are going. A company that redesigns its functions in order to serve more clients, rather than merely to cut costs, must make it clear to employees that their work is moving above the loop. What this means for the shape of professional firms in particular, I consider in a separate essay.
Pitfalls
Reinvention tends to have consistent causes of failure.
The first is when reinvention is treated as a technology purchase. A company buys an off-the-shelf AI product, as it might once have bought accounting software, and expects transformation to follow. Or it starts from a tool and then looks for a use case, rather than starting from a function and asking how the function should work. Or it hands the transformation mandate to its IT department, whose expertise lies in keeping existing systems running rather than in organisationally redesigning how work is done. Existing products have their place, and integrating them is often wiser than building everything from scratch. But they must be fitted to a redesigned function, not the function to them. One must not confuse means with ends.
The second is when reinvention is treated as a single project. Pilots are launched and never scaled, or a single programme is run to an end date, as though reinvention could be done once and for all. Some companies postpone everything until their data has been cleaned up, an exercise that can absorb years without producing anything, even though modern AI systems are far more tolerant of imperfect data than software of old. Reinvention is better understood as a continuing, iterative loop of its own, in which each redesigned function is measured, corrected and improved, and in which the foundations laid for one function make the next one faster to rebuild.
The third is when it is left to chance, or a wait-and-see approach is followed. Bottom-up adoption, in which each employee experiments with whatever tools they choose, produces scattered gains and no organisational redesign, because no individual employee has the authority to rebuild a function that crosses several departments or even jobs. Reinvention needs an owner, someone with the authority to change how a function works from beginning to end. It only works if it comes from the top.
Guidance on the Road
Could a company carry out such a reinvention by itself? In principle it could, if it had the right people and expertise, but in practice, very few companies do. Reinvention calls for two disciplines that are rarely found together. The first is organisational design, the industrial engineer’s understanding of how work flows through a company and how it ought to. The second is AI engineering, which is not the same as conventional software development and which most IT departments do not possess. Neither can succeed alone. Organisational design without engineering produces fanciful plans that are never built, and engineering without organisational design produces tools grafted onto workflows that should not exist.
This suggests three tests for evaluating who you should turn to for help. You should be skeptical of AI tools and platforms sold in the way software has always been sold, as products to be installed. You should be skeptical of developers who propose solutions before they have spent considerable time understanding the business. And you should be skeptical of consultants who can describe a transformation but lack the hardcore engineering ability to build it.
Reinvention has no final destination at which a company arrives and stops. Each function reinvented lays down knowledge, skills and infrastructure on which the next can be rebuilt more quickly, so that the roads of reinvention are laid as they are travelled. In time, the question of ends and means even reaches beyond the company’s constituent functions to the company as a whole. In the final analysis, its existing departments, hierarchies and jobs were also means, adopted when intelligence was scarce because they were the best way of achieving its overall ends. Reinvention that begins with a single function culminates, if pursued far enough, with the reinvention of the company itself, rebuilt to maximally realise the ends it exists to achieve, now liberated from the scarcity of intelligence.
Reach Out
Back to Thinking