Question Craft — Asking Questions That Get Real Answers
| Field | Value |
|---|---|
| Type | Skill Resource |
| Source | ~/.copilot/skills/technical-writing/references/question-craft.md |
| Description | Not specified |
Source Content
Question Craft — Asking Questions That Get Real Answers
Use this guide whenever a document asks questions of people: surveys, feedback forms, user research scripts, interview guides, or the clarifying questions an agent asks before writing. Generic questions get generic answers. The writers below built careers on refusing the generic — steal their moves.
The masters and their moves
Each profile ends with the move you can apply in a written question.
The profile interrogators
Joan Didion
Her technique was silence. She used her quiet, unassuming presence as a strategy, and sources rushed to fill the empty space with revealing admissions.
The move in writing: leave room. Follow a hard question with a large open text box and no suggested answers. Never stack a multiple-choice list under a question that deserves a story.
Janet Malcolm
She treated subjects with legalistic precision and asked brutal, foundational questions about self-deception and how people frame their own stories.
The move in writing: ask the question behind the question. Not “did the docs help?” but “what did you tell your teammate about the docs afterward?” People reveal more when describing what they told someone else.
Oriana Fallaci
The ultimate political interrogator. She asked world leaders aggressive, unvarnished questions about power — and forced Khomeini and Kissinger into shocking candor.
The move in writing: ask the unvarnished version once. Every survey earns one direct question with no cushion: “What almost made you give up?” Soft phrasing everywhere produces soft data everywhere.
The modern narrative masters
Terry Gross
Host of NPR’s Fresh Air. She builds instant intimacy through meticulously researched, empathetic questions that find the exact memory or turning point that shaped a person.
The move in writing: do the research first, and show it. “You mentioned in your ticket that the install failed twice — what happened the second time?” beats “describe any issues.” Referencing what you already know earns a real answer.
Louis Theroux
He uses an ultra-polite, intentionally naive style. It disarms people and coaxes them into explaining their own logic without feeling attacked.
The move in writing: play naive on purpose. “Walk me through it like I’ve never seen the tool” removes the fear of sounding dumb — for both sides. Naive questions surface the assumptions experts forgot they were making.
Amanda Ripley
An investigative journalist who trains writers to use mediation questions. Her work focuses on “complicating the narrative” — breaking through ideological loops to find what people actually want.
The move in writing: complicate the binary. Replace “do you prefer A or B?” with “what would have to be true for A to work for you?” The second question surfaces motivation; the first just counts votes.
Techniques shared by all of them
The pattern interrupt
Bypass rehearsed answers with unexpected, sensory-specific questions. “What was on your screen when it broke?” gets a memory; “how was your experience?” gets a script.
Looping
Treat the exchange as a conversation, not a checklist. Repeat what you heard in the respondent’s own words, then ask the follow-up. In surveys, this means branching: the answer to question 2 should change question 3.
Probing the resistance
Notice what the subject avoids, then circle it gently. If every answer skips the pricing page, the next question is about the pricing page. What people route around is usually the finding.
Rules for written questions
- One question per question. “Was setup fast and clear?” is two questions wearing one question mark. Split it.
- Concrete beats abstract. “Tell me about the last time you deployed” beats “how often do you deploy?” Memory of a specific event is reliable; self-estimates are not.
- Never lead. “How much did the new dashboard help?” assumes it helped. Ask “what changed after the new dashboard?”
- Ask for stories, not ratings, when you need insight. Ratings measure; stories explain. Use ratings only when you already know what you are measuring.
- End with the Didion question. Close every survey with open space: “What should we have asked about?”
A worked example
Jack shipped a survey asking “How satisfied are you with our CLI? (1–5)”. He got a 4.1 average and no idea what to fix.
Jill asked instead: “Think of the last time the CLI made you swear. What were you trying to do?” She got forty specific failures, and three of them accounted for most of the pain. The fix list wrote itself.
That is the whole craft. A rating told Jack people were mostly fine; a story told Jill exactly what to build next.