Any good Product Manager will tell you that a big part of their job is forming a deep understanding of customer needs, but the current crop of user idea suggestion portals might not be the best tool for the job.
What are idea portals and how they work?
Most feature idea portals have the same core mechanics:
- Users visit a dedicated website with a list of feature ideas from other users (and sometimes the company itself);
- Users can submit their ideas or vote and comment on existing ideas;
- Administrators review submissions, prioritize and publicly communicate their status to the users.
The premise of an idea portal is terrific: instead of product managers having to scratch their head as to what features their team should build, why not let users themselves to spell out what they need. Then have them prioritize ideas through voting, and from there it’s just a matter of picking the top ones for implementation.
But does this user-led workflow provide the best guide for your product development?
3 Problems with idea portals
1. Asking users to prioritize your product roadmap
Because the idea portal is a public forum, the implicit contract is that for investing time in suggesting a new product idea users at least deserve a thoughtful response from the product team. This adds administrative overhead on you, but that’s not the worst part.
If hundreds of users upvote an idea, it adds further pressure on you to implement the idea. Lucky you if the suggestion happens to align with your business and product strategy. If not — you are on the defense trying to rationalize to hundreds of users as to why you are not going to implement a popular idea. Suddenly, you are faced with a tough dilemma of breaching user trust and admitting that you might not be as ‘customer-centric’ as you made it seem or allowing the most vocal of your users to steer your roadmap.
2. Asking users to design your product
The way idea portals frame suggestions forces users to think in terms of solutions. This puts the user in the role of a product designer where they are expected to conceptualize, design and describe a solution which will improve your product or service.
It’s fair to say that most users aren’t qualified for this task and don’t have the same context as your team. Therefore most proposed feature ideas will frustrate your designers and engineers while at the same time lack in the rich context around the underlying problems that you need to know.
3. Prioritizing based on votes
Because feature idea lists are often ordered by the number of votes, it might be tempting to prioritize feature idea suggestions by the number of votes they attracted. If many people vote on an idea then surely there must be many people who need it. The problem with this approach is that not all votes are created equal.
Firstly, on idea portals, votes don’t come with any indication of how strong the user’s need is. It could range anywhere from “nice to have” to “my life depends on it”. A vote is a vote.
Secondly, votes might carry different weight depending on your product strategy. For example, if your quarterly goal is to decrease the churn of paying customers, you want to identify what functionality this segment lacks as it might be causing churn. It doesn’t matter if hundreds of free users vote an a suggestion if it has nothing to do with the needs of your paying customers.
A better way
1. Set the right expectations
When launching your idea forum, avoid setting the expectation that you will respond to every request or that you will implement the most popular ideas. Highlight that while you consider customer suggestions, every feature has to go through a rigorous process of research, prototyping, validation, design, engineering, and testing to make sure that only the most valuable features are implemented. This will free you to make decisions that are aligned with your product strategy.
2. Focus on customer problems
It is your job to craft solutions, not the customer’s. Users are the ultimate experts in their own problems, so you need to make sure that you are capturing their needs and pain-points from every idea suggestion.
You can encourage this by formatting your idea submission forms to focus on the following questions:
- What is the problem you’re experiencing?
- Describe the last time you encountered this problem.
- How will you know if this problem is solved?
- How will your life improve if it’s solved?
3. Segment you reports
Make sure that you have key customer metadata recorded against their idea suggestions so that you can segment into meaningful buckets. The types of metadata you track will depend on what distinguishes your customers. It might be their job title, company size, plan type, monthly activity. This will allow you to identify ideas that pertain to customer segments you care about serving and weed others.
4. Mix in other data sources
Instead of treating your idea portal as the only source of truth for customer needs, treat it as one of the inputs into your customer research process.
Depending on your business, you might have access to customer support tickets, sales conversations, user reviews, survey responses, UX interviews, and many other channels. Many of these channels collect data in a way that’s less biased than idea portals and when combined and analyzed will give you a much broader overview of your user needs.
5. Automate the analysis
With the advancements in Natural Language Processing (NLP) technology and Machine Learning in general, automating the analysis of unstructured customer feedback is becoming more and more accessible.
Given the increasingly large volumes of customer feedback that businesses are gathering from various sources, it makes sense to make sure that every piece is analyzed and learned from.
This is precisely what we set out to do at Prodsight.ai. We help with a cost-effective way of analyzing customer feedback for themes and sentiment.
When used with care, idea portals can be a fantastic source of customer feedback. Any form of customer involvement in product creation is a positive thing. However, the subtle ways in which idea portals can mislead and misinform product leaders are worth noting.