47 of 81
ContentsPart IV · Chapter 11

Chapter 11Asking well

Treat the first answer as a draft

The doctors’ trial has one more lesson. The researchers didn’t write their prompt once; they refined it over several rounds.1 A first answer is a first draft, and the request that produced it can be a draft too. Three habits help you improve both.

  • Hand it your sources. When the facts are in front of the model, it doesn’t have to recall them. In a 2020 study, a model that looked up relevant documents and read them along with the question gave more specific and factual responses than one without that step.2 Paste the policy, attach the schedule, quote the email you are answering.
  • Ask it to ask you. Begin with “Before you start, ask me anything you need to know.” Its questions show you what it would otherwise have guessed.
  • Say what to change. A follow-up such as “shorter, and lead with the deadline” takes a few seconds and keeps what already works.

Once a request works, keep it. The trial’s authors suggested that organizations could build well-designed prompts into the tools doctors already use, so that nobody has to invent a good one from scratch.1 You can do a small version of the same thing. Save the requests that worked for tasks you repeat, such as the monthly summary or the weekly update, and next time change only the parts that differ. A saved request is also easy to share with a colleague, which spreads the asking along with the answer.

An illustration, not a real case. A middle-school teacher is about to type “a quiz on fractions.” She stops and runs through the six parts instead. Who it’s for: sixth graders who have just learned to add fractions with different denominators. An example: one question copied from her own worksheet. Limits: eight questions, no word problems. The shape: questions first, answer key at the end. When the draft comes back, she reads it as she would a student teacher’s, then replies with what to change: “Make the last two easier, and add one with mixed numbers.” Two short rounds, and the quiz is hers.

This book was made the same way. Its chapters were drafted with AI help from instructions that named the reader, the research standard and the examples to use. Then every claim was checked against its source, and the drafts were revised.

Your turn

Try it. Pick a real task from your week: an email, a summary, a plan. With any AI tool you already use, send your usual one-line request first and keep the answer. Then start a new conversation and send the six-part version, with the key instruction at the start. Compare the two. Then test one of this chapter’s claims: begin a third conversation with “Before you start, ask me anything you need to know,” and count how many of its questions your first request had left it to guess. On paper instead: write out the six parts for the task, then circle each part your usual request leaves out. Each circle is a guess you have been asking the model to make.

Think about it. Think of the best briefing you ever got at work, from a manager, a mentor or a colleague handing over a project. Which of the six parts did it include? Which do you tend to leave out when you hand work to someone else?

So what makes one request work better than another is what makes a good briefing work: it says the job, who it’s for, the background, an example, the limits and the shape, and it puts the key instruction where it won’t get lost. Then it treats the first answer as a draft. A better request gets you a better draft, but not a checked one. The doctors’ trial ended with a warning against trusting the model without oversight, and that raises the next chapter’s question: how do you check what an AI tool tells you?

Check in

Try answering in your own words, then open each one to compare.read the answer to compare.

What are the six parts of a good request, and what happens when you leave one out?

The job, who it’s for, the background, an example, the limits and the shape you want. The model doesn’t stop to ask about a missing part; it guesses, and the guess may be wrong.

Why does an example in a request help so much?

A model writes by continuing the text in front of it, so a sample shows it the pattern to follow: tone, length and layout at once. The GPT-3 paper showed a model doing many new tasks from a few examples in the prompt, with no retraining.

Chapter 6 described the prompt as a stack of layers. Which layer does this chapter’s advice work on, and who writes the rest?

Your message, the one layer you control. The rest, such as the model maker’s and the app’s instructions, files and earlier turns, is put together by the software and mostly written by others.

A coworker is about to paste three long reports into an AI chat, with the line “compare only the 2025 figures” tucked between the second and third. What would you suggest before they send it?

Move that instruction to the start, and repeat it at the end, rather than burying it in the middle of the pasted material. Paste only the parts of the reports that matter. In tests, models used information in the middle of a long input less reliably than at the start or end.

Two requests ask for the same summary. One runs to several pages, with the project’s whole history and every meeting note pasted in. The other is a short paragraph that gives the job, the audience, one example, a length limit and the shape. Which would you expect to work better, and why?

Most likely the short one, as long as it covers what the model would otherwise guess. More material isn’t automatically more help: in tests, extra documents beyond a point added little and gave the model more to work through. What counts is having the right parts, with the key instruction where it won’t get lost.

Next: Chapter 12: Check before you trust →

Notes (2)
  1. 1Ethan Goh et al., “Large Language Model Influence on Diagnostic Reasoning: A Randomized Clinical Trial,” JAMA Network Open 7, no. 10 (October 28, 2024): e2440969, https://doi.org/10.1001/jamanetworkopen.2024.40969.
  2. 2Patrick Lewis, Ethan Perez, Aleksandra Piktus, Fabio Petroni, Vladimir Karpukhin, Naman Goyal, Heinrich Küttler, et al., “Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks” (preprint, arXiv, May 22, 2020), https://doi.org/10.48550/arXiv.2005.11401. Cited at abstract; p. 1.

Chapter 11 · page 4 of 4

Turn pages with the ← and → keys.

Cite this page

Using this book

© 2026 Steve Sparks. All rights reserved. Teachers and students may assign, read, quote and excerpt chapters of this book for classes and study, with credit to Steve Sparks and a link to aifromthepartsup.com. Anyone may quote short passages and cite any page, with a link back. To repost, reproduce or sell the book or larger parts of it, ask through GitHub.

Quoted material and figures from other sources remain their owners'.