Which requirement was hard to explain?
Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: requests are delayed because the intended task is unclear.
Operations and internal services / Survey guide
Operations and internal services · Practical survey guide
Software request process survey
Find friction before requesting an approved tool.
Opens product registration. Example questions are not imported automatically.
ILLUSTRATIVE QUESTIONNAIRE3 prompts
Try the first three questions here. Nothing is submitted or saved.
A useful starting point
Questions to understand the actual experience.
Find friction before requesting an approved tool. 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.
Where did you find approved alternatives?
The place someone searched for alternatives reveals whether approved options are discoverable before a new request. Improve references to current guidance, without presenting suggested tools as authorized or assuming an alternative meets every need.
What decision information was missing?
Turn the requested improvement into a testable next step. One illustrative action is: ask for the task and required capability.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which requirement was hard to explain? Where did you find approved alternatives? What decision information was missing?
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 assume requested software will be approved.
Requests are delayed because the intended task is unclear. This is a synthetic example, not a customer result. Do not assume requested software will be approved.
Before you send it
Check what your wording assumes.
Would you agree that everything about software request process was clear and easy?
Which requirement was hard to explain?
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
Requests are delayed because the intended task is unclear.
Choose an action to test
Ask for the task and required capability.
Check the experience again
After trying the change, repeat “Which requirement was hard to explain?” with people who experienced it. Check whether they still describe the original issue: requests are delayed because the intended task is unclear. 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: Find friction before requesting an approved tool.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which requirement was hard to explain?”, 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
Ask for the task and required capability.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which requirement was hard to explain? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| Where did you find approved alternatives? | Optional written explanation | Keep context that distinguishes different experiences. Do not assume requested software will be approved. |
| What decision information was missing? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Ask for the task and required capability. |
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 requirement was hard to explain?”, 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?
Requests are delayed because the intended task is unclear. This is an illustrative pattern to look for, not a claim about your respondents. Do not assume requested software will be approved.
What would a practical follow-up look like?
Ask for the task and required capability. After trying the change, repeat “Which requirement was hard to explain?” with people who experienced it. Check whether they still describe the original issue: requests are delayed because the intended task is unclear. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “Where did you find approved alternatives?”?
The place someone searched for alternatives reveals whether approved options are discoverable before a new request. Improve references to current guidance, without presenting suggested tools as authorized or assuming an alternative meets every need. 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 software request process 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