Turn something the user cannot answer alone into a questionnaire: a Markdown document for one person to fill out asynchronously, or to fill out together in a meeting. The recipient holds the knowledge the user lacks; the questionnaire should extract that knowledge.
Grill the send, not the subject。 Interview only around what the user can always answer: send : whom to send it to, and what needs to come back from them. The questions in the document then target the gap。
-
Whom to send it to? In one exchange, ask about the recipient's role, expertise, and relationship to the user. This determines the questionnaire's tone and how much context it needs to carry. This step is done when you know who the recipient is and what knowledge they have that the user does not.
-
What needs to come back? In one exchange, ask about the specific decisions or facts that the user cannot resolve alone and needs this person to provide. This step is done when you have a specific list clarifying what the user must ultimately be able to do or decide.
-
Write the questionnaire. Draft questions based on the gap from steps 1–2, and follow the Document structure below. Write the file to the current directory as
to-questionnaire-<slug>.md(slug from the topic), then report the path. Done when the file exists and every item the user listed in step 2 is covered by a question.
Document structure
Position the document as discovery questionnaire: the user lacks context, and the recipient has it. Order questions by descending importance; asynchronous communication may only get one chance; when there are more than a few questions, place them under ## headings by theme. Use the following template.
Purpose: <why this questionnaire exists, and which decision it relates to>
From: <user>, To: , How your answers will be used: <where the answers will be used>
Context
Use one paragraph to help a recipient who does not know the user's thinking build context. Enough for them to answer seriously, but do not fill a page.
How to answer
State the deadline and the approximate time required. Partial answers and "I don't know" are also valuable; when unsure, mark it rather than skipping it.
Use one ## section per theme, with questions ordered by descending importance. Each question contains only one idea; never combine multiple questions; place the answer stub directly below. Only add a line when the question could be misunderstood or answered perfunctorily: why this matters。
Why this matters: This determines whether we reserve resources now for a traffic spike, or handle it later.
Anything else?
Finally, provide a catch-all question: what else have we not asked that we should know?