Moving From a Project to a Product Mindset
<p>The Iron Triangle concept was born in the 50s. I won’t go into it’s long and varied history, but safe to say project folk the world over know it well and live by it. Frequently, it is used in stakeholder meetings to justify extending the timeline, when asking for more money, or to trim scope.</p>
<p>A variation of this triangle as things evolved was to add a centre-point of “Quality”, to sit with Time, Scope, and Cost/Budget.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*P6P31BMMXJFu3KqvGbFAMw.jpeg" style="height:289px; width:700px" /></p>
<p>Credit: Peter Morville — <a href="https://www.flickr.com/photos/morville/40648134582" rel="noopener ugc nofollow" target="_blank">https://www.flickr.com/photos/morville/40648134582</a></p>
<p>The addition of quality was supposed to be revelatory, but none of these considerations tackled the fundamental reason we do projects in the first place. What is the reason we do projects?</p>
<h1><strong><em>It’s about Value and Benefit</em></strong></h1>
<p>In the world of Product this is simply Value, which could be measured through Return on Investment, Revenue, Profit, Savings, or any similar kind of metric. So for me, there is one core aspect to every project or product delivery, which is the <strong><em>value </em></strong>of doing that thing.</p>
<p><a href="https://productcoalition.com/moving-from-a-project-to-a-product-mindset-699385d125d9"><strong>Visit Now</strong></a></p>