How Does Uservoice Always Know What Features Its Customers Want?

I came across the UserVoice Product Feedback forum recently, and it soon dawned on me that this is how software companies should find out what features it should build – based on what its customers/users want.

The process is pretty simple. Anyone can post a feature request in the Product Feedback forum, and other users can vote up feature requests they like. UserVoice puts the top voted feature requests into production.

This is an excellent example of crowdsourcing at work. Customers get what they want. UserVoice gets happy customers. It’s that simple. You can use the same concept for all types of product and service feedback.

Of course UserVoice isn’t the only software company asking its customers what features they want. But more often than not, software companies build features based on what they think their customers want or some new trend they have read about.

Why do that when you can ask your customers what they really want? After all, the reason for adding new features is to keep your customers happy, right? So why not ask them what would make them happy instead of guessing?

Are you adding features that your customers are asking for, or are you still adding features based on what you think your customers want?

UserVoice Product Feedback forum »

Sorry, comments are closed for this post.