Back to Blog

Your AI Is Performing. Who's Driving?

Your AI Is Performing. Who's Driving?

Here is the problem nobody is naming clearly enough: the AI in your business is performing. It is generating. It is responding. It is writing things and saying things and doing things. But nobody is actually directing it. And the difference between those two states is the difference between a business that gets stronger and one that slowly hollows out.

We have watched this same pattern emerge across five completely unrelated stories in the last week, and when you see it that many times from that many directions, it stops being a coincidence and starts being a signal worth naming.

Start with the easy one. Managers are using AI to write performance reviews, and it shows. Not just stylistically. It shows in the way the feedback has become generic, bloodless, technically accurate but emotionally inert. A performance review is a direction-setting conversation. It is a manager communicating to a person what matters, what needs to change, where the business is going. When AI generates that document without a real human who actually knows the person thinking hard about those questions first, the review becomes output without intent. The form is there. The steering is gone.

Now look at what Cisco just announced for Webex. An agentic framework that promises to turn fragmented customer interactions into continuous relationships. This is the enterprise dream: AI that handles customer conversations end to end, autonomously, at scale, without a human in the loop. And we get it. We understand the appeal. But there is a word buried in that pitch that should give you pause. "Agentic" means the system is making decisions. It is not just answering. It is choosing what to do next. Someone built the system. Someone turned it on. But who is holding the wheel moment to moment? At scale, probably nobody.

That is fine when the decisions are low-stakes. It becomes a serious problem when they are not.

Which is exactly what the ShinyHunters extortion case against a Boeing spin-off keeps reminding us. A teenager in Amman and a small gang were running sophisticated data theft and extortion operations against major corporations. These are enterprises with entire security departments. The gap they exploited was not technical. It was attention. Nobody was watching closely enough. The systems were running. The monitoring was in place. But active, human-directed attention to what was actually happening? Not enough of it. Automation creates coverage. It does not replace oversight.

Here is the thread. All three of those stories share the same skeleton: someone deployed a system to do a job, and then stepped away from the steering wheel because the system seemed to be running fine. The performance reviews were getting written. The customer conversations were being handled. The security dashboards were showing green. The output was happening. The direction was absent.

We think about this in terms of what a music research lab called Daydream is building. Their virtual recording studio lets you direct AI session players in real time, and the thesis behind the product is specifically about control. Their framing is worth sitting with: musicians steer each other through shared rules, a chart, a groove, a decision about who is carrying the melody. The control is not a separate layer bolted on top of the performance. It is woven into the performance itself. The direction is continuous. You do not set the groove at minute one and then leave the room.

That is the model that works. Not "set it up and check back later." Not "configure the agent and trust the output." Continuous, real-time, human-shaped intent running through every interaction the system has.

And then there is the Aeon film about an Iranian couple deciding whether to donate their late son's heart. What they navigated was the hardest version of this problem: how do you maintain direction, intention, meaning in a moment when everything has broken apart and the system you thought you were living inside no longer applies? What they did, and what made their choice matter, was refuse to let the decision become automated. They did not let the hospital system, the clock, the paperwork, or the grief make the call. They made the call. They stayed at the wheel. That is the only reason the story carries weight.

We are not saying do not use AI. We use it. It is genuinely useful. But we have been building on the web for 25 years and we have watched every wave of automation make the same promise: that the tool will handle it, that you can step back, that the system is smart enough now. And every time, the companies that thrived were the ones that kept a human actively directing the system, adjusting it, correcting it, reading the output with real judgment. The ones that handed over the wheel because the marketing said they could are the ones calling us two years later to figure out what went wrong.

The practical question, then, is not whether to automate. It is where does your intent actually live in the workflow? Not your initial configuration. Not your one-time setup. Your ongoing, real-time, contextual judgment. If you cannot answer that cleanly for each AI system you are running in your business, that system is performing without a director. It is a band playing without a chart. It might sound okay for a while. It will drift. And by the time you notice, it will have been drifting for months.

The best founders we work with treat their AI stack like a musician treats a collaborator. They set the direction constantly. They listen and adjust. They do not just hear output, they hear whether the output is serving the intent. That is a skill. It is not glamorous. It will not be on a conference panel about "the future of agentic AI." But it is the difference between a business that scales with intelligence intact and one that scales into noise.

You can automate the work. You cannot automate the direction. The moment you forget that, something in your business goes quietly off-key. It will keep playing. You just will not like where the song ends up.

Previous Post Who Actually Owns What You Build?