questionnaire-design
Installation
SKILL.md
Purpose
Design requirements questionnaires that collect structured data from many stakeholders when individual interviews are impractical. Questionnaires scale elicitation to large audiences but sacrifice depth -- they confirm and prioritize what you already know rather than discovering new requirements.
This is not a replacement for interviews (see skills/elicitation-interview/SKILL.md) or observation (see skills/observation-analysis/SKILL.md). Use questionnaires after initial elicitation to validate, prioritize, and quantify findings across a broader population.
Key Concepts
When Questionnaires Work (vs. Interviews)
| Criterion | Questionnaire | Interview |
|---|---|---|
| Audience size | 20+ stakeholders | 1-5 per session |
| Question type | Closed, structured, predefined options | Open-ended, exploratory |
| Discovery power | Low -- confirms known requirements | High -- discovers new requirements |
| Depth | Shallow -- no follow-up possible | Deep -- can probe and clarify |
| Geographic reach | Any location, asynchronous | Requires scheduling and access |
| Bias risk | Question wording, order effects | Interviewer leading, rapport effects |
| Best timing | After initial elicitation | Early in requirements discovery |