Lecture 3-1: Asking Well
Contents 31
- Lecture 1-1: What the Word "AI" Points To
- Lecture 1-2: How a Language Model Makes Words
- Lecture 1-3: Sounding Right Is Not Knowing
- Lecture 1-4: Reading a Conversation Closely
- Lecture 1-5: Practice Lab, Read an AI Answer
- Lecture 2-1: Invented Facts
- Lecture 2-2: Old Knowledge, Missing Sources, Uneven Coverage
- Lecture 2-3: Scripture and Theology, Where to Be Most Careful
- Lecture 2-4: Building a Checking Plan
- Lecture 2-5: Practice Lab, Find the Errors
- Lecture 3-1: Asking Well
- Lecture 3-2: Checking What You Are Given
- Lecture 3-3: What Must Never Be Typed In
- Lecture 3-4: Keeping Notes and Giving Credit
- Lecture 3-5: Practice Lab, Mend the Prompts, Mark the Secrets
- Lecture 4-1: Hand It Over, Help With It, Keep It
- Lecture 4-2: Office Work and Communication
- Lecture 4-3: Teaching and Study Materials
- Lecture 4-4: Where Teachers and Leaders Draw the Line
- Lecture 4-5: Practice Lab: Hand Over, Help, or Keep
- Lecture 5-1: Preaching and AI: A Theological Question
- Lecture 5-2: Care and Counselling
- Lecture 5-3: When Members and Young People Use AI
- Lecture 5-4: The Minister's Own Life
- Lecture 5-5: Practice Lab: Judge the Scene, Write a Position Paragraph
Weeks 1 and 2 taught two things. A chat assistant continues language plausibly, and it can be wrong in a calm, confident voice. This week moves from understanding to practice. The first practical skill is the simplest one: how to ask.
Many people treat the question box as a place for a short wish: "Write a talk about hope." What comes back is a smooth, average talk about hope. It fits nobody, because nobody was described to it. The fault is not in the tool alone. A request that says nothing gives the tool nothing to work with, and the tool will fill the empty space with whatever is most common.
This lecture gives a plain way to ask. It is not a magic spell and not a secret code. It is the same care a good teacher takes when she gives a helper a task: say what you want, for whom, in what form, and where the edges are. You will also see that asking well does not make an answer true. A well-asked question gets a more useful answer. It does not get a checked one. Checking is the next lecture.
What these 15 minutes give you
- Name the five parts of a clear request: purpose, audience, form, role and limits.
- Rewrite a vague request so that it carries those parts.
- Break a large task into steps and ask for one thing at a time.
- Improve a first answer by replying in the same conversation.
- Explain why a good prompt is not a guarantee of a true answer.
He who gives answer before he hears, that is folly and shame to him." — Proverbs 18:13
World English Bible
The heart of the righteous weighs answers, but the mouth of the wicked gushes out evil." — Proverbs 15:28
WEB
The first proverb is about answering before understanding. It fits both sides of the conversation. A person who asks without thinking gets an answer to a question nobody meant. The second proverb says that the righteous weigh their answers. A tool does not weigh. The weighing, before the question and after the answer, stays with the person.
1. Why a plain request gets a plain answer
Lecture 1-2 explained that a language model continues text with the words that most often follow. If your request is short and general, the most likely continuation is a short, general text. Nothing in it has your congregation, your passage, your reader or your purpose in mind. Nobody told the tool about them.
Compare two people asked to "make a notice". A volunteer who knows your community will ask: for which event, for whom, how long, in what tone? A stranger will make something generic. A chat assistant is always the stranger. It does not know your room. It will not ask unless you invite it to ask, and even then it only knows what you tell it.
So the first discipline is to supply what a stranger would need. Not private details. We will come to those in lecture 3-3, and the rule there is firm. What you supply is the shape of the task, not the secrets of anyone's life.
2. Five parts of a clear request
Here is a simple frame. You do not need to use all five every time, but you should know which ones you left out and why.
- Purpose. What is this for? "A notice for the weekly bulletin" is a purpose. "Something about the event" is not.
- Audience. Who will read or hear it? Age, reading level, language. "Adults who read English as a second language" changes the words a great deal.
- Form. What shape should the answer take? A list of five items, one paragraph of about 100 words, a table with two columns, a draft with a gap where you will add a name.
- Role. You may ask the tool to answer as if it were a careful editor, a plain-language checker or a patient teacher. This is a way to set the style of the answer. It does not give the tool the knowledge or the of that role. An "experienced pastor" voice is a voice only.
- Limits. What must it not do? "Do not add any facts I have not given you." "Use no more than 150 words." "Do not quote Scripture; I will add it." Limits keep the answer inside the space where you can check it.
3. Before and after
Here is an invented example (an invented example). A volunteer needs help with a short notice.
| Before | After |
|---|---|
| "Write a notice about the work day." | "I need a notice for our weekly handout. Purpose: invite members to a work day to clean the hall. Audience: adults and teenagers, many of whom read English as a second language. Form: three short sentences and one line with the time, which I will fill in. Limits: do not invent a date or a place; leave a gap marked [time]. Plain words only." |
The second request is longer than the first. It is also much easier to check, because the volunteer knows exactly what the answer should contain and what it must not contain. The answer to the first request would have had invented details, and the volunteer would have had to hunt for them.
Notice what the "after" request does not contain: no names, no phone number, no address, no member's situation. The task was described. No person was described. That habit is worth keeping.
4. One thing at a time
A large request is often answered in a large, blurred way. If you ask for "a whole study guide for six weeks, with questions, a summary, a prayer and a timetable", the answer will be broad and thin, and an error in week 3 may be hidden among a great deal of text.
Break it up. Ask first for an outline of six weeks and look at it. Then ask for the questions for week 1 only. Then ask for a plain-language rewrite of one paragraph. Each step gives you something small enough to read closely, which is what checking needs. A short answer you have read is worth more than a long one you have skimmed.
5. Improving an answer by conversation
The first answer is a first draft. You can reply in the same conversation: "Shorter." "Use simpler words in the second sentence." "Keep the first paragraph and change the last." "You added a date I did not give you. Remove it." This is normal and it is how most useful work is done.
Two cautions. First, a long conversation has limited memory (lecture 1-2). Early instructions can fade. If the answer starts ignoring your limits, restate them, or begin a fresh conversation with a short summary of what you need. Second, do not mistake a tool's agreement for correctness. If you say "Are you sure?" it may change its answer, and the new answer is not safer than the first. It is a new continuation. When a fact matters, go to a source, not to a second round of asking.
6. Asking for a plan of checking
One useful thing to ask for is not content but a list of what in the answer should be checked. For example: "List each factual claim in your answer as a separate line, so that I can verify them." The tool may miss some claims, and it may list a claim wrongly, so this does not replace your own reading. It does give you a list to start from.
You can also ask the tool to mark where it is making a guess, or to say "I do not know" instead of filling a gap. Be careful here too. A tool can say "I am not certain" about something that is true and sound confident about something that is false. The confidence of its words is not a measurement. Treat such a note as a prompt for your own care, not as an assurance.
7. What a good prompt cannot do
A good prompt improves usefulness. It does not improve truth. A beautifully asked question can still receive an invented quotation, a wrong date or a confident mistake about a church tradition. The tool does not become more knowledgeable because you were polite, detailed or clever.
This matters in ministry because a well-formed answer to a well-formed request looks trustworthy. It reads as if the tool had understood. Hold on to what you learned in lecture 1-3: sounding right is not knowing. Asking well and checking well are two halves of one habit, and the second half cannot be skipped.
8. Do not turn asking into a ritual
Some people collect "perfect prompts" as if they were charms, and believe that the right phrase unlocks a better truth. There is no such phrase. The five parts above are ordinary clear communication, nothing more. If a request says what it is for, whom it serves, what shape it takes and what it must not do, it has done its work. If a method claims to make the tool reliable by wording alone, be careful: the claim is stronger than anything the tool's nature allows.
Diagram 1. A request in five parts
Diagram 2. Before and after, side by side
| A vague request | A clear request |
|---|---|
| "Write something about forgiveness." | Purpose, audience, form and limits are all stated. |
| One long request for a whole course. | One small step, read closely, then the next. |
| "Are you sure?" asked again and again. | A named source opened and read. |
| A hope that the right wording makes it true. | Clear asking, then checking. |
In short
- A tool knows only what the request contains, so a clear request names purpose, audience, form, role and limits.
- A role sets the style of an answer; it does not give the tool the knowledge or calling of that role.
- Ask for one small thing at a time so that you can read each answer closely.
- A first answer is a draft; improve it by replying in the same conversation, and restate limits if it drifts.
- Asking well makes an answer more useful, never more true; checking is still needed.
| Front | Back |
|---|---|
| Five parts of a request | Purpose, audience, form, role and limits. |
| What a role does | It sets the style of the answer; it does not give knowledge or calling. |
| Why one step at a time | A small answer can be read closely and checked. |
| What a good prompt cannot do | Make an answer true. Only checking against a source does that. |
One sentence to remember Ask clearly so that the answer is useful, and then check it, because clear asking never makes an answer true.
This week's action Take one real task from your week, write a request with all five parts, and note which part you would have left out.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Think of a task in your own place that you might ask a tool to help with. Which of the five parts would you most likely leave out? What would the answer lack?
- Why is a longer request often easier to check than a short one?
- A friend says, "I found the perfect wording, and now it never makes mistakes." How would you reply kindly?
- Which tasks in your community are small enough to be asked one step at a time? Which are too large?
- What is the difference between asking a tool to play a role and giving it the knowledge of that role?