AI Missing the Point? Start With a Better Conversation

Why AI can sound right and still miss the point

When I give AI a document, I like to begin with something simple: tell me what you can about this. What do you think it says? What do you know from it? What do you still need?

I do that before asking for the finished piece of work. It gives me a chance to see its perspective, how it is going to communicate about the material, and what it is getting right or wrong.

Think about asking an employee to sell a house. You would not walk into the room, say “Go sell it,” and assume the person knew which house, what mattered about it, and what you wanted them to do. You would have a conversation first.

AI needs that context, too. The useful part of the first answer is that it gives you something you can inspect and correct before the work gets bigger.

This is one of the habits we practice in 15 Days of AI: getting from a conversation to useful work you can evaluate.

Watch Joe explain the habit

1 minute, 10 seconds. From The One-Person AI Business, 27:54–29:04.

Visual context: Joe speaks beside a shared Gemini screen showing a summary of an employee handbook. The lesson in this clip is his spoken explanation; no on-screen action is required to follow it.

Start with a conversation, not the finished assignment

Choose a short document whose contents you can check: an assignment brief, a procedure, meeting notes, or a handout. For a first attempt, familiarity is more useful than volume.

In the workshop, I used an employee handbook. We first asked what was in it, then moved toward a project guide and an onboarding checklist. You can follow that same progression with a much smaller source.

You can also practice by pasting the short example below into an AI conversation. Use materials you are permitted to share, and follow your school or workplace’s rules for the tool you choose.

What to ask before AI gets to work

My conversational starting point is simply to ask what AI can tell me about the material. When you want a more structured version, use this prompt. It adds a way to inspect the answer and leaves the final task for later.

Before doing the task, review the source I provided.

1. Tell me what it is, who it is for, and its main requirements.
2. Point to the passages that support your answer. Do not invent page numbers.
3. Identify anything important that is missing, unclear, or that you cannot access.
4. Separate what the source says from any suggestions of your own.
5. Ask what I want to do with it next. Do not create the final deliverable yet.

Keep your first answer brief enough for me to check.

The point is not to make AI promise it understands. The point is to get an answer you can compare with the original.

Read the text shown in the screenshot

Using only the employee handbook uploaded to this notebook, give a new reader a practical breakdown of the document so they understand what is in it and what they can do with it.

1. Start with two sentences explaining the document’s purpose and intended audience.
2. Create a concise table following the document’s actual structure. Use these columns: Section or topic; What you will find; How a reader could use it. Cover the major sections, combining minor sections where helpful. Cite the relevant handbook sections.
3. Suggest three useful tasks a new employee or onboarding coordinator could ask this notebook to do. Give one ready-to-use follow-up prompt for each.
4. End with a short What this document does not establish note. Distinguish content supported by the handbook from your proposed uses; do not invent policies or treat missing information as proof that no policy exists.

Use plain language and keep the whole answer under 500 words. Label the handbook as a historical 2012 practice example, not verified current company policy. Do not create a mind map, Canvas app, or code.

Catch a misunderstanding before it becomes a finished draft

Here is a fictional course brief created for this exercise. It is short on purpose: you can check every important requirement without searching through a long file.

Paste that source into your conversation, followed by the prompt above. Here is what to look for. These are illustrative checks, not a recorded AI response.

A useful correction is specific: The brief calls for one interview, not three. Correct that requirement and show the sentence you used.

After checking the answer, give it a job: Using those confirmed requirements, help me make an interview preparation checklist. Leave the actual interview quotations and reflection for me to write.

Check what’s right, what’s missing, and what it made up

A fluent summary can still miss a requirement. Open the original and compare the details that matter: names, dates, amounts, exceptions, intended audience and required outputs.

• Find the support. Does the cited passage actually say what the answer claims?
• Look for omissions. Did the answer leave out a requirement or restriction?
• Separate suggestions. Is a useful recommendation being presented as a rule from the source?
• Resolve unknowns. Ask the instructor, document owner or other appropriate person when the source does not answer an important question.

If you use Google’s notebook tool for source-based work, its citations can take you back to supporting passages. Open those passages and read them in context. Google explains how notebook citations work.

What to do when the conversation goes off track

It gives general advice instead of using your document.

Name the source again. Ask for a short quotation supporting each major point. If it cannot access the source, address that before requesting more work.

It says it cannot read the file.

Check that the intended file is attached and readable. Google recommends re-uploading a file if Gemini reports that it failed to analyze it. A short, shareable text excerpt can also let you narrow the exercise.

It keeps adding things the source does not say.

Ask for two labeled parts: “What the source states” and “My suggestions.” Check both. Repeating the instruction is not a substitute for reviewing the result.

The answer is too long to check.

Ask for the five most important requirements, each with its supporting passage. Work through one section at a time if needed.

Turn a checked answer into a useful next step

1. Choose the fictional brief above or one short document you know.
2. Ask what AI understands before assigning the final task.
3. Check three important details against the original.
4. Correct one issue, or explain why the checked details are supported.
5. Ask for one useful next step based on the confirmed requirements.

You have succeeded when you can explain what the source requires, what remains unknown, and why the next task makes sense. A polished answer alone does not tell you that.

Questions about getting more useful AI answers

About this lesson

Adapted from Joe McKenna’s The One-Person AI Business workshop, September 29, 2026. The opening explanation draws on his teaching at 27:54–29:04. The practice brief, structured prompt, checks and FAQs were developed for this article.

Official tool guidance checked September 29, 2026. Account features can change. Gemini file guidance · Notebook citation guidance

AI-assisted organization and supplementary examples. Clip captions are automatically generated.