The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

It’s Not the AI, It’s the Crap: Why Bad Inputs Break AI Projects

This entry is part 29 of 30 in the series Artificial Intelligence for Writers

TL;DR: Adopting AI at work without breaking your business comes down to four moves. Use AI to amplify the boring, repetitive work that drains your people, not to replace the judgment they get paid for. Identify the edge cases before you deploy. Keep a human in the loop wherever a mistake costs money or trust. Retrain your existing people on the new tools instead of firing them how I use AI without the crap. The companies that follow this pattern win the next decade. The ones that confuse “AI can do this task” with “AI can replace this job” learn the hard way, publicly and expensively. Klarna and the chatbot at your doctor’s office are the same disease at different scales.


I called my doctor’s office the other day to leave a message. The new AI chatbot picked up and launched into a two-minute uninterruptable speech about how it was going to help me. When that finally ended, it started a one-minute one.

Then more after that. Five minutes every call, every time, before I could get to a human or even leave a message.

The old phone tree was clunky. This was worse. And somebody at that medical practice spent real money to make it worse.

That clinic isn’t the exception. It’s the pattern. Companies are rolling out AI everywhere, and a lot of those rollouts are quietly hurting the businesses paying for them.

The fintech giant Klarna laid off 700 customer service workers and replaced them with an OpenAI-powered chatbot, then started rehiring humans when the CEO publicly admitted the AI produced “lower quality” service. Same disease, different scale.

Not because AI is bad. Because nobody asked the boring question first: where does this actually belong in our work, and where does it ruin things if we put it there?

I’ve been around long enough to watch this happen before. Different technology, same mistake.

AI Is an Amplifier, Not a Fixer

The single most useful thing I can tell you about AI at work is that it does not fix anything. It amplifies. Whatever you feed it, good or bad, comes back louder. Give it clean data and a clear question and it gives you something useful fast. Give it a mess and it gives you a bigger mess, delivered with total confidence.

This is why so many AI projects fail and why the failure gets blamed on the AI. The model did exactly what it was told. It took the garbage it was handed and produced more garbage, faster than any human could. The problem was never the tool. The problem was upstream, in the data, the process, or the thinking, and the AI just made that problem visible at scale.

Why Does AI Amplify Bad Data?

Most companies have worse data than they think. Records that contradict each other. Fields filled in three different ways by three different departments. Spreadsheets that a person can read with context but a machine reads literally. Point an AI at that and it does not flag the mess. It averages it, guesses at it, and hands you an answer that looks authoritative and is quietly wrong.

A human doing the same task would stop and say this does not add up. The AI does not stop. It fills the gap with the most likely-sounding text and moves on. That confidence is the dangerous part. A wrong answer that sounds unsure gets checked. A wrong answer that sounds certain gets shipped.

Vague Process In, Automated Confusion Out

The second source of crap is process nobody can actually explain. Ask most teams to write down exactly how they make a decision and they cannot. They do it by feel, by experience, by a hundred small judgments they have never put into words. That works when a person does it. It falls apart the moment you try to hand it to a machine.

If you cannot describe the process clearly, the AI cannot follow it. It will pick a version, usually the simplest one, and automate that. Now you have a fast, consistent, wrong process running at volume. The AI did not break your workflow. It exposed that your workflow was never really defined.

Vague Questions In, Vague Answers Out

The third source is the question itself. People ask AI broad, lazy questions and get broad, lazy answers, then conclude the AI is not smart enough. Ask it to make our marketing better and you get generic filler. Ask it a sharp, specific question with the real constraints included and the quality jumps.

This is a skill, and most people have not built it yet. The quality of what you get out is capped by the quality of what you put in. That is not an AI limitation. That is the same rule that governs every tool ever made. A better saw does not make you a better carpenter.

What Should You Fix Before Adopting AI?

Before you blame the model or shop for a different one, look at the three inputs. Is the data clean and consistent, or are you feeding it contradictions? Can you write down the process in plain steps, or does it live in someone’s head? Are you asking precise questions, or vague ones and hoping? Fix those and most of what people call an AI problem disappears.

I have watched companies spend months and real money trying to make an AI project work when the actual fix was a week of cleaning up their data and defining what they wanted. The AI was fine. The crap around it was the problem. Get the inputs right and the tool does exactly what it was supposed to do all along.

The Guides That Get Your Book Written, Published, and Sold

Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.

We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.

Frequently Asked Questions

If AI keeps giving bad answers, isn’t that the AI’s fault?
Almost never. AI is an amplifier. It takes whatever you give it and produces more of the same, faster. Bad data produces confident wrong answers. A vague question produces a vague answer. An undefined process gets automated into fast, consistent confusion. In nearly every failed AI project I have seen, the model did exactly what it was told. The garbage was already in the room before the AI arrived.
How do I know if my data is good enough for AI?
Look for contradictions and inconsistency. Are the same fields filled in different ways by different people? Do records disagree with each other? Does a spreadsheet only make sense if a human reads it with context the machine doesn’t have? A person catches those problems and pauses. AI does not pause. It averages the mess and hands you an authoritative answer that is quietly wrong. If you cannot trust the data yourself, the AI cannot either.
Why does AI produce confident answers that turn out to be wrong?
Because it fills gaps with the most likely-sounding text rather than stopping to flag uncertainty. A human doing the same task would say this does not add up. The AI keeps going and delivers the guess with total confidence. That confidence is the trap. A wrong answer that sounds unsure gets checked. A wrong answer that sounds certain gets shipped.
Can better prompts fix a bad AI project?
Sharper questions help, but they cannot rescue bad data or an undefined process. Prompting is one of the three inputs. Ask a precise question with the real constraints included and quality jumps compared to a lazy one. But if the data underneath is a mess or the process was never defined, no prompt will save it. Fix all three inputs, not just the one that is easiest to change.


What should I fix before blaming the AI?
Three things, in this order. The data: is it clean and consistent, or full of contradictions? The process: can you write it down in plain steps, or does it live in someone’s head? The question: are you asking something precise, or something vague and hoping? Fix those and most of what people call an AI problem disappears. The tool was fine. The crap around it was the problem.

📁︎ Artificial Intelligence

🏷︎ AI Adoption🏷︎ AI vs Human Ghostwriting🏷︎ AI Writing🏷︎ AI Writing Pitfalls

📝 Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

Leave a Reply

Your email address will not be published. Required fields are marked *