登录查看更多内容

Users are divided on a feature update. How do you navigate conflicting feedback to make the best decision?

由人工智能和领英社区提供技术支持

When a new feature update splits your user base, finding the right path forward can be challenging. You want to innovate and keep your product fresh, but not at the expense of alienating loyal users. The key is to navigate the sea of conflicting feedback with a strategic approach, ensuring decisions are made that serve the broader goals of your software project while respecting the diverse needs of your user community. It's a balancing act, requiring a mix of data analysis, empathy, and foresight. Let's explore how you can sift through the noise and make the best decision for everyone involved.

此文章中的业界达人

由社区从 5 条内容中精选。了解更多

Bibhu Choudhary
Ayberk Ya?a
Serge Vinokour

Intelligent Technology Executive - There is no necessity to be ARTIFICIAL in order to be INTELLIGENT

1 Gather Data

Start by collecting as much data as possible. Look beyond the loud voices and seek out the silent majority by using surveys, analytics, and direct user interviews. Quantitative data can reveal how many users are actually using the feature and how it impacts your key performance indicators (KPIs). Meanwhile, qualitative data provides insight into why users feel the way they do about the update. This dual approach gives you a fuller picture of the situation, helping you understand the scale of the division and the underlying reasons for it.

添加您的观点

Serge Vinokour

Intelligent Technology Executive - There is no necessity to be ARTIFICIAL in order to be INTELLIGENT
(已编辑)
举报内容
This is a Product Manager’s or Sales Team’s job to collect data and opinions BEFORE implementing the feature. The discussion after should be about keeping or removing the feature, and this is a business-focused decision , not somebody’s opinion.

已翻译

赞

2 User Personas

Consider creating or revisiting user personas. These fictional characters represent different segments of your user base and are based on real data and user behavior patterns. By mapping out how the feature update affects each persona, you can understand which aspects of the update are contentious and why. This exercise can also help predict how potential changes might impact different types of users, allowing you to tailor your approach to address the concerns of each group effectively.

添加您的观点

Ayberk Ya?a
举报内容
One thing I've found helpful for that is the fact that for most projects, especially in the initial stages, 3 to 5 well-defined personas are typically sufficient.

已翻译

赞

3 Prioritize Feedback

Not all feedback is created equal. Prioritize input based on factors such as the user's expertise, engagement level with your software, and how representative their opinion is of the wider user base. High-value users who use your software daily and have a deep understanding of its functionality might provide more insightful feedback than casual users. However, don't dismiss the latter entirely, as they can often point out usability issues that power users have learned to overlook.

添加您的观点

Huy Tr?n

Scaling AI & Web3 Products | Product & Operations Leader | SaaS, Blockchain & IoT Innovator
举报内容
Evaluate how each piece of feedback affects user experience and business goals. Consider the following factors: - Usability: How does the feedback improve or hinder user interaction? - Performance: Will the changes enhance or degrade system performance? - Long-term Benefits: Does the feedback align with long-term strategic goals? - Alignment with Vision: How well does the feedback match the company’s overall vision and objectives? By assessing these factors, you can prioritize feedback that provides the most value and aligns with both user needs and business objectives.

已翻译

赞

4 Test Iteratively

Implementing changes based on feedback should be an iterative process. Use A/B testing or feature flagging to roll out updates to a small segment of users first. This allows you to gather more feedback and monitor the impact in a controlled environment. Pay close attention to how the changes affect user behavior and satisfaction. Iterative testing can help you refine the update until it aligns better with user expectations and needs.

添加您的观点

Bibhu Choudhary
举报内容
AB testing is a great tool for evaluating feature updates. Create cohorts of users as 'rings'. The closest ring is that of the most forgiving users - you, your fellow engineers and PMs, The next ring is Alpha users, followed by Beta users. If you are lucky, you have a customer advisory board. Finally remember the big red button - you can always roll back your feature if it doesnt resonate with your users.

已翻译

赞
Krishna Swarup

Engineering Leader | Product Development | Cloud Native Applications | Agile Practitioner | Leading global cross-functional teams | Stakeholder Collaboration | Mentor
举报内容
While implementing AB testing (or Experiment variants, e.g. control variant gets 50% of traffic and v1 variant gets another 50% of traffic), build a monitoring and tracking frameworks and tools. They should measure the user behavior directly (e.g. events sent from the client/front end application) and the business metrics (e.g. new user created etc.). Combining these two types of metrics across the variants will give a better understanding of the feature behavior. And we need to build alerts and monitors for system and application behavior also.

已翻译

赞

5 Communicate Clearly

Communication is critical when addressing divided feedback. Be transparent about the reasons for the update and how user feedback is influencing subsequent changes. Provide clear channels for users to voice their opinions and ensure they feel heard. Regular updates on the progress of implementing feedback can help build trust and show that you are committed to improving the user experience based on their input.

添加您的观点

6 Balance Vision

Finally, balance the feedback against your software's long-term vision. User feedback is invaluable, but it should not dictate every decision. Sometimes, users resist change simply because it's new, not because it's bad. Consider the overall direction you want your software to take and weigh whether the feature update aligns with that vision. If it does, find ways to ease users into the change without compromising your goals.

添加您的观点

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Software Engineering

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

Users are divided on a feature update. How do you navigate conflicting feedback to make the best decision?

1

2

3

4

5

6

7

1 Gather Data

2 User Personas

3 Prioritize Feedback

4 Test Iteratively

5 Communicate Clearly

6 Balance Vision

7 Here’s what else to consider

Software Engineering

给文章评分

感谢您的反馈

更多Software Engineering相关文章

更多相关阅读内容