One participant's completed questionnaire: their scale ratings and open-text answers, shaped by question wording.
A survey response is one completed questionnaire: a single participantParticipantUser ResearchA person participating in researchView reference →'s answers across the scale items and open-text fields a study put to them. It is the atom of survey research. Each response is shaped by who answered and how the questions were worded.
The scale that most survey responses are built on traces to Rensis Likert, who introduced it in his 1932 Columbia dissertation, A Technique for the Measurement of Attitudes. Likert proposed a set of symmetric agree-disagree items with a neutral midpoint, summed into a single attitude score, and showed it correlated highly with the more laborious Thurstone scaling of the day. The format stuck because it was cheap to administer and easy to analyse.
The century since has been a study in what a response on such a scale does and does not capture. Research on information loss and bias in Likert responses documents how question order, the position of the positive end, and the granularity of the scale all push answers around. A Likert item gives you an ordinal position, not a measured quantity, and treating five points as if they were five equal units is a common analytical error.
Two response-level problems dominate practice. Response bias is systematic distortion in how people answer: acquiescence (agreeing by default), social desirability, and central-tendency clustering on the safe middle. Response rate is who answers at all, and a low rate raises the riskRiskComplianceA risk to the product or businessView reference → that responders differ from non-responders in ways that skew the result. Both are why a clean scale item still needsNeedUserA user need, pain, desire, or constraintView reference → careful sample sizing before any number means much.
A team ships a post-onboarding survey to 2,000 new users: four five-point Likert items on clarity and confidence, plus one open-text field asking what nearly stopped them. 280 responses come back, a 14% rate. The mean clarity score reads 4.1, which looks reassuring until the team checks the open text and finds a recurring complaint about a billing step that the closed items never asked about.
The quantitative scale gave them a trend they can track releaseReleaseProduct SpecificationA shipped version of the productView reference → over release; the open-text responses surfaced the cause the scale was blind to. They flag the 14% rate as a caveat, since the users frustrated enough to abandon may never have opened the survey, and they treat the 4.1 as directional rather than precise. The combination of scale and free text, read together, is what turns raw responses into a usable signal.
In the Unified Product Graph, a survey response sits in the user-research region as the individual datum a study gathers at scale. The Research StudycollectsSurvey Responsehierarchy edge ties each response to the study that fielded it, preserving the response rate and sampling context that decide how much the number is worth. The research_study_collects_survey_responseSurvey ResponseevidencesInsightcross-domain edge then connects responses upward to the findings they support, so any insight can be traced back to the specific responses behind it and audited for whether the sample was large and unbiased enough to carry the claim.survey_response_evidences_insight
Worked example: Trellis
Trellis used structured survey responses to measure how much preview and reversibility raised a director's stated willingness to grant the agent autonomy. Each response quantified what the qualitative observationsObservationUser ResearchA specific behaviour or statement observedView reference → suggested: that the governing levers, see before it runs, undo after it does, move a hesitant director toward the trusted, activated workspace that is Trellis's north-star metricMetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →.
Type-specific fields on BaseNode
response_countnumberTotal responses
completion_ratenumberCompletion (0–1)
methodenumDistribution method
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
2 edge types connected to this entity.
research_study_collects_survey_responsesurvey_response_evidences_insight