When AI helps and when it does not

So the question is never "Is AI smart enough?" The question is "Does this task reward plausible, or does it demand verified?"

The two-question decision rule

Before you trust an AI's output, ask two things:

1. Is this a draft or a final answer?

A draft is something you will review and edit. A final answer goes straight out the door with your name on it.

2. Is it easily verifiable?

Can you check it in seconds, or would a mistake slip through unnoticed?

Here is the rule:

• Green light: It's a draft, OR you can verify it quickly. Use AI freely.
• Yellow light: It's a final answer but easy to check. Use AI, then verify every claim.
• Red light: It's a final answer AND hard to verify AND someone is accountable for it being right. Do not outsource this to AI.

Green-light tasks: let AI run

These play to the model's strengths: language, structure, and first drafts.

Reformatting and reshaping

You give it the content. It just changes the form. Low risk, because the facts came from you.

• Turn messy notes into a clean email.
• Convert a paragraph into bullet points.
• Rewrite a blunt message in a warmer tone.

First drafts of anything

A blank page is expensive. A rough draft you can fix is cheap.

• Draft a job description, then edit for accuracy.
• Outline a presentation.
• Write three subject-line options for a newsletter.

Brainstorming and explaining

• "Give me 10 angles for a blog post about remote work."
• "Explain how compound interest works, like I'm 15."

If a brainstorm idea is slightly off, you just don't use it. No harm done.

Red-light tasks: do not trust the output alone

These need exact facts, current data, or real accountability. The lawyer's mistake lives here.

Exact facts and figures

• Legal citations, medical dosages, tax rules, specific statistics.
• "What was Apple's exact revenue in Q3 2024?"

The model may produce a number that looks right and is wrong by billions.

Current or real-time information

A model's core knowledge has a "training cutoff" (the date its built-in knowledge stops). On its own, it does not know today's news, today's prices, or what happened this morning.

In 2026, most tools (ChatGPT, Gemini, Claude) can search the web when you ask, which helps a lot. But "can search" is not "did search," and search results can still be misread. Always check the actual source link.

Anything where someone is accountable

• Sending medical advice to a patient.
• Filing official documents.
• Public statements your company will stand behind.

If a human is responsible for it being correct, a human must verify it.

Math and precise counting

Models have improved, but they still slip on multi-step arithmetic. For real calculations, use a calculator or a spreadsheet, or ask the AI to write code that does the math instead of doing it in its head.

The yellow zone: verify, don't trust

Most real work lives here. The trick is making verification fast.

A great move: ask the AI to show its sources so you can check them.

Then you actually click the sources. If it can't produce a real, checkable source, treat the claim as unverified.

Another tactic: ask it to flag its own uncertainty.

This won't catch everything, but it surfaces the riskiest claims so you know where to look.

For a clear, free primer on how these systems generate text (and why they make things up), see Google's Introduction to Large Language Models.

A real workflow: drafting a customer email

Let's combine everything. Say you need to email a customer about a refund policy.

Step 1 (Green): Draft the structure.

Draft a friendly email to a customer asking about our refund window.
Leave a [PLACEHOLDER] anywhere a specific policy detail should go.
Don't invent any policy numbers.

Notice the instruction: don't invent details. You force the AI to leave gaps instead of guessing. The gaps are honest. A fabricated "30-day policy" is dangerous.

Step 2 (Red, so you do it): Fill in the facts.

You look up your actual refund policy and replace each [PLACEHOLDER] yourself. This is the part with real accountability, so a human owns it.

Step 3 (Green): Polish.

Here's my completed email with real policy details.
Tighten the wording and keep the tone warm. Don't change any numbers.

The AI did the heavy lifting on language. You owned the facts. That division of labor is the whole game.

When AI quietly crosses from green to red

Watch for the sneaky shift. A task starts as a harmless draft and slides into a final answer without you noticing.

You ask for a "draft" report, like the numbers, paste them into a real document, and ship it. Now those AI-generated numbers are a final, accountable answer, and nobody verified them.

The fix: decide up front which parts are draftable language and which parts are facts you must verify. Mark the facts. Never let an unchecked number graduate to "final."

A quick mental checklist

Before you hit send on anything AI touched:

1. Did I add or verify every specific fact, number, name, and date?

2. Did I click any source links the AI gave me?

3. If this needed current info, did the tool actually search, and did I check the result?

4. Would I be comfortable if a mistake here had my name on it?

If any answer is "no," you're not done.

Key Takeaways

• Ask two questions before trusting AI output: Is it a draft or a final answer, and can I verify it quickly? Drafts and verifiable tasks are green. Hard-to-verify final answers are red.
• Green light: reformatting, first drafts, brainstorming, explaining. The risk is low because you supply and control the facts.
• Red light: exact facts, current data, precise math, and anything where a human is accountable. Verify these yourself, every time.
• Make verification fast: ask the AI for checkable sources, tell it to flag low-confidence claims, and instruct it to leave [PLACEHOLDER] markers instead of guessing.
• Watch the silent shift from draft to final. The moment an unchecked AI number lands in a document you ship, it became your accountable answer. Verify before it graduates.