Chapter 3 · The colleague nobody interviewed
One sentence, at the end of a meeting
The monthly operations review at Ostermill runs the last Tuesday of the month and it runs long. Tom Brindle said it at the end of the February one, after the aging report had been on the screen for eleven minutes and everyone had run out of things to say about it.
We should get some AI on this.
Nobody in that room heard a proposal to add a decision-maker to the company. They heard a suggestion about software, which is what it sounded like, and it went into the minutes as an action item for Dana to look into.
Notice what the sentence does not contain.
There is no comparison in it. It proposes a technology against nothing, and against nothing every technology looks brilliant. It does not name what the thing would decide, or what it would be allowed to do without asking, or who would answer for it when it was wrong, because those questions do not attach to software and everyone present understood Tom to be talking about software.
It does not even contain a noun for the thing that would do the work. AI is a field. A field cannot be given an account, a boundary, or a manager.
He was not talking about software, and he could not have known he was not. This book will call the thing an agent, which is the word Tom needed and did not have. The category was missing from the room, and so was the word, and of the two the category is the larger absence.
What a company does before it adds an actor
Think about what Ostermill does when it adds a person. Any person.
A new receivables clerk goes through a posting, a screen, two interviews, a reference check, an offer contingent on a background check, a start date, an onboarding week, ninety days of probation, and a manager who owns their output from the first morning. A contractor gets a statement of work, acceptance criteria, an end date and a termination clause. A vendor survives security review and whatever procurement has learned to be suspicious about since the last time. Even a new server gets a change ticket, a rollback plan and somebody's name on it.
None of that is bureaucracy for its own sake. It is scar tissue. Every gate in that sequence exists because a company somewhere got burned without it, and most of them were installed by people who were personally present for the burning.
The agent skipped all of it.
It arrived as a software integration, because integration was the only category on the shelf, and integrations do not get interviewed. On a Monday it started reading the records Ruth used to read and making the class of decisions Ruth used to make. Nobody checked its references. Software does not have references.
Except this software does, in every sense an organization chart cares about, and writing the file that was never created is a clarifying exercise.
Employment history: trained by a company you have never visited, on material you cannot inspect, to preferences nobody wrote down for you. Temperament: agreeable under clear instruction, and under ambiguity reverting to defaults chosen by its maker, which you will discover one situation at a time. Cultural fit: unknown, and worse than unknown, unknowable, because the culture it absorbed is not local to your company and no interview probes it. References: none. Probation: none. Review cadence: none scheduled. Termination process: ask IT and watch them think about it for the first time.
A company that hired a person on that file would deserve what followed.
Some of them are already running in your company.
The objection, which is correct and beside the point
The obvious objection arrives here and it deserves a straight answer rather than a dodge.
Agents are not people. They are tools. Treating them as staff is anthropomorphic confusion, it flatters the technology, and it invites a category of sloppy thinking this industry has more than enough of already.
All of that is right about the metaphysics. None of it touches the argument.
The organization chart does not care about consciousness. It cares about who acts. A tool waits to be picked up, does exactly what it is told, and stops. This thing acts, at machine speed, with authority somebody delegated to it, and it does so in conditions its maker never described to you.
The entire apparatus of hiring gates was never about the inner life of the hire. It was about the risk of adding an actor to a system that already works. Strip out the personhood and the risk sits exactly where it was. All you removed was the paperwork.
The paperwork was the protection.
There is a second objection, quieter and better. Some of those gates are about personhood and nothing else: employment law, benefits, the duty of care an employer owes a human being. Those do not transfer and should not. What transfers is the narrower set, the ones that exist because an actor with authority can do damage, and that set is most of the sequence.
What Tom actually proposed
Go back to the sentence, now that the file exists.
We should get some AI on this.
Read against the hiring sequence, that sentence proposes hiring somebody to make forty-one judgment calls a week, with no posting, no interview, no reference check, no probation, no named manager, and no termination process, into a role that has never been written down, at a company where the only person who understands the work has been doing it for twenty-two years and has never been asked to explain it.
Tom is not careless. He is the most protective person in the building about customer relationships, and he raised it because the aging report was hurting the accounts he covers. He said a reasonable sentence in a reasonable meeting and everyone present understood it the same way, which is the problem rather than the excuse.
An agent is a hire. No company hires for a role nobody can describe.
That sentence is the whole of the next phase of this book, and it is worth being clear about what it costs, because it is not free. Describing the role means writing down what Ruth knows, which nobody has budgeted, which nobody has scheduled, and which is difficult work that will surface disagreements the company has been comfortably avoiding for years.
Ostermill takes about five weeks to do it, and the five weeks are the reason the rest of this book has anything to show you.