Keep the finding specific
Users search menus for filters hidden in a toolbar.
Product and software research / Survey guide
Product and software research · Practical survey guide
Filter discoverability survey
Improve how users narrow large result sets.
Opens product registration. Example questions are not imported automatically.
EXAMPLE INVITATION BRIEF
Help us understand this experience.
Improve how users narrow large result sets.
- Who should respond
- Product users who attempted the described task
- When to ask
- Ask after someone has encountered the situation described in “Which result did you want to exclude?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Before sending, explain handling, optional participation, and contact details. This example is not sent by the preview.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Choose an action to test
Place relevant filters near the result list.
Check the experience again
After trying the change, repeat “Which result did you want to exclude?” with people who experienced it. Check whether they still describe the original issue: users search menus for filters hidden in a toolbar. Compare explanations and sample context, rather than claiming the change caused an improvement.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which result did you want to exclude? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Where did you look for filters? | Optional written explanation | Keep context that distinguishes different experiences. Do not infer task success from filter clicks. |
| What label would help find the right filter? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Place relevant filters near the result list. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Read the answers carefully
Keep the conclusion within the evidence.
Do not infer task success from filter clicks.
Users search menus for filters hidden in a toolbar. This is a synthetic example, not a customer result. Do not infer task success from filter clicks.
A useful starting point
Questions to understand the actual experience.
Improve how users narrow large result sets. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Which result did you want to exclude?
The result someone wanted to exclude identifies their narrowing task and the criteria they expected to use. Confirm the relevant filter exists before promising it.
Where did you look for filters?
The filter search location reveals whether controls appear where users expect to narrow results. Improve discoverability and explain the actual scope, without interpreting difficulty finding filters as proof that the needed filter exists.
What label would help find the right filter?
A helpful filter label identifies wording that connects an available control to the exclusion task. Test the label near the result list without changing its documented scope.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which result did you want to exclude? Where did you look for filters? What label would help find the right filter?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Improve how users narrow large result sets.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which result did you want to exclude?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Place relevant filters near the result list.
Before you send it
Check what your wording assumes.
Would you agree that everything about filter discoverability was clear and easy?
Which result did you want to exclude?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
Build with SurveyTeams
Draft your own filter discoverability questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Questions, answered.
Who should receive this questionnaire?
Product users who attempted the described task. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “Which result did you want to exclude?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Users search menus for filters hidden in a toolbar. This is an illustrative pattern to look for, not a claim about your respondents. Do not infer task success from filter clicks.
What would a practical follow-up look like?
Place relevant filters near the result list. After trying the change, repeat “Which result did you want to exclude?” with people who experienced it. Check whether they still describe the original issue: users search menus for filters hidden in a toolbar. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Where did you look for filters?”?
The filter search location reveals whether controls appear where users expect to narrow results. Improve discoverability and explain the actual scope, without interpreting difficulty finding filters as proof that the needed filter exists. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Continue exploring