The Person the Difficulty Was Building

There is a category of question almost nobody is asking about AI. Not what it replaces. Not what it accelerates. Not what it makes cheaper. The question is: what does it do to the person using it?

\n

Because here is what the productivity framing conceals. Every AI tool is sold as a remover of difficulty. The thing that took you four hours now takes four minutes. The thing that required expertise now requires only intent. The thing that was hard — hard in the specific, grinding, humbling way that forced you to grow into someone capable of doing it — now takes no effort at all. The difficulty is gone. The friction is gone. The struggle is gone.

\n

And what arrived in its place is output. Clean, efficient, professional output.

\n

But here is what the output framing leaves out: some of the difficulty you removed was the very thing that was building you into the person who could do the work.

\n

Not the skill. The person.

\n

There is a difference. The skill is transferable. You can learn to write in any style, code in any language, analyze with any framework. Skills are modular. They can be acquired and discarded as the market demands. The person is not modular. The person is the accumulated architecture of who you became through the specific difficulties you chose to face — and the specific way those difficulties shaped your patience, your taste, your tolerance for ambiguity, your capacity to sit with discomfort, your willingness to keep going when the thing you were making was not yet good and the feedback was not yet arriving.

\n

Those qualities are not skills. They are dispositions. And they are built through the experience of working through something hard — not through the experience of having the hard thing removed.

\n

When the AI removes the difficulty, it removes the output cost. But it also removes the formation cost. The cost of becoming someone who could handle this kind of problem. That cost was not incidental. It was the mechanism by which the person who would eventually produce excellent work was constructed. The excellent work was the byproduct. The person was the product.

\n

I think about this in the context of my own journey into AI. The moment that started it all was helping my daughter with AP Calculus. Not because the tool saved time — she still had to learn the math herself. Because the tool transformed the experience from frustration to possibility. It did not do the calculus for her. It showed her that the calculus was doable. That was the awakening. That was the design principle. The tool should expand what the human is capable of becoming — not replace the process by which the human becomes capable.

\n

That is a very different design principle than the one most of the industry is currently optimizing for. Most of the industry is optimizing for: what can we remove? What can we automate? What can we make frictionless? What can we collapse from hours to seconds?

\n

Those are all valid questions. But they are questions about the work. They are not questions about the worker.

\n

And the worker is the thing that matters more.

\n

Because the work will always be regenerated by the next tool. The worker cannot be regenerated by anything. The worker is built through the accumulated difficulty of their experience. Through the projects that were hard. Through the clients that were demanding. Through the deadlines that forced a level of excellence the person did not yet possess but had to develop in order to meet. Through the failures that were costly enough to change behavior. Through the moments where the person had to grow into the size of the problem — because the problem was not going to shrink to fit the person.

\n

Remove that growth pressure and you remove the mechanism by which the person becomes capable. Not just skilled. Capable. The difference matters. Skilled is having the technique. Capable is having the character. The technique can be transferred. The character cannot. And character — the willingness to persist, the taste to know when something is not yet right, the patience to sit with ambiguity, the courage to ship something imperfect because the market will decide and you cannot control the outcome — that character is built through the experience of facing difficulty and choosing to engage with it rather than avoid it.

\n

The tool does not know the difference between removing unnecessary friction and removing necessary formation. The tool removes friction. All friction. The friction that was waste and the friction that was training data for the human soul. The friction that was slowing you down and the friction that was making you stronger. The friction that was cost and the friction that was tuition.

\n

The tool cannot tell the difference. And the person using the tool almost never asks the question that would reveal the difference: what am I becoming by letting the tool do this?

\n

Not what am I saving. What am I losing.

\n

Because every time you let the tool remove a difficulty, you are also removing the opportunity to grow through that difficulty. Sometimes the difficulty is waste — a tax that produces nothing and should be eliminated. The formatting fix. The data entry. The scheduling back-and-forth. Those are costs that do not build you. They should go.

\n

But some of the difficulty is formative. The difficulty of writing a clear email to a client who is frustrated — that difficulty is building your capacity for empathy under pressure. The difficulty of wrestling with a complex problem before responding — that difficulty is building your capacity for patience and nuance. The difficulty of sitting with a blank page before the insight arrives — that difficulty is building your tolerance for the creative void where all original thinking actually happens.

\n

Remove those difficulties and you do not just remove the work. You remove the person the work was making.

\n

Here is the diagnostic that should change how every professional thinks about their use of AI going forward. For every task you are tempted to automate, ask yourself: what person was this task building? Not what output is this task producing — what person is the experience of producing this output constructing?

\n

If the answer is nothing — if the task is purely mechanical, purely tax, purely cost with no character-forming dimension — then automate it. Remove it. Let the tool do it. You are not losing anything.

\n

But if the answer is something — if the difficulty of the task is building your patience, your taste, your capacity for nuance, your tolerance for ambiguity, your willingness to engage with something that does not yet have a clean answer — then be very careful before letting the tool do it for you. Because you are not just removing a task. You are removing a development opportunity. You are not just saving time. You are losing the person you were becoming through the use of that time.

\n

This is the distinction almost nobody is making. The distinction between difficulty that is waste and difficulty that is formation. Between friction that slows you down and friction that makes you stronger. Between cost that should be eliminated and cost that was the tuition for the person you were becoming.

\n

The tool will automate all difficulty equally. It does not know the difference. You do. You have to know the difference. Because if you automate all difficulty — if you let the tool remove every friction, every struggle, every moment of productive discomfort — you will get efficiency. You will get output. You will get productivity.

\n

And you will get a person who has never had to grow into the size of a problem. Who has never had to develop the character to handle the hard thing. Who has never had to sit with the discomfort of not-knowing long enough for the insight to arrive. Who has never had to face the blank page and choose to engage with it rather than prompt the tool.

\n

That person will be efficient. That person will also be hollow. Not because they are weak — because they were never asked to be strong. Not because they lack skill — because they never had to develop the character that the difficulty would have built.

\n

So choose carefully. Not all difficulty is worth keeping. Some of it is pure waste. Some of it is the thing that should have been automated a decade ago. But some of it is the thing that was making you who you need to become. And the thing that was making you who you need to become — that is the thing you should protect most carefully from the tool that is designed to remove it.

\n

The tool should improve the human experience. Not reduce it. It should awaken creativity. Not flatten identity. It should expand what you are capable of. Not remove the difficulty that was building the capacity.

\n

The difference between those two design principles — automation as removal versus automation as expansion — that is the difference between a future where people are more capable and a future where people are just more efficient. And the more efficient future will feel hollow in ways nobody planned for.

\n

Because efficiency is not the point. The person is the point. And the person was built by the very difficulty you are now trying to automate away.

\n

Some of that difficulty deserves to go. Some of it deserves to stay. The person who can tell the difference — that is the person who will use the tool well. The person who cannot tell the difference — that is the person the tool will use.

\n

The person the difficulty was building is still here. Whether they remain is up to you.