Keep the finding specific
Staff cannot distinguish the new process from the old route.
Operations and internal services / Survey guide
Operations and internal services · Practical survey guide
Process change announcement survey
Check whether people understand a specific process change.
Opens product registration. Example questions are not imported automatically.
FOLLOW THE FEEDBACK
- Understand the context
What step changed for your role?
- Investigate the friction
Which effective date was unclear?
- Choose a next check
What example would help?
A planning aid, not automated analysis of your answers.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Choose an action to test
Show one approved before-and-after task example.
Check the experience again
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.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| What step changed for your role? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Which effective date was unclear? | Optional written explanation | Keep context that distinguishes different experiences. Do not infer adoption from notice readership. |
| What example would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Show one approved before-and-after task example. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Read the answers carefully
Keep the conclusion within the evidence.
Do not infer adoption from notice readership.
Staff cannot distinguish the new process from the old route. This is a synthetic example, not a customer result. Do not infer adoption from notice readership.
A useful starting point
Questions to understand the actual experience.
Check whether people understand a specific process change. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What step changed for your role?
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.
Which effective date was unclear?
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.
What example would help?
Turn the requested improvement into a testable next step. One illustrative action is: show one approved before-and-after task example.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What step changed for your role? Which effective date was unclear? What example would help?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Check whether people understand a specific process change.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “What step changed for your role?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Show one approved before-and-after task example.
Before you send it
Check what your wording assumes.
Would you agree that everything about process change announcement was clear and easy?
What step changed for your role?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
Build with SurveyTeams
Draft your own process change announcement questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Questions, answered.
Who should receive this questionnaire?
Colleagues who used or delivered the described internal process. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “What step changed for your role?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Staff cannot distinguish the new process from the old route. This is an illustrative pattern to look for, not a claim about your respondents. Do not infer adoption from notice readership.
What would a practical follow-up look like?
Show one approved before-and-after task example. 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.
How should I ask “Which effective date was unclear?”?
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. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Continue exploring