From Elon Musk to Practical Deredundancy
“I reckon about 80% of that could go tomorrow and nobody would suffer.”
That was psychiatrist / philosopher Iain McGilchrist speaking about the “dead weight of bureaucracy” surrounding teachers, universities, hospitals and schools.
His suggestion was wonderfully provocative: look critically at the managerial and administrative superstructure and ask how much of it could simply disappear.
I immediately thought: Yes.
And then: Hang on. How would we actually know?
Because something can be frustrating, bureaucratic and apparently pointless while quietly carrying an important function.
And something can work perfectly well while no longer having any good reason to exist.
That distinction becomes particularly important as AI gives us extraordinary new powers to make existing systems faster and cheaper.
What if we’re about to become extremely good at optimising things that shouldn’t exist?
McGilchrist made the comment during a conversation with John Vervaeke and Daniel Schmachtenberger on the psychological drivers of the metacrisis.
Elon Musk and the other answer: delete it
There is another highly visible contemporary response to organisational complexity.
Delete things.
Elon Musk’s restructuring of Twitter/X and his later DOGE involvement brought an unusually aggressive version of organisational subtraction into public view.
Musk has explicitly described his engineering approach as beginning by questioning requirements and then trying to “delete the part or process,” arguing that people have a tendency to add things back rather than remove them.
There is something compelling about this.
Organisations accumulate.
Committees acquire subcommittees. Temporary procedures become permanent. Reporting requirements generate further reporting requirements. Systems built to solve yesterday’s problems remain long after their originating conditions have changed.
Sometimes nobody can quite remember why something exists.
But Musk’s approach also makes the inverse problem unusually visible.
Deletion is not proof of redundancy.
A department might look expendable until its absence reveals a dependency nobody had noticed.
A procedure might appear bureaucratic until something goes wrong and we discover that it was carrying accountability.
Apparently duplicated expertise might actually provide resilience.
Spare capacity might look inefficient precisely until the moment it is needed.
So we have at least two tempting responses to cumbersome systems:
Optimise them.
Or:
Delete them.
Neither, by itself, answers the harder question:
What can genuinely disappear without destroying something consequential?
We already have a substantial vocabulary for this
I started looking around.
Unsurprisingly, organisations have been trying to remove unnecessary complexity for a very long time.
There is already an extensive neighbouring vocabulary.
| Approach | What it typically seeks to achieve | A question it may leave unresolved |
|---|---|---|
| Process simplification | Reduce unnecessary steps and complexity | Does the process itself still need to exist? |
| Lean management | Eliminate waste and improve value delivery | Who determines what counts as value? |
| Delayering | Remove management layers and shorten decision pathways | What judgement, coordination or accountability were those layers carrying? |
| Administrative burden reduction | Reduce paperwork, reporting and compliance costs | Which apparent burdens protect something consequential? |
| Business process reengineering | Radically redesign workflows for improved performance | Are we redesigning around purposes that still warrant pursuit? |
| Organisational rationalisation | Consolidate overlapping functions, systems or resources | Is apparent duplication actually carrying resilience or independent judgement? |
| Cost cutting | Reduce expenditure | What capabilities disappear alongside the costs? |
| Automation | Transfer tasks from humans to technological systems | Should those tasks continue to exist at all? |
| Subtractive redesign | Improve something by removing rather than continually adding | By what criterion do we determine that a subtraction is beneficial? |
| Purpose-preserving simplification | Remove unnecessary activity while protecting essential function | What if the inherited purpose itself needs reconsideration? |
This isn’t an argument that these disciplines never ask such questions.
Sophisticated practitioners certainly do.
The third column is deliberately phrased as a question each approach may leave unresolved.
But putting them alongside one another helped me see the problem more clearly.
We can simplify a process.
We can remove organisational layers.
We can eliminate waste.
We can automate tasks.
We can redesign workflows.
We can even become extremely good at preserving the purpose of an institution while radically simplifying how that purpose is accomplished.
And still not ask:
Why does this purpose appear necessary in the first place?
This is where I encountered Practical Deredundancy
Dr Leon Tsvasman uses the term Practical Deredundancy. https://leontsvasmansapiognosis.substack.com/p/before-you-automate-it-prove-it-should?utm_source=share&utm_medium=android&r=3aclg
When I first began exploring his idea, I translated it into something I could readily understand:
Remove unnecessary mediation while preserving consequential function.
Or perhaps:
Purpose-preserving simplification.
That seemed pretty good to me.
Leon corrected me. 😂
Because the more radical implication of deredundancy is that the purpose itself cannot automatically be exempted from examination.
A procedure may efficiently perform a function.
That function may successfully serve a purpose.
And that purpose may be an inherited response to conditions that no longer exist.
So we can follow the chain further:
PROCESS → FUNCTION → PURPOSE → CRITERION → CONDITIONS
At each level we can ask:
Why is this necessary?
And eventually we may discover that something we have been treating as an unavoidable organisational necessity is actually a consequence of conditions that could themselves be changed.
That is a very different proposition from:
How can we do this more efficiently?
It is also different from:
What can we cut?
AI makes this question urgent
This is where Practical Deredundancy became particularly interesting to me.
Because AI is astonishingly good at helping us perform existing activities differently.
A reporting burden consumes enormous staff time?
Automate the report.
A compliance process requires repetitive checking?
Build an agent.
A meeting generates administrative work?
Summarise it automatically.
An organisation produces huge quantities of documentation?
Let AI produce it faster.
All potentially useful.
But there is a prior question:
Should this activity still be necessary at all?
Leon put the danger wonderfully:
“Otherwise AI might merely make obsolete institutions cheaper to maintain.”
That stopped me.
Because efficiency cannot tell us whether something warrants continuation.
A perfectly functioning system can be perfectly redundant.
But we shouldn’t simply start deleting things either
This is where McGilchrist’s provocative 80% becomes difficult in practice.
Imagine walking into a university and announcing:
Right! Which 80% are we deleting?
😬
How do we know?
Something that looks redundant from the standpoint of present performance might carry:
accountability, institutional memory, resilience, judgement, corrigibility, exploratory capacity or unrealised possibility.
This particularly matters because organisations often contain deliberate redundancy.
Two people knowing how to perform a critical function might look inefficient — until one leaves.
Unused capacity might look wasteful — until circumstances change.
A human checkpoint might look slower than automation — until an unusual case requires judgement that the automated system cannot exercise.
And experimentation is almost definitionally inefficient if measured only against today’s outputs.
So Practical Deredundancy cannot simply mean less.
Nor does it mean preserving everything that currently serves some identifiable purpose.
The harder inquiry is:
Which necessities could cease to be necessities at all — without diminishing our capacity to originate, revise and answer for consequential decisions?
And then comes the question I find most exciting:
What new human possibilities might become available as a result?
That changes the emotional character of the inquiry.
We’re no longer merely hunting for waste.
We’re asking what all this organisational machinery is preventing people from having the capacity to do.
I want to test this in the real world
This is where my own role begins.
I am not claiming to have developed another organisational efficiency methodology.
I haven’t.
I’m interested in finding out what happens when Tsvasman’s research architecture encounters a real inherited organisational necessity.
So I am developing a small Practical Deredundancy pilot.
I am looking for one or two organisations willing to bring a substantive process, practice or administrative burden whose necessity can be examined without reducing the inquiry to cost-cutting.
We might begin with deceptively simple questions:
What is this process actually doing?
What does it preserve?
What would disappear if we removed it?
What conditions made it necessary?
Do those conditions still exist?
What criterion makes this activity appear necessary?
Could we change the conditions so that the necessity itself disappears?
And:
What human possibility might become available if it did?
Perhaps we discover that the process really is necessary.
Perhaps we discover that part of it is carrying something nobody realised.
Perhaps we discover that we’re automating an activity we shouldn’t be doing.
Or perhaps we discover that the most interesting intervention isn’t changing the process at all.
It is changing the conditions that made the process necessary.
That’s what I want to find out.

Practical Deredundancy is grounded in the research architecture developed by Dr Leon Tsvasman. I am independently developing and testing an application and facilitation layer for real organisational cases.
If you have responsibility for an inherited organisational practice whose necessity deserves serious examination, I’d be interested in hearing from you.





