User feedback can come from various sources, such as surveys, interviews, reviews, ratings, support tickets, social media, forums, analytics, and user testing. Each source has its own advantages and disadvantages, and you should use a combination of them to get a comprehensive and balanced view of your users' opinions, problems, and suggestions. You should also segment your feedback sources by user type, such as potential, new, active, or churned users, to understand their different perspectives and motivations.
At Meesho, we prioritized understanding user sentiments beyond mere ratings. Implementing L1 and L2 reason features through A/B testing for 10M+ users proved insightful. Prior to development, we conducted extensive secondary research via Google Play Store reviews, surveys, and ratings. Subsequently, primary interviews validated our hypothesis, leading to meticulous mockup designs and rigorous testing. Despite the significant engineering investment, the feature yielded over 100% fill rate increase, demonstrating its substantial value in enriching user feedback and refining our Quality North Star metrics approach. Later it helped us to identify the exact reason behind product returns
Turn Feedback into Features, Fueling Software Success! ?? I'd advise: - Gather feedback from diverse sources: surveys, interviews, and social media. ?? - Use tools like spreadsheets or feedback management software for organization. ?? - Employ affinity diagrams or Kano models for categorizing feedback. ?? - Validate and prioritize feedback to align with product goals. ?? - Recognize that not all feedback is equally valid or important. ?? - Regularly collect and analyze feedback for ongoing improvements. ?? - Use LinkedIn Product Pages to engage with your product community. ?? - Ensure feedback drives innovation while staying true to your vision. ?? Pro Tip: UserVoice is great for aggregating and analyzing user feedback! ???
In my experience, getting the people who use your product on a daily basis to provide feedback to you and your Dev Team is priceless. Also, going out to where they are using your product is very beneficial. You get to see first hand how they work on a daily basis. It also helps to take an experienced UXD colleague with you.
Opt for Targeted Feedback Analysis aligning with strategic direction and technological capabilities. So you’re not chasing trends, but creating features that make sense for the product. Make Data-Driven Decisions:Look beyond surface-level feedback and understand the underlying user behaviors and needs. Utilize Cross-Functional Brainstorming in the ideation process. Utilize Rapid Prototyping allowing experimentation with new ideas to get a real sense of their potential.
Using user feedback to generate new ideas and features: 1. Collect feedback through surveys, interviews, and analytics. 2. Categorize and prioritize insights based on impact. 3. Host brainstorming sessions with cross-functional teams. 4. Prototype and test the most promising ideas. 5. Continuously loop user feedback into the development process. Listening to users fuels innovation and ensures your product evolves to meet their needs. P.S. What's the most valuable feedback you've ever received?
Once you have collected user feedback from different sources, you need to organize and categorize it to make sense of it. You can use tools like spreadsheets, databases, or feedback management software to store, filter, and sort your feedback data. You can also use methods like affinity diagrams, Kano model, or MoSCoW technique to group your feedback into themes, problems, needs, and desires. By organizing and categorizing your feedback, you can identify patterns, trends, gaps, and opportunities for improvement.
After identifying your feedback sources and gathering the feedback, it's important to categorize and organize the feedback. Categories can be based on different aspects like usability issues, bugs, feature requests, user experience, pricing feedback, etc. This helps in understanding the frequency of certain types of feedback, which can be indicative of areas that require attention.
There are 3 general aspects that matter: 1. Performance benchmark. It measures the performance. 2. User experience and style. It measures the experience. 3. Build quality. It measures the physical quality. You should get feedback from your company, consultants, potential customers & customers for each of those 3 things. The initial impression, long term impression, and their opinion for particular questions that are asked will provide subjective feedback that is important for product development. You should also do benchmark objective testing to test different performance metrics, user experience and build quality. That gains you objective benchmark scores.
Not all user feedback is equally valid or important. Some feedback may be based on inaccurate assumptions, personal preferences, or outdated information. Some feedback may be relevant only to a small segment of users, or conflict with your product vision or goals. You need to validate and prioritize your feedback to determine which ideas and features are worth pursuing and which ones are not. You can use criteria like user impact, business value, feasibility, and alignment to validate and prioritize your feedback. You can also use techniques like user personas, jobs to be done, or user stories to define and communicate your feedback-based requirements.
A good feedback validation technique includes two key components: Quantitative analysis measures parameters related to product performance, such as sales statistics and user engagement. For example, an Amazon Product Manager analyses sales data and website traffic to detect an issue. Qualitative feedback focuses on subjective information from sources such as customer reviews and support tickets. This could include analyzing product reviews or evaluating consumer inquiries or order-related issues made with customer support. The intersection of these methodologies yields a clearer picture of user needs, which effectively guides iterative product development.
Before you implement your feedback-based features, you need to prototype and test them to see how they work and how your users respond to them. You can use tools like wireframes, mockups, or interactive prototypes to create low-fidelity or high-fidelity versions of your features. You can also use methods like usability testing, A/B testing, or beta testing to evaluate your features with real or representative users. By prototyping and testing your features, you can validate your assumptions, measure your outcomes, and gather more feedback for improvement.
Before implementing feedback-based features, it's crucial to prototype and test them to gauge their functionality and user response. - Use tools like wireframes, mockups, or interactive prototypes to create low or high-fidelity versions of the features. - Employ methods like usability testing, A/B testing, or beta testing to evaluate them with real or representative users. Prototyping and testing help validate assumptions, measure outcomes, and gather feedback for further improvement, ensuring the final product meets user needs and expectations.
Define the underlying assumptions or hypotheses before moving forward with prototyping. Assume, for example, that a lack of Zoom on an e-commerce store lowers?conversion rates since customers are unable to review?product specifications. Every assumption needs to have a specific testing strategy attached to it. For instance, A/B testing can be used, to compare two user groups: one that has access to the zoom capability and the other that does not. Then, comparisons are made between the groups using metrics like conversion rates and engagement (time spent on the page, interaction with product images). By systematically testing each assumption, you can gather empirical evidence to inform the development of feedback-based features.
Once you are confident that your feedback-based features are ready to launch, you need to plan and execute your release strategy. You can use tools like feature flags, rollout plans, or changelogs to control and communicate your launch process. You can also use methods like feedback loops, user adoption, or product analytics to monitor and measure the performance and impact of your features. By launching and monitoring your features, you can ensure that they deliver value to your users and your business.
Launching feedback-based features involves careful planning and execution of your release strategy. - Utilize tools such as feature flags, rollout plans, and changelogs to control and communicate the launch process effectively. - Employ methods like feedback loops, user adoption tracking, and product analytics to monitor and measure the performance and impact of your features post-launch. This ongoing monitoring helps ensure that your features deliver value to both your users and your business, allowing you to make informed decisions for future iterations and improvements.
User feedback is not a one-time event, but a continuous process. You need to learn and iterate from your feedback-based features to keep improving your software products. You can use tools like retrospectives, roadmaps, or backlog grooming to review and plan your next steps. You can also use methods like customer satisfaction, net promoter score, or retention rate to assess and improve your user loyalty and satisfaction. By learning and iterating from your feedback-based features, you can create a culture of user-centric innovation and growth.
Let's have a news app. While developing such an app feedback is essential, and it could be tracked using app-surveys, reviews, ratings etc. Upon feedback UI, content quality , features could be iterated upon reviews Users content could be personalized, regular review enables trend identification and areas to improve upon and A/B tests, usability tests shall be performed regularly to iterate effectively. And necessary metrics like engagement, retention, satisfaction gauges user response provement upon user feedback and market conditions would eventually establish the app's relevance in this domain.