The head of ops asks the room what the AI is actually doing at the company.
Three people answer. Three different answers.
“It writes our email drafts.”
“It’s helping the sales team prep for calls.”
“I think marketing has it running social posts.”
Nobody in that room is lying. Nobody in that room is right, either.
This company signed off on AI adoption six months ago. They bought the seats. Rolled out the training. Put a custom GPT in front of the sales team. Put a marketing assistant in front of content. Put an email helper in front of Susan on the CSR queue. The check cleared. The team was told they were “using AI.”
Now leadership is in a Monday standup trying to figure out why nothing feels different.
Here’s the thing. Nothing feels different because nobody hired anyone.
The document you signed was a purchase order. It was not an org chart.
You bought a contractor and never assigned a project manager.
Read that out loud. If a real general contractor pulled up to your building next week with no work order, no supervisor, no clear deliverable, and no acceptance rule, you would not be surprised when the work turned into chaos. You would probably fire somebody on your side of the deal. Not theirs.
AI is not exempt from that rule. The moment you gave the sales team a custom GPT and told them “use this when it makes sense,” you handed a contractor a hard hat and pointed at a jobsite. You did not tell them what to build. You did not tell them who to check in with. You did not tell them what “done” looked like.
You cannot deploy a hire without an org chart.
Every one of those AI initiatives that stopped feeling alive after six weeks has the exact same shape. Somebody bought a tool. Nobody hired a role.
Tool-shaped output is what happens when nobody manages the tool
Look at the sales GPT that only works when the founder remembers to open it before a call. That is not a sales assistant. That is a browser tab. The founder is the only project manager it has, and the founder is not standing at his desk pre-briefing his own tool at eight in the morning.
Look at the marketing assistant that has drafted forty social posts and scheduled zero. That is not a content station. That is a folder. Nobody owns the review step. Nobody owns whether the post ships. So the drafts pile up like a stack of paint samples in a garage.
Look at the CSR helper that writes replies half the team quietly rewrites and half the team quietly sends. That is not an assistant. That is a coin flip. Nobody named the acceptance rule. So each CSR is running their own private policy inside the same queue.
Yeah. That is not adoption. That is drift.
Here’s the thing. The tool did not fail in any of those scenes. The role never got placed.
The org chart has a missing role
Every real team has three shapes on it. Somebody who owns the taste. Somebody who owns the routing. Somebody who owns the doing.
In the Station Plan, those three shapes have names. The Chef is the human at the center who owns what “good” looks like. The Pass is the role that routes work in and accepts work out. The Line is where the actual work gets made. When AI shows up in the business, it usually joins the Line. Sometimes it takes over a whole station on the Line. Either way, the Line does not run without the Pass, and the Pass does not run without the Chef.
Most companies that “adopted AI” this year put a tool on the Line without ever naming the Pass. So the work goes into the tool. The work comes out of the tool. Nobody in between is answering the question “is this what we needed?”
The Pass is the missing role. That is the whole diagnosis. If you are looking up from the first hill of your AI rollout and wondering why nothing feels like a team, this is what you are looking at.
The contractor test
Imagine a real general contractor pulled into your building tomorrow morning. Truck, tools, crew.
Nobody on your side had assigned a project manager. Nobody had described a scope. Nobody had named the acceptance rule.
What happens? The crew stands on the sidewalk. Or they frame something ordinary and leave. Or half of them think the job is finished and half keep working, and the punch list at the end becomes a fight.
You would look at that mess and say “nobody was managing this.” You would not blame the contractor. You would blame the placement.
Now do the same test on your AI-enabled workflow.
Four lines on one page.
- The AI takes this kind of work.
- This person routes the work in.
- This is what comes back.
- This person accepts, rejects, or escalates the result.
If any of those four lines is blank, you have not hired anyone. You have opened a tool.
Right? It really is not more complicated than that.
But this is not “replace the team”
The trap here is reading the contractor metaphor as “the contractor replaces the human.” That is the wrong read. A contractor without a project manager is chaos. AI without a manager is chaos. The point is not that AI displaces the manager. The point is that AI, like any contractor, needs one.
Not the human out. The role in.
I have literally sat in leadership meetings where the CEO said “we’re using AI for social,” and the head of marketing sat next to them and thought “we are?” Both statements were true and neither of them was operational. The tool was in the building. The role was not.
Does that make sense? The reason your six-month-old AI rollout feels stalled is not that you bought the wrong tool. It is that nobody wrote down which of your people owns the routing and the acceptance for it.
Not “we all use it as needed.” That is the drift sentence. That is the sentence that produces coin flips at the CSR queue. The acceptance rule is a person and a standard, not a shrug.
The move for Monday
Run the Contractor Placement Test.
Pick one AI workflow that is currently running in the business. Not a new one. Not the one you have been meaning to roll out. One that is already live and has been for a month or more.
Take one page. Write four lines.
- The AI takes this kind of work.
- This person routes the work in.
- This is what comes back.
- This person accepts, rejects, or escalates the result.
Guardrail: do not add a new tool during the test. You are not shopping. You are staffing. Owner of the move: the leader who first pushed the pilot, or the owner who signed the invoice. Metric: one page, four lines, in the language the people who will actually do the routing and the accepting would use.
Next step: say the acceptance rule out loud in the next team meeting. If the room cannot name who accepts the AI’s work, no one has been hired yet. If they can, you just placed your first AI role. Now do the next one. You already know which workflow is second on the list.
The close
You cannot deploy a hire without an org chart.
The question was never which AI to buy. It was who routes the work into it, accepts the work out of it, and owns the result. Nothing about your rollout changes until that question has four names attached to four lines.
Get out the page. Write the four lines. See who is actually standing at the Pass on Monday morning.
Original framework. Distilled from client work. This piece names the Station Plan, specifically the Pass and the Line. More at incrayon.com/frameworks/station-plan/. Closes the Mount Stupid arc. The AI Employee Handbook series (parent at Your AI Employee Handbook Is Not a Policy, and Friday’s child, Write the Job Before You Hire the Tool) picks up once the role has been placed and it’s time to write the job spec.
~ source material · Original framework. Distilled from client work.
