<?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 Mohammed Mohsin on Medium]]></title>
        <description><![CDATA[Stories by Mohammed Mohsin on Medium]]></description>
        <link>https://medium.com/@Mohsin.M?source=rss-8118d58662c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*juNjLVZxdXSmdPMM.jpg</url>
            <title>Stories by Mohammed Mohsin on Medium</title>
            <link>https://medium.com/@Mohsin.M?source=rss-8118d58662c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:21:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Mohsin.M/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[How to own a ‘Product’ aka the Product Owner !]]></title>
            <link>https://medium.com/@Mohsin.M/how-to-own-a-product-aka-the-product-owner-d14fd99654b8?source=rss-8118d58662c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d14fd99654b8</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[2022]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mohammed Mohsin]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 03:25:39 GMT</pubDate>
            <atom:updated>2022-06-09T03:25:39.390Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to own a ‘Product’ a.k.a the Product Owner !</h3><p>As most organizations adopt Agile , the Product Owner role is becoming more and more prevalent . While some organically grow people into this role , most of them hire laterally . Unfortunately, the understanding of the role is not accurate and even if it is they fall into some of the anti-patterns and pitfalls, here we will try to list on how we can be more effective as a Product Owner in the Agile context and the common anti-patterns.</p><p><strong>Product Vision</strong></p><p>As a Product Owner, your primary and most critical responsibility is to see where the Product is <em>NOW</em> and envision its future. For this we need to understand the product itself , the end users , the industry and also keep abreast with the changes in the overall eco system. This takes a lot of efforts in terms of understanding user behavior, company strategy and the latest in technology and how it is driving user behavior.</p><p>One of the common anti-pattern is that we assume the Product vision or the road map is a fixed goal and is not subject to change which is wrong as things are so dynamic that we need to keep revisiting our vision and correct them when it warrants.</p><p><strong>Stakeholder Management</strong></p><p>Product Owners work with different stakeholders, but the most important ones are the costumers/end-users, however there are others who also play a critical role — the development team, the marketing team, the executive sponsors, whosever life is impacted even by the remotest way whatsoever is a stakeholder. POs usually need to spend a lot of interacting with these stakeholders, in fact it forms a major chunk of their day to day life as a PO.</p><p>Unfortunately, companies tend to become ruled by hierarchies and rampant with politics and POs need too avoid pleasing people and focusing only on forwarding their own career rather than making customers happy ( the idealist that I am ) .</p><p><strong>Prioritization and Value</strong></p><p>A good Product Owner is someone who delivers VALUE , his/her every move is keeping the value in the center of all decisions . POs get a lot of requests from many stakeholders and prioritizing them is a challenge , however if they have their vision clear and aware of the value they can wade through this and do what is right at the point.</p><p>A common mistake is POs having a flurry of requirements in their backlog making it bloated and cluttered, an effective PO deletes unnecessary requirements and has a clear and concise backlog which reflect the long term vision. Also, agreeing to a requirement which is coming from a high ranking executive but has no added value as such just because you cannot say NO is a waste of resources.</p><p><strong>Technology and Analytics</strong></p><p>While a PO is not expected to code , it always helps to understand the basics of technology such as APIs, cloud, DevOps etc. This helps them communicate better with the technical teams and empathize on technological constraints. In the real world they would deal with lot of technical jargons and they should make an honest effort to understand them as learning is a life long journey.</p><p>Most companies think a good technical person will become a good Product Owner which is not true as POs need a different skill set to manage people without authority, and all the soft skills which come with it. And there are ample examples where non technical people have been greatly successful like in the case of Airbnb, Alibaba,etc.</p><p>While we deliver value its important to measure them going along and see the impact of our delivery time and again and readjust so analytics are key and a good PO keeps an eye on the data and inferences decisions from it.</p><p>While this is not an exhaustive list and the context of whether you are a B2B or a B2C PO, the industry and the stage of the company itself do matter a lot but these are some generic things which all Product owners have to do regardless of the above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d14fd99654b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>