Keep the finding specific
Errors appear far from the affected input.
Product and software research / Survey guide
Product and software research · Practical survey guide
Form error message survey
Improve recovery from invalid form entries.
Opens product registration. Example questions are not imported automatically.
BEFORE YOU INVITE PEOPLE
Local planning aid. No answers are submitted or saved.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Choose an action to test
Place clear correction guidance beside the field.
Check the experience again
After trying the change, repeat “Which error message needed explanation?” with people who experienced it. Check whether they still describe the original issue: errors appear far from the affected input. 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 collect real submitted personal information.
Errors appear far from the affected input. This is a synthetic example, not a customer result. Do not collect real submitted personal information.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Improve recovery from invalid form entries.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which error message needed explanation?”, 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
Place clear correction guidance beside the field.
A useful starting point
Questions to understand the actual experience.
Improve recovery from invalid form entries. 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 error message needed explanation?
An error needing explanation identifies wording that does not make the input problem understandable. Record the message and context without collecting submitted values.
How did you identify the affected field?
The way someone located the affected field reveals whether the error message connects its explanation to a specific input. Improve that connection and recovery guidance, without collecting submitted values or implying every error is user-caused.
What instruction would help correct it?
A useful correction instruction identifies what users need to recover at the affected field. Explain verified requirements without assuming the error was caused by the user.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which error message needed explanation? How did you identify the affected field? What instruction would help correct it?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which error message needed explanation? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| How did you identify the affected field? | Optional written explanation | Keep context that distinguishes different experiences. Do not collect real submitted personal information. |
| What instruction would help correct it? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Place clear correction guidance beside the field. |
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.
Before you send it
Check what your wording assumes.
Would you agree that everything about form error message was clear and easy?
Which error message needed explanation?
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 form error message 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?
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 error message needed explanation?”, 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?
Errors appear far from the affected input. This is an illustrative pattern to look for, not a claim about your respondents. Do not collect real submitted personal information.
What would a practical follow-up look like?
Place clear correction guidance beside the field. After trying the change, repeat “Which error message needed explanation?” with people who experienced it. Check whether they still describe the original issue: errors appear far from the affected input. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “How did you identify the affected field?”?
The way someone located the affected field reveals whether the error message connects its explanation to a specific input. Improve that connection and recovery guidance, without collecting submitted values or implying every error is user-caused. 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