Surveys

Your Research Goal

Choose who to survey based on your research goal. If you’re gathering feedback on a live product or feature, existing users are your best source. If you’re testing a new idea or exploring an unfamiliar space, consider potential users or a lookalike audience that reflects your target user type.

Set Up for Segmented Results

To make your insights more actionable, ask a few key questions at the start of your survey to help you segment responses later—such as user role, experience level, or how frequently they use your product. Keep these questions short, relevant, and respectful. They provide critical context when interpreting answers and identifying patterns across different user groups.

Anonymity Can Increase Honesty

Decide whether your survey will be anonymous. Anonymity can encourage more honest responses—especially when you’re asking about sensitive topics or pain points.

If you’d like the option to follow up with specific participants, include a clear opt-in question at the end of the survey allowing them to provide their contact information.

No matter which approach you take, be transparent. Set expectations early so participants understand how their data will be used and whether their responses will be attributed to them.

Surveys can be useful at multiple stages of a project—each offering a different kind of value. The key is to plan ahead, so the insights come in time to inform meaningful decisions.

Use Surveys as Strategic Checkpoints

Surveys work well as lightweight, scalable check-ins that complement deeper research methods like interviews or usability testing. You might use them:

• Early on, to explore user needs, attitudes, or pain points
• Mid-way, to validate concepts, design directions, or feature priorities
• After launch, to measure satisfaction, usability, or feature adoption

By placing surveys at key inflection points, you can make more informed decisions—and ensure the project stays aligned with user needs.

Build in Enough Time—Not Just for the Survey Itself

Running a successful survey involves more than just sending it out. To truly benefit your project, you’ll need to account for each step in the process:

• Planning and creating the survey (1–3 days): Crafting good questions, reviewing with stakeholders, and setting up your tool
• Fielding the survey (3–10 days): Giving participants enough time to respond, especially if you’re targeting busy users
• Analyzing results (2–5 days): Cleaning data, reviewing patterns, and summarizing insights
• Sharing and acting on insights (2–5 days): Aligning with your team, presenting findings, and using them to guide design or roadmap decisions

All of this can take 1–3 weeks, depending on complexity. If insights are needed for a sprint, feature decision, or stakeholder presentation, make sure your survey timeline aligns accordingly.

Keep Surveys Timely and Actionable

The biggest risk with survey research is getting results too late to influence decisions. If the team has already moved on, even great insights may be dismissed or ignored.

To get the most out of your effort, plan surveys to lead, not lag—so they feed directly into the phase of the project where clarity is needed most.

Quality First, Then Quantity

You don’t always need hundreds of responses—but you do need the right people. A small, well-targeted sample (30–100 participants) can reveal strong patterns, especially if the feedback is consistent across users who closely match your audience.

Confidence Comes from Coverage

If your goal is to identify generalizable trends or compare subgroups (e.g., by role, experience, or demographics), then a larger, more diverse sample increases the reliability of your insights. The more consistent a result is across a broad range of users, the more confidently you can act on it.

This is the essence of the confidence equation: higher volume + higher diversity = higher trust in what you’re seeing.

Beware of Drawing Conclusions from Too Little

It’s tempting to treat a few strong quotes or percentages as definitive—but small samples can be misleading. Just because 3 out of 5 people say something doesn’t mean it holds true for your wider user base. A handful of responses should be treated as signals, not proof.

If your sample size is small, treat your results as directional. Use them to inform where to explore further—not as the final word.

Match Your Sample to Your Goal

For quick feedback on a narrow feature, a smaller, focused group may be enough. For shaping major decisions, validating hypotheses, or presenting data to stakeholders, invest in broader outreach to increase coverage and confidence.

Before writing your survey, get clear on what you’re trying to learn. A strong goal gives your survey structure and ensures the results lead to useful insights—not just interesting data.

Start with a Clear Objective

Begin by framing a research question that your survey will answer. Examples include:

• “How do users feel about this workflow?”
• “Which feature is most valuable?”
• “What’s preventing users from completing a task?”

This focused approach will help you choose the right participants, craft the right questions, and recognize useful patterns in your results.

Avoid Survey Creep

Trying to answer too many questions at once can make your survey long, unfocused, and hard to analyze. Stick to one clear objective. If you have multiple goals, consider breaking them into separate surveys or research activities.

Ask Yourself These Questions First

Before writing your survey, check your alignment by asking:

• What decision will this survey help inform?
• Is this the right method to answer that question?
• How will I use what I learn?

These answers will guide the survey’s length, structure, and tone.

Purpose Drives Quality

With a clear goal in place, your survey becomes a purposeful tool—not just a list of questions. It helps you stay focused, collect cleaner data, and make better, more confident decisions.

Surveys can unlock valuable insights—but they’re even more powerful when your team is aligned on what you’re trying to learn and why.

Involve Stakeholders Early

Before drafting your survey, connect with key stakeholders—product managers, designers, marketers, engineers, leadership, or support teams. Ask them:

• What do you want to learn from users right now?
• Are there assumptions we should test?
• What upcoming decisions could this survey support?

Getting input upfront helps you design a survey that reflects shared goals and fills real knowledge gaps across the team.

Create Buy-In for the Results

When teammates help shape the survey, they’re more likely to trust and use the findings later. Early collaboration builds ownership and encourages action based on the results, rather than treating the survey as an isolated research activity.

Choosing the right survey tool can make your process smoother and your results more reliable. Look for these key features when selecting a platform:

• Ease of Use: The tool should be simple to set up and easy for respondents to complete.
• Question Types & Logic: Support for different question formats (multiple choice, rating scales, open text) and skip or branching logic to create a tailored experience.
• Customization: Ability to match your brand or survey style for a polished, professional look.
• Distribution Options: Multiple ways to share your survey—via email, links, or embedded in apps or websites.
• Data Export & Analysis: Easy access to raw data with export options (CSV, Excel) and built-in analysis tools or integrations.
• Accessibility: Ensure the tool supports accessibility standards for all users.
• Security & Privacy: Look for platforms that respect data privacy and comply with relevant regulations.
• Cost & Availability: Consider budget and platform availability; for example, Microsoft Forms is widely accessible and free for the Yale Community.

Selecting a tool with the right features for your goals and audience helps ensure smooth data collection and actionable insights.

 Keep It Short

Surveys should take 5 minutes or less to complete—10 minutes at most. The longer the survey, the higher the risk of drop-off or rushed answers. Being respectful of your users’ time increases both completion rates and response quality.

Set Expectations Up Front

Let participants know exactly what they’re committing to before they begin. Include a brief intro message at the top of your survey that answers:

• How long it will take (e.g., “This survey takes 3–5 minutes”)
• Why their input matters
• Whether their answers are anonymous

Setting expectations creates trust and encourages more thoughtful, complete responses.

Use a Progress Indicator

If your survey tool supports it, enable a progress bar or percentage tracker. This helps reduce abandonment by showing participants how far along they are and how much is left.

Even in shorter surveys, this small UI detail makes the experience feel more transparent and manageable.

Prioritize Only What You Need

Be ruthless about cutting unnecessary questions. Every additional item adds cognitive load and increases the chance of survey fatigue. Focus on what you absolutely need to learn for this phase of the project—not everything you’re curious about.

You can always follow up with more targeted research later if needed.

When designing a survey, remember—you’ll be reviewing the results manually or with limited tools. Think ahead about how you’ll process the data.

Use Open-Ended Questions Sparingly

Open-ended questions can offer rich, qualitative insight—but they take much more time and effort to analyze. Use them strategically, and only when you truly need detailed, user-generated responses that you can’t get from a structured format.

Lean on Structured Formats for Clarity

For most questions, stick to clear, structured formats like:

• Multiple choice (single or multi-select)
• Rating scales (e.g., Likert or numerical)
• Dropdowns or yes/no toggles

These types of questions make it easier to spot trends, filter responses, and visualize data—especially if you’re reviewing results in spreadsheets or basic analytics tools.

Use Conditional Logic for Smarter Depth

If your survey platform supports it, use conditional logic to keep the experience efficient. For example, if a respondent answers “No” to “Were you able to complete the task?”, follow up with a targeted open-ended question like “What got in your way?”

This keeps the survey shorter for most users, while still capturing deeper insight where it’s needed most.

Balance Depth and Efficiency

The goal is to strike a thoughtful balance: fast, actionable insights from structured questions, with targeted depth when the context demands it. That way, you gain clarity without creating a mountain of qualitative data you don’t have time to analyze.

Arrange questions so they flow smoothly, guiding respondents from broad to specific topics. Group related questions together to create a logical progression that feels intuitive, not jarring.

Using section headers or page breaks can help organize the survey and make it easier to navigate, keeping users engaged from start to finish.

Before finalizing your survey, consider where and how your audience is most likely to respond. Check your user analytics or survey distribution channel—if many participants access emails on their phones, optimize for smaller screens.

Keep layouts simple and avoid lengthy text inputs that can be frustrating on mobile. But if your survey is mainly completed on desktop (like work emails), focus on a design that fits that context. Adapting to your users’ habits helps boost completion rates and response quality.

Write questions that are simple, direct, and free of bias, jargon, or confusing terms. Avoid business speak and acronyms that your audience might not understand.

Examples:

Confusing or Complex Wording:

• Instead of: “Rate your experience with the SaaS integration on a scale from 1 to 5.”
  Try: “How easy was it to connect your software with our platform?”
• Instead of: “Do you agree that the onboarding process aligns with company OKRs?”
  Try: “How well does the onboarding process help you understand your role?”

Bias or Leading Wording:

• Instead of: “Do you love our amazing new feature?”
  Try: “How useful is this feature in your daily work?”
• Instead of: “Wouldn’t you agree that the update improved your experience?”
  Try: “How would you rate your experience after the update?”

Acronyms:

• Instead of: “Are you satisfied with the ROI of our CRM platform?”
  Try: “How satisfied are you with the results you get from our customer management tool?”
• Instead of: “Do you frequently use the API for data exports?”
  Try: “How often do you use the tool to export data?”

Using clear, neutral language ensures your questions are easy to understand and encourages honest, useful feedback.

Choose your question formats based on the type of data you need and how you plan to analyze it.

• Closed-ended questions (like multiple choice, Likert scales, or yes/no) are great for spotting trends, measuring sentiment, and producing structured data that’s easy to summarize and compare.
• Open-ended questions are better for exploring ideas, understanding context, or capturing insights you didn’t anticipate—but they take more effort to review and analyze.

Using a thoughtful mix of question types creates a better experience for respondents—keeping the survey clear and efficient—while giving you both measurable data and meaningful qualitative input. Each question should serve a purpose, helping you answer your core research goal.

Example: 

Post-Launch Feedback Survey

You’re collecting feedback on a newly released feature. Here’s how you might mix question types:

• Closed-ended (structured):
  “How often have you used the new feature in the past week?”
  (Multiple choice: Never, Once, 2–3 times, Daily, etc.)

  “How easy was the feature to use?”
  (5-point rating scale)

• Open-ended (exploratory):
  “What did you find most helpful or frustrating about the feature?”
  (Open text response)

This mix gives you quantitative data to measure usage and usability trends, and qualitative feedback to understand the “why” behind user experiences—all while keeping the survey efficient to complete and analyze.

A double-barreled question asks about two (or more) things at once, but only allows for one answer. This can confuse respondents and produce unclear, unreliable data—because you won’t know which part of the question they were responding to.

Example:

Instead of: “How easy and enjoyable was the experience?”
Ask:

• “How easy was the experience?”
• “How enjoyable was the experience?”

Instead of: “Did the feature save time and reduce errors?”
Ask:

• “Did the feature save you time?”
• Did the feature help reduce errors?”

When in doubt, break compound ideas into individual questions. It may slightly increase survey length, but the insights will be much more accurate and actionable.

Look for trends across your data—not just in averages or percentages, but in repeated language, themes, or behaviors.

In closed-ended responses, patterns can show up in strong leanings toward certain options or consistent scoring. In open-ended answers, repeated phrases or frustrations often point to key opportunities or pain points.

Pro tip: Even small surveys can surface big signals when multiple users say the same thing.

Don’t treat your results as one big average. Break them down by key user segments—such as new vs. returning users, roles, plan types, or device usage.

This can reveal differences in needs or pain points across groups and help you prioritize more effectively.

Example: New users may struggle with onboarding steps that experienced users breeze through.

Raw data rarely drives action on its own. Instead, summarize what you learned and why it matters. Highlight key findings, include compelling user quotes, and use visuals (charts, percentages, or themes) to make insights easier to absorb.

Tailor your reporting format to your audience—executives may want quick summaries and trends, while product teams may need more detail and supporting evidence.

Always tie results back to the original goal of the survey. What decision does this data support?