{
  "title": "Software request process survey",
  "questions": [
    "Which requirement was hard to explain?",
    "Where did you find approved alternatives?",
    "What decision information was missing?"
  ],
  "question_notes": [
    "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.",
    "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.",
    "Turn the requested improvement into a testable next step. One illustrative action is: ask for the task and required capability."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Optional short text",
      "reason": "Retain the specific point or condition described; avoid replacing it with an unexplained rating."
    },
    {
      "question": 2,
      "format": "Optional written explanation",
      "reason": "Keep context that distinguishes different experiences. Do not assume requested software will be approved."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Ask for the task and required capability."
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "note": "Examples to adapt. Not a validated instrument."
}