How do you manage incoming feature requests and prioritize your roadmap? How do you figure out what you should work on next?
These are tough questions for any product manager — or any team trying to prioritize the work they need to accomplish. Efficient requirements management takes skill in all companies. But in more complex organizations, it takes real expertise.
Click any of the following links to skip ahead:
Here are four tips to make roadmap planning and requirements management more efficient, meaningful, and enjoyable:
As a great product manager, you must establish a "goal first" approach and a true north for your product based on the best information you have. Reaffirm your strategy and tweak it as necessary, but stay grounded in what you are trying to achieve. This is even more important if there are several teams involved in managing the product. The product team must agree on strategic initiatives first, then align the roadmap and requirements against them. (They must also make the necessary trade-offs as a group.) Explain to the company and product team where you are headed and the value that new releases and features will deliver to customers and the business. If you do, your company and team will follow. If you lose your direction or whip-saw the team back and forth, then complaints will quickly beat you down.
Lead with conviction
In all organizations, competing interests demand that different enhancements and improvements be made to the product. There's a reason that PMs are considered the CEOs of their product. They must make tough decisions and lead with conviction. Even on great teams where consensus and trust come easy, someone must make the final call when there are real reasons for disagreement. If you do not resolve these disagreements and try to push indecision into engineering, they will either smile and start building what they think is right or thrash and simply stall out.
Write more (and less) down
Engineers often complain that there is not enough written down, which makes it impossible to focus their efforts. Capture features and their related stories or requirements as bite-sized chunks (instead of long requirements docs). This gives you a record of what customers and other key groups are requesting. It also allows you to incrementally improve these ideas and add additional details over time. The key is to capture what's essential and what the new capability should enable. This is not the place to detail every last bit of minutiae or explain how engineering should build each feature.
Note: If you must produce a requirements doc as part of your process, build and publish it dynamically on the Features > List view. Just filter by the release, add features and descriptions, and you're done.
Rank features based on business value
If you are taking the first three actions, then this last one is relatively easy. If not, it is nearly impossible to quantify the value of each feature and do a good job of prioritizing next steps.
But sometimes the highest-scoring feature is not the one your team needs to address next. It could be that your team has some capacity at the end of the week and you want to find low-effort features to tackle quickly. Or maybe you want to see features with a high impact on a metric, like customer satisfaction — say, anything scoring between 90 and 100 points, regardless of effort. In these cases, you should filter your list report by scorecard metric, not by total score.
Navigate to Features > List to pull up a list report of your features. Filter the list to show a subset of your features (you may want to look at features still in parking lots or features with a particular tag), then add filters or data columns for each of your scorecard metrics.
In the Add filter and Add data modals, you will have the option to add the metrics for any scorecard in use in your account. So it is helpful to know ahead of time which scorecard applies to your features in your workspace.
To do this, navigate to Settings ⚙️> Workspace > Configure > Scorecard for features. If you see a custom scorecard there, note its name, then search for that scorecard in the Add filter and Add data modals — each scorecard metric will append the scorecard name. If you see the default scorecard there, search for the Aha! default features scorecard in the Add filter and Add data modals.
If filtering by these values, click the filter dropdown and select from the numerical filter options to show values that are a range, a comparison, blank, or not blank. You can apply multiple filters at once — for example, you may want to filter for features with very low effort and greater-than-average value.