<?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 Shashant Jasani on Medium]]></title>
        <description><![CDATA[Stories by Shashant Jasani on Medium]]></description>
        <link>https://medium.com/@shashant?source=rss-d6469d0605b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4xkuG41n-JWox0Ej1U_pfw.jpeg</url>
            <title>Stories by Shashant Jasani on Medium</title>
            <link>https://medium.com/@shashant?source=rss-d6469d0605b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:47:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shashant/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[Why Product Managers shouldn’t use credit cards?]]></title>
            <link>https://medium.com/@shashant/why-product-managers-shouldnt-use-credit-cards-578f552be2fa?source=rss-d6469d0605b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/578f552be2fa</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Shashant Jasani]]></dc:creator>
            <pubDate>Fri, 14 Apr 2017 17:34:48 GMT</pubDate>
            <atom:updated>2017-04-26T06:41:54.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*Z6zNHWO1vjGPURXGzD4fog.png" /></figure><p>We’ve all been there; we’ve had our eye on something we really can’t afford but we purchase it by putting the charge on one or many credit cards. We satisfy our initial desire, feeling the elation of what that something brings, but soon after it is countered with the stress caused by paying off the balance.</p><p>Feature enhancements are often obtained in a similar manner for product managers. The urgency to deliver a new, exciting feature is generally fueled by a customer demand or a strategic initiative, regardless of the motivating factors.<br>Thus, we as product managers frequently push for the quickest path to elation and backlog the stress. The joy of shipping that highly desired feature as soon as possible overshadows the technical and product debt that is potentially incurred. <br>Such debt may inhibit the ability to evolve the feature, hamstringing us to known limitations and potentially spawn additional &amp; unforeseen consequences.</p><p>The message here isn’t to scare us from taking chances or to shun against moving fast. We build products and features in an agile world and there are already tools and processes in place to help us navigate around risk and errors.<br>The message here is to sometimes exercise patience and while doing so, we put ourselves in a much better position to afford that product feature.</p><h3><strong>What does it mean to save up for a Product Feature?</strong></h3><p>While we save up for something we want to buy, a few things naturally happen:</p><p><strong><em>Reinforce our need for it</em></strong><br>When the need is recognized, the effort to achieve it tends to be consistent and relentless.</p><p>The goal here is to gather the team and build a common understanding of the need. This can be achieved by simple team exercises, review of comparable competitor implementations and/or first-hand experience of the problem(s) that this feature will solve for. <br>And just as much as we would like to reinforce the need, we may actually even end up realizing the lack of need for it, causing it to be no longer desired.</p><p><strong><em>Perform research and justification</em></strong><br>Whenever we are going to spend a considerable amount of time &amp; energy on something, we tend to seek out best practices, lessons learned and validation.</p><p>The goal here is to allow the team to wrap their minds around what we are building and how best we can build it given our means. As much as we would like to think of ourselves as a know-it-all, given a little bit of time for research, we are not only more educated but also more confident.</p><p><strong><em>Prepare to maintain it</em></strong><br>When large purchases are made, they rarely come without maintenance costs. As we are saving up to purchase that something itself, we are also preparing ourselves for the additional cost it comes with to keeping it functional.</p><p>For example:</p><blockquote>Adding a pool to your home, comes with the cost to first building that pool but then it follows with the cost of increased water use, increased energy use and of course periodical cleaning services.</blockquote><p>The goal here is to understand how our world may change before we actually build that something. Are we going to create processes in our day to day that did not exist before? Are we going to overload our current systems and hardware? Are we using the appropriate architecture to allow for this feature to grow? <br>As an added bonus, we may actually even enhance the scope of the initiative to include the shoring up, allowing for a more stable and successful feature enhancement.</p><p>I am a big believer in failing fast, allowing me to quickly course correct. But that does NOT mean I am okay to drive blind. <br>By reserving the adequate time to build alignment, approach and understanding, we enable for a smooth experience, for both our team and our users.</p><p>Just as it’s easy to buy things with a credit card without the actual means to be able to pay it off, we can unfortunately queue up improperly planned features and cause our team to deflate momentum and velocity. <br>Unforeseen debt can lower your quality of life, the same can happen with product features. The unforeseen technical debt and bugs can lower the quality of your product. <br>Paying off credit card debt isn’t easy and requires discipline. Such discipline can sometimes require you to forgo fun activities and stick to the basics. The same can surely happen with paying off the debt for a feature that wasn’t properly planned for. Your backlog becomes littered with more bugs and technical tasks, only geared to course correct a poorly planned feature. Instead of spending time on continuously elevating your product, you end up spending time fixing the multitude of issues introduced.</p><p>So, as responsible Product Managers, be mindful and disciplined when it comes to urgency of feature requests. Build up the necessary savings so you can spend wisely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=578f552be2fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>