<?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 Mughees on Medium]]></title>
        <description><![CDATA[Stories by Mughees on Medium]]></description>
        <link>https://medium.com/@mughees_22033?source=rss-5486b5fe4f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SkQHL3Y1l7omf7YK</url>
            <title>Stories by Mughees on Medium</title>
            <link>https://medium.com/@mughees_22033?source=rss-5486b5fe4f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:20:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mughees_22033/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[3 Tips How Product Managers Can Say No to Stakeholders]]></title>
            <link>https://medium.com/@mughees_22033/3-tips-how-product-managers-can-say-no-to-stakeholders-aebfeb49a97f?source=rss-5486b5fe4f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/aebfeb49a97f</guid>
            <category><![CDATA[client-relationship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saying-no]]></category>
            <dc:creator><![CDATA[Mughees]]></dc:creator>
            <pubDate>Mon, 20 Jun 2022 13:40:51 GMT</pubDate>
            <atom:updated>2022-06-20T13:40:51.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*xmYQrm9m-lUKs3yXKhCJDQ.jpeg" /></figure><p>Saying no is a firm part of our job as product managers and product owners trying to please everyone and taking on board every idea is hardly a recipe for achieving product success.</p><p>But saying no can be tough especially when we are facing a senior assertive stakeholder. In the following I&#39;ll share three tips to help you address this challenge.</p><p>Imagine that you’re talking to John, a senior sales person who’s been involved with the product for a while. John mentions the upcoming product release and says you really must add the enhanced reporting feature.</p><p>You know though that it is impossible to add the feature to the development effort the deaf team is struggling with the current workload and moving the date is not an option.</p><p>What’s more you suspect that John’s request may be motivated by the desire to meet his sales targets but John is a well-connected and influential individual who doesn’t like to be told that he is wrong.</p><p><strong>How can you decline his request without offending him and losing his support?</strong></p><h3>Tip number one</h3><p>Don’t feel bad about saying no, declining a request can be hard. You might not want to disappoint John to stay with the example. You might worry that saying no will anger him and lead to conflict or you might not want to be seen. But somebody who has a can-do attitude and wants to help saying no however is part and parcel of a product person’s job. If you said yes to every idea and request you would end up with a feature soup.</p><p>A product having a poor user experience and unlikeable value proposition. You must choose carefully, if you believe it would be hard for you to say no to John, this may suggest that you lack the necessary authority. You lack the authority and respect essential to be in control of the product. If this is the case, look into how you can improve your product leadership.</p><h3>Tip number two</h3><p><strong>E</strong>mpathize with the individual having decided that you can’t accept john’s request you might be tempted to share your view with the stakeholder and say for <strong>instance I&#39;m sorry john</strong> but there is no way that i can add the feature to the current release.</p><p>The development team is struggling to implement the features we’ve agreed to and I can’t really push out the dates. I’m sure you’ll understand this now.</p><p>This might seem like a reasonable answer. it’s direct and it offers an explanation but would it be effective now if john does not feel heard and understood it will be hard for him to accept not as an answer, no matter how valid your arguments are instead he might feel rejected and react with disappointment or anger. <strong>He might think that you don’t appreciate his views and don’t care about his needs consequently.</strong></p><p>He may no longer fully trust and support you to avoid this situation and maximize the chances that John can receive annoyance. <strong>I recommend that you empathize with the stakeholder before you offer an answer.</strong></p><p><strong>Find out first:</strong></p><ul><li>Why the feature is important to John</li><li>What is his personal vested interest in getting the feature included in the release.</li><li>Why does it matter to him so much?</li></ul><p>Only if john feels understood will he open up to your perspective listen to your arguments and accept that you can’t add the feature to the release the following three listening techniques will help you with this:</p><ul><li>First give the individual your full attention. Maintain eye contact and show the person that you are interested in what she or he has to say.</li><li>Second, keep an open mind even if you disagree with what you’re hearing or if you dislike the individual listening with the intention to understand not to answer. John might be right after all and you should add the feature to the release.</li><li>Third pay attention to the person’s body language non-verbal information like voice pitch gestures facial expressions they express the speaker’s feelings which help you uncover the individual’s underlying interests.</li><li>And finally ask clarifying and probing questions to check that you have correctly understood what was said and encourage the other person to provide more information you might say. For instance can you please help me understand why adding the feature is so important to you.</li></ul><h3>Tip number three</h3><p>This tip reframe the conversation stakeholders often request specific features without necessarily being fully aware of the problems that they address. But value is hardly created by adding a single piece of functionality at least as long as our product is young or changing so instead of debating an individual feature with john try and reframe the conversation explore which user or customer problem the functionality would help address how would implementing the feature benefits the customers and users and why do some customers viewed as crucial to stay with the example and would there be an alternative way to achieve the desired impact and additionally consider.</p><p>If the feature is aligned with the product goal of the current development effort the outcome you want to achieve that might be for example to enter a new market or increase engagement will address the user problem, help you meet this goal and create the desired outcome.</p><p>If the answer is yes then you should consider adapting the development efforts and you may decide to add the feature to the release assuming that you can make appropriate adjustments like reducing or removing other features or extending the delivery date but if the answer is no then you probably should.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aebfeb49a97f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>