The best way to collect user feedback

· 4 min read
The best way to collect user feedback

generic feedback forms aren't the best way to collect feedbackThis user feedback form should look familiar. Most apps and websites have one.

But, is it really the best way to collect user feedback?

We’d argue that it isn’t.

It’s actually a very costly way to collect feedback: it creates a ton of urgent, manual work.

What should you do instead? Let your users submit and vote on feedback.

This switch will save you time and money, help you make better product decisions, and your users will love it.

Here’s a deeper dive into the issues with using a feedback form to collect user feedback. And, why user voting is a better solution.

Issue #1: Feedback forms waste time and money

The problem isn’t the form itself — it’s what happens after the form is filled out.

Feedback submitted via forms creates a mountain of requests. Full-time jobs are made just to process these requests, respond, and keep track of what was said.

At best, a spreadsheet is maintained to keep track of how many people ask for specific features. At worst, someone has to remember that “a lot of people have mentioned this bug recently.”

Either way, valuable information gets lost.

And, managing requests with a feedback form is expensive.

It costs you in labor hours associated with sifting through feedback. You might make bad product decisions because you didn’t have enough information. Both of these are costly.

Collect user feedback easily with Canny

Avatar

Andrew Rasmussen

Hi, I'm a co-founder of Canny. Before that, I was a software engineer at Facebook. I love JavaScript, rock climbing, nerding out about the future, and SaaS.

All Posts · Twitter

Issue #2: Canned responses are demoralizing

Responding to every piece of feedback isn’t realistic. There’s too much.

To get around this, most companies use canned responses:

This message is clearly automated. The user is left wondering, “Did anybody read my feedback? Are they going to build my feature?” Who knows.

How demoralizing. Why would they ever want to give feedback again?

If people don’t feel like you care about what they have to say, they’ll stop caring about you. This hurts the strength of your brand, which can negatively impact growth.

Issue #3: Live chat isn’t made to collect user feedback

Live chat is a great, lightweight way to communicate with your users. It‘s just a costly medium for collecting user feedback.

Live chat is essentially the same flow as the feedback form. It still generates tons of time-sensitive, manual work for your support team.

Consider how people typically use live chat :  with their friends. They’re used to getting a personal, timely response.

With canned responses and multi-hour delays, you’re setting them up for disappointment.

Solution: Let users submit feedback and vote on requests instead

Let’s say you let your users submit feedback requests, and vote on which new features your team should build.

Users can vote with the click of a button, so collecting this data requires zero effort.

user-votes

If you use a tool like Canny, you can associate each vote with a user id, so you know exactly who is voting. In other words, you know exactly which users want which features.

Remember that spreadsheet? The one that keeps track of which users want which features? The one that most support and product teams create and maintain manually?

When users can vote on features, you’ll get more complete data, but with a tiny fraction of the effort.

Keep users in the loop

Letting users vote cuts out tons of support work. And, you’re left with something manageable.

Responding to just the top 5% of user feedback requests addresses 50% of votes.

This makes it possible to write detailed responses. By doing so, users will know you’re listening.

They’ll love being involved in your product development process. They’ll specifically mention that you’re great at responding to feedback. This might mean 5-star app reviews, and when they tell their friends about your product.

Direct, meaningful interaction with users sets you apart from your competition. It boosts word-of-mouth growth.

Dive into the data

Now that you’ve got a beautiful pile of organized data, you can easily answer questions like:

  • What are my top 5 feature requests?
  • Which features does our biggest/most important/longest-standing customer care about?
  • Which customers want XYZ specific feature?

You can even take it a step further. Your CRM knows all sorts of stuff about your users. So, if you use a tool that integrates with your CRM, you can do further “feedback segmentation.”

You could choose to only view votes from:

  • Enterprise customers
  • Churned users
  • Qualified leads
  • …and so on

This filtering is especially helpful when your team is focused on a specific goal. Maybe you’re focused on reducing churn or driving enterprise sales. Viewing votes from churned users or enterprise customers would be helpful here.

Simplify the process of collecting user feedback

Most companies collect user feedback wrong. It creates unnecessary work for them and demoralizes their users.

But there’s a simple solution. By letting your users submit and vote on feedback, you get more complete data for a tiny fraction of the effort. And your users will love you for it.

Still on the fence about if you need a user feedback tool? Check out our article on determining if a user feedback tool is right for you. You can also try Canny free for 14 days to see it in action.

Avatar

Andrew Rasmussen

Hi, I'm a co-founder of Canny. Before that, I was a software engineer at Facebook. I love JavaScript, rock climbing, nerding out about the future, and SaaS.

All Posts · Twitter

Canny is a user feedback tool. We help software companies track feedback to build better products.

Leave a comment

avatar
wpDiscuz
© Canny 2020
Privacy · Terms · Security
canny-backstage

Come backstage, where we share an honest look into building Canny. You’ll be the first to know when we post new content.

Avatar

Andrew Rasmussen

Hi, I'm a co-founder of Canny. Before that, I was a software engineer at Facebook. I love JavaScript, rock climbing, nerding out about the future, and SaaS.

All Posts · Twitter