# Process change announcement survey

Check whether people understand a specific process change.

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

## 1. What step changed for your role?

Answer: ____________________

## 2. Which effective date was unclear?

Answer: ____________________

## 3. What example would help?

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: staff cannot distinguish the new process from the old route.
2. An unclear effective date identifies uncertainty about which procedure applies to the next task. Distinguish announcement and implementation dates using confirmed information, without assuming readership establishes understanding or adoption of the change.
3. Turn the requested improvement into a testable next step. One illustrative action is: show one approved before-and-after task example.

Interpretation caution: Do not infer adoption from notice readership.


## Illustrative finding and follow-up

Observation: Staff cannot distinguish the new process from the old route.

Action to test: Show one approved before-and-after task example.

Follow-up: After trying the change, repeat “What step changed for your role?” with people who experienced it. Check whether they still describe the original issue: staff cannot distinguish the new process from the old route. Compare explanations and sample context, rather than claiming the change caused an improvement.