Your AI Integration Is Stuck in 1992
Most AI agents are pointed at the person, not the business. Steve Jobs warned us about this trap 34 years ago
I've been watching a Steve Jobs talk from 1992 and it explains most of what's wrong with how people are using AI in 2026.
He gave it at MIT Sloan, after he'd left Apple and was running NeXT. He was citing Paul Strassmann, a guy who'd been CIO at Xerox, the Pentagon, and NASA, and had spent two decades studying where corporate IT actually paid off.
The Two Columns
Strassmann had found something simple. Every company he looked at spent about 2% of revenue on IT. The number was roughly the same whether the company was winning or losing. What moved was what the tech was doing.
Some companies pointed the 2% at individual work. Tools that made one person's day faster. Word processors, spreadsheets, email. The memo still got written. It just got written in an hour instead of three. Strassmann called this management productivity, but the simpler way to say it is that the tech was speeding up the people.
Other companies pointed the 2% at the business itself. Tech that shortened the cycle that made the money. Catch the stockout before it stocks out. Push the invoice the day the work finishes. Reprice the product the hour demand shifts. This is operational productivity, or just: the tech was speeding up the business.
Same budget. Same era. The winners pointed the tech at the business. The losers pointed it at the people, got faster workers, and wondered why the P&L didn't move.
Swap "PC" For "AI"
Now do the substitution. The whole talk plays.
A lot of the 2026 conversation is sloppy about this because it mistakes form factor for direction. The popular take is that copilots are old, agents are new, ship the agents. As if the shape of the thing decides where it's pointed. It doesn't. Agents can be pointed at the person or at the business. Most of them are pointed at the person.
An agent that drafts your board update is pointed at you. An agent that triages your inbox is pointed at you. An agent that summarizes every call and files the notes is pointed at you. No matter how autonomous it is, if the thing it's doing is making one person faster at their own work, it's speeding up a person, not the business.
Faster People Is Not A Faster Business
You might push back here. If the people inside my business get faster, isn't the business faster too? No, and it's worth knowing why.
A business cycle is mostly waiting, not working. The lead sits in an inbox for four hours before anyone sees it. The demo is three days out. The proposal waits two days for approval. The onboarding call is booked for next Tuesday. Most of the clock on any revenue cycle is idle time between handoffs, not working time on a task.
AI pointed at a person shortens working time. The rep answers in thirty seconds instead of five minutes. AI pointed at the business removes waiting time between handoffs. The lead gets qualified and replied to in thirty seconds instead of four hours overnight. Compressing waiting is how cycles actually get shorter. Speeding up a person at a non-bottleneck step is a local optimization. It feels like progress on the Monday standup and doesn't show up in the quarter.
What About Personal Productivity?
Fair question. If I'm a solo operator, am I not the whole business? If I get faster, doesn't the business get faster?
Yes, if you're truly solo. A one-person business has no handoffs. The person is the cycle. An agent that makes you reply faster is also an agent that shortens lead-to-response time. The two columns collapse into one because the person is the operation.
But the moment anyone else is in the loop, they separate again. A VA, a contractor, a part-time editor, a freelancer. Once there are handoffs, the wait time between them is where the clock lives. Speeding up your own work while the handoffs stay slow is the same old trap at small scale.
There's also a simpler case. You just want your work to feel better. You want your inbox less painful. You want your deck to write itself. That's fine. Just don't pretend you're transforming the business when you're adopting a personal tool. Both can be true. They're just different things. Buy the personal tool, use it happily, and point a different agent at the loop.
The mistake isn't pointing AI at yourself. The mistake is pointing all of your AI at yourself and calling it strategy.
Size Is Not The Tell
Size isn't the way to sort this either. I kept assuming "pointed at the business" meant building a whole pipeline. That's one way. It isn't the only way.
A short agent that watches the support inbox and pings the success team the moment a high-value account says something churn-like is pointed at the business. A small script that catches the pricing error before the quote leaves the office is pointed at the business. One well-placed thing at one critical step can shorten the revenue cycle by a day.
The question isn't how big the agent is. It's what gets faster when it runs, the person or the business.
Where I Almost Pointed AgentUse
I'll tell on myself because I almost got this wrong.
Last year I built AgentUse, an open source framework for composing agents. Once the infrastructure was sitting on my laptop the temptation was obvious. Point it at myself first. That's the fastest demo. Agents answering my email. Agents writing my newsletter outlines. Agents drafting replies on X. I had a whole shortlist.
I caught myself before I shipped any of it. I was about to use the thing I'd built to make my own typing faster. Same 1992 mistake. Sharper tools.
So I pointed AgentUse at LifeHack's business instead. For LifeHack the cycle is idea to draft to publish to audience. A handful of small agents, each sitting at a step that used to slow the cycle down. One watches for angles worth writing about. One drafts against the style guide. One handles distribution to Substack, LinkedIn, and X on schedule. I review. I intervene when it matters. I don't sit in the middle of the flow.
None of those agents is complicated. In AgentUse they're just markdown files, plain English instructions. The thing that matters isn't the code, it's what they're pointed at. Each one removes wait time from the cycle, not working time from my day.
When an agent is a paragraph anyone can write, the only thing left that separates a winning AI stack from a losing one is where you plug it in.
Six months in, LifeHack publishes more than it used to, and my calendar has more room in it, not less. The agents don't make me a faster typist. They make the business move faster whether I'm at my desk or not.
The Monday Audit
If you want to run this on your own stack, don't count your agents. Map them.
Sketch how revenue actually moves in your business. Lead in, qualified, demo, close, onboarded, renewed. Or idea in, made, shipped, bought, supported. Whatever your cycle is. Mark the handoffs, not just the tasks. Most of the clock lives between the boxes, not inside them.
Now look at every AI integration you've shipped. For each one, ask one question. When this runs, does the business move faster, or does one person get faster at their own work?
Then ask it of the whole stack. If you unplugged every AI integration tomorrow, would the cycle stretch out, or would a few people just type more?
Most operators I've run this with realize their agents are almost entirely pointed at people. A few realize it's a hundred percent. The number is rarely below sixty.
The reaction is always the same. A pause, then a quiet laugh, then "but everyone is building them there." That's true. Strassmann's losing companies weren't stupid either. They pointed their tech where their peers pointed it, which is why they all ended up on the wrong side.
The reason this keeps happening is that it's an attention problem, not a technology problem. Pointing an agent at yourself feels like action. You ship it, you see it working, the demo lands. Pointing an agent at the business feels like work. You have to sit with how the business actually runs, figure out where the wait time lives, and wire something into it you trust enough to let run. Most operators don't want to do the second thing. So they do the first and call it transformation.
The Trap Is Older Than AI
The split isn't an AI thing. Strassmann drew it studying mainframes in the seventies. Jobs translated it to PCs in 1992. We're living it in AI in 2026. Three eras. Three technologies. Same split. Each time new tech shows up, a loud generation of tools points at the person and a quieter generation points at the business. Person tools get the press. Business tools get the returns.
The question in 2026 isn't whether you're shipping agents. Everyone is. The question is whether your business moves any faster because of it.
If you run the audit this week and the business isn't any faster, that's fine. Most of us started there. It just means the transformation you think you're doing hasn't started yet. The tech is new. The trap is 1992.
If you want to hear Jobs make the argument himself, the full MIT Sloan talk is on YouTube. The management versus operational split is about four minutes in.
Where is your AI pointed? Send me a message and tell me what you found.