1. Gathering user feedback

One of the first things I learned was that I couldn’t just assume what users wanted. I had to listen. It’s easy to think we know what users need, but the real value comes from directly hearing from them. My go-to methods are a mix of surveys, user interviews, and usability tests.

• Surveys help me gather broad feedback from a wide range of users, which is useful for spotting common trends.
• User Interviews provide a deeper understanding of why users behave the way they do, which is helpful for grasping the nuances of a feature.
• Usability Tests allow me to see firsthand how users interact with the product, revealing any issues or ideas that weren’t obvious before.

The key is not to rely on just one method. Combining them helps me get a full picture of where to focus next.

2. Categorizing feedback

After collecting the feedback, the next step is categorizing it. This part is crucial because it helps me identify the recurring themes and patterns, which make it easier to figure out where to focus my time and energy.

I break the feedback into categories such as:

• Pain Points: Issues that users are struggling with the most.
• Feature Requests: New features that users are asking for.
• Usability Issues: Challenges that prevent users from navigating the product easily.

By grouping the feedback, I can start to see which areas of the product need the most attention and which features could have the most impact.

3. Using the impact vs. effort matrix

This is where I get strategic. I use the Impact vs. Effort matrix to evaluate the potential value of each feature compared to the resources required to implement it.

I place each feature on a grid:

• High Impact, Low Effort: These are the features to prioritize—they bring a lot of value with little effort.
• High Impact, High Effort: These are important but will take time and resources. I typically save these for later.
• Low Impact, Low Effort: These are the nice-to-haves that can be implemented once higher-priority features are done.
• Low Impact, High Effort: These features are usually avoided unless they align with a critical business goal.

This matrix helps me prioritize features by focusing on what will deliver the most value with the least amount of effort.

4. MoSCoW method for clarity

When there are many features to consider, I use the MoSCoW method to help make things clearer. It’s a simple way to categorize features based on their importance, and I find it helps guide conversations with stakeholders.

Here’s how I apply it:

• Must Have: Critical features that users need.
• Should Have: Important features, but not essential right now.
• Could Have: Nice-to-have features that would improve the experience but aren’t essential.
• Won't Have: Features that aren’t needed at the moment and can be put on hold.

This method helps me communicate priorities clearly and ensures everyone on the team is on the same page.

5. Communicating with stakeholders

Once I’ve decided on priorities, I make sure to communicate my reasoning to stakeholders. This is a crucial part of the process. It’s important to explain why certain features are prioritized over others, especially when there are competing interests from different teams.

I always try to back up my decisions with data and insights from user feedback, whether that’s a pattern I noticed in surveys or a direct quote from a user interview. This approach helps create a shared understanding among the team and ensures the product development stays aligned with user needs.

6. Iterating and re-prioritizing

Feature prioritization isn’t a one-time task. As I continue gathering feedback and learning more about user needs, I often have to revisit my priorities. This iterative approach ensures that the product remains focused on what matters most and that I’m always addressing the evolving needs of users.

Feature prioritization is about making choices and staying focused on what will provide the most value. By listening to users and keeping an iterative mindset, I’ve been able to deliver products that better meet their needs.