Which field was hardest to complete?
The hardest mobile field identifies the input interaction requiring closer layout or control review. Record relevant conditions without collecting the entered value.
Product and software research / Survey guide
Product and software research · Practical survey guide
Mobile form completion survey
Find obstacles when entering information on phones.
Opens product registration. Example questions are not imported automatically.
QUESTION WORDING LAB
Assumes a positive answer
Would you agree that everything about mobile form completion was clear and easy?
Ask about the actual situation
Which field was hardest to complete?
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.
A useful starting point
Questions to understand the actual experience.
Find obstacles when entering information on phones. 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.
When did the keyboard obscure instructions?
Keyboard obstruction identifies the moment mobile users lose instructions needed to complete a field. Review the layout at that point and available guidance, without assuming one device observation describes all screen sizes or input methods.
What input change would help?
A proposed input change identifies an interaction to trial on small screens. Compare actual completion behavior without assuming a preference applies to all devices or input methods.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which field was hardest to complete? When did the keyboard obscure instructions? What input change would help?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Read the answers carefully
Keep the conclusion within the evidence.
Do not equate device preference with accessibility.
Long dropdowns are difficult to navigate on phones. This is a synthetic example, not a customer result. Do not equate device preference with accessibility.
Before you send it
Check what your wording assumes.
Would you agree that everything about mobile form completion was clear and easy?
Which field was hardest to complete?
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.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Long dropdowns are difficult to navigate on phones.
Choose an action to test
Test shorter searchable options on small screens.
Check the experience again
After trying the change, repeat “Which field was hardest to complete?” with people who experienced it. Check whether they still describe the original issue: long dropdowns are difficult to navigate on phones. Compare explanations and sample context, rather than claiming the change caused an improvement.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Find obstacles when entering information on phones.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which field was hardest to complete?”, 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
Test shorter searchable options on small screens.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which field was hardest to complete? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| When did the keyboard obscure instructions? | Optional written explanation | Keep context that distinguishes different experiences. Do not equate device preference with accessibility. |
| What input change would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Test shorter searchable options on small screens. |
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
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 field was hardest to complete?”, 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?
Long dropdowns are difficult to navigate on phones. This is an illustrative pattern to look for, not a claim about your respondents. Do not equate device preference with accessibility.
What would a practical follow-up look like?
Test shorter searchable options on small screens. After trying the change, repeat “Which field was hardest to complete?” with people who experienced it. Check whether they still describe the original issue: long dropdowns are difficult to navigate on phones. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “When did the keyboard obscure instructions?”?
Keyboard obstruction identifies the moment mobile users lose instructions needed to complete a field. Review the layout at that point and available guidance, without assuming one device observation describes all screen sizes or input methods. 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 mobile form completion 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