Design + Organisational Thinking
Design for Independence
What if the best measure of our work is how well it continues without us?
Have you ever been contacted by a client about a minor detail they should have been able to handle themselves? Or felt that your work was only as reliable as your presence?
I used to think that indispensability was a sign of value. Then a piece of career advice from my father gave me a question I could not ignore.
The advice—and the problem inside it
“Work to make your employer dependent on you.”
I took those words to heart. Over time, however, I began to see the drawbacks of creating dependency. If a process succeeds only because one person is present, it is fragile by design. It restricts the team, complicates transitions and eventually restricts the person everyone depends on.
That tension led me to the idea of Design for Independence.
What is Design for Independence?
In an employee–employer relationship, it means creating processes and systems that remain useful without our constant involvement. The system should carry the knowledge, intent and safeguards that would otherwise exist only in one person’s head.
This takes planning, iteration and a long-term view. It also forces us to make decisions transparent, introduce checks and balances, and clarify what should happen when circumstances change.
- 01
Make the process visible
Document the reasoning, sequence and ownership behind the work so that knowledge is shared instead of remaining implicit.
- 02
Preserve the intent
Explain which qualities must remain consistent and why, not only which steps someone should repeat.
- 03
Create safe boundaries
Give people enough control to act independently while protecting the decisions that should not change.
- 04
Plan for the handover
Treat transitions as a design condition from the beginning rather than an emergency at the end.
Independence creates resilience
Transparent systems make transitions less disruptive when employees change roles or leave. They also create space for growth: people can move towards larger responsibilities instead of remaining trapped as the only person capable of completing a recurring task.
Designing this way compels us to contribute more than the immediate deliverable. We have to anticipate possible failures, make our reasoning understandable and leave behind a structure that others can improve.
The work is not truly complete when the task is finished. It is complete when the value can continue.
Independence is not the same as automation
There is a risk in pushing the idea too far. A highly mechanised process can remove judgment, creativity and the human knowledge that helps people respond to unfamiliar situations.
The goal is therefore not to eliminate human input. It is to separate routine dependence from meaningful participation.
Systemise
- Repeated instructions and predictable decisions
- File structures, standards and approval checks
- Knowledge needed for routine maintenance
Protect
- Human judgment in unfamiliar circumstances
- Space for interpretation, creativity and dissent
- Conversation around consequential decisions
The principle extends beyond employment
Design for Independence applies wherever intent must survive beyond its original creator.
- 01
Brand identity
Brand guidelines preserve a recognisable essence even after the original designers move on.
- 02
Repairable products
Platforms such as iFixit help people maintain products without permanent dependence on repair services or the brand itself.
- 03
Durable organisations
Apple, Microsoft, Google and Braun continued to evolve after their founders stepped away because their values were carried by institutions, cultures and systems.
A CAD thought experiment
Industrial designers encounter small dependencies throughout production. A manufacturer may need to change a fillet radius or adjust another minor CAD detail, yet still depend on the designer to reopen the model and make the modification.
What if a limited-functionality CAD tool allowed the manufacturer to make those changes independently—within boundaries defined by the designer?
Set limits
The designer identifies which dimensions and features may be changed safely.
Share control
The manufacturer receives only the adjustments needed for production.
Validate
The software checks every change against the original constraints.
Keep moving
Minor corrections continue without interrupting the designer’s larger work.
The manufacturer gains useful autonomy, the designer retains control over intent, and both spend less time coordinating minor revisions. It is one small example of how independence can be designed into a tool.
Why the idea matters now
AI is freeing more processes from direct human dependence. That makes the question more important, not less. We need to decide which knowledge should be embedded in tools, which decisions require people, and how responsibility moves between them.
The opportunity is to create systems that are self-sufficient without becoming thoughtless: resilient enough to continue, transparent enough to question and flexible enough to improve.
Conclusion
Design the value to outlast your presence
Design for Independence asks us to leave behind more than a finished task. It asks us to leave clarity, usable knowledge and room for the next person to act.
Done carefully, it can produce processes, products and organisations that are more resilient, more sustainable and more capable of growth—without removing the human judgment that made them valuable in the first place.
The aim is not to make people unnecessary. It is to make progress possible without unnecessary dependence.
