How did you expect items to be saved?
Expected saving behavior identifies how users think items persist or are organized. Compare that expectation with supported behavior without promising indefinite storage.
Ecommerce and retail / Survey guide
Ecommerce and retail · Practical survey guide
Wishlist usability survey
Understand expectations about saved shopping items.
Opens product registration. Example questions are not imported automatically.
EXAMPLE INVITATION BRIEF
Help us understand this experience.
Understand expectations about saved shopping items.
- Who should respond
- Shoppers who attempted the described purchasing task
- When to ask
- Ask after someone has encountered the situation described in “How did you expect items to be saved?”, 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 useful starting point
Questions to understand the actual experience.
Understand expectations about saved shopping items. 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.
What visibility information was missing?
Missing visibility context identifies uncertainty about whether saved items are private, shared or publicly accessible. Explain verified controls and limitations, without assuming the wishlist offers privacy settings that have not been demonstrated.
What organization would help?
A useful organization identifies how people would group saved items for a practical task. Check available controls separately from visibility or sharing conditions.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. How did you expect items to be saved? What visibility information was missing? What organization would help?
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 |
|---|---|---|
| How did you expect items to be saved? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What visibility information was missing? | Optional written explanation | Keep context that distinguishes different experiences. Do not publish lists without permission. |
| What organization would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Explain list visibility before sharing. |
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 wishlist usability was clear and easy?
How did you expect items to be saved?
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.
Read the answers carefully
Keep the conclusion within the evidence.
Do not publish lists without permission.
Users cannot distinguish private lists from shared links. This is a synthetic example, not a customer result. Do not publish lists without permission.
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 distinguish private lists from shared links.
Choose an action to test
Explain list visibility before sharing.
Check the experience again
After trying the change, repeat “How did you expect items to be saved?” with people who experienced it. Check whether they still describe the original issue: users cannot distinguish private lists from shared links. 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: Understand expectations about saved shopping items.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “How did you expect items to be saved?”, 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 list visibility before sharing.
Before you send it
Questions, answered.
Who should receive this questionnaire?
Shoppers who attempted the described purchasing 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 “How did you expect items to be saved?”, 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 distinguish private lists from shared links. This is an illustrative pattern to look for, not a claim about your respondents. Do not publish lists without permission.
What would a practical follow-up look like?
Explain list visibility before sharing. After trying the change, repeat “How did you expect items to be saved?” with people who experienced it. Check whether they still describe the original issue: users cannot distinguish private lists from shared links. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “What visibility information was missing?”?
Missing visibility context identifies uncertainty about whether saved items are private, shared or publicly accessible. Explain verified controls and limitations, without assuming the wishlist offers privacy settings that have not been demonstrated. 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 wishlist 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