to-questionnaire

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

转化为问卷

Turn into a Questionnaire

将用户无法独自回答的问题转化为一份问卷——一份 Markdown 文档,交给某个人异步填写,或在会议中共同填写。接收者拥有用户缺乏的知识;问卷负责把这些知识挖掘出来。
审问"发送"而非"主题"。 只询问用户关于"发送"的问题——这是他们总能回答的:发给谁,以及需要什么回来。文档中的问题则针对接收者所知与用户所需之间的差距
  1. 发给谁? 用一个来回问清楚接收者的角色、专长,以及和用户的关系。这决定了问卷的语气和需要携带多少上下文。完成条件:你知道了接收者是谁,以及他们知道什么用户不知道的东西。
  2. 你需要什么回来? 用一个来回问清楚用户无法独自解决、需要从这个人那里获得的具体决策或事实。完成条件:你有了一个具体的清单,列出用户必须能据此做出或决定的事情。
  3. 撰写问卷。 针对步骤 1-2 中确定的差距起草问题,遵循下面的文档结构。将问卷写入当前目录下的
    to-questionnaire-<slug>.md
    文件(slug 来自主题),并报告文件路径。完成条件:文件存在,且用户在步骤 2 中提到的每一个项目都有对应的问题覆盖。
Turn questions that you cannot answer alone into a questionnaire — a Markdown document, to be filled out asynchronously by someone, or together in a meeting. The recipient has knowledge that you lack; the questionnaire is responsible for extracting that knowledge.
Interrogate "sending" rather than "the topic". Only ask the user about "sending" — something they can always answer: who to send it to, and what needs to come back. The questions in the document target the gap between what the recipient knows and what the user needs.
  1. Who to send it to? Use a back-and-forth to clarify the recipient's role, expertise, and relationship with the user. This determines the tone of the questionnaire and how much context needs to be included. Completion condition: You know who the recipient is and what they know that the user doesn't.
  2. What do you need back? Use a back-and-forth to clarify the specific decisions or facts that the user cannot solve alone and needs to obtain from this person. Completion condition: You have a specific list of things that the user must be able to act on or decide based on.
  3. Write the questionnaire. Draft questions targeting the gaps identified in steps 1-2, following the document structure below. Write the questionnaire into the file
    to-questionnaire-<slug>.md
    in the current directory (slug comes from the topic), and report the file path. Completion condition: The file exists, and every item mentioned by the user in step 2 is covered by a corresponding question.

文档结构

Document Structure

将文档定位为一份发现问卷:用户缺乏上下文,接收者掌握它。按重要性排序——异步意味着你可能只有一次机会——当问题超过几个时,用
##
标题按主题分组。使用下面的模板编写。
<questionnaire-template>
Position the document as a discovery questionnaire: the user lacks context, and the recipient has it. Sort by importance — asynchronous means you may only get one chance — when there are more than a few questions, group them by topic using
##
headings. Use the template below to write.
<questionnaire-template>

<问卷标题>

<Questionnaire Title>

目的: 此问卷存在的原因以及它所影响的决策。
来自: <用户> — 发给: <接收者> — 你的回答将用于: <去向>
Purpose: The reason this questionnaire exists and the decisions it impacts.
From: <User>To: <Recipient>Your responses will be used for: <Destination>

背景

Background

一段话,为不了解用户背景的接收者提供上下文。足以让他们回答好问题,不超过一页。
A paragraph providing context for recipients who don't know the user's background. Enough to help them answer the questions well, no more than one page.

如何回答

How to Respond

截止日期和大致的投入时间。部分回答和"我不知道"同样有用——如果你对任何内容不确定,请标注出来,而不是跳过它。
Deadline and approximate time investment. Partial answers and "I don't know" are equally useful — if you're unsure about anything, please mark it instead of skipping it.

<主题标题>

<Topic Heading>

每个主题一个
##
部分。每个部分下按重要性排序的问题。每个问题只有一个想法——绝不复合——每个问题下方直接留有回答位置,并且仅在问题可能被误解或导致敷衍回答时才添加一行_为什么这很重要_。
<question-example>
One
##
section per topic. Questions sorted by importance under each section. Each question contains only one idea — never compound — with a space directly below each question for answers, and add a line of Why this matters only if the question might be misunderstood or lead to perfunctory answers.
<question-example>

系统预计在发布时承担多少负载?

What load is the system expected to handle at launch?

为什么这很重要:它决定了我们是现在为突发流量做准备,还是推迟到以后。
</question-example>
Why this matters: It determines whether we prepare for sudden traffic now or postpone it until later.
</question-example>

还有其他问题吗?

Any Other Questions?

一个开放的收尾问题:我们没问到但你应该告诉我们的任何事?
</questionnaire-template>
An open closing question: Anything we didn't ask but you should tell us?
</questionnaire-template>