Level 100: How AI works: AI at work and in life · Module 100.5

Two coworkers write together in a notebook beside a closed laptop.
Ask for a draft.

Talking to AI well · Plain gear

What you will learn

The course request checklist: a job, the facts, an example, rules, and something checkable.
The course combines advice on stating the job and supplying facts and examples (s1, s5), setting rules and allowing uncertainty (s5, s6), and asking for a checkable answer (s6). It is not a tested formula.
Figure data as text

A request you can check

This is the course’s checklist, not a formula tested as a whole.

PartWhat you writeLesson sources
The jobSay what you want and who it’s for.s1, s5
The factsGive the information it needs for this job.s1, s5
An exampleShow what a good answer looks like.s1, s5
The rulesSet limits and say what to do if unsure.s5, s6
Something checkableAsk for quotes or figures you can verify.s6

What you type into an AI tool is called a prompt. A prompt is like a note to a very fast new helper. The helper is smart and has learned a lot, but it has never met you. It does not know your job, your customer or your deadline unless you tell it.

One rule never changes. The AI writes a draft. You decide what happens next. It does not send, sign or agree to anything for you.

Short is not best

Lots of people type a few words, like "write an email to a supplier." Then the AI has to guess. Who is the supplier? What should the email say? How long should it be?

Researchers collected more than 10,000 prompts that people shared online.1 Almost all of them had a main part that explained the job and the background. Then the researchers ran a smaller test with one AI, GPT-4, on two kinds of jobs: writing for search engines and writing prompts for making pictures. When they took that main part out, the scores dropped more than when they took out any other part.1

A company that makes AI tools, Anthropic, says the same thing in its own guide. It says to treat the AI like a brilliant new worker who does not know how your team does things. The clearer you are, the better the result.2

The five parts of a good request

This course uses a five-part checklist. Think of it like ordering a cake from a baker.

  1. The job. Say what you want and who it is for. "A birthday cake for my dad's 60th."
  2. The facts. Give the details it needs. "Chocolate. Serves 12. Pick-up on Saturday."
  3. An example. Show what good looks like. "Like the one in this photo."
  4. The rules. Say what to avoid. "No nuts. Keep it under $40. Call me if you are not sure."
  5. Something you can check. Ask them to read it back. "Write down what you are making, so I can check it."

Here is why each part helps.

One popular trick is to start with "act as an expert." In those two tests, that made only a tiny difference.1 The job and the facts did more.

A real case: a clear job, done faster

In 2022, researchers gave 95 programmers the same job: build a piece of software called a web server.6 The job was very clear. It came with twelve tests, and you were done when your work passed all twelve.6 About half of them could use an AI coding helper. Among the programmers who finished, the ones with the AI helper took less than half as long on average: 55.8% less time.6 That is time saved on one task. It does not mean they got 55.8% more work done overall.

This study did not test prompts. It shows something else: what a clear job with a built-in check looks like. Everyone knew what "done" meant. It was also only one task, and the researchers did not check how good the code was.6

The first answer is a first draft

Think about writing an important email. You write it, read it, then fix it. Researchers found that AI is the same. It does not always give its best answer on the first try.7 When they asked the AI to look at its own answer, say what was wrong and try again, the answers got better on seven different kinds of tasks.7

In that research, the AI wrote the feedback for itself. You can be the one who gives the feedback instead. The study did not test people writing feedback, so the tips below are this course's advice based on it, not proven results.

Good follow-ups to try:

At Big Widget Company (a made-up story)

Big Widget Company and its people are made up. The research above is real.

Priya buys parts for Big Widget Company. She needs a supplier to deliver two weeks later.

The AI wrote the draft. Priya made the call. What if the supplier writes back asking for more money? That is not Priya's call to make. She does not ask the AI to agree. She waits, and takes it to her manager.

Three-yes check (only the parts about asking well; lesson 100.9 covers Get to Yes, Stay at Yes and Recover to Yes in full).

Remember

Words to know: prompt, context (the facts you give it), example, follow-up, iterate (try again and improve).

Sources

  1. s2 Yihan Ma, Xinyue Shen, Yixin Wu, Boyang Zhang, Michael Backes, and Yang Zhang (2024). The Death and Life of Great Prompts: Analyzing the Evolution of LLM Prompts from the Structural Perspective. Paper. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩ ↩ ↩ ↩
  2. s5 Anthropic (2026). Prompting best practices (Claude documentation). Official doc. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩
  3. s1 Tom B. Brown et al. (2020). Language Models are Few-Shot Learners. Paper. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩
  4. s6 Anthropic (2026). Reduce hallucinations (Claude documentation). Official doc. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩ ↩ ↩ ↩ ↩
  5. s7 AiGovOps Foundation (2026). The AiGovOps Foundation café — start with your problem (Practice home page; object table, Receipt row). Official doc. Checked 2026-11-17 by source-checker round-3 re-check (separate Claude Code session 1b682d3d). ↩ ↩
  6. s4 Sida Peng, Eirini Kalliamvakou, Peter Cihon, and Mert Demirer (2023). The Impact of AI on Developer Productivity: Evidence from GitHub Copilot. Paper. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩ ↩
  7. s3 Aman Madaan et al. (2023). Self-Refine: Iterative Refinement with Self-Feedback. Paper. Checked 2026-11-17 by source-checker round-2 re-check (separate Claude Code session 9d48e5af). ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩

Next: the quiz