<?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 Anand Daga on Medium]]></title>
        <description><![CDATA[Stories by Anand Daga on Medium]]></description>
        <link>https://medium.com/@ananddaga?source=rss-a2e026b6870d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*H64DsyOAZ9IPsOXz.</url>
            <title>Stories by Anand Daga on Medium</title>
            <link>https://medium.com/@ananddaga?source=rss-a2e026b6870d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:22:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ananddaga/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 is sunsetting software so difficult]]></title>
            <link>https://medium.com/@ananddaga/why-is-sunsetting-software-so-difficult-911181b090f2?source=rss-a2e026b6870d------2</link>
            <guid isPermaLink="false">https://medium.com/p/911181b090f2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Anand Daga]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 22:57:35 GMT</pubDate>
            <atom:updated>2017-09-15T02:01:52.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*h5_PKfrUTWPWjNCS498ZMQ.jpeg" /></figure><p>Software companies have gotten better in increasing their output (thanks to improved development processes) but obviously not all the deployed modules, screens and APIs go on to become winners. If a module has not caught on, the cost of actually keeping it ‘alive’ is likely higher than the cost of gracefully retiring it. However, most organizations do not have good processes to identify these underused features and remove them from the offering. In the best case scenario, the underused software only consumes minimal QA resources on an ongoing basis, and in the worst case, it becomes an impediment to the development of other competitive modules (either because of legacy hurdles it imposes, or due to it getting more and more intertwined with critical modules). The product management and engineering teams likely know about the bloat but the pressures to get another release out the door often pushes off any serious sunsetting / retirement discussion.</p><p><strong>Measure what needs to be removed</strong></p><p>To identify the bloat modules objectively and transparently, Product Management should (along with Engineering and Sales’ input) lead the initiative to establish the metrics that will be used to identify the modules to be sunsetted — for example if module revenue (or browser X usage) falls below x%, the department will start monitoring actively and if it falls below y%, the business will discontinue the module (the ‘start monitoring’ metric will help give sunsetting planning visibility to other departments in case they need to either take corrective action or inform clients — more like an early warning system). Metrics should be in the usual areas of revenue (LTV, MRR, penalty, etc.), volume/usage (% of targeted users actually using it), legal implications (generally a binary value, with possibly a financial implication). The metrics and the thresholds may need to be adjusted by product or business line. In some cases, PM may need to get a final sign-off from either executive management or a few specific clients (generally depending on the enterprise value of that client).</p><p><strong>Dedicate development budget for addressing the bloat</strong></p><p>Product Management and Engineering teams should proactively dedicate a small portion of their development budgets for addressing the bloat (call it whatever may work for your organization — “Technical debt handling”, “Operations issues handling”, “Performance optimization”). The budget does not have to be spent evenly across the year — it could be concentrated in a single release every year, or spread in different amounts per release. The point is the process should be institutionalized and agreed upon with management so that the difficult decision is not put off forever, or that management does not express surpise when it comes time to pay this portion of the bill.</p><p><strong>Dos and don’ts</strong></p><p><em>Communicate to internal groups and clients</em></p><p>Once the sunsetting candidates have been identified, PM (along with Marketing) should communicate the following:</p><p>· Timeline for retirement</p><p>· How will data (collected through those modules) be handled (archived / given back to the client)</p><p>· How can users substitute for the functionality (if needed, PMs should be willing to guide clients towards 3rd-party sources in case they offer solutions for the sunsetted modules)</p><p>· Compliance implications (if any)</p><p><em>Conduct a webinar</em></p><p>· The PM team may also want to do a webinar specifically to address each of above issues proactively. The only thing worse than not retiring something is to retire it and then have an important client make the inconvenient call up the executive chain.</p><p><em>Monitor Support calls post deployment</em></p><p>· Once the release has been deployed, PM should work closely with Support to monitor the client calls to proactively identify any major negative impacts</p><p><em>Check dependencies on other groups</em></p><p>· Ensure that Ops / Finance has removed the sales related line item for the module (if individually sold), Marketing has removed references from collaterals and that Help team has updated all printed / online help materials.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=911181b090f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should SaaS companies perform partnership diligence and execution differently?]]></title>
            <link>https://medium.com/@ananddaga/should-saas-companies-perform-partnership-diligence-and-execution-differently-ebeb2df19b88?source=rss-a2e026b6870d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebeb2df19b88</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[channel-partners]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Anand Daga]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 02:11:20 GMT</pubDate>
            <atom:updated>2017-09-12T01:37:02.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*2N1-MQWxsSkjwFJknfsuaw.jpeg" /></figure><p>SaaS companies, known for their open architectures, scalable platforms and fast time-to-market, may find the traditional model of extensive upfront partnership diligence (with comprehensive joint financial analysis and projections, exhaustive use case and support scenario analysis, and comprehensive marketing messaging prep) impeding and expensive. SaaS companies may require a higher number of partners, or different partners for different reasons. Many of these companies have a few inherent structural (for the most part) advantages which allows them to get into alliances without investing significantly upfront while simultaneously increasing the chances of getting the finished joint “product” right.</p><p><strong>Paypal and its winning partnership with credit-card companies</strong></p><p>First, let us take the <a href="http://www.barrons.com/articles/paypal-ceo-moving-money-shouldnt-be-so-hard-1502479845">Paypal case study</a> (credit — Barron’s). Paypal has generally encouraged clients to fund their accounts using their bank accounts rather than credit cards (better financial terms on bank account funds). However, they also knew that many clients prefer using their credit cards. Paypal decided to test the results of clients who could more intuitively pay using their credit cards (they have long allowed clients to use both, but making bank accounts more appealing). While the clients expectedly chose the credit card option more, but they also increased their Paypal-based transactions. Increased transaction volumes have offset the increased credit card fees. Paypal’s stock has been on a tear on Wall Street.</p><p>Could Paypal have pulled off the same if it had followed the traditional partnership diligence methods? Maybe, or maybe not. But the point here is that it was able to improve its alliance results more innovatively and expeditiously.</p><p><strong>The inherent structural advantages</strong></p><p>SaaS and modern companies have the following advantages in general:</p><ol><li><em>Open technical architectures and well-defined APIs</em>: Companies that have well-defined APIs can create inter-system integrations with minimal configuration and without requiring significant technical resources. As a lot of modern partnerships are dependent on integrations, companies with well-defined APIs likely enjoy a strategic competitive advantage over others (and even the ones that do not have well-defined integration points can likely use middleware software such as<a href="https://www.actian.com/data-integration/dataconnect-integration/"> Actian’s DataConnect</a>, which ease the integration burden and costs).</li><li><em>Use of Lean Startup (or similar) methodologies</em>: Many modern companies already use Lean Startup methodology and they can apply these techniques to alliances — rolling out skinny “partnership MVPs” (minimal integration points, limited functionality and deployed to a few users). Once the targeted clients validate the first iteration, the partners can refine their product further.</li><li><em>Conduct A/B testing</em>: As an extension to the Lean Startup point above, partners can both perform basic A/B testing to validate their joint assumptions (for e.g. did users who were able to pay with a credit card use their accounts more compared to the ones who could use their debit cards).</li></ol><p><strong>Takeaways</strong></p><p>If your company has the advantage of some or all of the structural tenets outlined above, then you may be better off treating a partnership like any other MVP project — define a small partnership sliver, develop it with minimal resources and roll it out to your choice clients. Leverage their input to refine the assumptions. Further, it may be better to get more engagement from your technical staff rather than the corporate types (pricing, marketing, etc.) — get them involved only after the basic partnership assumptions have been validated. Lastly, if you do not already, make APIs and integration points a critical development goal rather than an after-thought. It will likely pay for itself by expediting partnerships at some later stage.</p><p><strong>PS</strong>: I have used Actian DataConnect at a previous employer (to connect a SaaS-based tax product with SAP and Oracle ERPs) though there are several such commercial offerings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebeb2df19b88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The death of the local bike shop]]></title>
            <link>https://medium.com/@ananddaga/how-does-a-small-business-compete-in-the-age-of-amazon-d7a680676846?source=rss-a2e026b6870d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a680676846</guid>
            <category><![CDATA[retail]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[lead-generation]]></category>
            <category><![CDATA[cycling]]></category>
            <dc:creator><![CDATA[Anand Daga]]></dc:creator>
            <pubDate>Sun, 10 Sep 2017 15:34:52 GMT</pubDate>
            <atom:updated>2017-09-11T19:09:35.862Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Yacdkg5HmnqcZwdOVGNvug.jpeg" /></figure><p>This weekend, at the local bike shop, I was surprised to see a prominent “Amazon bike pick-up” sign inside. My first thought — the bike shop is losing sales and turning into an outlet to assemble bikes bought online. Buying a bike without a test-ride and the associated tactile satisfaction is not my idea of progress. So, I was piqued to learn more about this unlikely partnership — what I learned however, was exactly the opposite of what I was expecting.</p><p>Peter, the owner, explained that Amazon had genuinely been a boon for his small business. Many online buyers are busy parents getting bikes for their kids, or young professionals getting their first bike. Without Amazon, they would never have known about Peter’s store. Once they step in to collect their bike, his sole goal is to win their business over the long-term. He has made critical operational changes to his service model — new subscription-style maintenance plans, complementary safety &amp; ergonomics review, and increased high-end bikes inventory. On the back-end, Peter’s created better systems to capture and mine client profile data. The net result — an increasing number of those clients end up buying accessories not originally planned for, and many of them come back to buy premium or specialized bikes as they outgrow their online bought one.</p><p>Only time will tell how long Peter’s personalized service, data-mining, and relationship building will sustain his bike shop. But, it is heartening to see that even as brick-and-mortar obituaries are being written, small retailers are innovating, and are able to harness Amazon to create a mutually beneficial relationship. Peter could have very well channeled Twain — “<em>The reports of my bike shop’s death are greatly exaggerated</em>.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a680676846" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To create product longevity, focus more on moat-building than on innovation]]></title>
            <link>https://medium.com/@ananddaga/to-create-product-longevity-focus-more-on-moat-building-than-on-innovation-c40f063729a3?source=rss-a2e026b6870d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c40f063729a3</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Anand Daga]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 18:19:15 GMT</pubDate>
            <atom:updated>2017-09-08T00:20:29.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/453/1*9X9BgkmMJPZj0pXJZ48E9A.jpeg" /></figure><p>Moats have been used to protect assets since the old Egyptian and Babylonian eras. Successive cultures — Asians, Africans and Europeans — have all used it at some time in their history, either for defensive or agricultural reasons. In each case, two moat attributes mattered more than anything else — depth and width. A modern-day Product Manager can leverage these thoughts to protect their key asset (the product) against competition and market forces.</p><p><strong>Innovation Temptation</strong></p><p>Deploying a new mobile app or incorporating a natural-language based bot into a product is tempting for a product manager. Building an “innovative” new feature addresses a PM’s intellectual curiosity, enables great internal roadmap decks and glossy external Marketing communications. However, when it comes to enhancing a product’s long-term sustainability and market differentiation, PMs — similar to our forefathers — may be better served by focusing on the more tactical aspect of moat-building.</p><p><strong>Innovation is product-centric, moat-building is user-centric</strong></p><p>When a Product Manager asks questions such as “How could I differentiate my <em>product</em> from the competitors’?” “How can I incorporate the latest technology (into the <em>product)</em>?”, “What are the latest technological trends?”, they are focusing on product innovation. These questions may lead to ideas such as mobile app, bot development, natural language based interfaces, etc. Most of these must be good ideas in the context of the product they are being planned for, but it is also possible that the use cases may not be well-defined or simply ahead of its time, the payback may be distant and the risk-reward balance itself may be skewed.</p><p>Moat-building on the other hand happens slowly and often mundanely as the natural outcome of when a Product Manager asks questions such as “What would improve <em>User </em>X’s online experience?”, “How could we make it easier for <em>User</em> Z to import and mine data on our platform?”, “How can we enable <em>Users</em> M and N to collaborate seamlessly?”. Questions like these lead to the development of features that are more user-friendly and in-synch with the user’s actual workflow (both within computer systems as well as manual workflows). They are geared to address a user’s real pain points. And obviously, the more user and process friendly a system is, the more a user will be inclined to use it, the more data they will enter into it, the more they will collaborate on that platform, the more they will tell peers about it … you get the drift. These basic and daily actions will eventually lead to a deeper and broader product moat.</p><p><strong>A synergistic pair</strong></p><p>This article does not mean to imply that innovation is not important. Far from it. Innovation and moat-building really go hand-in-hand. But to really innovate, you have to focus on the basic blocking and tackling first. Only if you have a great product that users actually love and use regularly would it make sense to introduce a bot feature within a mobile app. Done wrong, they would be a vanity project at best, and may lead to expensive opportunity costs at worst. Done right, innovation would be building blocks that further extend the moat.</p><p>PS: <a href="http://twistedsifter.com/2011/05/impressive-moats-around-the-world/">20 impressive moats around the world</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c40f063729a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>