# Data export experience survey

Improve the handoff from product views to downloads.

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

## 1. Which information did you expect in the file?

Answer: ____________________

## 2. What format did your next task require?

Answer: ____________________

## 3. What export explanation was missing?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Expected file content identifies the data scope users need for their next task. Compare it with actual documented exports without implying universal availability or filter support.
2. The required format links the export to a concrete downstream task, distinguishing readability from processing needs. Explain supported outputs and their scope, without claiming compatibility with tools or workflows that were not tested.
3. A missing export explanation identifies uncertainty about scope, formatting or downstream use. Explain verified behavior without promising compatibility or completeness that has not been tested.

Interpretation caution: Avoid collecting real exported confidential data.


## Illustrative finding and follow-up

Observation: Users expect filtered rows but receive the full dataset.

Action to test: Explain whether current filters apply to exports.

Follow-up: After trying the change, repeat “Which information did you expect in the file?” with people who experienced it. Check whether they still describe the original issue: users expect filtered rows but receive the full dataset. Compare explanations and sample context, rather than claiming the change caused an improvement.