Set the decision
Assess directory visibility descriptions.
Communities and membership / Survey guide
Communities and membership · A focused questionnaire
Member directory privacy copy survey
Assess directory visibility descriptions.
Opens product registration. Example questions are not imported automatically.
FOLLOW THE FEEDBACK
- Understand the context
Who could view the profile?
- Investigate the friction
Which field visibility was unclear?
- Choose a next check
What choice instruction was missing?
A planning aid, not automated analysis of your answers.
From question to next step
Make the feedback useful.
Invite relevant voices
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.
Choose an action
State verified visibility and choices.
Read the answers carefully
What these answers cannot establish.
Do not promise privacy without verification.
Directory pages omit viewer scope. This is an illustrative pattern, not observed customer data. Do not promise privacy without verification.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Directory pages omit viewer scope.
Choose an action to test
State verified visibility and choices.
Check the experience again
After testing this change—State verified visibility and choices.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Directory pages omit viewer scope.” 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.
A useful starting point
Three questions for this specific decision.
Assess directory visibility descriptions. These prompts examine audience meaning, field scope, choice clarity. 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.
Who could view the profile?
Read for audience meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Which field visibility was unclear?
Read for field scope. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
What choice instruction was missing?
Read for choice clarity. 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. Who could view the profile? Which field visibility was unclear? What choice instruction was missing?
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 this entire experience was clear and easy?
Who could view the profile?
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.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Who could view the profile? | Optional free text; none or not applicable accepted | Read for audience meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| Which field visibility was unclear? | Optional free text; none or not applicable accepted | Read for field scope. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What choice instruction was missing? | Optional free text; none or not applicable accepted | Read for choice clarity. 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
Questions, answered.
Who should answer?
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.
What does the first question help explain?
Read for audience meaning. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. It supports this decision: Assess directory visibility descriptions.
What should I preserve in the second answer?
Read for field scope. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
How should I read the third answer?
Read for choice clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. Do not promise privacy without verification.
What would a practical follow-up look like?
State verified visibility and choices. After testing this change—State verified visibility and choices.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Directory pages omit viewer scope.” 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.
Can I load this automatically in SurveyTeams?
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.
Inside the product
Create a manual draft and check the questions
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.
- Start a draft with this decision in mind: Assess directory visibility descriptions.
- Copy or select only applicable questions from this page. Add them as optional text prompts; the download is an editorial definition, not a product importer.
- Preview the respondent wording. Do not promise privacy without verification. Explain your actual response handling before distribution.
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
Adapt these questions in your own survey.
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