# Software release feedback survey

Understand how a specific change affected existing work.

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

## 1. Which changed workflow have you used since the release?

Answer: ____________________

## 2. Did the change make that workflow easier or harder?

Answer: ____________________

## 3. What should be clarified before the next release?

Answer: ____________________

## 4. Was it clear why the workflow changed?

Answer: ____________________

## 5. Which previous shortcut do you still need?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Ask about a workflow actually used after release; do not require evaluation of changes the person has not encountered.
2. Separate easier, unchanged, and harder experiences and tie the answer to the named workflow.
3. Identify information needed before the next release rather than assuming the product change itself must be reversed.
4. Check whether the reason was understood; understanding a change does not necessarily imply agreement with it.
5. Find the task supported by an old shortcut so a replacement can address the need rather than reproduce the exact control.

Interpretation caution: Compare users who experienced the change; untouched users cannot evaluate it.


## Illustrative finding and follow-up

Observation: Example release answers describe a removed shortcut that supported a frequent task.

Action to test: Explain the change and investigate a supported replacement for that specific task.

Follow-up: After testing the action, revisit this original observation: Example release answers describe a removed shortcut that supported a frequent task. 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.