Which task were you trying to simplify?
Optional short textRetain the specific point or condition described; avoid replacing it with an unexplained rating.Product and software research / Survey guide
Product and software research · Practical survey guide
Feature discoverability survey
Find why useful capabilities remain unnoticed.
Opens product registration. Example questions are not imported automatically.
DESIGN THE ANSWER SPACE
Where did you look for help?
Optional written explanationKeep context that distinguishes different experiences. Do not claim a feature exists without source evidence.What example would explain the capability?
Optional improvement suggestionKeep the suggested change separate from whether it has been tested. Test task-oriented labels and examples.Suggested formats to adapt, not preconfigured product fields.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Users miss a relevant tool because its label is unfamiliar.
Choose an action to test
Test task-oriented labels and examples.
Check the experience again
After trying the change, repeat “Which task were you trying to simplify?” with people who experienced it. Check whether they still describe the original issue: users miss a relevant tool because its label is unfamiliar. Compare explanations and sample context, rather than claiming the change caused an improvement.
Read the answers carefully
Keep the conclusion within the evidence.
Do not claim a feature exists without source evidence.
Users miss a relevant tool because its label is unfamiliar. This is a synthetic example, not a customer result. Do not claim a feature exists without source evidence.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Find why useful capabilities remain unnoticed.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which task were you trying to simplify?”, 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
Test task-oriented labels and examples.
A useful starting point
Questions to understand the actual experience.
Find why useful capabilities remain unnoticed. 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 task were you trying to simplify?
The task users wanted to simplify identifies why a capability might be relevant. Confirm actual support and account conditions before framing it as an available solution.
Where did you look for help?
The help location reveals whether users could find an explanation linking a capability to their task. Improve verified guidance and labels, without assuming awareness of a feature means it is available to every account.
What example would explain the capability?
A useful capability example identifies the practical demonstration needed to explain the feature's scope. Use verified behavior without implying availability to every account.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which task were you trying to simplify? Where did you look for help? What example would explain the capability?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which task were you trying to simplify? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Where did you look for help? | Optional written explanation | Keep context that distinguishes different experiences. Do not claim a feature exists without source evidence. |
| What example would explain the capability? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Test task-oriented labels and examples. |
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.
Before you send it
Check what your wording assumes.
Would you agree that everything about feature discoverability was clear and easy?
Which task were you trying to simplify?
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 feature 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 task were you trying to simplify?”, 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 miss a relevant tool because its label is unfamiliar. This is an illustrative pattern to look for, not a claim about your respondents. Do not claim a feature exists without source evidence.
What would a practical follow-up look like?
Test task-oriented labels and examples. After trying the change, repeat “Which task were you trying to simplify?” with people who experienced it. Check whether they still describe the original issue: users miss a relevant tool because its label is unfamiliar. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Where did you look for help?”?
The help location reveals whether users could find an explanation linking a capability to their task. Improve verified guidance and labels, without assuming awareness of a feature means it is available to every account. 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