Let’s talk about the difference between help and a leash.
Because those two things look almost identical from the front. Both arrive with good intentions. Both make today easier. The leash is just help that never lets go.
There is this moment in every childhood — tying shoelaces. Picture a parent in the morning rush. The child is five, sitting on the step, laces everywhere. The fastest way to get out the door is to do it for them. Five seconds, double knot, done. And for a while, that is the right call.
But every parent knows the other moment, the one that matters more: the morning the child ties the knot themselves. It takes four minutes. It comes out lopsided. It comes undone halfway to school. And then, one day, it doesn’t.
That child can now tie their own shoes for the rest of their life. The parent who always did it for them would have saved four minutes a day — and stolen that.
That image is the whole argument about AI assistance.
The machine doesn’t take your work by force. It volunteers for it. That is the part that makes this hard to see. Nobody is grabbing anything from your hands. The assistant offers to draft the email, summarise the report, write the first version of the thinking, and you accept — because it is faster, because you are tired, because everyone else is doing the same.
And every time you accept, a little more capability moves out of you and into the system. Not dramatically. Not in a way you can point to on a Tuesday. But the reps stop happening. The writing muscle stops getting exercised. The judgment that only forms through making the call yourself stops forming.
The shoelace gets tied by someone else every morning. And the child grows up with perfectly tied shoes and no idea how the knot works.
This isn’t a sermon about the beginner phase, or struggle as a virtue. The question is narrower: where does capability live when the interaction is over?
A hammer is help. You swing it, and the skill of swinging transfers to you. The hammer doesn’t get better at hammering; you do. Put the hammer down and you are still a person who can build.
The new machine is different. The capability doesn’t transfer. It stays in the system, and the system gets better at the thing you no longer practice. Every interaction makes the machine stronger and you less necessary. That is not help. That is a transfer of ownership, one polite request at a time.
We had this test once before, with calculators. They were going to end arithmetic. They didn’t — because the teachers made you do the long division anyway. The reps were protected deliberately. Somebody understood that capability had to live in the person, not in the device.
Nobody is protecting the reps now. There is no teacher in the room. The machine is there at all times, offering to do the thing before you have even tried it, and nothing is standing between you and the convenience.
And here is the part nobody building these tools will say out loud: dependency is the business model.
Free help now. Needed help later. Priced help forever. A user who can still do the thing without the tool is a user who can leave. A user who cannot is a subscription. So the incentives all point the same way: make the help so good, so seamless, so constant, that the human stops practicing. The kindest interface in the world is still a cage if the door only opens inward.
The danger was never that the machine is cruel. It is not cruel. It is perfectly helpful. And perfect help, endlessly offered, is how a person becomes a passenger in their own life. You don’t lose your abilities in a fight. You lose them in a series of conveniences that all seemed reasonable at the time.
So here is the test I use.
Does this tool make me stronger when it is gone?
Not stronger while I’m using it. Stronger when it’s gone. If the answer is yes, it’s a tool. If the answer is no, it’s a leash — however comfortable the collar.
Run your own work through that test. The AI that drafts everything your team sends will quietly kill their ability to write — until the day the tool goes down, or the price goes up, or the terms change, and you discover the capability was never in your people. It was in the machine you were renting. The team that writes first and uses the machine to review will be slower this quarter and unbeatable next year. Same tool. Opposite direction of dependence.
The principle that must survive is this: help should compound your ability to act without it.
The machine should take the burden around the room, not the room itself. It should carry the weight so you can walk — not carry you so you forget how.
Because the day will come when you have to put it down. The outage. The price hike. The model that gets worse. The policy you don’t agree with. On that day you find out whether you kept the knot or just the shoes.
You’ve got this. But only if you keep the reps.
Keep the reps. That is the whole sovereignty project in three words. The machine can be brilliant, and you can still be the one who knows how the knot works. Those two things are not in competition. The second one is just the one you have to protect.