Which responsibility was difficult to locate?
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: people search for tasks but directory entries use job titles.
Operations and internal services / Survey guide
Operations and internal services · Practical survey guide
Internal contact directory survey
Improve finding the right organizational contact.
Opens product registration. Example questions are not imported automatically.
FOLLOW THE FEEDBACK
- Understand the context
Which responsibility was difficult to locate?
- Investigate the friction
What role label was unclear?
- Choose a next check
What directory update would help?
A planning aid, not automated analysis of your answers.
A useful starting point
Questions to understand the actual experience.
Improve finding the right organizational contact. 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.
What role label was unclear?
An unclear role label reveals why a directory entry does not explain who handles a task. Add current responsibility descriptions and approved contact routes, without publishing private contact information or relying solely on job titles.
What directory update would help?
Turn the requested improvement into a testable next step. One illustrative action is: add responsibility keywords to approved entries.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which responsibility was difficult to locate? What role label was unclear? What directory update 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 publish private contact information.
People search for tasks but directory entries use job titles. This is a synthetic example, not a customer result. Do not publish private contact information.
Before you send it
Check what your wording assumes.
Would you agree that everything about internal contact directory was clear and easy?
Which responsibility was difficult to locate?
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
People search for tasks but directory entries use job titles.
Choose an action to test
Add responsibility keywords to approved entries.
Check the experience again
After trying the change, repeat “Which responsibility was difficult to locate?” with people who experienced it. Check whether they still describe the original issue: people search for tasks but directory entries use job titles. 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: Improve finding the right organizational contact.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which responsibility was difficult to locate?”, 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
Add responsibility keywords to approved entries.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which responsibility was difficult to locate? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What role label was unclear? | Optional written explanation | Keep context that distinguishes different experiences. Do not publish private contact information. |
| What directory update would help? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Add responsibility keywords to approved entries. |
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?
Colleagues who used or delivered the described internal process. 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 responsibility was difficult to locate?”, 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?
People search for tasks but directory entries use job titles. This is an illustrative pattern to look for, not a claim about your respondents. Do not publish private contact information.
What would a practical follow-up look like?
Add responsibility keywords to approved entries. After trying the change, repeat “Which responsibility was difficult to locate?” with people who experienced it. Check whether they still describe the original issue: people search for tasks but directory entries use job titles. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “What role label was unclear?”?
An unclear role label reveals why a directory entry does not explain who handles a task. Add current responsibility descriptions and approved contact routes, without publishing private contact information or relying solely on job titles. 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 internal contact directory 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