Which change did you try to undo?
Optional short textRetain the specific point or condition described; avoid replacing it with an unexplained rating.Product and software research / Survey guide
Product and software research · Practical survey guide
Undo and recovery survey
Check how users recover from accidental changes.
Opens product registration. Example questions are not imported automatically.
DESIGN THE ANSWER SPACE
Where did you look for recovery options?
Optional written explanationKeep context that distinguishes different experiences. Do not promise recovery of permanently deleted data.What explanation would help?
Optional improvement suggestionKeep the suggested change separate from whether it has been tested. Explain undo scope where the action occurs.Suggested formats to adapt, not preconfigured product fields.
A useful starting point
Questions to understand the actual experience.
Check how users recover from accidental changes. 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.
Which change did you try to undo?
The change someone tried to undo identifies the action and scope that required recovery. Preserve the sequence without assuming all changes can be reversed.
Where did you look for recovery options?
The recovery location reveals whether users can discover actual options after an accidental change. Improve references to supported recovery routes and limits, without implying that every action can be reversed or every record restored.
What explanation would help?
A helpful explanation identifies the recovery route or scope users could not understand. Describe supported options and limits without promising restoration of every item.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which change did you try to undo? Where did you look for recovery options? What explanation would help?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Before you send it
Check what your wording assumes.
Would you agree that everything about undo and recovery was clear and easy?
Which change did you try to undo?
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.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which change did you try to undo? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Where did you look for recovery options? | Optional written explanation | Keep context that distinguishes different experiences. Do not promise recovery of permanently deleted data. |
| What explanation would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Explain undo scope where the action occurs. |
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.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Check how users recover from accidental changes.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which change did you try to undo?”, 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
Explain undo scope where the action occurs.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
People cannot tell whether undo affects all selected items.
Choose an action to test
Explain undo scope where the action occurs.
Check the experience again
After trying the change, repeat “Which change did you try to undo?” with people who experienced it. Check whether they still describe the original issue: people cannot tell whether undo affects all selected items. Compare explanations and sample context, rather than claiming the change caused an improvement.
Read the answers carefully
Keep the conclusion within the evidence.
Do not promise recovery of permanently deleted data.
People cannot tell whether undo affects all selected items. This is a synthetic example, not a customer result. Do not promise recovery of permanently deleted data.
Before you send it
Questions, answered.
Who should receive this questionnaire?
Product users who attempted the described task. 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 “Which change did you try to undo?”, 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?
People cannot tell whether undo affects all selected items. This is an illustrative pattern to look for, not a claim about your respondents. Do not promise recovery of permanently deleted data.
What would a practical follow-up look like?
Explain undo scope where the action occurs. After trying the change, repeat “Which change did you try to undo?” with people who experienced it. Check whether they still describe the original issue: people cannot tell whether undo affects all selected items. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Where did you look for recovery options?”?
The recovery location reveals whether users can discover actual options after an accidental change. Improve references to supported recovery routes and limits, without implying that every action can be reversed or every record restored. 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.
Build with SurveyTeams
Draft your own undo and recovery 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 ↗Continue exploring