To Questionnaire

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. Use the question shape from grilling for the setup questions — AskUserQuestion where available, otherwise chat.

The recipient has none of the user's context, so grilling's Frame the problem, then ask and Write it in Simplified Technical English rules govern the whole document, not just the setup questions. A question the recipient must decode is a question they answer badly or skip.

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 under the effort's .scratch/ directory as questionnaire-<slug>.md (slug from the topic), alongside the map or spec it serves — never loose in the repo root. When it unblocks a wayfinder ticket, link it from that ticket through the tracker's Assets operation. Report the path. Done when the file exists, is linked from any ticket it serves, and every item the user named in step 2 is covered by a question.

Document structure

Frame the document as a discovery questionnaire: the user lacks context, the recipient holds it. Order questions most-important-first — async means you may only get one pass — and group them under ## headings by theme once there are more than a handful. Write it using the template below.