Interpretation Basics
Interpret survey results alongside the question, audience, and response count. Each method answers a different product question.
What do the survey results mean?
FastPoll
Read FastPoll's answer distribution alongside its response count.
- A clear lead — Check that it holds as responses arrive.
- A close split — Check the sample size and whether options overlap.
- Low support — Check the wording before dismissing the option.
See the FastPoll response format.
UserChoice
UserChoice uses repeated conjoint choices to measure product trade-offs. Look for consistent preferences across tasks.
- Preference strength — Stable gaps are more useful than small differences.
- Consistency — Unstable choices may depend on context or unclear concepts.
- Segments — Compare groups only when each has enough responses.
See the UserChoice reference.
PricePoint
Van Westendorp estimates perceived price boundaries; Gabor-Granger tests demand at stated prices. For Van Westendorp, read:
- Too-cheap boundary — Where low prices begin to raise quality concerns.
- Too-expensive boundary — Where price resistance becomes significant.
- Acceptable range — Test it against costs, positioning, and actual purchases.
See the PricePoint reference and Van Westendorp guide.
FeaturePriority
FeaturePriority starts with Kano, then uses MaxDiff and pairwise comparisons when enough features advance. Interpret each completed stage:
- Kano — Separate basic expectations, performance needs, and attractive features.
- MaxDiff — Read relative importance and stable gaps between features.
- Bradley-Terry — Read relative preference from pairwise choices.
- Group differences — Check each sample before drawing segment conclusions.
See the FeaturePriority reference and Kano guide.
OpenFeedback
Group OpenFeedback comments by recurring problems. Keep specific examples and important exceptions.
- Themes — Group comments about the same need or problem.
- Context — Note where the problem happens and whom it affects.
- Examples — Keep concrete details that explain the underlying need.
See the OpenFeedback response format.
Reaction
Reaction measures a quick response with faces, thumbs, or a heart. Follow up to learn why someone reacted that way.
- Positive — Check that respondents represent your intended audience.
- Mixed — Use OpenFeedback to understand the split.
- Negative — Investigate the cause before changing the content.
See the Reaction response format.
Is the evidence strong enough to act?
- Match evidence to risk. Pricing or roadmap commitments need more evidence than reversible copy changes.
- Keep exceptions visible. A severe accessibility or data-loss issue can matter even when reported once.
- Combine counts and comments. Use numbers for scale and feedback for context.
- Check timing. Releases, outages, and promotions can affect results.
- Review together. Compare interpretations before deciding.