When not to use AI: a practical test for business leaders

AI has got good enough that people now suggest it for problems it has no business touching. That happens with every new tool. The hard part is knowing when to say no, and you do not need to be technical to spot it.

Use a rule when the rule is clear

If the work follows a stable rule, write the rule. Don’t ask an AI model to decide whether an invoice is overdue, whether a field is blank, whether a file exists, or whether a number has crossed a threshold. Software has done that kind of logic reliably for decades, and it does not hallucinate.

AI is worth reaching for when the input is messy, the wording varies, or you need to interpret documents, images or language.

Use a form when the problem is missing data

Often the issue isn’t intelligence at all. Your staff or customers simply aren’t giving you the information you need. A better form with required fields, some validation and a cleaner handoff will fix that more reliably than any model.

AI can help read messy submissions. It’s a poor patch for a process that never asks for the right information in the first place.

Use integration when people are copying data

When staff are shifting data between systems you already know, API integration is usually the answer. AI might classify or tidy a few fields along the way, but the actual job is connecting the systems and deciding who owns what.

Swapping copy-paste for a language model is rarely the clean path.

Avoid AI where errors are unacceptable and review is weak

AI can be wrong, and wrong with total confidence. You can manage that when a human checks the output, when the system shows its sources, and when a mistake costs little. It gets much harder when the output decides something about safety, legal position, money, medical care or someone’s job, and nobody is reviewing it.

If you can’t support review, logging and correction, slow down.

Watch for novelty bias

AI can make a weak process feel exciting for a few weeks. Then the old problems wander back in: nobody owns the data, the approvals are still missing, and no one is on the hook for maintenance. A plain workflow fix looks boring next to a demo and usually does more.

The test is whether AI changes the outcome, not whether it changes the demo.

A useful question

Ask yourself: if this model vanished tomorrow, what simpler system would we build instead? If the answer is a database, an integration, a form or a rule engine, start there. If the answer is still “we genuinely need to read messy language, images or documents at scale”, then AI is probably the right tool.

Good AI strategy includes restraint. Turning down the wrong use cases is how you protect budget for the ones worth doing.