customer-survey-designlisted

# Customer Survey Design Design surveys that produce **answers you can act on**, not vanity data. The discipline is starting from the decision the survey must inform and writing questions that don't lead the respondent — most surveys fail by asking biased questions that confirm what the author hoped. The second, quieter failure mode is fielding a survey that can't answer its own question: 60 responses split across five segments, then decisions made on ±13-point noise. This skill computes what a readable survey actually requires **before** anything is sent — and refuses to bless segment cuts the sample can't support. ## When to use The user is about to field a survey and needs the questions, structure, and sample plan to be right before it goes out. ## Before you start 1. **Name the decision.** What will you do differently based on the results? If a question doesn't inform a decision, cut it. 2. **Identify the respondents** and how you'll reach them (existing customers, churned users, prospects, market panel) — this shapes wording and length. Get the reachable audience size and a realistic response rate if known. 3. **List the cuts you'll report.** If the readout says "by segment," the sample must be sized for the smallest cell, not the total. 4. **Pick the survey type** to match: PMF ("how would you feel if you could no longer use this?"), NPS + why, onboarding/CSAT, churn reason, or discovery. ## Method The engine (`resources/survey-design.js`, Node, stdlib only) com