# Feature prioritization survey

Understand the jobs behind feature requests.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Which proposed improvement would help your current work most?

Answer: ____________________

## 2. What would you use it to accomplish?

Answer: ____________________

## 3. How do you handle that need today?

Answer: ____________________

## 4. How often do you encounter the underlying need?

Answer: ____________________

## 5. What consequence does the current workaround have?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Connect a preferred improvement to current work rather than ranking features solely by novelty.
2. Ask for the task the improvement would enable so votes can be compared with actual needs.
3. Identify the existing workaround; a preference does not establish that the need is currently unmet.
4. Check how often the need occurs so a rare critical task and a frequent convenience are interpreted separately.
5. Assess the workaround's consequence without assuming that a new feature would remove every cost or error.

Interpretation caution: Votes alone do not measure implementation cost or willingness to pay.


## Illustrative finding and follow-up

Observation: Example votes favor a popular request while comments reveal infrequent use of the underlying task.

Action to test: Compare task frequency and consequence before ranking requests solely by votes.

Follow-up: After testing the action, revisit this original observation: Example votes favor a popular request while comments reveal infrequent use of the underlying task. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.