Happy Thursday! When exploring the landscape for a project, it can be difficult to sift through the dozens of ideas that teams have to build out a great product. The really difficult part is that all these ideas may be exceptional, and there’s almost never enough room to fit them all in one project. That’s why we start out our projects by laying out all the ideas we have to implement into the product, and then stack ranking them to determine their priority.

Here’s how you can successfully prioritize at the beginning of a project:

  • Identify the problem space. Before we start brainstorming all the possibilities in a project, we need an idea of what challenges the customer is facing that we can solve for. Behavioral surveying with free response questions helps paint a picture of how your audience is describing their own gaps and needs, so you can brainstorm what features might solve those needs. Once you understand the problem space, it’s time to get all your ideas out on the table for everyone to see.

  • Explore every opportunity. What’s the business value, what’s the problem this is solving, who is it solving for? A detailed description is needed to explain how each of these features is actually improving the user’s experience. Once there’s understanding around feature, you can start determining which hold the most value for the project.

  • Determine their value to the business. Not only do you need to know how important each feature is to your team, you also need to identify which features are bringing true value to the users. Behavioral surveying can help you establish the user value for each feature, which should then be correlated with the business value and technical feasibility for building it out. We sum these values up using a 0-15 score of how important that feature is for the project. Now everyone is aligned on what the opportunities are for each project, and which features to start pursuing first.

Once you’ve prioritized your deliverables in a project, it can be helpful to create a burndown list for the actual order that you’ll be tackling these components in. Here’s where stack ranking comes in! Using the priorities you’ve already established, we can draw out the specific order in which these features should be produced to bring more structure to your project flow. 

Join the conversation to discuss how you rank features for your project!

Take our one-question survey 👇

Go win your day,
Morgan & The Helio Team

Did this answer your question?