# Beta testing feedback survey

Turn early-use feedback into specific product fixes.

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

## 1. Which task did you try in this beta?

Answer: ____________________

## 2. At which step did the result differ from your expectation?

Answer: ____________________

## 3. How serious was the impact on completing your task?

Answer: ____________________

## 4. Could you reproduce the unexpected behavior?

Answer: ____________________

## 5. What non-sensitive context would help explain the issue?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Identify the task exercised so reports from different beta workflows are not collapsed into a single verdict.
2. Locate the point where actual behavior diverged from expectation without assuming the expectation was correct.
3. Describe task impact separately from frustration; a visible glitch and a blocked workflow need different priorities.
4. Check repeatability while allowing intermittent issues; failure to reproduce does not invalidate the original observation.
5. Request only non-sensitive context such as device class or steps, excluding tokens, private records, and credentials.

Interpretation caution: Record environment details separately; do not ask for passwords or access tokens.