methodatlas
RunsheetUX Research

Surveys

ComplexityMedium
Time3-14 Tage
Participants50+
FormatAsync
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstResearch Questionnot in catalog

A precise research question exists that can meaningfully be answered with structured responses from many people.

Without: Without research question, a long questionnaire with nice numbers emerges, but with no decision value.
Complete firstTarget-group segmentnot in catalog

Target group and desired sample are defined, including exclusion criteria and recruiting channel.

Without: Without sample plan, percentages are not robust and are easily overinterpreted.
02

Preparation

What needs to be ready before start

Materials

Survey tool such as Typeform, Google Forms, Qualtrics or LimeSurvey; questionnaire draft; sample plan; evaluation sheet; consent and privacy text.

People / roles

Research owner for questionnaire and evaluation; domain reviewer; optional data analyst; participants from clearly defined segment.

Pre-read

Research question, target group, desired n count, decision supported by results, and hypotheses or answer options.

Time needed

3-14 days

Setup

Limit questionnaire to maximum 8-12 minutes. Use required questions sparingly. Pilot with 3-5 people before sending.

03

Core question

The one question this method answers

Which patterns, frequencies or priorities appear in a sufficiently large target group?

04

Flow

Marker: Phase

StepDurationActionHint
1Operationalize research question
30-60 minDefine decision, hypotheses and measurable variables. Include only questions that directly contribute to evaluation.If nobody can explain which decision a question influences, it does not belong in survey.
2Build questionnaire
60-120 minWrite clear questions with appropriate answer formats, keep scales consistent and put demographic questions at end.No double-barreled questions such as "easy and fast". Each question measures exactly one thing.
3Run pilot
30-60 minTest questionnaire with 3-5 people, correct unclear wording and drop-off points.A pilot saves more time than it costs. Scales and multiple choice are especially often misunderstood.
4Collect data
2-10 daysSend survey to target group, check response, send reminders and mark obvious quality problems.Fast response from a single channel can be biased. Document source of responses.
5Evaluate and decide
2-4 hClean responses, analyze frequencies and segments, formulate core statements with uncertainty and limits.Survey results show patterns, not automatically causes. Why questions often need follow-up interviews.
05

Artifact

What comes out at the end

Form

Survey report with research question, sample, field time, questionnaire, cleaned n count, charts, segment analysis, key insights and decision recommendation.

Versioning / ownership

Save questionnaire, field time and raw data as snapshot. On repetition, assign version number and mark question changes as breaking changes.

Tool alternatives
  • Typeform
  • Google Forms
  • Qualtrics
  • LimeSurvey
  • SurveyMonkey
  • Airtable Forms

surveys-working-template.md

Compact working template for Surveys with research question, sample, questionnaire, and readout.

Surveys Working Template

Goal

Collect structured responses at scale and turn them into measurable insight.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Research setup

  • Research question:
  • Target group:
  • Questionnaire:
  • Sample and distribution plan:
  • Response scale:

Output artifacts

  • Survey results:
  • Charts:
  • Segment insights:

Open questions

  • ...

Next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

surveys-beispiel.md

Concrete filled scenario, fictional example

Survey - Onboarding problems in tax-firm portal

Research question: Which steps in client onboarding create most drop-offs? Sample: 142 clients, field time 2026-05-06 to 2026-05-12, n=118 after cleaning.

Top results:

  • 48% name document upload as hardest step.
  • 31% do not confidently understand DATEV approval.
  • 22% drop off because they do not know which documents are complete.

Segment: New founders under 12 months name upload problems much more often at 61%.

Decision: Prioritize upload checklist and progress indicator. Three interviews with founder segment follow to clarify causes.

07

Pitfalls

Recognize symptoms and steer against them

Trap

Too many questions

Symptom

Drop-off rate rises, free-text answers become short or empty.

What to do

Cut questionnaire back to decision question and remove nice-to-have questions.

Trap

Leading wording

Symptom

Answer options visibly steer toward preferred solution.

What to do

Write neutrally, balance options and let pilot participants think aloud.

Trap

False percentage certainty

Symptom

Small samples presented with decimals.

What to do

Show n count, report rough magnitudes and name uncertainty.

Trap

Deriving why from multiple choice

Symptom

Team interprets motives although only behavior or preference was asked.

What to do

Mark causes as hypotheses and deepen with interviews or usability testing.

Trap

Response bias ignored

Symptom

Only very satisfied or very frustrated users respond.

What to do

Document recruiting channel and non-responses, do not sell results as whole market.

08

Stop criteria

Done signals checkable in under a minute

No clear research question or decision exists.
Target group and recruiting channel are not defined.
Questionnaire contains sensitive data without privacy clarification.
Sample too small for segment statements.
Team needs deep understanding rather than patterns in larger sample.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.