Why technology becomes an obligation — and what to do first
In every workshop or leadership conversation, someone asks the same question: "What technology would you recommend to solve our problems?" There is always a new option. Always a silver bullet.
Why technology becomes an obligation — and what to do first
In every workshop, coaching session, or leadership conversation, someone asks the same question.
"What technology would you recommend to solve our problems?"
AI, platforms, dashboards, tools — there is always a new option. Always a silver bullet.
Technology begins as an option.
If we are not careful, it becomes an obligation — often an expensive one.
Editor's note — where this sits
This essay sits in the Physics layer of the Idea to Value system — the diagnostic system for understanding what sits between an idea and the value it creates. Here, the argument is about what actually occupies that space — people, not tools — and why technology, introduced without that understanding, tends to obstruct the very flow it was meant to support. It extends the thinking in Mistaking the Map for the Territory and Communication as a Super Power.
The Idea to Value system — five layers
Comfort in the machine
Technology is comforting. It promises efficiency, integration, speed, and simplicity. It offers dashboards where uncertainty once lived. It gives the impression of control.
Inside organisations, it often delivers something else: more tools to manage, more licence costs, more integrations, more training, more migration, more places for work to hide. The organisation becomes busy managing technology rather than creating value.
The human middle
The reality is uncomplicated.
Between every idea and the value it creates, there are people. Their clarity, their habits, their conversations, their relationships, their ability to cooperate, coordinate, and decide. People take ideas and turn them into value. Most problems arise here — not in software, not in process diagrams, not in dashboards.
Trying to fix human problems with technology is like buying a megaphone. It amplifies what is already there. It does not change what is broken.
Technology as obligation
Once introduced, technology rarely remains neutral.
It demands configuration, governance, training, updates, sometimes entire platform migrations. It becomes a structure people must adapt to — rather than a tool that adapts to people. The organisation bends around the tool. Work reshapes itself to fit the system. The obligation grows quietly.
Effectiveness before efficiency
John Seddon captured the order simply: study the problem, fix the problem, then bring in technology.
Technology should support effective work — not compensate for ineffective work. There is little value in making something ineffective more efficient.
A different question
When someone asks which tools to adopt, I ask something else.
"Are you already good at turning ideas into value?"
If the answer is yes, technology can help you go faster. If the answer is no, technology will help you go faster in the wrong direction.
Start with people. Create value together. Then use technology to accelerate.
The order that endures
Sometimes technology is intrinsic to the product — infrastructure, platforms, pipelines. Even then, effectiveness precedes selection.
Tools do not create value. People do. Technology can amplify human systems. It cannot replace them.
And when we forget that, technology stops being an option and quietly becomes an obligation.
Cultivated Studio
The argument is here. The diagnostic is in Studio.
Studio members get the extended frameworks for applying this thinking in practice — how to audit technology obligation in an existing organisation, how to sequence the people work before the tooling decisions, and how the Idea to Value system functions as a diagnostic for technology selection rather than a justification for it. If you're sitting in a room where someone is about to buy a platform to fix a people problem, Studio has the tools for that conversation.
Explore Cultivated Studio →
