This practical guide will help you decide on the respective steps of your journey towards the final product. <\/p>\n\n\n\n Our app development and design agency<\/a> has acquired a ton of experience with prioritization. And now, we would like to present you with our own framework<\/strong> for joggling with the many features you have in mind and assigning them priority<\/strong>.<\/p>\n\n\n\n We call it The PriX Method <\/strong>by Pixelfield, as it combines the strengths of multiple validated frameworks for prioritization. It includes both qualitative and quantitative assessments. <\/p>\n\n\n\n Before we jump to the step-by-step guide for prioritization<\/strong>, let’s answer some fundamental questions to make sure that we are all on the same page.<\/p>\n\n\n\n It’s pretty simple: <\/p>\n\n\n\n Are you, or will you soon be, part of a team building or improving a digital product<\/strong>?<\/p>\n\n\n\n Are you preparing the MVP development<\/a> for your startup? <\/p>\n\n\n\n Will you be involved in the process of creating a roadmap<\/strong> and planning releases<\/strong> (these terms will be discussed in more detail soon)?<\/p>\n\n\n\n Then this guide and The PriX Method by Pixelfield will definitely come in very handy!<\/p>\n\n\n\n A product roadmap<\/strong> is essentialy both a strategic document and handy visual overview of your team’s vision for your digital product development. <\/p>\n\n\n\n It captures the planned journey from the very first version all the way to the final product<\/strong> which provides users with all the desired features and value.<\/p>\n\n\n\n App developers for startups<\/a> generally don’t plan too far ahead as the roadmap would be too likely to change based on market reaction and new demands. Contrarily, owners of mature digital products can think of more long-term plans.<\/p>\n\n\n\n As the name suggests, your roadmap should depict a map of feasible steps<\/strong>, each bringing your users the best value with regard to your objectives for that particular stage of your roadmap. <\/p>\n\n\n\n These steps are called releases<\/strong>. Each release includes a set of features which are about to be added to the product. We strongly recommend to release small and fast<\/strong>:<\/p>\n\n\n\n Prioritization<\/strong> is a crucial discipline for tech startups and all other app developers<\/a>. It includes a complex analysis<\/strong> of all potential features and solutions you have come up with for your product.<\/p>\n\n\n\n The goal is to create a feasible set of features<\/strong> for a planned release. This set cannot be based simply on popularity rankings – you need to take into account many different aspects<\/strong> and consider the value of the features from the perspectives of various stakeholders<\/strong>.<\/p>\n\n\n\n The chosen features should provide value for the most part of this release’s target user segment<\/strong> while taking into account the goals of this stage<\/strong> of the product roadmap. They should also be in line with your capacities<\/strong> allocated for the upcoming release. And finally, they should logically fit into the map of user stories.<\/p>\n\n\n\n There are some very helpful frameworks available which can help you with the complex task of product prioritization for startups and app developers<\/a>. KANO, RICE, Story mapping, The MoSCoW method, Product tree, Cost of delay, and Opportunity scoring, to name a few.<\/p>\n\n\n\n However, we believe that none of these popular frameworks fully captures the complexity of prioritization, And that’s why we crafted our own framework – The PriX Method<\/strong>, which allows you to make the most out of the strengths of multiple approaches<\/strong> to prioritization.<\/p>\n\n\n\n Our framework includes an easy-to-follow sequence of strategical decisions<\/strong>, qualitative assessments, and quantitative estimates. <\/p>\n\n\n\n The outcome is a visualization of features prioritized in line with your goals, target user group, and user stories of your product.<\/p>\n\n\n\n Let’s take a look at the prioritization approaches we used to build The PriX Method.<\/p>\n\n\n\n This simple framework developed by Intercom’s product management team<\/a> is a very handy tool for assessing priority with actual numbers. <\/p>\n\n\n\n RICE stands for Reach<\/strong>, Impact<\/strong>, Confidence<\/strong>, and Effort<\/strong>, the four factors the framework uses to evaluate each candidate feature or solution.<\/p>\n\n\n\n Although we are big fans of the RICE method, we believe that four factors simply cannot cover the complexity of product prioritization. That’s why RICE is only one part of The PriX Method.<\/p>\n\n\n\n Another useful method of quantifying the value of features. The Cost of Delay is essentially an estimate of the money you will lose each week if the feature is introduced later than in the upcoming release.<\/p>\n\n\n\n This technique allows you to assign monetary value<\/strong> to the features in your product backlog. The best way to use this information is to devide the weekly\/monthly Cost of Delay by the duration of implementing the feature at hand.<\/p>\n\n\n\n Our London-based app developers<\/a> are of the opinion that this metric shouldn’t be purely monetary. Most app developers for startups<\/a> would agree that many of a roadmap’s stages have other primary goals than increasing revenue. That’s why we adjusted this metric in our own framework.<\/p>\n\n\n\n Another handy tool for identifying the most significant project ideas for the next release.<\/p>\n\n\n\n MoSCoW stands for Must-Have<\/strong>, Should-Have<\/strong>, Could-Have<\/strong> and Won’t-Have <\/strong>features. The output of the MoSCoW analysis<\/strong> is a filled-in matrix that will help you quickly plan next releases.<\/p>\n\n\n\n We adjusted the method a bit for the purpose of our own framework. But if you wish to get a better insight into the original MoSCoW analysis, watch the short video below.<\/p>\n\n\n\n![\"\"](\"https:\/\/pixelfield.co.uk\/blog\/wp-content\/uploads\/2020\/04\/Feature-Prioritization-101-1024x717.png\")
Who will benefit from this guide?<\/h2>\n\n\n\n
How will you benefit from this guide?<\/h2>\n\n\n\n
What is a product roadmap and how to work with it?<\/h2>\n\n\n\n
![\"\"](\"https:\/\/pixelfield.co.uk\/blog\/wp-content\/uploads\/2020\/04\/product-tl-1024x632.png\")
What is product prioritization?<\/h2>\n\n\n\n
![\"\"](\"https:\/\/pixelfield.co.uk\/blog\/wp-content\/uploads\/2020\/04\/emma1530748538874-1024x576.jpg\")
Origins of The PriX Method for prioritization by Pixelfield<\/h2>\n\n\n\n
RICE<\/h4>\n\n\n\n
![\"\"](\"https:\/\/pixelfield.co.uk\/blog\/wp-content\/uploads\/2020\/04\/RICE-1024x497.png\")
Cost of Delay<\/h4>\n\n\n\n
![\"\"](\"https:\/\/pixelfield.co.uk\/blog\/wp-content\/uploads\/2020\/04\/cost-1024x603.png\")
MoSCoW<\/h4>\n\n\n\n