<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aram Petrosyan on Medium]]></title>
        <description><![CDATA[Stories by Aram Petrosyan on Medium]]></description>
        <link>https://medium.com/@arampetrosyan?source=rss-2187f69dc533------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Xya6mzI330K_8PoN2u7Odg.jpeg</url>
            <title>Stories by Aram Petrosyan on Medium</title>
            <link>https://medium.com/@arampetrosyan?source=rss-2187f69dc533------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:13:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arampetrosyan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Product/Project prioritization based on economic impact and financial throughput]]></title>
            <link>https://arampetrosyan.medium.com/product-project-prioritization-based-on-economic-impact-and-financial-throughput-243f7497b005?source=rss-2187f69dc533------2</link>
            <guid isPermaLink="false">https://medium.com/p/243f7497b005</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[kanban-method]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <dc:creator><![CDATA[Aram Petrosyan]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 21:26:20 GMT</pubDate>
            <atom:updated>2021-07-09T13:10:44.380Z</atom:updated>
            <content:encoded><![CDATA[<p>Whoever knows me comprehends the fact that I am more of a process-oriented guy rather than a product hence you might be curious on why I am going to talk about project/product prioritization in this article however I see the value in sharing my experience in terms of structuring the proper process around prioritization cause I see a trend of “more features = more value for the end-users” concept leading great products to miserably fail.</p><p>I won’t explain each term/concept in this article and instead will focus on the approach and will provide relevant links so that you can explore those terms/concepts in detail if you are not already familiar with those.</p><p>I will mainly focus on:</p><ol><li>Prioritization of features within the predefined value stream/product/project depends on the methodology/framework, organizational structure</li><li>Prioritization of projects within the predefined program/portfolio</li></ol><p>So for both, the following approach works pretty well regardless of the methodology/framework and organizational structure.</p><p>In order to have proper prioritization in place you need to have two main inputs handy:</p><ol><li>Projected Market Value</li><li>Projected Flow Time (effort estimation)</li></ol><p>Nowadays it is common to skip the projected market value input and rely on effort estimation to trigger prioritization because it is REALLY complex to determine end-user value in various situations. In any case money ($$$) is MANDATORY for proper prioritization.</p><p>In various cases, you may find that there is no expected outcome in terms of money for a particular project/product if you are working on NGO or government projects mainly oriented to end-user benefits in terms of reducing the time they spend on any of their activities. So let’s see how we can quantify projected market value in these complex cases.</p><p>There are numerous articles describing how to forecast projected market value ($$$) in SaaS or fixed price product/service environment hence I would focus on the NGO/government services where I prefer to leverage the <a href="https://foldingburritos.com/articles/2015/04/08/customer-value-in-a-software-product/">Value = Benefits/Cost</a> concept shared by Folding Burritos. I would highly advise reading this article if you are not familiar with the Benefits/Cost type of value definition. In case you have your own way of defining the value ($$$) you can skip this article and proceed reading.</p><p>Let’s say you have the first input ($$$) handy hence the next step is to determine the Flow Time of each feature/project.</p><p><a href="https://tameflow.com/blog/2013-07-23/replacing-cycle-time-with-flow-time/#:~:text=Flow%20Time%20(FT)%2C%20or,terms%20of%20units%20of%20productivity.">Here</a> you can read about the definition of Flow Time that I am referring to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ITWgqqOAhJXshp1ockGx0Q.png" /></figure><p>In order to simplify I would say forecasted Flow Time is the forecasted duration of your feature/project. Man-days estimation will also fit this exercise however I won’t advise going with it, because it doesn’t count Wait Time (queues) within the flow of work unless you can’t get a flow time (duration) estimate but the idea is to use flow time which consists of both touch time (value-added time) and wait times (queues, impediments, non-value-added time).</p><p>So let’s START!</p><p>See below the sequential prioritization scheme:</p><h4>Compare Financial Throughput rate = Projected Market Value/Herbie Flow Time</h4><p>So first of all you need to know what Herbie means in this context hence please refer to this great <a href="https://yorkesoftware.com/2018/07/18/explaining-herbie/">article</a> explaining the concepts of Herbie from the book “<a href="https://www.amazon.com/Goal-Process-Ongoing-Improvement/dp/0884271951">The Goal</a>” in a more accessible way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*XkEDegaCSWGIjLubFVmeKg.jpeg" /></figure><p>I would highly recommend reading “<a href="https://tameflow.com/book/tame-your-work-flow/">Tame your Work Flow</a>” where ToC (Theory of Constraints) and management by exception with advanced mental models are explained in detail leading to a pragmatic and human-centered systems-thinking approach for creating breakthrough performance-innovation in knowledge-intensive digital-businesses.</p><p>So let’s say you already know what does Herbie Flow Time mean (flow time of the constraint in your workflow, for example, UAT stage, see below image):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XBkc0lUg8Hm7ZsjLIFvZA.jpeg" /></figure><p>Above is just a random example, in the majority of the cases “Development” stage would be the constraint in software development.</p><p><strong>Example:</strong></p><p><em>Project/Feature 1</em></p><p>Forecasted market value: 100$</p><p>Herbie forecasted flow time: 5 days</p><p>Throughput rate: 100/5 = 20</p><p><em>Project/Feature 2</em></p><p>Forecasted market value: 200$</p><p>Herbie forecasted flow time: 15 days</p><p>Throughput rate: 100/15 = 13.333</p><p><strong>Project 1 wins and should be prioritized to start first even if project 2 forecasted market value is higher!</strong></p><h4>2. Compare Cost of Delay (ROI for MBAs) = Projected Market Value/E-to-E Flow Time</h4><p><strong>Example:</strong></p><p><em>Project/Feature 1</em></p><p>Forecasted market value: 100$</p><p>Herbie forecasted flow time: 5 days</p><p>Throughput rate: 100/5 = 20</p><p><em>Project/Feature 2</em></p><p>Forecasted market value: 200$</p><p>Herbie forecasted flow time: 10 days</p><p>Throughput rate: 200/10 = 20</p><p>In this case, we will compare CoD values</p><p><em>Project/Feature 1</em></p><p>Forecasted market value: 100$</p><p>Forecasted E-to-E flow time: 15 days</p><p>Throughput rate: 100/15 = 6.6</p><p><em>Project/Feature 2</em></p><p>Forecasted market value: 200$</p><p>Forecasted E-to-E flow time: 25 days</p><p>Throughput rate: 200/25 = 8</p><p><strong>Project 2 wins and should be prioritized to start first!</strong></p><p><strong>NOTE:</strong> Leverage CoD comparison only if financial throughput rate ratio is equal for both projects as highlighted above.</p><h4>3. Compare E-to-E flow time</h4><p>In this case, we will compare the E-to-E Flow Time of each project because let’s assume CoD is the same.</p><p><strong>Example:</strong></p><p><em>Project/Feature 1</em></p><p>Forecasted market value: 100$</p><p>Forecasted E-to-E flow time: 15 days</p><p>Throughput rate: 100/15 = 6.6</p><p><em>Project/Feature 2</em></p><p>Forecasted market value: 200$</p><p>Forecasted E-to-E flow time: 30 days</p><p>Throughput rate: 200/30 = 6.6</p><p><strong>Project 1 wins because the Forecasted E-to-E flow time is shorter.</strong></p><p>Compare E-to-E flow time for each project only if N1 (Financial Throughput rate ratio) and N2 (Cost of Delay) highlighted in the above 2 examples are equal.</p><p>Hope the approach described above will help you to better prioritize your projects and features :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=243f7497b005" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>