Keep the finding specific
Archived discussions lack time context.
Communities and membership · A focused questionnaire
Improve old-discussion discovery.
Opens product registration. Example questions are not imported automatically.
EXAMPLE INVITATION BRIEF
Improve old-discussion discovery.
Before sending, explain handling, optional participation, and contact details. This example is not sent by the preview.
A worked interpretation example
Illustrative scenario. These are not customer results.
Archived discussions lack time context.
Show dates and current-status labels.
After testing this change—Show dates and current-status labels.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Archived discussions lack time context.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
Read the answers carefully
No private discussion contents.
Archived discussions lack time context. This is an illustrative pattern, not observed customer data. No private discussion contents.
From question to next step
Improve old-discussion discovery.
Ask after an adult respondent has encountered this specific situation. For draft-copy testing, show the actual material first; accept none or not applicable when the issue did not occur.
Show dates and current-status labels.
A useful starting point
Improve old-discussion discovery. These prompts examine topic intent, archive meaning, date need. Choose only questions your audience can answer. A missing detail can be answered with none; do not assume an issue occurred.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Read for topic intent. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for archive meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for date need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. What past topic did you seek? Which archive label was unclear? What date context was missing?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
| Question | Suggested format | What to preserve |
|---|---|---|
| What past topic did you seek? | Optional free text; none or not applicable accepted | Read for topic intent. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| Which archive label was unclear? | Optional free text; none or not applicable accepted | Read for archive meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What date context was missing? | Optional free text; none or not applicable accepted | Read for date need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
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
Would you agree that this entire experience was clear and easy?
What past topic did you seek?
The first wording assumes a positive outcome and combines clarity with ease. The revised prompt asks about the concrete situation; respondents may report no difficulty.
Inside the product
The real SurveyTeams screenshot shows a separate labelled synthetic event survey. It demonstrates the manual builder, not this questionnaire already loaded and not the task described in the software being evaluated.
Creation and preview were exercised in the observed account. Distribution, results and other features are separate workflows and depend on account conditions.
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 ↗Before you send it
Adult members, volunteers or organizers who encountered the described community activity. Ask only about the step each person actually encountered; voluntary responses are not automatically representative.
Read for topic intent. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. It supports this decision: Improve old-discussion discovery.
Read for archive meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for date need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. No private discussion contents.
Show dates and current-status labels. After testing this change—Show dates and current-status labels.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Archived discussions lack time context.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
The page offers text, CSV, JSON and Markdown downloads plus manual copying. Registration does not import the questionnaire. Use account-supported features and verify your own response-handling arrangements.
Continue exploring