to-questionnaire

Topics in the source

• Document structure
• Context
• How to answer
• What load is the system expected to handle at launch?
• Anything else?

Turn something the user can't answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them. Grill the send, not the subject. Interview the user only about the send, which they can always answer: who it goes to, and what they need back. The questions in the document then target the gap between what the recipient knows and what the user needs. 1. Who is it going to? Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't. 2. What do you need back? Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide. 3. Write the questionnaire. Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to to-questionnaire- .md in the current directory (slug from the topic) and report t

This is an excerpt. Refer to the complete source and its current requirements.