# Saved view usability survey

Check expectations around reusable result views.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. What did you expect the view to remember?

Answer: ____________________

## 2. Who should be able to see it?

Answer: ____________________

## 3. What information was unclear when saving?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. What a view should remember identifies expectations about retained filters, ordering or display settings. Compare each expectation with the product's actual saving behavior.
2. 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.
3. Unclear saving information identifies a missing explanation about retained configuration or visibility. State the verified scope before saving without promising untested privacy controls.

Interpretation caution: Do not promise sharing permissions without verification.


## Illustrative finding and follow-up

Observation: Users confuse personal and shared saved views.

Action to test: Explain visibility before saving a view.

Follow-up: 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.