liveBook · Manning

User survey

As explained in Design for Developers

A survey is a structured set of questions used to collect information from users or other respondents.

A user survey is a structured set of questions for gathering information from a target audience. It is a low-cost, accessible research technique that can collect both quantitative responses, such as ratings, and qualitative feedback, such as reasons and opinions. Surveys help turn assumptions about users into evidence that can guide product and UX decisions. section 4.2.3 section 3.3.2

Start with a specific learning goal. Decide what you need to understand from the target audience, then write only questions that serve that goal. A focused survey is easier to complete and produces feedback that is easier to compare, interpret, and share with a team. section 4.2.3

Design a survey around useful answers rather than a long list of possible questions:

  • Define the question you need the survey to answer before drafting individual prompts. section 4.2.3
  • Keep the survey short and divide a broad topic into smaller surveys or categories when necessary. section 4.2.3
  • Pair rating questions with a chance to explain the rating, so a score has context. section 4.2.3
  • Choose a digital tool based on the features needed; some tools can show different follow-up questions according to an earlier answer. section 4.2.3
  • Aggregate the findings into a report so research can inform the wider design and development process. section 3.3.2

Adding context to a feature rating

A survey can ask web developers, “On a scale of 1 to 10, how useful would you find this feature?” That number alone does not explain the response. Follow it with a prompt asking why the feature would or would not be useful. The rating makes responses comparable; the explanation reveals the need, concern, or expectation behind it. section 4.2.3

When a topic contains many possible features or questions, group them into meaningful categories and survey one category at a time. For example, feature feedback can be separated into CSS and JavaScript groups instead of placing every feature in one long questionnaire. This reduces participant effort while preserving a clear scope for each set of results. section 4.2.3

Surveys complement other user-research activities. They can gather broad feedback efficiently, while one-on-one interviews offer an opportunity to explore an individual participant’s thoughts and attitudes in greater depth. Use the method that matches the question you need answered, then communicate findings clearly to the people shaping the experience. section 4.2.3 section 3.3.2

How Design for Developers covers it

How deep it goes
Explains goal-setting, short scoped questionnaires, ratings with follow-ups, category grouping, and optional branching; does not detail analysis methods.
Examples
Uses a web-browser feature survey with 1-to-10 usefulness ratings, reasoning follow-ups, and CSS and JavaScript categories.
What you can do after
Apply it via digital survey tools to collect focused ratings and explanations from a target audience.
How it connects
Connects surveys with user research, qualitative data, quantitative data, user interviews, UX design, and web development.

Also explained in

Compare how 6 books explain user survey →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Design for Developers. The section links point to the parts of the book it draws on.