Where did you expect the menu?
The expected menu location identifies a discoverability mismatch during a mobile task. Compare the route with available navigation rather than assuming the user overlooked it.
Product and software research / Survey guide
Product and software research · Practical survey guide
Mobile navigation survey
Improve finding product areas on small screens.
Opens product registration. Example questions are not imported automatically.
QUESTION WORDING LAB
Assumes a positive answer
Would you agree that everything about mobile navigation was clear and easy?
Ask about the actual situation
Where did you expect the menu?
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.
A useful starting point
Questions to understand the actual experience.
Improve finding product areas on small screens. 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 label was hard to understand?
An unclear navigation label reveals a mismatch between the destination and the user's task vocabulary. Clarify the actual area or provide appropriate context, without assuming a preferred label guarantees discovery for every user.
What task needed fewer navigation steps?
A task needing fewer steps identifies where mobile navigation creates unnecessary movement. Test the relevant journey without assuming the shortest route always preserves needed context.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Where did you expect the menu? Which label was hard to understand? What task needed fewer navigation steps?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Users cannot find reports behind an unfamiliar icon.
Choose an action to test
Add a clear label and test report navigation.
Check the experience again
After trying the change, repeat “Where did you expect the menu?” with people who experienced it. Check whether they still describe the original issue: users cannot find reports behind an unfamiliar icon. 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 |
|---|---|---|
| Where did you expect the menu? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Which label was hard to understand? | Optional written explanation | Keep context that distinguishes different experiences. Avoid assuming desktop paths work on mobile. |
| What task needed fewer navigation steps? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Add a clear label and test report navigation. |
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 mobile navigation was clear and easy?
Where did you expect the menu?
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.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Improve finding product areas on small screens.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Where did you expect the menu?”, 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
Add a clear label and test report navigation.
Read the answers carefully
Keep the conclusion within the evidence.
Avoid assuming desktop paths work on mobile.
Users cannot find reports behind an unfamiliar icon. This is a synthetic example, not a customer result. Avoid assuming desktop paths work on mobile.
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 “Where did you expect the menu?”, 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 cannot find reports behind an unfamiliar icon. This is an illustrative pattern to look for, not a claim about your respondents. Avoid assuming desktop paths work on mobile.
What would a practical follow-up look like?
Add a clear label and test report navigation. After trying the change, repeat “Where did you expect the menu?” with people who experienced it. Check whether they still describe the original issue: users cannot find reports behind an unfamiliar icon. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Which label was hard to understand?”?
An unclear navigation label reveals a mismatch between the destination and the user's task vocabulary. Clarify the actual area or provide appropriate context, without assuming a preferred label guarantees discovery for every user. 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.
Build with SurveyTeams
Draft your own mobile navigation 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 ↗Continue exploring