The Self and the Machine

Part I of Between Panic and Euphoria

By Daniel Dines with Claude and GPT.

A friend of mine, a lawyer, said something to me recently that I cannot shake.

The painful thing was not that her craft might be replaced. She had made some peace with that. The painful thing was that the self she had built through two decades of work might no longer be needed.

The cases she had taken. The judgment she had developed. The relationships she had built. The way she had learned to think. The reputation she had earned. All of that had formed her into a particular kind of lawyer. Now the machine could reproduce much of the visible work on demand.

For her, the money was not the deepest point; for many people it will be. What she named was harder: the self she had become. And the machine did not need her to have become anyone. I think she named more precisely than most accounts what is actually at stake. Not only the income. The self.

If she is right at the individual level, the same logic scales. Take the maximalist fantasy seriously for a moment: a version of the future in which fifty million Einstein-level problem solvers, willing to do any work, are available for pennies in a data center. If that is the version coming, her concern is not specific to her or to law. It is everyone’s. Every kind of work that built a self in someone is about to be reproduced on demand by something that did not have to become anyone.

Here is the concrete test: imagine adding one of those Einsteins to your company.

IT creates the account. It gets email, Slack, calendar, documents, permissions, and a virtual machine. You invite it to meetings. You assign it tasks. You ask people to onboard it. You expect it to learn the company. You expect it to mentor others. You expect it to become senior.

This sounds possible because modern companies already work this way. COVID-19 proved that organizations can run through screens, documents, calls, chats, tickets, dashboards, repositories, and virtual machines.

But remote work did not turn the interface into the person.

A remote human brings the self through the screen. The account is only the channel. The human arrives with memory, ambition, shame, pride, reputation, loyalty, fear, social instinct, and something to lose.

The AI account is different: you have created access and connected capability to the company, but you have not hired a self.

Her concern is real either way. The question is whether the version she fears is the version coming, and what kind of future the answer leaves room for.

That is what this essay is about.

Two audiences, one program

Every executive I talk to is trying to accelerate AI in their company and does not know how. The board wants the plan. The competitors are moving. The vendors are selling. The headlines are screaming. The actual path through the work is unclear.

Inside the same companies, employees are anxious. Not just about the next two years. About their futures. About their children’s futures. About whether the work they built a life around still exists in five years.

These are not two problems. They are one problem seen from opposite sides. AI adoption and workforce transformation have to happen at the same time. Not AI in the CTO’s office and workforce redesign six months later in HR. Not pilots first and people later. Not headcount first and architecture later.

This is one program. To deploy AI well, leaders have to know what work the system can be trusted with. To redesign the workforce well, they have to know what work AI absorbs and what work still needs humans. Neither question has an answer that does not go through the other.

Separate them and both fail. AI gets deployed into old bottlenecks, so individual output rises but the company does not move faster. Or leaders cut people before they understand what those people were carrying: trust, culture, customer memory, mentorship, initiative, and judgment under consequence.

The savings show up quickly; the damage shows up later.

The right program maps the work, builds the map and rails the agent will act inside, redesigns roles at the same time, and preserves the human capacities the new system still needs. Do these together, or do not pretend you are transforming the company.

The point is not to slow adoption down. The point is to accelerate adoption through an operating model that can survive contact with real work. Faster AI adoption and workforce transformation are the same program: the technical system and the human system have to be designed together.

I run an automation company. That is my declared bias. If this argument is right, AI adoption requires more than models. It requires automation, orchestration, governed actions, audit, rollback, workflow, and substrate. Companies like mine benefit from that conclusion.

But the argument is not that AI is weak. The argument depends on AI being strong. AI is the new cognitive layer of the enterprise. It drafts, classifies, recommends, translates, synthesizes, and increasingly builds automations. Humans remain needed where the institution needs initiative, trust, culture, mentorship, commitment, and judgment by name. Automation remains needed where execution must be exact, cheap, auditable, repeatable, and governed.

The claim is not that one replaces the others. The claim is that the next enterprise coordinates all three.

The thesis

The transition is not simply AI replaces humans. It is the enterprise being split into three jobs:

AI proposes. It drafts, classifies, summarizes, recommends, translates, structures, and generates candidates at scale.

Humans decide. They set direction, own judgment, carry trust, face customers, keep culture, and bear consequence by name.

Automation executes. Workflow engines, rules, transactions, systems of record, audit trails, and deterministic systems do the work that must be done cleanly every time.

The model drafts, the human owns the call, and the system executes.

The combination produces work no component could produce alone. AI alone makes too many small errors at speed to be trusted with consequence. Humans alone are too slow and too narrow to absorb the volume the enterprise produces. Automation alone is too brittle for the long tail of judgment cases.

The three together scale. This is not a branding exercise. It is what works when you take each component seriously.

The claim is simple. Put AI where it generates and reasons well. Put humans where judgment, trust, initiative, and consequence still need a person. Put automation where the action must be executed cleanly every time.

The consequence is also simple: every AI deployment decision is also a workforce decision. Every workforce decision is also an AI architecture decision. You are deciding who proposes, who decides, who executes, who verifies, who owns the relationship, who carries the culture, and who trains the next generation.

That is one design problem, not two — and it has to be scored honestly. Every AI program has two ledgers: a productivity ledger and an institutional ledger. The first records what got faster, cheaper, or more scalable. The second records what was lost, preserved, or rebuilt: trust, mentorship, customer memory, escalation judgment, culture, apprenticeship, accountability. Most companies track only the first ledger. That is how they hollow themselves out while reporting productivity gains.

Why the model cannot be the whole system — and what the rest of the system is made of — is where Part II begins.

Drafted and edited with AI assistance. The argument, the examples, and the responsibility are mine.