AI Can't Read the Room

I pressed enter. Several hundred tickets updated instantly. And for about three seconds, I felt great about it.

This is the story I wish someone had told me before AI became a core part of how I work. Not a warning about AI being dangerous — I'm not that guy. I use AI for everything. But there's a job AI does brilliantly, and a job it cannot touch, and when I confused the two, it cost me weeks of political repair across multiple relationships I'd spent months building.

Here's what happened, what I learned, and the system I rebuilt from the wreckage.

The Moment

I had an advantage. While everyone around me was hitting enterprise AI restrictions and getting nowhere, I'd found workarounds. I could query our systems effectively. I was pulling analysis that would have taken months — and teammates started coming to me because of it.

Leadership noticed. They put together a cross-functional working group to actually engage with what the data was showing. If you've ever worked in IT at a mid-size enterprise, you know how rare that is. Cross-functional alignment — business side and IT actually looking at the same numbers and agreeing on what they showed — almost never happens. This did.

We spent months building it. The working group pushed back on methodology. They helped tune the results. And we got to something I hadn't expected: everyone agreed on what the data showed. They didn't all like it, but they agreed on how it was gathered and they agreed we were looking at something real. That kind of trust — where the other side stops looking for the hole in your data and starts helping you answer the question — is fragile. I knew it. I was proud of what we'd built.

Then one of the reports flagged a specific problem: a large number of tickets were missing critical data fields. Work was going to stall without them. And I realized — with AI — I could fix that. Not over weeks. In minutes. Mass ticket update, every affected record, all at once.

I tested the query. It worked. I ran it on a sample. Looked clean.

Then I made three mistakes in a row.

Three Mistakes, One Enter Key

Mistake one: I didn't test on a single ticket before going wide. Basic QA. I know that. But the sample had looked fine, the logic was sound, and I was confident. I skipped the step because it felt redundant. It wasn't.

Mistake two: I didn't coordinate with my business partners first. The people who had been in that room with me. The people who had spent months helping shape the analysis. I didn't give them thirty seconds of "hey, I'm about to do this thing, heads up."

Mistake three: I put a deadline in the ticket updates — and an ultimatum. Not a gentle reminder. A hard line: complete this by this date or the ticket closes. I had AI helping me write clearly, specifically, efficiently. And AI helped me write a very clear, very specific, very efficient ultimatum and fire it at several hundred people simultaneously.

The ticket system doesn't know it's a mass update. It treats every change like a personal notification. So several hundred people, across multiple business teams, got the same message, at the same moment, with no context, with an ultimatum, and with no one from their side having been warned it was coming.

Fear moves faster than facts in an organization. What people don't understand, they fill with the worst interpretation available.

I didn't know any of this yet. I was at my desk. Satisfied. Moving on to the next thing.

Then my IMs lit up. The one that stopped me was from the business partner I was closest to on the working group — the one who had pushed hardest to get their leadership on board. The one whose trust I had spent months earning.

"How could you."

Not a question. That period at the end wasn't a typo. That was someone who had put their credibility on the line for this collaboration and just watched me detonate it.

What the Business Heard

What I intended: We have a data quality problem. I found a way to flag it systematically. Here's the deadline for resolution.

What the business heard: IT ran an automated process on your tickets without warning, without asking, and now you have a pile of manual work to do or your requests get closed.

They didn't hear "efficiency." They heard "IT is doing things to us again." Every conversation we'd had about AI being a collaborative tool — every sample we'd walked through together, every carefully built moment of shared trust — compressed into one data point: IT uses AI to move the bottleneck to us.

And there were people on the business side who had been skeptical of this effort from the beginning. They weren't malicious — they just hadn't been convinced yet. I gave them everything they needed to confirm what they'd already believed.

What made it worse: AI itself became part of the accusation. The framing that stuck in some corners wasn't "Jimmy made a mistake." It was: "This is what happens when IT goes unsupervised with AI tools." AI had been politically neutral six months before. After that day, it wasn't.

The document was right. The analysis was right. The problem it identified was real. And it still cost me.

The Turning Point — I Was Optimizing the Wrong Variable

My first response was to optimize harder. If the output caused problems, the output needed to be better. Cleaner prompts. More precise formatting. Airtight documentation.

The AI got better. The political problem got worse.

Because I was optimizing the wrong variable.

Here's what I eventually understood: I had outsourced the drafting. That's fine — that's what AI is for. But in outsourcing the drafting, I had accidentally outsourced the read. The political read, the relational read, the "is this the right moment to send this to this person" read.

Those are two different jobs. Only one of them AI can do.

The drafting job: Is this document well-written? Is the analysis clean? Is the logic reproducible? Is the data sourced? AI is excellent at this. I'm not going back.

The read job: Does this document land well right now, with this specific audience, given what happened in their world in the last seventy-two hours? That job has no AI.

Once I saw that line, I couldn't unsee it. I started noticing it everywhere — in my own work and in conversations with other technical professionals using AI heavily. The pattern was the same: high output quality, high political friction. More confident in what they were sending. Less aware of how it was landing.

Because AI gives you confidence. That's one of its real features. You send a prompt, you get a clean output, and there's a part of your brain that says "that's handled." The problem is that "that's handled" extends further than it should. You start treating the document as the deliverable when the document was always just an artifact. The deliverable is the outcome. The outcome lives in the room. And AI doesn't have access to the room.

The Ghostwriter and the Diplomat

After I worked through the fallout — weeks — I rebuilt how I use AI at work. Not less AI. Different AI. A cleaner line between what AI owns and what I own.

I call it the Ghostwriter and the Diplomat.

AI is the Ghostwriter. It owns structure, research, drafts, synthesis, and documentation. Anything that gets evaluated on correctness alone — is the logic sound, is the data accurate, is the writing clear. I don't second-guess the Ghostwriter. I don't retype what AI wrote because it doesn't feel like mine. I treat it like a skilled collaborator who understands the assignment.

You are the Diplomat. You own the political layer. Deciding if this lands now. Who sees it first, and in what order. How it gets framed before it leaves your hands. What the room already believes before it arrives. Whether to send it at all.

The Ghostwriter produces. The Diplomat deploys. You need both to actually move anything in an organization. And only one of them is you.

Most technical professionals who are getting passed over while working harder than anyone else aren't missing Ghostwriter skills. They're missing Diplomat skills — and they don't realize it because the AI output is so consistently good that it masks the gap.

The 60-Second Political Scan

The practical version of the Diplomat job is five questions. Sixty seconds. Run them before anything significant leaves your hands.

The full checklist is at fromittoinfluence.com/political-scan. Free. Five questions formatted for the sixty seconds before you hit send.

What Changed After I Fixed It

The AI output didn't change. I was still using AI for everything I was using it before — if anything, I leaned into it harder. Because I'd freed up mental space from not trying to do the political read inside the document. I stopped trying to write documents that were politically aware. I started writing documents that were technically excellent and then separately doing the political awareness work before they left my hands.

Two jobs. Clean separation. Both done better.

The relationships that had gone quiet came back. Not because the work improved — the work was already good. They came back because I stopped surprising people. That's the thing about trust in an organization: you don't build it with quality. Quality is the floor. Trust is built with predictability. The thirty-second heads-up before something goes wide. The question: "Is now a good time for me to bring this to your director, or do you want to loop in first?" The check-in that says "I have the analysis ready — what's the political temperature right now?"

None of that is in the document. All of it is the reason the document gets a fair read.

The business partner who sent me "how could you" — that relationship came back. It took time and an honest conversation about what I had done wrong — not just the mechanics, but the specific thing I had skipped and why I had skipped it. That conversation was uncomfortable. It was worth having.

You don't overcome a bad moment with a good document. You overcome it with time and pattern.

Your Audit Question

Think back over the last thirty days. Has anything you sent with AI assistance landed wrong — even though it was technically correct? An email that got a cold response. A document that generated friction instead of momentum. A recommendation that turned into a defensive conversation.

If yes — that's not an AI problem. That's a Diplomat gap. The Ghostwriter did its job. You skipped yours.

And it's fixable. The 60-Second Political Scan is where to start.

The most dangerous thing about AI at work isn't that it produces bad output. It's that it produces good output so consistently that you stop asking whether the output is the point.

In organizations, the output is rarely the point. The output is what you're measured on. The room is what you're working in. Those are two different systems. AI only sees one of them.