# Feature page comprehension survey

Improve explanations of a specific product capability.

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

## 1. What task does the page describe?

Answer: ____________________

## 2. Which claim needs an example?

Answer: ____________________

## 3. What question remains before trying it?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: readers cannot connect the feature description to their workflow.
2. A claim needing an example identifies where abstract capability wording exceeds the visitor's understanding. Show a verified task and relevant conditions; an illustration must not imply features or outcomes that were not demonstrated.
3. Turn the requested improvement into a testable next step. One illustrative action is: add a truthful task-based example.

Interpretation caution: Do not claim capabilities beyond verified evidence.


## Illustrative finding and follow-up

Observation: Readers cannot connect the feature description to their workflow.

Action to test: Add a truthful task-based example.

Follow-up: After trying the change, repeat “What task does the page describe?” with people who experienced it. Check whether they still describe the original issue: readers cannot connect the feature description to their workflow. Compare explanations and sample context, rather than claiming the change caused an improvement.