Your AI Didn't Break Your Team

It Showed You What Was Already Broken

It Showed You What Was Already Broken

Somewhere in the last year, the marketing org at a global medical-equipment maker did something a lot of companies are doing right now. They looked at their agency spend, roughly a million dollars a year of it, and decided AI could absorb most of that work. They cut the spend. They stood up AI tools across the team. On paper, it was a clean win. Then the work actually started, and the team found out what the agencies had been quietly doing for years besides writing copy and building decks. They had been the connective tissue. The thing that made five different sub-teams sound like one company. Once that tissue was gone, and AI was doing the generating, the marketing org discovered it had never had a single source of truth. It had brand guidelines in one place, campaign history in another, and no shared understanding of voice that lived anywhere except in the heads of the vendors who had just been let go. Every group had already started building its own custom GPT, trained on whatever slice of data that group happened to have. Each one was fast, confident, and fluent. None of them agreed with the others. The organization had developed a split brain, and AI did not cause it. AI just removed the last thing that had been quietly patching over it.

The organization was already fractured. AI just stopped hiding it.

This is the part leaders get backwards. The instinct, when AI output looks inconsistent or the rollout feels messy, is to blame the tool. Wrong model, wrong prompt, wrong vendor, wrong training. Send everyone to a workshop. Buy a better license tier. None of that fixes what actually happened at the medical-equipment maker, because the problem was never the model. It was that five sub-teams had never agreed on what “on brand” meant, had never centralized what campaigns had already run, and had never built a shared source of truth because a small army of agency staff had been absorbing that inconsistency by hand. Humans were the buffer. Nobody had designed the buffer. It had just accumulated, the way undocumented process always does, until the day someone cut the budget line that funded it. AI does not create organizational dysfunction. It is a speed multiplier, and speed multiplies whatever is already there. A team with a shared foundation gets faster at doing good work. A team without one gets faster at producing confident, fluent, contradictory work, and finds out about the contradiction days sooner than it would have with a slower process and a human buffer catching the seams. The tool is not the diagnosis. It is the thing that made the diagnosis impossible to keep avoiding.

This is not a marketing problem, and it is not a one-company problem

It is tempting to file this under brand consistency and move on. Resist that. The same pattern shows up anywhere a team quietly outsourced its coherence to a human buffer and then automated around that buffer without noticing it was there. A regulated bank rolls out an assistant across the workflow layer and instantly surfaces which teams had informal, undocumented pay bands and who actually approves what, because the tool cannot respect a boundary nobody wrote down. A product organization spins up parallel AI-assisted design sprints across business units that had never shared a single design system, and gets five plausible answers to the same brief instead of one. A research group lets every analyst build a personal assistant on their own corner of the data, and stops being able to explain why two people, working from the same underlying numbers, produced two different conclusions in the same week. None of these are AI failures. They are the same organizational fracture, dressed differently by industry. The tool exposes it because the tool does not know, and was never told, which version of the truth is the real one. This is the new friction in miniature. AI did not eliminate the work of building a coherent organization. It relocated that work, from the years-long background task of quietly patching gaps by hand to a single, unmissable moment when the patches are gone and the gaps are visible in the output. The friction of building coherence never disappeared. It just moved from invisible to unavoidable, and it moved fast enough that most leaders have not caught up to where it landed.

Split brain has two shapes, and most organizations build both at once

Once you see this pattern, it shows up everywhere, and it shows up in two opposite failure modes that somehow coexist inside the same company. The first shape is what happened in marketing: total dispersal. Every team, sometimes every person, builds a custom GPT trained on its own slice of data. Each one is locally confident. None of them share a voice, because none of them share a foundation. You end up with a dozen assistants that are each fluent in their own dialect and mutually unintelligible to each other, which is a strange kind of progress. Everyone got faster. Nobody got aligned. The second shape is the opposite instinct, usually deployed as the fix for the first one. Leadership sees the fragmentation, panics, and points one enterprise-wide tool at everything the company owns. This is supposed to be the unifying move. In practice it produces something closer to a watered-down house style than a shared brain. Feed a model everything, undifferentiated, and it has to average across all of it. The result is often worse and blander than what a focused, well-scoped model would have produced on its own, because breadth without curation is not the same thing as a shared foundation. It is just a bigger pile of unshaped context. Both failure modes trace back to the same root cause: nobody treated context as something that needed to be designed. Context was either left to fragment by default, or dumped in wholesale and left to dilute by default. Neither is a decision. Both are the absence of one.

AI is only as good as the context you give it, and context is not a technology problem

There is a useful discipline hiding underneath the prompting conversation, and most organizations never get to it because they are stuck arguing about prompting instead. Call it context shaping: the deliberate work of deciding what belongs in the shared foundation, what belongs at the team level, and what should never be centralized at all. Too broad, and the model has no way to distinguish signal from noise. It steers off toward the statistical average of everything you have ever written, which is nobody’s actual voice. Too narrow, siloed team by team, and you get a company that talks to itself in a dozen dialects and calls that autonomy. The discipline is finding the altitude in between: a foundation specific enough to sound like your company, general enough that five teams can build on it without diverging. That altitude is not a model setting. It is an organizational decision, and it looks a lot like the decisions good facilitation has always forced onto the table. Who owns the shared definition of “on brand”? What actually belongs in that definition, and what was always going to be team-specific judgment layered on top? Who has the authority to say a sub-team’s fast, fluent output does not count as canonical, even though it shipped first? None of these questions have a technical answer. They have an organizational one, and an organization that has never had to answer them before AI arrived will not enjoy discovering that AI is now the reason it has to.

Audit your context before you audit your AI

If you are looking at inconsistent, contradictory, or oddly generic AI output across your organization, resist the urge to start with the tool. Start with three questions instead. Does a single source of truth actually exist, or does it live implicitly in the heads of people you have not lost yet? The marketing org found out the hard way that “we all basically know our brand voice” is not a source of truth. It is an assumption that survives only as long as the people who hold it stay in the room. Write it down, and write it down before you cut the humans who were quietly maintaining it. Is your context shaped at the right altitude, or has it defaulted to one of the two failure modes? If every team has its own model trained on its own slice of the world, you have dispersal by accident. If you have pointed one tool at everything and hoped scale would produce coherence, you have dilution by accident. Either way, nobody chose this. Someone needs to. And who is accountable for the connective tissue that used to be invisible labor? Before you eliminate a role, a vendor, or a budget line that has been absorbing inconsistency for years, ask what happens to that inconsistency once the absorption stops. It does not disappear. It surfaces, usually in front of a client or a regulator, at the worst possible moment, wearing a very confident, very fluent, completely wrong AI-generated deliverable. Naming the canonical layer is smaller work than most leaders expect, and that is exactly why it keeps getting skipped. It does not require a data platform migration or a six-month governance initiative. It requires someone in the room willing to say, on the record, “this is the version of our voice, our numbers, our brand that every team builds on top of, and here is what stays yours to decide locally.” That sentence is a facilitation act, not a technical one. Most organizations have simply never been forced to say it out loud, because the humans absorbing the gap never asked them to. This is not an argument against cutting the agency spend, and it is not an argument against giving teams AI tools. It is an argument for sequencing. Build the shared foundation first. Name who owns it. Decide, deliberately, what stays local and what has to be canonical. Only then let the speed loose on top of it, because speed on top of a shared foundation compounds, and speed on top of a fractured one just gets you to the fracture faster.

The savings were real. So was the bill that came due

The million dollars the medical-equipment maker cut from its agency budget was a real number, and the efficiency case for making that cut was not wrong. What was wrong was the assumption that the savings and the organizational debt were unrelated line items. They were not. The agencies had been the invisible interest payment on years of undocumented process, and the day the payment stopped, the debt came due all at once, in public, in AI’s voice. Every organization racing to consolidate spend into AI right now is making some version of this same bet, whether it knows it or not. The tool will do what you ask, faster than anything you have used before. It will not tell you that what you asked for was five different answers wearing one company’s logo. That is a question only a leader willing to look at the organization’s own foundation, and not just its tool stack, will think to ask before the invoice comes due. The next time an AI rollout produces something inconsistent, resist the reflex to retrain the model or reshuffle the vendor. Look instead at what the tool just made impossible to ignore. Then go fix that, because that was always the actual job. If you are staring at a pile of confident, contradictory AI output right now and you are not sure whether the problem is your model or your organization, that is worth a real conversation before you spend another dollar on either one.