What did you expect the view to remember?
What a view should remember identifies expectations about retained filters, ordering or display settings. Compare each expectation with the product's actual saving behavior.
Product and software research / Survey guide
Product and software research · Practical survey guide
Saved view usability survey
Check expectations around reusable result views.
Opens product registration. Example questions are not imported automatically.
ILLUSTRATIVE QUESTIONNAIRE3 prompts
Try the first three questions here. Nothing is submitted or saved.
A useful starting point
Questions to understand the actual experience.
Check expectations around reusable result views. 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.
Who should be able to see it?
Expected viewers reveal uncertainty about whether a saved view is personal, shared or restricted. State the verified visibility rules and choices, without promising privacy or access controls beyond the current product's demonstrated behavior.
What information was unclear when saving?
Unclear saving information identifies a missing explanation about retained configuration or visibility. State the verified scope before saving without promising untested privacy controls.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What did you expect the view to remember? Who should be able to see it? What information was unclear when saving?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Read the answers carefully
Keep the conclusion within the evidence.
Do not promise sharing permissions without verification.
Users confuse personal and shared saved views. This is a synthetic example, not a customer result. Do not promise sharing permissions without verification.
Before you send it
Check what your wording assumes.
Would you agree that everything about saved view usability was clear and easy?
What did you expect the view to remember?
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 worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Users confuse personal and shared saved views.
Choose an action to test
Explain visibility before saving a view.
Check the experience again
After trying the change, repeat “What did you expect the view to remember?” with people who experienced it. Check whether they still describe the original issue: users confuse personal and shared saved views. Compare explanations and sample context, rather than claiming the change caused an improvement.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Check expectations around reusable result views.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “What did you expect the view to remember?”, 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
Explain visibility before saving a view.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| What did you expect the view to remember? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Who should be able to see it? | Optional written explanation | Keep context that distinguishes different experiences. Do not promise sharing permissions without verification. |
| What information was unclear when saving? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Explain visibility before saving a view. |
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
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 “What did you expect the view to remember?”, 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 confuse personal and shared saved views. This is an illustrative pattern to look for, not a claim about your respondents. Do not promise sharing permissions without verification.
What would a practical follow-up look like?
Explain visibility before saving a view. After trying the change, repeat “What did you expect the view to remember?” with people who experienced it. Check whether they still describe the original issue: users confuse personal and shared saved views. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Who should be able to see it?”?
Expected viewers reveal uncertainty about whether a saved view is personal, shared or restricted. State the verified visibility rules and choices, without promising privacy or access controls beyond the current product's demonstrated behavior. 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 saved view usability 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