How to design a survey (step by step, with examples)

A well-designed survey gives you clean, analyzable data. A badly designed one gives you confidently wrong conclusions — biased questions produce biased answers, and no amount of analysis fixes bad inputs. This guide covers how to design a survey that actually measures what you intend, from goal to question wording to the metrics that matter.

Step 1: Start with the decision, not the questions

Before writing a single question, answer: what decision will this survey inform? "Should we invest in the mobile app next quarter?" leads to a focused survey; "let's see what users think" leads to a bloated one nobody can act on. Write the decision at the top of your draft and cut any question that doesn't serve it.

Step 2: Choose the right question types

Each question type suits a different job:

Type	Use it for	Example
Multiple choice (single)	One answer from a set	"Which plan are you on?"
Multiple choice (multi)	Several answers apply	"Which features do you use?"
Rating scale / Likert	Attitude strength	"How satisfied are you? (1–7)"
NPS	Loyalty / word-of-mouth	"How likely to recommend? (0–10)"
CSAT	Satisfaction with a specific interaction	"How satisfied with support? (1–5)"
CES	Effort of completing a task	"How easy was it to…? (1–7)"
Ranking	Relative priority	"Rank these features by importance"
Open-ended	The why behind the numbers	"What would you improve?"

Rule: match the type to the analysis you'll run. If you need to compare groups statistically, use scales; if you need reasons, use open-ended — but sparingly, since they cost respondents effort and you time to code.

Step 3: Write unbiased questions

This is where surveys live or die. The most common biases and their fixes:

Leading questions — "How much did you love the new design?" presupposes love. Fix: "How would you describe your experience with the new design?"
Double-barreled questions — "How satisfied are you with our speed and support?" measures two things at once. Fix: split into two questions.
Loaded language — "Do you support this common-sense change?" Fix: neutral wording.
Absolutes — "Do you always use feature X?" Fix: offer a frequency scale (never / rarely / sometimes / often / always).
Assumptive questions — "What do you like about our mobile app?" assumes they use it. Fix: gate with a screening question first.

Worked example. Bad: "How helpful was our amazing new dashboard?" (leading + loaded). Good: "How would you rate the new dashboard? (Very unhelpful → Very helpful)" with a follow-up open-ended: "What, if anything, would make it more useful?"

Step 4: Order questions to reduce bias

Start easy — a simple, engaging question builds momentum. Don't open with demographics or a hard rating.
Group by topic — jumping between themes tires respondents.
Sensitive questions later — demographics and personal questions go near the end, after trust is built.
Avoid order effects — earlier questions can prime later answers; randomize option order for lists where it matters.

Step 5: Keep it short

Completion rate falls as length rises. Every extra question costs you responses and data quality (fatigue → straight-lining). Target 5–10 minutes maximum, and ruthlessly cut anything that doesn't serve the decision from Step 1. A focused 8-question survey beats a sprawling 40-question one every time.

Step 6: Pick your metric (NPS, CSAT, or CES)

If you're measuring experience, choose the metric that matches the question you're answering:

NPS (Net Promoter Score) — long-term loyalty and word-of-mouth. "How likely are you to recommend us? (0–10)"
CSAT (Customer Satisfaction) — satisfaction with a specific touchpoint. "How satisfied were you with…? (1–5)"
CES (Customer Effort Score) — how easy a task was; a strong predictor of loyalty. "How easy was it to…? (1–7)"

Full breakdown: NPS vs CSAT vs CES. Using a standard, validated metric means your results are benchmarkable and your scale is already proven — don't reinvent a satisfaction scale.

Step 7: Set your sample size before you launch

Decide how many responses you need before fielding, based on your confidence level and margin of error. For a large population at 95% confidence and ±5% margin, that's roughly 385 completed responses. Use a sample-size calculator to set the target — under-recruiting makes results unreliable, over-recruiting wastes reach.

Step 8: Pilot before you launch

Send the survey to 5–10 people first. Watch for questions people misread, options that don't fit, and where they drop off. A 20-minute pilot catches the ambiguous question that would have ruined 300 responses.

Step 9: Plan the analysis first

Know how you'll analyze before you write questions — it prevents un-analyzable data. If you plan to compare segments, make sure you capture the segmenting variable. If you'll run significance tests, use scales, not free-text. See how to analyze survey data.

Survey design checklist

[ ] One clear decision the survey serves
[ ] Question types matched to the analysis
[ ] No leading, loaded, or double-barreled questions
[ ] Easy questions first, sensitive ones last
[ ] Under 10 minutes to complete
[ ] A validated metric (NPS/CSAT/CES) where relevant
[ ] Sample size set in advance
[ ] Piloted with 5–10 people
[ ] Analysis plan written before launch

Common survey design mistakes

Writing questions before defining the decision — leads to bloat and un-actionable data.
Leading and double-barreled questions — the biggest sources of biased data.
Too long — fatigue destroys data quality in the back half.
Custom satisfaction scales when a validated NPS/CSAT/CES would be benchmarkable.
No pilot — you only find the broken question after it's ruined your dataset.

Design and analyze a survey free

ResearchRocket includes a drag-and-drop survey builder with 16 question types — including NPS, CSAT, CES, Likert, and rating-scale presets — plus distribution (shareable links, email lists, QR codes), and a real statistics engine to analyze the results. You design, field, and analyze in one place, with thematic coding for the open-ended responses.

FAQ

How do you design a good survey? Start with the decision it will inform, choose question types that match your analysis, write unbiased questions (no leading, loaded, or double-barreled wording), keep it under 10 minutes, use a validated metric, set your sample size in advance, and pilot before launching.

What are the main survey question types? Multiple choice (single and multi), rating scale/Likert, NPS, CSAT, CES, ranking, and open-ended. Match the type to the analysis you plan to run.

How do I avoid bias in survey questions? Avoid leading questions (that presuppose an answer), double-barreled questions (that ask two things at once), loaded language, and assumptive wording. Use neutral phrasing and offer balanced scales.

How long should a survey be? Aim for 5–10 minutes. Completion rate and data quality both drop as length grows, so cut every question that doesn't serve your core decision.

Should I use NPS, CSAT, or CES? NPS for long-term loyalty, CSAT for satisfaction with a specific interaction, CES for how easy a task was. Choose the one that matches the question you need answered.

How many responses does a survey need? Set it by confidence level and margin of error — roughly 385 for a large population at 95% confidence and ±5% margin. Use a sample-size calculator before launching.

Design and analyze a survey free on ResearchRocket →