When not to use AI (even if the board asks for it)

High-stakes decisions without review

If a wrong answer could change someone’s medical care, legal status, or credit, AI should assist—not decide. Human review is not optional polish; it is the product.

Regulated decisions often need explainability and audit trails that generic chat interfaces do not provide out of the box.

Rare edge cases you cannot test

If your business runs on unusual exceptions (“unless the client is in this county and ordered before Tuesday”), a generic model will get bored and invent patterns.

Fix the workflow or the data first. Rules engines and better forms often beat a chatbot here.

If you cannot describe the happy path in a paragraph, you are not ready to automate the exceptions.

Dirty data nobody owns

AI magnifies messy CRMs and spreadsheets. If two departments disagree on what a field means, automation will ship faster garbage.

Clean the source of truth, then automate.

Brand, trust, and nuance

Some companies sell careful judgment. If your edge is tone, relationships, or creative taste, a generic draft can make you sound like everyone else.

Use humans for the line that wins the deal; use tools for prep and research if you use them at all.

When you lack capacity to supervise

If nobody can review outputs this week, do not turn on customer-facing automation this week.

Understaffed teams sometimes reach for AI to paper over capacity gaps—that is when mistakes reach customers fastest.

What to do instead

Say no with a better next step: a smaller pilot, a manual process with a checklist, or a integration that does not need generative AI at all.

Teams respect clarity more than buzzwords.

Document the “not yet” decision: what gate you are waiting on—data, legal, staffing—so you revisit on a date instead of forgetting.

• Improve forms and handoffs before you add language models
• Buy better reporting before you buy another assistant
• Run a human-only baseline so you know if automation helped