When not to use AI.

Most of the writing about AI in business focuses on getting more out of it. Better prompts. Smarter workflows. Bigger outputs. That's most of the game, and it's worth getting right. But there's a smaller, less-discussed piece of the same skill set: knowing the moments when AI is the wrong tool. Using AI in those moments doesn't make you faster. It makes you slower, less accurate, and sometimes embarrassed in front of a customer. Five situations where the right move is to close the AI window and do the work yourself.

1. When the stakes of being wrong are high and verification is slow

AI produces fluent, confident output regardless of whether the underlying facts are right. For most everyday tasks, that's fine — you spot-check, edit, and ship. But when the cost of a mistake is large and verification takes longer than just doing the work yourself, AI flips from helpful to dangerous.

Examples: pricing a complex job, drafting a contract clause, writing legal language, calculating a tax position, advising on a regulatory question. The fluency of the AI output gives you a false sense of progress, while the work of confirming each piece is right takes longer than just doing it carefully from the start.

The tell: if you'd need to fact-check every line before you trust the output, you're better off writing every line yourself. The verification costs more than the generation saves.

2. When the work requires personal judgment your customer is paying you specifically for

Customers hire experts for the expert's judgment. A general contractor charges a premium because they've seen a thousand jobs and know which decisions matter. A consultant earns their fee because of pattern recognition no algorithm has. A financial advisor adds value because they know this client.

When you delegate that judgment to AI — letting it write the recommendation, draft the analysis, decide the priority — you're charging for expertise and delivering generic output. The customer feels it. They may not be able to articulate it, but they know the difference between a recommendation that comes from someone who's been doing this for twenty years and one that came from a chatbot. Don't outsource the part of the work the customer is actually paying for.

The tell: if removing your name from the output wouldn't change anything, the work probably shouldn't have your name on it.

3. When you don't know the topic well enough to evaluate the output

This is the one almost nobody talks about, and it's the one that gets people in the most trouble. AI is most dangerous when you ask it about something you don't already know enough about to spot mistakes.

If you ask AI to summarize a business model you understand, you'll catch any errors. If you ask it to summarize a technical domain you don't understand, you'll trust the output because nothing in it sounds wrong to you — and you'll have no idea whether it's right. Using AI as a substitute for expertise you don't have is the fastest path to confidently saying things that are wrong.

The tell: if the AI knows more than you do about the topic, you cannot evaluate its output. Either learn enough to evaluate it, or have someone who already has that knowledge review it before it goes anywhere.

4. When the relationship matters more than the message

An apology to a customer you wronged. A condolence note to someone who lost a parent. A direct message to a team member you respect. A thank-you to someone who went out of their way for you.

The content of these messages matters less than the fact that you took the time to write them. AI can produce a well-structured, grammatically perfect, emotionally appropriate version. But what the recipient is responding to isn't the prose — it's the time and care behind it. AI-drafting an apology is the same gesture as having an assistant write it: it works mechanically and it fails relationally.

This is true even when you carefully edit the AI output to sound like you. The other person can't tell, but you can — and the relationship subtly notices. Some words have to be your own words.

The tell: if the message is meant to make someone feel something, and that feeling is rooted in your effort, write it yourself.

5. When you're using AI to avoid thinking

This is the most subtle one and the one most worth catching in yourself. AI is a phenomenal tool for executing on a clear idea. It is a terrible tool for skipping past the part where you figure out the idea. The pattern looks like this: you face a hard problem, you don't want to think about it, you ask AI for "options" or a "framework," and you accept whatever it produces because the friction of pushing back is higher than the friction of going along.

The output looks productive. You have a thing now where before you had nothing. But the thinking that should have happened — the part where you wrestled with the problem and made a decision based on your context, your priorities, your gut — got short-circuited.

The cost shows up later. The decision you didn't really make turns out to not fit your situation, because it was a generic decision rather than yours. The plan you had AI generate falls apart in execution because you didn't internalize it.

The tell: if you can't argue back against the AI's output — if you'd accept whatever it gave you because you don't really have a position of your own — you're using AI to skip the thinking, not to assist it. Close the window. Sit with the problem.

The general rule

AI is excellent at execution and average at judgment. The pattern that works is: you do the thinking, AI does the work. The pattern that fails is the inverse — letting AI think while you copy-paste.

The skill of knowing when to reach for AI and when to leave it alone develops over time. Most people start by using AI for everything, get burned a few times, and gradually learn the boundaries. Five categories above are the ones most worth memorizing up front, because they're the ones where the cost of the mistake is highest and the warning signs are quietest.