Indaba Platform All articles
Opinion

The Intern Who Never Asks Questions: Why Your AI Copilot Keeps Making Confident Mistakes

Indaba Platform
The Intern Who Never Asks Questions: Why Your AI Copilot Keeps Making Confident Mistakes

Photo by Photo by Vitaly Gariev on Unsplash on Unsplash

There's a specific flavor of embarrassment that comes from watching an AI assistant confidently cite a policy that hasn't existed since 2022. The tone is flawless. The formatting is immaculate. The information is fiction.

If you've experienced this, I have news that's equal parts freeing and annoying: the problem isn't the model. It's the mess you handed it.

The Shiny Tool Fallacy

American small teams have developed a pattern. A new AI tool launches, someone on the team sees a demo on LinkedIn, and within a week it's wired into the knowledge base, the support inbox, and the onboarding docs. Everyone nods solemnly about "leveraging AI to move faster."

Then the outputs start landing in Slack, and they're subtly, confidently wrong. The AI summarizes a process doc that was abandoned two pivots ago. It answers a customer question using last year's pricing. It writes an onboarding email referencing a tool nobody's touched since the reorg.

The instinct is to blame the vendor. The reality is more awkward: AI doesn't fix disorganized information. It industrializes it.

Your Copilot Is a Very Obedient Intern

Think of your AI assistant as an intern with a photographic memory, infinite stamina, and absolutely zero judgment about which sources are trustworthy. Feed it a wiki with three conflicting versions of your refund policy, and it won't ask which one is current. It'll blend them into something that sounds authoritative and is none of the above.

A human intern — even a mediocre one — asks questions. "Hey, this doc says one thing and Dave says another. Which wins?" An AI copilot doesn't ask. It averages. And the average of two wrong answers is a very polished wrong answer.

This is why AI adoption is such a brutal honesty test for small teams. Enterprises at least have information architects whose job is to care about this stuff. A ten-person startup usually has a Notion workspace that's half gospel, half archaeology.

The Cleanup Nobody Budgeted For

Here's the pitch nobody's selling: spend two weeks making your existing knowledge AI-ready before you spend another dollar on AI tooling. It's unglamorous work, and that's exactly why it's valuable — your competitors won't do it.

The AI-Readiness Checklist:

  1. Appoint a source of truth, per topic. Not a person — a document. For every recurring question (pricing, refunds, escalation paths, brand voice), one doc is canonical. Everything else gets deleted or marked "outdated" in bold letters.

  2. Kill the zombie docs. Anything untouched for six months is either promoted to current or moved to an archive folder the AI can't see. Sentimental attachment to old playbooks is how confidently wrong answers get born.

  3. Write for a stranger. Rewrite key docs assuming the reader has zero context — because your AI has exactly that. "Send it through the usual channel" is useless. "Post in the #billing-escalations Slack channel" is gold.

  4. Date everything. AI tools weight recency more than you'd think. A doc with "Last updated: March 2025" at the top is worth ten undated ones.

  5. Run the loyalty test. Before trusting your copilot with customer-facing work, ask it twenty real questions from your support inbox. Check every answer by hand. The failure rate will tell you exactly how much cleanup is left.

The Upside Hiding in the Chore

Here's what makes this worth it beyond the AI angle: a cleaned-up knowledge base is valuable even if you never buy another intelligent tool. Faster onboarding. Fewer repeated questions in Slack. Less tribal knowledge trapped in one person's head.

The teams getting genuinely impressive results from AI copilots right now aren't the ones with the biggest budgets or the fanciest models. They're the ones who spent a boring fortnight in 2024 deleting duplicate docs and rewriting their SOPs in plain English. The AI just made their good habits visible.

So before you add another AI tool to the stack, ask a different question: if a brilliant new hire read everything in our knowledge base tomorrow, would they come out smarter or more confused?

If the answer is the second one, you already know what your copilot is going to say. Confidently, beautifully, and completely wrong.

All Articles

Related Articles

Grief-Test Your Calendar: Which Meetings Would Anyone Actually Mourn?

Grief-Test Your Calendar: Which Meetings Would Anyone Actually Mourn?

Flexibility Shouldn't Mean Your Coworker in Austin Eats Dinner With Slack Open

Flexibility Shouldn't Mean Your Coworker in Austin Eats Dinner With Slack Open

That 3 PM Crash Might Not Be Your Body — It Might Be Your Browser Tabs

That 3 PM Crash Might Not Be Your Body — It Might Be Your Browser Tabs