Business Requirements Gathering & Prioritization Survey

Thanks for taking a few minutes to help scope this project! Your input shapes what gets built and in what order. About 6-8 minutes, and there are no wrong answers — we want your honest experience with how things work today.

Which best describes your relationship to this project?

• Business or functional stakeholder
• End user / day-to-day operator
• Technical or IT stakeholder
• Sponsor or decision-maker
• Other

Describe how you currently handle (Replace with the task/workflow this project addresses, e.g., 'processing expense reimbursements'). Walk through the steps as you'd explain them to a new hire.

How much do you agree with each statement about the current process or system?

Of the capabilities being considered for this project, which matters most and least to you? (Template note: replace the options below with the actual candidate features or requirements for your project.)

• (Replace with capability A, e.g., real-time reporting)
• (Replace with capability B, e.g., mobile access)
• (Replace with capability C, e.g., automated approvals)
• (Replace with capability D, e.g., single sign-on)
• (Replace with capability E, e.g., audit trail/history)
• (Replace with capability F, e.g., bulk data import)
• (Replace with capability G, e.g., custom notifications)

How disruptive would it be to your work if this project were delayed by six months?

You have 100 points to distribute across these priorities based on what matters most for the new solution. Allocate more points to what matters more.

• Ease of use
• Speed and performance
• Reporting and analytics
• Integration with other tools/systems
• Cost to implement and maintain

What would tell you this project succeeded, six months after launch?

• Faster turnaround time
• Fewer errors or rework
• Better visibility or reporting
• Less manual, repetitive work
• Improved compliance or audit-readiness
• Other

Are there any constraints we should factor in — budget, deadline, compliance rules, or systems it must work with?

Identify the single requirement or capability the respondent ranked highest (from the prioritization exercise or constant-sum allocation) and probe the concrete story behind it: what specifically goes wrong or takes too long today, how often it happens, and what workaround they currently use. If they described a delay as highly disruptive, ask what breaks first and who else is affected. Push past vague answers like 'it would help a lot' to get a specific example from the last 30 days.

Which team or department are you part of? (Optional)

• (Replace with Department A)
• (Replace with Department B)
• (Replace with Department C)
• (Replace with Department D)
• Prefer not to say

How long have you been in your current role? (Optional)

• Less than 6 months
• 6 months to 2 years
• 2 to 5 years
• More than 5 years
• Prefer not to say

That's everything — thank you for the detail! Your answers feed directly into the requirements document and priority list for this project, and may be quoted (anonymously) to explain why a feature made the cut.