Better Follow-Up Questions, Better Results

Improve the draft by naming the problem you actually see.

The first draft arrives. It has the right date and a cheerful opening. It also sounds as though it was written for a corporate retreat, and it leaves out where volunteers should check in.

You type, “Try again.”

The second draft has a new opening. The missing check-in instruction is still missing.

The assistant changed something. You needed it to change something specific.

Follow-up questions are how you direct the next revision. You do not need to start over every time a draft falls short. You need to identify the gap, explain the correction, and check that the revision solved it.

Read for a purpose before giving feedback

Suppose a fictional organizer named Marcus supplied these facts for a repair workshop:

• October 31, 2026, from 2 to 4 p.m.
• Cedar Room at Maple Hall.
• No experience required.
• Attendees bring a notebook.
• Check in at the welcome table.
• Reply to reserve one of the available places; no number of places was supplied.

The sample draft says:

Participants are invited to an immersive skills-development experience in the Cedar Room at Maple Hall on October 31, from 2 to 4 p.m. Bring a notebook and prepare to enhance your capabilities. Reply to reserve a place.

Before revising, Marcus identifies three gaps: stiff language, missing reassurance about experience, and missing check-in instructions.

That diagnosis is more useful than “I don't like it.” It gives him a way to recognize improvement.

You can sort feedback into four ordinary categories: facts, missing content, organization, and voice. Fix incorrect facts and missing essentials before polishing style.

Make the first correction narrow enough to inspect

Marcus starts with content:

Keep the event name, location, date, time, notebook instruction, and reply action. Add that no experience is required and that attendees should check in at the welcome table. Do not invent capacity, fees, or services. For this revision, focus on complete information.

Here is an illustrative revision:

Participants are invited to a repair skills-development workshop in the Cedar Room at Maple Hall on October 31, from 2 to 4 p.m. No experience is required. Bring a notebook and check in at the welcome table. Reply to reserve a place.

The voice still needs work, but the named content gaps are closed. Marcus can verify that without being distracted by five other changes.

For a simple task, it is fine to fix several related issues at once. Separating revisions is a teaching technique and a useful debugging habit, not a rule that every edit needs its own conversation turn.

Tell the assistant what to preserve

“Make this friendlier” can cause more than a change in tone. It may add a promise that everyone will leave with a repaired item or that refreshments are included.

Those additions are not merely stylistic.

Marcus supplies a second direction:

Keep every verified detail from the current version. Rewrite for a neighbor attending for the first time. Use ordinary words and a welcoming tone. Replace “skills-development” and avoid promises about results. Return only the revised invitation.

A possible result:

Come to our repair workshop in the Cedar Room at Maple Hall on October 31, from 2 to 4 p.m. No experience is required. Bring a notebook and check in at the welcome table when you arrive. Reply to reserve a place.

This version solves the tone problem while keeping the essentials. Marcus should still compare it with his fact list. An instruction to preserve information is not proof that every detail survived.

Quote the trouble spot

When you can point to a sentence, do it.

“The paragraph about timing is unclear” is helpful. “In the sentence beginning ‘Before arrival,’ distinguish the reply deadline from the event start time” is better when that is the actual problem.

You can also describe the reader's difficulty:

A first-time volunteer will not know what “intake” means here. Replace it with the specific action they need to take.

This connects the edit to its purpose. It avoids a revision that merely swaps one unfamiliar term for another.

For tables, name the row and column. For code, name the observed behavior and expected behavior. For a study explanation, name the first step you do not understand.

Do not reward agreement instead of accuracy

Sometimes the assistant's answer is correct and your objection is mistaken. A useful follow-up makes room for that possibility.

Imagine a plan showing three groups of eight people: 24 people total. You think the total should be 26.

“You're wrong; fix it” encourages a correction without explaining the evidence. Instead ask:

I expected 26, but the table shows 24. Check the group counts and arithmetic. Explain the discrepancy, and keep the correct number even if my expectation is wrong.

You can verify three times eight yourself. In a factual dispute, ask for the original evidence and inspect it. A changed answer, an apology, or a more confident tone does not establish which version is correct.

The AI Fluency course describes a cycle of specifying the work, evaluating what comes back, and refining the description while keeping human judgment involved. The revision method in this article applies that cycle to an everyday draft. Claude Academy: The Description–Discernment loop.

Students: ask for feedback you can act on

“Is my paragraph good?” may produce praise without helping you improve it.

A more useful request is:

Compare my paragraph with this assignment rubric. Identify one claim that needs evidence and one sentence whose meaning is unclear. Ask me a question that helps me revise each. Leave the rewriting to me.

Use an assignment only where that assistance is permitted. If it is not permitted, practice the same skill on a paragraph you wrote for an unrelated exercise.

After revising, explain what changed and why. That explanation helps distinguish your understanding from the assistant's fluency.

You can also challenge feedback: “You called this irrelevant. Which rubric requirement does it fail to support?” Treat criticism as something to evaluate, just as you would evaluate praise.

Know when a fresh start will help

A conversation can collect incompatible directions: formal, casual, very short, fully detailed, aimed at experts, aimed at beginners.

If the assistant keeps reviving old choices, prepare a clean brief with the current facts, the best draft, and the one next task. A new conversation needs the actual material; a reference to “that document from before” may not supply it.

Article 019 will show a full recovery method. For now, use this rule: continue when a targeted correction works; restart when you are spending more effort untangling old instructions than doing the task.

Your exercise

Use Marcus's fact list and the first sample draft. Make two revisions of your own: one for completeness and one for the intended reader.

Save all three versions. Beside each change, write the problem it solves. Then check every date, place, required item, and next action against the source list.

Completion check: Your revisions solve the problems you named, preserve the correct details, and add no unsupported promises.