I am working on a new design for bank reconciliation in a piece of accounting software. We have identified our users' existing workflows and problems with our current design from an earlier round of customer interviews.
A couple of additional feature suggestions for bank reconciliation came up from our team based on other user needs they have seen in the past. An example is the ability to attach notes and files to a bank reconciliation. I'm not sure to what extent our users would actually use these features (they weren't core needs that we found in the earlier interviews), and I don't want to add to development time and clutter the screen with these bonuses if there's not high value in them for our users.
I'm planning to use a remote survey tool such as Verify to study this. I could ask the question in a couple of ways off the top of my head:
- How likely would you be to use [feature] on a scale of 1-10?
- How likely would you be to recommend [feature] to a colleague on a scale of 1-10?
- Would you have a use for [feature] in your regular process (yes or no)?
What is the best way to ask the question and interpret the results in order to get an accurate assessment of how widely-used these bonus features would be? I don't want to bias the results by respondents being agreeable.