Keep the finding specific
Groups disagree about who communicates schedule changes.
Communities and membership · Practical survey guide
Clarify expectations across collaborating community groups.
Opens product registration. Example questions are not imported automatically.
ILLUSTRATIVE FINDING → ACTION
Groups disagree about who communicates schedule changes.
Agree a shared communication owner.
Synthetic scenario, not a customer result.
A worked interpretation example
Illustrative scenario. These are not customer results.
Groups disagree about who communicates schedule changes.
Agree a shared communication owner.
After trying the change, repeat “Which responsibility needs explanation?” with people who experienced it. Check whether they still describe the original issue: groups disagree about who communicates schedule changes. Compare explanations and sample context, rather than claiming the change caused an improvement.
Choose the response format
| Question | Suggested format | What to preserve |
|---|---|---|
| Which responsibility needs explanation? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What resource expectation differs? | Optional written explanation | Keep context that distinguishes different experiences. Do not disclose confidential partnership terms. |
| What checkpoint would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Agree a shared communication owner. |
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.
Read the answers carefully
Do not disclose confidential partnership terms.
Groups disagree about who communicates schedule changes. This is a synthetic example, not a customer result. Do not disclose confidential partnership terms.
A useful starting point
Clarify expectations across collaborating community groups. 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: groups disagree about who communicates schedule changes.
Different resource expectations reveal an unresolved contribution or dependency between community partners. Agree the relevant scope and ownership before collaboration rather than assuming goodwill implies identical commitments.
Turn the requested improvement into a testable next step. One illustrative action is: agree a shared communication owner.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which responsibility needs explanation? What resource expectation differs? What checkpoint would help?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
From question to next step
Start with the decision: Clarify expectations across collaborating community groups.
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which responsibility needs explanation?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Agree a shared communication owner.
Before you send it
Would you agree that everything about community partnership feedback was clear and easy?
Which responsibility needs 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
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
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 “Which responsibility needs explanation?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Groups disagree about who communicates schedule changes. This is an illustrative pattern to look for, not a claim about your respondents. Do not disclose confidential partnership terms.
Agree a shared communication owner. After trying the change, repeat “Which responsibility needs explanation?” with people who experienced it. Check whether they still describe the original issue: groups disagree about who communicates schedule changes. Compare explanations and sample context, rather than claiming the change caused an improvement.
Different resource expectations reveal an unresolved contribution or dependency between community partners. Agree the relevant scope and ownership before collaboration rather than assuming goodwill implies identical commitments. 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.
Continue exploring