# Developer documentation feedback survey

Discover whether instructions support a concrete implementation task.

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

## 1. What were you trying to build?

Answer: ____________________

## 2. Which example or instruction did you need but could not find?

Answer: ____________________

## 3. Could you complete the task after following the documentation?

Answer: ____________________

## 4. Which assumption about your environment was unclear?

Answer: ____________________

## 5. What would make the example easier to adapt?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Anchor the response to the task being built rather than a general opinion of the documentation.
2. Identify a missing example or step so a revision can address the reader's actual obstacle.
3. Distinguish following the instructions from reaching a useful result in the reader's environment.
4. Locate an unstated environment assumption without collecting private configuration values.
5. Find the change that would make adaptation possible; an example that runs unchanged may still fail the user's real task.

Interpretation caution: A useful reference and a useful quick-start solve different reader needs.


## Illustrative finding and follow-up

Observation: Example developers can follow the code sample but cannot identify the required setup assumptions.

Action to test: State the supported environment and expected result beside the example.

Follow-up: After testing the action, revisit this original observation: Example developers can follow the code sample but cannot identify the required setup assumptions. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.