All software platforms must evolve to thrive and survive by adjusting to users’ needs and, when justified, expanding core functionality. The challenge for leadership and product teams is to select the features that provide the greatest ROI with acceptable risk. Too often, feature development is driven more by gut instincts than by a more methodical evaluation of options. In this article, we’ll walk through a very approachable method for identifying and validating your winners in the backlog.
When determining your software’s next set of features, consider feedback from various sources, including customers, user experience, and key stakeholders. This list of features can be displayed in a visual representation or roadmap of where your software is headed and used to explain your vision. A product roadmap is not just a development schedule but a communication tool for the internal team, customers, and key stakeholders. Some features may need to be broken down into smaller features to be accurately scored.
After receiving feedback from users, customers, and key stakeholders, it is time to prioritize features on your product roadmap. Where do you start? Like prioritizing tasks within a to-do list, begin by comparing the value associated with each feature and the resources needed to complete it. One strategy to do this is by comparing Value vs. Risk.
Value is, of course, a key aspect of any product development. This is what drives not only your business goals but also user or customer success. Often, understanding the value of certain features can come easier than identifying risks. When we can work and build relationships with our customers and/or users, hearing what brings value can come naturally. However, Risk is often overlooked and critical in determining how to manage your product successfully.
Before we determine what to build, let’s identify the risks of each feature. Risk in this context can have a few different meanings. Before diving into each one, obtain feedback from various individuals within a cross-functional team. If you do not have a team that you work with already, find individuals who provide subject matter expertise. Key individuals to include in these conversations can be those with a background in product development, intellectual property, customer/user success, or business strategy, to name a few. When diving into these conversations, consider the below questions:
Each of the above categories may be unique to your project. With your team, determine which is the most important.
Now we need to identify value. Value in this context can also have a few meanings.
We just defined Risk and Value in this context, so now we can score or grade each feature. There are several ways to do this. For example, you can make up your scoring system and think broadly and relatively to the features on the list, such as “Low, Medium, High.” You can also score features on a 1-5 numeric or Likert scale. However, I recommend starting simply until you become more familiar with the process.
Create a table like the one below with at least four columns. The column on the left will be the list of features. “Source” can be where those features came from. For example, was this feedback from a customer? This information then ties back to your Product Requirements. The two columns will be where you will score your Value and Risk. Lastly, the “Roadmap” column is where you will indicate when on the roadmap you expect to work on the feature.
UX: user experience, BV: business value, CS: customer success
Let’s work through this example.
The first feature we will score on is: “integration with social media.”
Let’s do one more. The next feature we will score is: “Single-Sign-On.” Users asked for this feature, and from a business value perspective, it will increase the likelihood of a person making an account.
Once we have prioritized features, we can develop or add them to our product roadmap. The far-right column in the graphic above leaves a space to add when you plan to develop that feature. There are many types of roadmaps, but for the sake of simplicity, we can place our features on a timeline. Using a timeline helps you determine when it is realistic to work on a feature. Consider roadblocks such as the availability of your resources, big marketing events coming up, or customer meetings. It is particularly important to consider High Risk, High Value items that may take a longer time to execute but are important to accomplish. In this case, it may make sense to break these into smaller features before adding them to the roadmap.
Once you can compare features on a timeline, you start to see patterns in when you’ve decided to work on each feature. However, a timeline isn’t always necessary. Especially for ideas coming off the ground, it is often simpler to decide your next goals for the days or months ahead versus an entire year. Check out this blog post for more detail on developing a strategic plan and product roadmap.
Now that you have a list of prioritized features and your roadmap, you can share it with your team and key stakeholders. This exercise will help you consider the value and risks of what you are building before having critical conversations and getting feedback.
In order to evaluate and prioritize the Risk vs. Value of feature development, it is important to consider the various meanings of Risk and Value in the context of your project. This includes factors such as cost, time, effort, strategic vision, milestones and KPIs, and user and customer success. By comparing these factors, it is possible to make informed decisions about which features to prioritize on your product roadmap. This will help you achieve your business goals and deliver value to your users and customers.
If the concepts in this article peak your interest, let us know. The REEA Global User Experience Research team can deliver studies that inform the next iteration of your product with nuanced user feedback and then engage an in-house team of 140+ engineers to bring it to life. To learn more about how to compare Risk vs Value, please contact us today.
Explore REEA Global’s recent articles featuring:
” Their work was on time, within budget, and of the highest quality. In addition to their core expertise, the REEA GLOBAL team has a lot of skill in anticipating unspoken needs. The result was a final deliverable that was much better than envisioned ”
Court – Executive Director
” Our entire team, including our executive leadership, found this to be an incredibly valuable investment that allowed us to change a few things, even mid-build to ensure the next version release of our product was as user-friendly as possible ”
Jessica – Head of Product
” They went above and beyond meeting our design needs and easily saved our company 6 months to a year’s worth of work. REEA delivered a gorgeous product design that put us on par with our much larger competitors. We are now punching way above our weight and REEA is one of the reasons why. ”
Tim – Co-Founder
” It has been a pleasure to work alongside their experienced frontend and backend developers as a team to meet our product goals. REEA Global’s staff is professional, reliable, and trustworthy — a great partner through the challenges of software development. ”
Deena – Head of Product
” The team is super responsive and is helping us prioritize our needs. The weekly meetings allow us to check in and give us an opportunity to bring up issues in a timely manner. ”
Karen – Director of Clinical Programs
” The team was organized and prepared in addition to providing the executive team with seamless communication and full transparency during the process, something we had lacked in prior relationships I would highly recommend the REEA Global team. ”
Evan – CEO & Founder
” REEA was seamless in their setup and, more importantly, integration with the existing team. The work product was excellent, and we certainly plan to keep using them ”
Jason – CEO