What question were you trying to answer?
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: older discussion answers look current in search results.
Communities and membership · Practical survey guide
Find obstacles when searching shared knowledge.
Opens product registration. Example questions are not imported automatically.
Try the first three questions here. Nothing is submitted or saved.
A useful starting point
Find obstacles when searching shared knowledge. 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.
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: older discussion answers look current in search results.
A misleading search result reveals where labels or snippets suggest the wrong content. Inspect the expected topic and actual result without requesting private discussions or assuming the search index is faulty.
Turn the requested improvement into a testable next step. One illustrative action is: show dates and review status clearly.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What question were you trying to answer? Which search result was misleading? What label would help identify useful answers?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Read the answers carefully
Community answers may need independent verification.
Older discussion answers look current in search results. This is a synthetic example, not a customer result. Community answers may need independent verification.
Before you send it
Would you agree that everything about community search experience was clear and easy?
What question were you trying to answer?
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
Illustrative scenario. These are not customer results.
Older discussion answers look current in search results.
Show dates and review status clearly.
After trying the change, repeat “What question were you trying to answer?” with people who experienced it. Check whether they still describe the original issue: older discussion answers look current in search results. Compare explanations and sample context, rather than claiming the change caused an improvement.
From question to next step
Start with the decision: Find obstacles when searching shared knowledge.
Invite people with relevant experience. Ask after someone has encountered the situation described in “What question were you trying to answer?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Show dates and review status clearly.
Choose the response format
| Question | Suggested format | What to preserve |
|---|---|---|
| What question were you trying to answer? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Which search result was misleading? | Optional written explanation | Keep context that distinguishes different experiences. Community answers may need independent verification. |
| What label would help identify useful answers? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Show dates and review status clearly. |
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
Members and volunteers involved in the described activity. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
Ask after someone has encountered the situation described in “What question were you trying to answer?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Older discussion answers look current in search results. This is an illustrative pattern to look for, not a claim about your respondents. Community answers may need independent verification.
Show dates and review status clearly. After trying the change, repeat “What question were you trying to answer?” with people who experienced it. Check whether they still describe the original issue: older discussion answers look current in search results. Compare explanations and sample context, rather than claiming the change caused an improvement.
A misleading search result reveals where labels or snippets suggest the wrong content. Inspect the expected topic and actual result without requesting private discussions or assuming the search index is faulty. Use an optional written explanation when predefined choices would hide relevant context.
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
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.
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Continue exploring