<?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 Deepak Deolalikar (B2B SAAS PM) on Medium]]></title>
        <description><![CDATA[Stories by Deepak Deolalikar (B2B SAAS PM) on Medium]]></description>
        <link>https://medium.com/@deepak.deolalikar?source=rss-524d3c775f17------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1UjYQH5QGmMCHR9irVf7lA.jpeg</url>
            <title>Stories by Deepak Deolalikar (B2B SAAS PM) on Medium</title>
            <link>https://medium.com/@deepak.deolalikar?source=rss-524d3c775f17------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:12:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deepak.deolalikar/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[Value Proposition vs Positioning]]></title>
            <link>https://medium.com/design-bootcamp/value-proposition-vs-positioning-ee07119d7d4b?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee07119d7d4b</guid>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 19:00:12 GMT</pubDate>
            <atom:updated>2025-08-05T21:36:44.806Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, during a product strategy class session, someone raised a question:</p><p>“What’s the difference between value proposition and positioning?</p><p>Are they not the same?</p><p>Why not just use value proposition?”</p><p>It’s a good question that gets to the heart of go-to-market strategy. While these terms are often used interchangeably, they serve distinct purposes. Getting this distinction right can mean the difference between resonating with your market and getting lost in the noise.</p><p>If I say the name “Tom Cruise”. What do you think of? <br>Action Hero. <br>That is positioning.</p><p>There are two fundamental truths in marketing that everyone should know:</p><p><strong>1. There is a lot of noise.</strong></p><p>Too many players, Conflicting messages.</p><p>Try searching for a CRM software. You will be bewildered. And I was a PM in a CRM company. A few months ago, I was at the RSAC conference in San Francisco. There were about 1000 vendors booths. All selling Cybersecurity solutions. For the life of me, I could not distinguish one booth from the the other. Same words. Same language. “we help secure your enterprise from bad actors”</p><p><strong>2. People think in boxes.</strong></p><p>I learnt about this in the classic book “Positioning” by Jack Trout. Highly recommended. <br>He says that people have compartments for everything.</p><p>Founders will get this. When you explain your product to an investor, they sometimes retort back “oh, so your like X”. <br>That’s boxing.</p><p>They want to place you in a box. <br>No matter how hard you try to say “No, No, we are different”.</p><p>But the reality is, for a human mind it is easier to comprehend something that fits a box that already exists vs creating a new box for them. It’s OK to be in a box. It gives you the opportunity to truly differentiate. It’s easier to differentiate in a box than to create a new box in the minds of people.</p><h3>A Simple Analogy: Coffee Shops</h3><p>Before diving into B2B examples, let’s start with something everyone understands: your local coffee scene.</p><p><strong>Starbucks Value Proposition:</strong> “The perfect coffee experience, wherever you are that reminds you of cafe in Europe where you can have the best coffee, relax and connect with friends.” (consistent quality and convenience)</p><p><strong>Starbucks Positioning:</strong> “The premium coffee chain” (positioned above fast-food coffee, below artisanal coffee shops) or “Get the European cafe experience”</p><p>When someone sees that European reference, it evokes visuals or memories of their own cafe experiences in say Paris or Vienna. They don’t talk about the great coffee yet. Thats positioning. Once you are in that box, now you can compare the coffee types or ingredients etc.</p><p><strong>Local Artisan Coffee Shop Value Proposition:</strong> “Discover exceptional single-origin coffee crafted by expert roasters, using organic material sourced from ethical practices in 3rd world countries” (superior taste and craftsmanship)</p><p><strong>Local Artisan Coffee Shop Positioning:</strong> “The authentic alternative to corporate coffee” (positioned against chains like Starbucks)</p><p>See the term “corporate coffee”. What does that evoke in you?</p><p>Bland, boring, cookie cutter. So the local coffee shop is positioning against all that and give you a real authentic coffee experience. That’s positioning.</p><h3>What Is a Value Proposition?</h3><p>Your value proposition is the promise of value you deliver to customers. It’s the specific benefit or outcome your product creates, articulated in terms your customers care about.</p><p>A strong value proposition answers: <em>“What valuable outcome will customers achieve by using our product?”</em></p><h3>Value Proposition Examples:</h3><p><strong>Slack:</strong> “Slack is where work flows. It’s where the people you need, the information you share, and the tools you use come together to get things done.”</p><p><strong>Salesforce:</strong> “Grow your business faster with the world’s #1 CRM.”</p><p><strong>Zoom:</strong> “Video communications empowering people to accomplish more.”</p><p>Notice how each focuses on the customer outcome — improved workflow, business growth, or enhanced productivity.</p><h3>What Is Positioning?</h3><p>Positioning is how you want your product to be perceived relative to alternatives in the customer’s mind. It’s about claiming a specific spot in the competitive landscape and in your buyer’s mental framework. Remember the box.</p><p>Positioning answers: <em>“How should customers think about us compared to other options?”</em></p><h3>Positioning Examples:</h3><p><strong>Monday.com:</strong> “The work OS that lets you shape workflows, your way” (positioned against rigid project management tools)</p><p><strong>Notion:</strong> “One workspace. Every team.” (positioned as the all-in-one alternative to fragmented productivity tools)</p><p><strong>Airtable:</strong> “Part spreadsheet, part database, and entirely flexible” (positioned between Excel and complex databases)</p><p>Salesforce: “No Software”</p><p>Each claims a unique space relative to existing categories and competitors.</p><h3>When to Use Each</h3><h3>Lead with Value Proposition When:</h3><ul><li><strong>Launching new products</strong> where you need to establish clear customer value</li><li><strong>Creating marketing copy</strong> for landing pages, ads, or sales materials</li><li><strong>Training sales teams</strong> on how to articulate customer benefits</li><li><strong>Conducting customer interviews</strong> to validate problem-solution fit</li><li><strong>Developing pricing strategy</strong> around delivered value</li></ul><h3>Lead with Positioning When:</h3><ul><li><strong>Entering crowded markets</strong> where differentiation is critical</li><li><strong>Competing against established players</strong> and need to carve out unique space</li><li><strong>Messaging to analysts and press</strong> who need to categorize your solution</li><li><strong>Building brand strategy</strong> for long-term market presence</li><li><strong>Fundraising conversations</strong> where investors need to understand your competitive moat</li></ul><h3>How They Work Together</h3><p>The magic happens when value proposition and positioning reinforce each other. Your positioning should make your value proposition more credible and compelling.</p><p><strong>Example: Figma</strong></p><ul><li><strong>Value Proposition:</strong> “Build better products as a team” (collaborative design outcome)</li><li><strong>Positioning:</strong> “The collaborative interface design tool” (positioned against single-user design tools like Sketch)</li></ul><p>The positioning (collaborative) directly supports the value proposition (team-based product building).</p><h3>Common Mistakes to Avoid</h3><p><strong>Mistake #1: Making them too similar</strong> Your value prop shouldn’t just restate your positioning. “We’re the leading CRM” (positioning) vs. “Increase sales by 30%” (value proposition).</p><p><strong>Mistake #2: Positioning without substance</strong> Claiming to be “innovative” or “best-in-class” without clear differentiation from alternatives.</p><p><strong>Mistake #3: Value prop without proof</strong> Promising outcomes you can’t deliver or measure.</p><p><strong>Mistake #4: Ignoring the customer’s frame of reference</strong> Your positioning means nothing if customers don’t understand the category you’re positioning against.</p><h3>Practical Next Steps</h3><p>I am not an expert on positioning and highly recommend you follow people like April Dunford and Anthony Pierri.</p><p>But at a high level.</p><ol><li><strong>Audit your current messaging:</strong> Can you clearly distinguish your value proposition from your positioning?</li><li><strong>Map your competitive landscape:</strong> What alternatives do customers consider? How do you want to be different?</li><li><strong>Interview recent customers:</strong> What outcomes did they achieve? How do they describe you to others?</li><li><strong>Test both independently:</strong> Does your value proposition resonate even without competitive context? Does your positioning make sense to someone unfamiliar with your product?</li><li><strong>Align your team:</strong> Ensure everyone from product to sales understands both and when to use each.</li></ol><p>The companies that win in B2B don’t just have great products — they have crystal-clear value propositions that resonate with customers and sharp positioning that cuts through market noise. Master both, and you’ll find your go-to-market strategy becomes significantly more effective.</p><p>Positioning and value proposition definitions are all part of a PM job. Don’t relate that to marketing. Yes, they may work on the copy, language, style but you have to work with them to determine how you position your product vis a vis the competition and the customer mindset.</p><p>Positioning opens doors. <br>Value Prop opens wallets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee07119d7d4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/value-proposition-vs-positioning-ee07119d7d4b">Value Proposition vs Positioning</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Vitamins and Painkillers: The 4-Layer Product Urgency Spectrum]]></title>
            <link>https://medium.com/design-bootcamp/beyond-vitamins-and-painkillers-the-4-layer-product-urgency-spectrum-e7aa4dcd26a5?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7aa4dcd26a5</guid>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 21:46:45 GMT</pubDate>
            <atom:updated>2025-07-29T22:05:47.076Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Build Your GTM Strategy Around the Product Urgency Spectrum</h3><p>The “vitamin vs painkiller” framework has become gospel in product management circles. The conventional wisdom is simple: build painkillers, not vitamins. Painkillers solve urgent problems that people will pay for immediately, while vitamins are nice-to-have supplements that are easily skipped.</p><p>But this binary thinking is dangerously oversimplified. In reality, customer problems exist on a spectrum of urgency, and understanding exactly where your product sits on this spectrum is crucial for determining your go-to-market strategy, sales approach, and messaging.</p><p>Let me propose a more nuanced framework with four distinct layers of problem urgency, each requiring fundamentally different product and business strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IdFf6UbfR6YcDPOWcTw4Mw.png" /></figure><h3>Layer 1: Chemotherapy — Existential Urgency</h3><p>At the most extreme end of the spectrum are problems that threaten the very existence of a business or individual. Like chemotherapy for cancer patients, these solutions address do-or-die situations where failure to act means catastrophic consequences.</p><p><strong>Characteristics:</strong></p><ul><li>Immediate, existential threat</li><li>Price sensitivity is minimal</li><li>Competitive comparison is secondary to speed and effectiveness</li><li>Decision-making is centralized and fast</li><li>Customer will pay almost any price for a solution</li></ul><p><strong>Examples:</strong></p><ul><li><strong>Cybersecurity incident response:</strong> When a company discovers a data breach, they need immediate help. They’re not comparison shopping — they’re calling the first reputable security firm they can find.</li><li><strong>Legal crisis management:</strong> A company facing a regulatory investigation or lawsuit needs legal counsel immediately. They’re not negotiating hourly rates.</li><li><strong>System recovery solutions:</strong> When a company’s core systems go down, they need restoration services now. Downtime costs exponentially more than any recovery solution.</li><li><strong>Emergency funding:</strong> A cash-strapped startup facing payroll in 48 hours will take funding at almost any terms.</li></ul><p><strong>Product Strategy Implications:</strong></p><ul><li>Focus on availability and speed of deployment over feature richness</li><li>Premium pricing is not only acceptable but expected</li><li>Sales cycles are measured in hours or days, not weeks</li><li>Word-of-mouth and reputation are your primary marketing channels</li><li>Customer success means preventing the catastrophic outcome, not optimizing for efficiency</li></ul><h3>Layer 2: Painkiller — High Urgency with Options</h3><p>Traditional painkillers represent problems that are urgent and painful but not existential. Customers actively seek solutions and are willing to pay, but they have the luxury of comparison shopping and test alternatives. e.g. Blood pressure medication (unless life threatening). If you skip a day, you likely will not die. And you can shop which brand/ does combination is best for you.</p><p><strong>Characteristics:</strong></p><ul><li>Clear, immediate pain point</li><li>Customers actively seek solutions</li><li>Price-sensitive but willing to pay for quality</li><li>Competitive evaluation is important</li><li>Few customers may delay or avoid treatment</li></ul><p><strong>Examples:</strong></p><ul><li><strong>Recruiting software:</strong> Growing companies need to hire quickly, but they’ll evaluate multiple ATS solutions before deciding.</li><li><strong>Expense management tools:</strong> Finance teams hate manual expense reporting, but they’ll demo several solutions to find the best fit.</li><li><strong>Customer support platforms:</strong> Bad customer service hurts business, but companies will compare Zendesk, Intercom, and others before choosing.</li><li><strong>Accounting software:</strong> Small businesses need bookkeeping help, but they’ll evaluate QuickBooks, Xero, and FreshBooks first.</li></ul><p><strong>Product Strategy Implications:</strong></p><ul><li>Strong competitive differentiation is crucial</li><li>Free trials and demos are essential for evaluation</li><li>Sales cycles are moderate (weeks to months)</li><li>Content marketing and comparison content perform well</li><li>Customer success focuses on immediate pain relief and quick time-to-value</li></ul><h3>Layer 3: Cough Syrup — Moderate Urgency, Specific Needs</h3><p>Cough syrup problems are annoying and persistent but not debilitating. Customers want solutions but can be selective about timing and specific features. They might even wait to see if the problem resolves itself. Or maybe just sip warm water at home. Unless the degree of cough is really bad, in which case it might in #2 above.</p><p><strong>Characteristics:</strong></p><ul><li>Persistent irritation or inefficiency</li><li>Customers can be specific about requirements</li><li>Price-conscious comparison shopping</li><li>Easy to postpone or work around but not for long</li><li>Feature fit is more important than speed</li><li>Clear ROI to justify is needed</li></ul><p><strong>Examples:</strong></p><ul><li><strong>Marketing automation tools:</strong> Marketing teams want to automate campaigns but can survive with manual processes while they evaluate options.</li><li><strong>Design collaboration software:</strong> Design teams want better collaboration but can continue using email and Slack while finding the right tool.</li><li><strong>Time tracking applications:</strong> Consultants know they should track time better but can continue with spreadsheets while shopping for the perfect solution.</li><li><strong>Social media management platforms:</strong> Social media managers want efficiency but can manually post while evaluating Buffer, Hootsuite, and others.</li></ul><p><strong>Product Strategy Implications:</strong></p><ul><li>Detailed feature comparison and customization options are important</li><li>Longer sales cycles (months) as customers take time to evaluate</li><li>Free tiers or extended trials help customers test fit</li><li>SEO and content marketing are crucial for discovery</li><li>Customer success focuses on workflow optimization and feature adoption (coughs generally takes weeks to resolve)</li></ul><h3>Layer 4: Vitamin — Long-term Hygiene, Easy to Skip</h3><p>Vitamins represent long-term improvements or preventive measures. Customers understand the theoretical benefit but feel no immediate urgency. These are the easiest solutions to postpone indefinitely.</p><p><strong>Characteristics:</strong></p><ul><li>Long-term benefits without immediate pain</li><li>Very easy to skip or delay</li><li>Extensive research and comparison</li><li>High churn risk</li><li>Requires education and habit formation</li></ul><p><strong>Examples:</strong></p><ul><li><strong>Analytics and reporting tools:</strong> Companies know they should make more data-driven decisions but can continue with gut feelings and basic reports.</li><li><strong>Employee wellness programs:</strong> HR knows wellness is important but can postpone implementation indefinitely.</li><li><strong>Backup and disaster recovery:</strong> IT teams know they should have better backups but often delay until after a crisis, at which point they fall into #1 or #2.</li><li><strong>Learning management systems:</strong> Companies want to upskill employees but training often gets deprioritized.</li></ul><p><strong>Product Strategy Implications:</strong></p><ul><li>Heavy investment in education and content marketing</li><li>Long sales cycles (6+ months) with multiple touchpoints</li><li>Strong onboarding and engagement strategies to prevent churn</li><li>ROI calculators and case success stories are essential</li><li>Customer success focuses on habit formation and proving long-term value</li></ul><h3>Strategic Implications for Product Managers</h3><p>Understanding where your product sits on this urgency spectrum fundamentally changes how you should approach product development and go-to-market strategy:</p><p><strong>For Chemotherapy products:</strong> Build for reliability and speed, not feature richness. Invest in customer success and incident response. Price for value, not market rates.</p><p><strong>For Painkiller products:</strong> Focus on competitive differentiation and clear value propositions. Invest in sales enablement and comparison content. Balance features with usability.</p><p><strong>For Cough Syrup products:</strong> Emphasize flexibility and customization. Invest in content marketing and SEO. Build comprehensive trial experiences.</p><p><strong>For Vitamin products:</strong> Lead with education and long-term value propositions. Invest heavily in onboarding and engagement. Build strong communities and user habits.</p><p>The key insight is that there’s no universal “right” strategy — only the right strategy for your specific position on the urgency spectrum. A chemotherapy approach won’t work for vitamin problems, and a vitamin approach will fail for chemotherapy problems.</p><p>Before you design your next product roadmap or launch strategy, ask yourself: Are you building chemotherapy, a painkiller, cough syrup, or a vitamin?</p><p>Your answer should reshape everything from your pricing model to your sales process to your success metrics.</p><p>The most successful product managers don’t just build great products — they build great products with strategies perfectly matched to their position on the urgency spectrum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7aa4dcd26a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-vitamins-and-painkillers-the-4-layer-product-urgency-spectrum-e7aa4dcd26a5">Beyond Vitamins and Painkillers: The 4-Layer Product Urgency Spectrum</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art and Science of Product Management]]></title>
            <link>https://medium.com/@deepak.deolalikar/the-art-and-science-of-product-management-22f84fcc735d?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/22f84fcc735d</guid>
            <category><![CDATA[product-success]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Wed, 02 Jul 2025 04:27:49 GMT</pubDate>
            <atom:updated>2025-07-02T04:27:49.046Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Art and Science of Product Management</strong></p><p>Recently I was in a prospect discussion who wanted to give Ziply a try. I was excited to showcase the features and how they might be able to benefit.</p><p>I thought I had done my part. Then the customer shared some concerns.</p><p>For context, Ziply helps amplify social content organically via employees, executives, channel partners and influencers to get more reach and generate warmer conversations.</p><p>Creating content is client responsibility.</p><p>So I thought.</p><p>He went to explain their main concern. That their content does not have a wow factor. I am thinking thats not part of my tool. But then I realized without great content, Ziply’s value proposition is meagre.</p><p>For comparison, think of an AI powered video maker. You can use it to create videos but will the video be WOW!</p><p>That is a function of your creativity and your prompts.</p><p><strong>The art and science of products</strong></p><p>When we talk about building great products, we often focus on <em>how</em> they work — the features, the tech stack, the UX. That’s the <strong>science</strong> of product management.</p><p>But when I came home after the meeting, I realized equally important, and often overlooked, is the A<strong>rt</strong>: how people actually use your product to solve real problems.</p><p>Both matter.</p><p>But they require different mindsets, different skills, and different approaches to customer success.</p><p>Now you may ask, if you train them how to use the product, then it should be fine.</p><p>Have you bought an Instant Pot? It comes with two booklets.</p><ul><li>The user manual. The Science.</li><li>The recipe book. How best to use it. The Art.</li></ul><p>I can be adept at setting the temperature and the timing of the Instant Pot. Whats the point if I don’t know what to make or how to make. But they help with the art of the possible.</p><h3>The Science: Building the Tool</h3><p>This is the obvious part — the technical foundation that product managers spend most of their time on.</p><ul><li>How does the product integrate with other systems?</li><li>How do users sign up, onboard, and start using it?</li><li>Is the interface intuitive?</li><li>Are the features robust and reliable?</li><li>Does it scale under load?</li><li>Can we maintain and iterate on it efficiently?</li></ul><p>Take Calendly as an example. The science is in building scheduling functionality — syncing with calendars, managing time zones, handling rescheduling logic, sending automated reminders, managing buffer times between meetings. If that doesn’t work, nothing else matters.</p><p>But here’s the thing: <strong>getting the science right is table stakes</strong>. It’s necessary but not sufficient for product success.</p><h3>The Art: Helping People Use It Well</h3><p>Here’s where the real leverage comes in. Once the tool <em>works</em>, the next question is: <em>How should people actually use it to get the most value?</em></p><p>That’s the art and it’s where most products leave massive value on the table.</p><h3>The Spectrum: From Tools to Transformation</h3><p>The most successful products exist on a spectrum. On one end, you have pure tools. On the other, you have transformation platforms that fundamentally change how people work.</p><p><strong>Pure Tools</strong> (Science-Heavy):</p><ul><li>GitHub (version control)</li><li>Stripe (payments)</li><li>AWS (infrastructure)</li></ul><p>These focus primarily on robust functionality. Users are often technical and willing to figure out implementation details.</p><p><strong>Transformation Platforms</strong> (Art-Heavy):</p><ul><li>Salesforce (sales transformation)</li><li>Shopify (e-commerce transformation)</li><li>HubSpot (marketing transformation)</li></ul><p>These don’t just provide features — they provide methodologies, best practices, and entire business frameworks.</p><p>Most successful B2B products fall somewhere in the middle, but the trend is clear: <strong>the art is becoming increasingly important as a differentiator</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zknsa7qygJNrSZfGSx0HOA.png" /><figcaption>The Art and Science of building great products</figcaption></figure><p>Let’s look at some more examples.</p><h3>Notion: From Tool to Operating System</h3><p>Notion is a powerful tool for notes, wikis, databases, and more.</p><p><strong>The science:</strong></p><ul><li>Rich text editing</li><li>Relational databases</li><li>Real-time collaboration</li><li>API integrations</li><li>Mobile synchronization</li></ul><p><strong>The art:</strong></p><ul><li>Use case templates (product roadmap, CRM, meeting notes, OKR tracking)</li><li>Community-shared workflows (second brains, team hubs, company wikis)</li><li>Examples from real companies (how Pixar uses Notion, startup operating systems)</li><li>Certification programs for “Notion consultants”</li><li>Regular showcases of power users and their setups</li></ul><p>It’s one thing to <em>know</em> how to use Notion. It’s another to use it to run your entire company from a single app.</p><h3>Slack: Beyond Messaging</h3><p><strong>The science:</strong> Real-time messaging, file sharing, integrations, search.</p><p><strong>The art:</strong> Channel organization strategies, meeting reduction frameworks, asynchronous communication best practices, workflow automation examples, remote team culture building.</p><p>Slack doesn’t just enable team communication — it teaches teams <em>how</em> to communicate better.</p><h3>Figma: Democratizing Design</h3><p><strong>The science:</strong> Vector editing, real-time collaboration, version control, developer handoff.</p><p><strong>The art:</strong> Design system templates, component libraries, workflow examples from top design teams, educational content about design thinking, community showcases.</p><p>Figma transformed design from a specialist activity to a collaborative team sport.</p><h3>The Hidden Complexity of “Art”</h3><p>Teaching people how to use your product effectively is deceptively complex:</p><p><strong>Understanding Context:</strong> You need to deeply understand your users’ jobs, constraints, and success metrics — not just their immediate pain points.</p><p><strong>Balancing Flexibility with Guidance:</strong> Too much prescription and you limit creativity. Too little and users get overwhelmed by possibilities.</p><p><strong>Scaling Personalization:</strong> Different user segments need different guidance, but you can’t create infinite variations.</p><p><strong>Evolving Best Practices:</strong> As your product grows and changes, so do the optimal usage patterns. You need systems to capture and distribute this evolving knowledge.</p><p><strong>Measuring Success:</strong> How do you know if users are getting value? Feature usage metrics often don’t correlate with business outcomes.</p><h3>You Still Need to Show It — Even If It’s Not Core</h3><p>Sometimes this “art” piece may not be part of your core value prop. You might think, <em>“Our job is to provide the platform. The customer will figure out how to use it.”</em></p><p>That thinking is increasingly risky in competitive markets.</p><p>Even if your product is a platform or a toolkit, people need help understanding:</p><ul><li>What’s a smart way to use it?</li><li>Where should they start?</li><li>What use cases are most valuable?</li><li>How do other successful customers use it?</li><li>What are the common pitfalls to avoid?</li></ul><p>In my previous company, a CRM company, we used to say “Build your own adventure”. That’s a great tagline for the product that is so flexible and versatile. But it’s terrible from positioning and adoption perspective. Sales cycles were long. Adoption curves were longer. Even then many customers would not dare touch complex features.</p><p>Then we changed from pure platform play to use case play. Then things got better. Customers knew how to take advantage of the platform in the context of their use case.</p><h3>The Resource Question: Where to Invest</h3><p>The art requires different resources than the science:</p><p><strong>Science teams need:</strong> Engineers, designers, QA, infrastructure specialists, security experts.</p><p><strong>Art teams need:</strong> Customer success managers, content creators, community managers, solutions consultants, training specialists, data analysts who understand user behavior (not just product metrics).</p><p>Many product teams are heavily weighted toward science.</p><p><strong>The most successful products invest roughly equally in both sides.</strong></p><h3>What This Means for Product Managers</h3><p>As a product builder, it’s your job to get the product <em>to work</em>. But it’s also your job to help people <em>get the most out of it</em>.</p><p>This means asking different questions:</p><p><strong>Science questions:</strong></p><ul><li>Does this feature work as expected?</li><li>Is the user experience intuitive?</li><li>Can we build this efficiently?</li></ul><p><strong>Art questions:</strong></p><ul><li>Have we shown users what great usage looks like?</li><li>Do we provide templates, workflows, and case studies?</li><li>Are we helping users connect product features to their real goals?</li><li>What would success look like for different user segments?</li><li>How can we help users discover unexpected value?</li></ul><p>If you stop at usability, you’ve done half the job. The rest is enabling transformation.</p><h3>The Competitive Advantage</h3><p>Here’s the strategic insight: <strong>Science is getting commoditized, but art is getting more valuable.</strong></p><p>Today, you can spin up a sophisticated web application in hours using modern AI tools. APIs, databases, authentication, payments — the technical building blocks are increasingly standardized.</p><p>But teaching people how to transform their work? That requires deep domain expertise, customer empathy, and continuous learning. It’s much harder to replicate.</p><p>The companies winning in competitive categories aren’t necessarily the ones with the best features. They’re the ones helping users achieve outcomes that seemed impossible before.</p><h3>Getting Started: The Art Audit</h3><p>Want to assess where your product stands? Ask these questions:</p><ol><li><strong>Discovery:</strong> Can new users easily find examples of how others like them use your product successfully?</li><li><strong>Onboarding:</strong> Does your onboarding end with “here are the features” or “here’s how to achieve your goals”?</li><li><strong>Ongoing Value:</strong> Do you have systems to help users discover new ways to get value as their needs evolve?</li><li><strong>Community:</strong> Are your most successful users sharing knowledge with others? Are you facilitating this?</li><li><strong>Measurement:</strong> Do you track business outcomes for users, not just product engagement?</li></ol><h3>Conclusion</h3><p>The distinction is clear: <strong>science</strong> is how the product works, while <strong>art</strong> is how it’s used effectively. Science has become necessary but not sufficient for product success. Art is increasingly where products differentiate themselves and create lasting competitive advantage.</p><p>Even if teaching best practices isn’t part of your core value proposition, you still need to show users what good looks like. The art side requires different teams, different metrics, and fundamentally different thinking than traditional product development. It demands customer success managers who understand user journeys, content creators who can translate complex workflows into simple guidance, and community builders who can facilitate peer learning.</p><p><strong>Product success needs both dimensions</strong> — and the most successful products invest roughly equally in each. The companies that recognize this early and build comprehensive capabilities on both sides will own their categories. In increasingly competitive markets, art is becoming the primary source of defensible advantage because it’s much harder to replicate deep domain expertise and user empathy than it is to copy features.</p><p>The future belongs to products that don’t just work well, they help people work better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22f84fcc735d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t start with an MVP.]]></title>
            <link>https://medium.com/design-bootcamp/dont-start-with-an-mvp-17897ae1e478?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/17897ae1e478</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[saas-product-management]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Tue, 28 May 2024 17:38:57 GMT</pubDate>
            <atom:updated>2024-05-28T21:51:18.005Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is a common dialogue I go through in my coaching and advising.</p><p>PM: What should be the MVP? <br>Me: Depends. What is your hypothesis to test?</p><p>PM: What should be the hypothesis? <br>Me: Depends. What is the biggest assumption or risk on which you are banking your product on?</p><p><strong>Don’t think MVP</strong></p><p>I will not debate the definition of MVP here.</p><p>Instead of asking what my MVP should be, first ask what is your biggest assumption. When you are starting out as a new startup or even building a new product in an existing company, you are making assumptions.</p><p>Your assumptions are roughly in this order :</p><ul><li>Is there a customer need?</li><li>Is this a one off need for a few people or a need for many?</li><li>Is this a high priority need?</li><li>Will they actually use it? Will users change habits?</li><li>Will it actually work and provide value?</li><li>Can we build it ? Profitably ?</li><li>Can we scale GTM?</li></ul><p>These are the starting assumptions at least for new products. For existing products, there are other risks like retention risk, competitive risk, economic risk etc.</p><p>Bringing a new product to market carries risks throughout its life cycle. As a founder or a product manager, you need to be aware of these risks all the time.</p><p>When you start a new product, the biggest risk is if there is even a need. As you progress in your products journey, your risk profile changes.</p><p>At any given point of time there is one assumption that is is the <strong>riskiest</strong>. And that’s the risk you want to test for. Once you test for that, then move to the next riskiest item.</p><p>For this article, let’s focus in the initial set of risks for a new product. The goal is to test your assumption before expending any time or resources on building a product</p><p>So instead of asking what your MVP should be, ask what’s the biggest assumption or risk is at this time. Then create a hypothesis based on that assumption. And then design the cheapest experiment. There are many ways to cheaply experiment and prove your hypothesis. You don’t have to build something at this stage.</p><p>This is an example of how Zappos did it.</p><p><em>Assumption or Risk</em>: Will people buy shoes online? Tony Hsieh wanted to use the internet to sell shoes online. Amazon had already started the online model with books. But shoes? He was not sure and wanted to confirm that assumption.</p><p><em>Hypothesis</em> : X% of people who visit our site will buy shoes online. ( I don’t recall the exact percentage he had in mind.)</p><p><em>Experiment</em>: Create a web site with pictures of shoes people can buy. Tony would go to a shoe store and take pictures of shoes from his camera. Then upload them on his site. When someone ordered, he would get an email, go back to the store to buy the shoe and then ship it.</p><p>Did he invest in supply chain, pricing optimization, SEO, UX?</p><p>NO. All that are super critical and would come later. But what’s the point of investing in all that when no one will actually buy a shoe online. That’s a mistake Webvan did around the same time and spent almost a billion dollars building the full product for online groceries.</p><p>Let’s go through the key risks for your new product and what you can do to validate your assumptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lq8kETRl-8hr3wAZ" /></figure><p><strong>Need</strong> <strong>Risk : Is there a need?</strong></p><p>One of the classic mistakes I have seen from many startups is they think they have built a solution based on their own experiences. If I had this problem, others have it too.</p><p>You think customers might have a pain point because you have experienced it but when you speak to customers, it may turn out they don’t consider this a pain point. This is the holy grail of product management and the most risky of product assumptions that needs to be uncovered during discovery.</p><p>Talk to your target customers. In B2B, talk to at least 10–15 potential prospects in the segment you are targeting. Ask them about the pain point. Confirm that they actually have a problem.</p><p>Sometime the problem only exist in our heads. We need to ensure that it is also in our prospects head. And talking to customers is a best way to validate your assumption about a need.</p><p>The point of talking to customers is to reduce this risk. If this risk holds true, then your product or business will not go anywhere. If you are in B2B, working on a new product in a new space, you have no option but to talk to customers and confirm the pain point.</p><p><strong>Priority Risk: Customer has pain point, but its not top of mind</strong></p><p>In B2B, business customers have a lot of pain points. They are always battling business challenges related to marketing, sales, operations, production and so on. They simply cannot work on all the challenges at the same time. So they prioritize.</p><p>How? They prioritize based on what is important to them as a business at that time. And when you are selling them a product, it has to be a pain point that is a high priority for them.</p><p>Otherwise they will simply defer or not even bother. This is something you have to uncover as part of your discovery process.</p><p>You can do some experiments to determine how they are solving the problem today. Let’s say you are helping sales team with AI recommendations that helps improve pipeline quality and conversions. Create a landing page with the right messages and see how many prospects sign up. You can offer them a white paper or a check list of things that helps improve pipeline. Create a lead magnet that helps you validate that this is something a customer wants to solve today.</p><p>If no one signs up to your free offer, then you know it’s not a priority.</p><p><strong>Small Market Risk: Customer has pain point, but not many have this problem</strong></p><p>There are two variants within this risk.</p><p>First, there is a pain point that you uncovered in a couple of discovery sessions, but not many customers resonate with that. Find out why this pain point is not applicable to them. What other pain points do they need to solve?</p><p>Second, the market is not too big. Imagine you want to build a CRM for Llama farmers. You spoke to a couple of them and they both mentioned a need for s system to manage their customers. But how many llama farmers are there.</p><p>So this is a market size risk.</p><p>You have uncovered a pain point in a couple of discovery sessions. But how do you ensure that this is not a one off need. This pain point should be more prevalent across a large set of customers. You need to speak to many many customers to ascertain a pattern. If many customers report the same pain point, then you have a market to go after.</p><p>Your initial discovery will give you clues on how prevalent the pain point is.</p><p><strong>Usage Risk : Will users actually use it?</strong></p><p>In the book “The Right It”, Albert Savoia write about the Palm Pilot. In the mid 1990s, there was a company that create the first personal digital assistant (PDA), way before iPhones and BlackBerry. You could look up your appointment calendar, find the phone number of someone you want to call and take notes.</p><p>This was a physical device which meant spending a lot of R&amp;D money to even develop a prototype. What if after building this expensive prototype, few people use it. Changing habits is a really hard thing to do. This is what the founder did.</p><p>He create a small wooden box with the rough dimensions of his planned device. In the box he placed sheets of paper. On the paper, he noted down his daily appointments for the week.</p><p>His assumption was will he ever take out the box from his pocket to check his appointment. His hypothesis was when I need to know about my next appointment, I will check against my “device”. After a week, he concluded that majority of the time he used the device. He tested this with a few colleagues as well. Only when they were sure that people will rely on this device, they proceeded to build it. Of course, Palm Pilot was a massive success until new tech aka smart phone came along.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/0*YkPeikB2gefiy0C4" /></figure><p>You may have the best technology and you actually might even have evidence that this is a big user pain point to solve, but the risk is if people will actually use it. The Zappos MVP experiment is a good example as well.</p><p>Look around your home and see how many product you have bought that you have hardly used. Look into your kitchen for gadgets or utensils you hardly used.</p><p>That’s a risk. Because if people don’t use your product, they will not renew, they will not recommend and your product will languish. So it is critical to test your hypothesis that at least some people will actually use your product when they need it.</p><p>If you are building a SAAS product, how will you test for this hypothesis?</p><p>This is where you can get creative. I was recently advising a product team building a mental health app. I asked that when people are in a mental crisis, will they actually remember to use your app and get help. They assumed they would.</p><p>I recommended they create a simple google form and ask some questions. Make the link to the form easily available on your site. Now check how many people will actually come to the form. Now they did not tell users it is a form. They just said come to this page for help. In a week, 40% of their audience actually visited the form and answered the 2 questions. That proved that when they need it, they will use it.</p><p>Your hypothesis should be something like “When a user needs to do a Job X, at least 40% of my target will actually use it”</p><p>Create the lowest cost experiment to test this hypothesis. With no code, landing pages, clickable screens, you have a lot of options. Proceed to build your product once your hypothesis is validated. Be creative.</p><p>Here is a brilliant example of how one founder tested an idea of a product in Ikea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*2TisJmcDX_07w4gX" /></figure><p><strong>Note:</strong> Usage risk above is not the same as usability risk. Usage risk happens if the user does not even use the product when it is needed. It’s not top of mind or they forgot about the product.</p><p>Usability pertains to ease of use and is covered under solution risk below.</p><p><strong>Solution Risk: Solution does not solve or is a hassle to use</strong></p><p>At this point, you have validated that there is a real customer need and they will use your product when needed. Now you can proceed to build the product. But there is another risk looming.</p><p>What if it does not work?</p><p>What if it is too much hassle?</p><p>At this stage, you will likely need a minimal product. In this minimum product, only build that core feature that you plan to solve for the user which will be your main differentiation. e.g. You want to build a sales recommendation tool using AI for sales reps to find the best opportunities in their pipeline. Create a bare minimum feature using AI that provides recommendations. It can be a simple one page app. Now test if the recommendations are accurate and do they work most of the time.</p><p>The risk here is that customers do not find the product valuable. By creating a low fidelity prototype, you validate that the product will actually create the value for your customer. It will also help you determine how to reduce friction in usage so that it is not a hassle to use.</p><p>e.g. maybe this tool for sales rep should be integrated with their CRM, otherwise it will be too much of a hassle. What other integrations might be needed?</p><p>Remember, at this stage whether this is a priority for them is not an issue. You already tested that before. The risk is they will use it but not find enough value.</p><p>The key thing to remember for your prototype is that you only need to test for the real core value proposition. You don’t need to test single sign on, audit trails, fancy dashboard or SOC 2 compliance. These bells and whistles will come in later.</p><p><strong>Conclusion:</strong></p><p>Don’t think of MVP from a product perspective. The P in the MVP is a misnomer. It was coined back in 2008 and the name has stuck.</p><p>It should really be called MVE…an experiment. As you can see from some of my examples above, most are actually not products. They are experiments to test your hypothesis.</p><p>Find the riskiest of assumptions at any point of time and test for that before you move to the next assumption. This is a much better way to validate than creating an MVP. What is the cheapest way your can test your assumption, without having to build the product.</p><p>Follow this process.</p><p>Assumption : What is my assumption or risk that I need to validate or invalidate? Hypothesis: How will I know if the assumption is valid. Create a statement like this ” of the X number of people who try, Y% will do Z”</p><p>Experiment: Design the cheapest and fastest way to experiment your hypothesis.</p><p>Do you have to test every risk?</p><p>If you are building an improved version of a product that is better than the incumbents, then you don’t need to test the need or priority risk. Customers are already using something today which means they have a need and they will use your product. Your risk is if your product is actually better than the incumbents. That’s where you can start.</p><p>If you are creating something new, then you don’t know if there is a need, let alone if users will use it. So you start your experimentation from the beginning.</p><p>You can download my <a href="https://substack.com/redirect/05b29830-04d2-4ac9-8d15-415c6b8f8fbb?j=eyJ1IjoiZ2N1aDMifQ.O-i2IXoywepWGoyDdwUeGhN0PsuIITDYcnBfFlGCuSA">template</a> here to identify the types of risks a new product faces.</p><p><a href="http://productsos.substack.com/">Subscribe</a> to my newsletter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17897ae1e478" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/dont-start-with-an-mvp-17897ae1e478">Don’t start with an MVP.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the PM Job Description]]></title>
            <link>https://medium.com/@deepak.deolalikar/beyond-the-pm-job-description-15d66d680b8e?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/15d66d680b8e</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Wed, 08 May 2024 18:11:11 GMT</pubDate>
            <atom:updated>2024-05-08T18:11:11.748Z</atom:updated>
            <content:encoded><![CDATA[<p>A product manager’s job description has a number of bullet points, but there are many more things they do on a daily basis that are unwritten.</p><p>Here are some things that I have done that were not part of the job description.</p><ul><li>I read the GDPR law …3 times</li><li>Worked with finance to add SKUs</li><li>Worked with legal to change legal T&amp;C and privacy policies</li><li>Reviewed support tickets</li><li>Improved triaging process with support</li><li>Trained sales people to give better demos</li><li>Created a process for customer success to do usage based followups</li><li>Hooked up the Vonage accounts of sales people with salesforce (in a startup)</li><li>Get Snacks from Costco for the office (in a startup)</li></ul><p>None of these will ever be in a job description. And yet, beyond the product work, PMs should do whatever it takes to deliver value to customers.</p><p>There are many types of PM roles such as outbound, inbound, technical PM, product owners etc. I will not discuss these here. But for any PM role, there are certain traits that are expected. Many of these are personality oriented, others are learnt through experience.</p><p>A product manager does a lot of different things to get their product out in the market.</p><p>If you are considering transitioning to product management, consider these skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/153/0*iRDKBjIJDMC8bo63.jpeg" /></figure><p>Here are some samples of things they do that may not be listed in a typical job description.</p><p>This is not an exhaustive list.</p><p><strong>Ability to Collaborate Cross Functionally</strong></p><p>Product managers are often seen running around meetings to meetings. To get to product launch, they have to juggle several tasks and collaborate with almost every organization in the company. During my last product launch I touched almost every department –</p><ul><li>Product Marketing for the goto market planning and launch activities</li><li>Sales for training the sales reps</li><li>Channels for partner provisioning and communication</li><li>Support for documentation and training</li><li>Legal to update the contract language</li><li>Internal applications to add a new SKU in the order form.</li></ul><p>All of the above are in addition to the daily work collaborating with engineering, UX, architects, release management and operations to get the product out the door. An important lesson is that getting the product out of the door is not enough, you have to get it into the hands of the users. A subtle but huge difference. Even after launch, you have to keep working with sales, account managers and support to ensure that the product is being used.</p><p>If something is blocking a launch or product usage, then it is the product manager’s job to get it unblocked. Simply saying “this is not my job” or “they were supposed to do it” is not going to cut it.</p><p><strong>Persuasion and Influence</strong></p><p>One of the hardest part of a product manager role is to persuade everyone to your way of thinking. Even if people don’t report to you, you still have to influence them. That’s what makes it tough. Product manager is the focal point for assimilating inputs from various sources, based on which they are able to make informed decisions about the product. Now they have to report back and influence stakeholders to get along — to engineers, architects, UX, marketing or even your company executives.</p><p><strong>Effective Communications</strong></p><p>Sometimes you will see in a JD but it’s vague at best.</p><p>Whatever goes in the product manager’s head has to be communicated out to the right audience. Having excellent communication skills is not just the ability to confidently present. It’s about explaining your thought process to various audiences. Choosing the right tone and the right granularity is important to get your message across effectively. This comes with practice.</p><p><strong>Decisions</strong></p><p>Product managers have to make many decisions. Some decisions are very hard to do.</p><p>Which of these two features to prioritize?</p><p>Which of these two bugs to fix?</p><p>Should I defer the bug that is impacting a large customer?</p><p>There are many different frameworks for decision making and they vary by company, by product, by situation. Pick one that suits your situation. Once you have arrived at a decision, you need to hold on to it and be able to justify rationally, preferably with numbers to back them.</p><p><strong>Subject Authority</strong></p><p>A good product manager is the subject authority on a number of topics. They need to know their own product area at the back of their hand. They also need to be the expert on the industry, the competition and most important their own customers. They also need to be aware of the peripheral areas such as architecture, legal, commercial, marketing etc.</p><p>Once we were planning a major feature in a product which violated a specific article in GDPR. Our customers MSA did not have a provision that would have helped us circumvent that. So I had to have the subject matter knowledge not just on the product but also our own MSA and the law.</p><p><strong>Rapid Context Switching</strong></p><p>On an average day, a product manager could be doing all of these just by lunch time.</p><ul><li>Attend scrum</li><li>Problem solve a specific ticket with an engineer</li><li>Provide a roadmap presentation to a customer</li><li>Brainstorm the value proposition messaging with product marketing</li><li>Talk to exec staff about an upcoming product strategy session</li><li>Respond to Slack message from your engineering lead who needs you to clarify a specific ticket ASAP</li><li>Continue working on your roadmap presentation due tomorrow</li></ul><p>A good product manager can rapidly switch contexts and still be able to maintain their true north.</p><p>And there are many more such traits a PM need to have.</p><p>By the way, nothing wrong in having a job with multiple facets. It is by design.</p><p><strong>Are you considering a PM job or struggling in the one you have?</strong></p><p>Thinking about trying out a PM job or feeling lost in the one you’re in?</p><p>If you like the idea of a job where things aren’t always clear-cut, then a PM role might be for you.</p><p>But if you prefer more structure, there are other roles that might suit you better.</p><p>A while back, I hosted a talk about becoming a product manager. I noticed something: a lot of the attendees, especially engineers, wanted to become PMs. It’s easy to think the grass is greener on the other side. But before you switch, talk to someone who’s already a PM and get a sense of what it’s really like.</p><p>Becoming a successful PM isn’t just about following rules or reading books; it’s about being okay with not always knowing what’s going to happen next. So, make sure it’s the right fit for you before you make the move.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15d66d680b8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is not changing in 2024 for product managers?]]></title>
            <link>https://medium.com/design-bootcamp/what-is-not-changing-in-2024-for-product-managers-9fdeaeb2f71f?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fdeaeb2f71f</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 05:17:33 GMT</pubDate>
            <atom:updated>2024-01-04T04:12:52.296Z</atom:updated>
            <content:encoded><![CDATA[<p>This year, 2023, we witnessed significant changes.</p><p>The economy, interest rate, inflation, unemployment had some significant swings. On the other hand, there were exciting new technologies, namely AI and LLM, that took our world by storm.</p><p>There were some who said that PMs are doomed as ChatGPT can write specs. Some others said ChatGPT will help the product managers do a better job.</p><p>What will happen only time will tell.</p><p>In a world where AI is making big changes, everyone’s talking about how product management is evolving. But let’s take a moment to look at the things that won’t change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Mu5BWo8bJysgiUiC.png" /></figure><p><strong>Building Products that Create Business Impact</strong></p><p>One unwavering truth persists: the ultimate goal is to build products that significantly contribute to business impact, whether in terms of revenue generation or customer retention. In 2024, as always, the core mission remains unchanged — products must be strategic assets that drive tangible value to the company.</p><p><strong>Prioritizing for Lasting Customer Value</strong></p><p>The fundamental principle guiding product prioritization endures: the focus must be on creating lasting customer value that translates into a tangible business impact. There are 100s of prioritization frameworks and more will be created. The ultimate goal for prioritization remains the same — ensuring that the chosen features align with customer needs and contribute meaningfully to the company’s success. You could use AI to help you summarize or arrange your feature sets, but you still need to make a judgement call.</p><p><strong>Crafting Timeless Product Positioning</strong></p><p>The way a product is positioned and messaged continues to hinge on how customers and the market perceive it. In 2024, product managers must remain attuned to these perceptions, adapting their positioning strategies to align with customer expectations and market dynamics.</p><p><strong>How Customers Decide to Buy</strong></p><p>The process of how customers evaluate and decide on the value of a product remains a timeless aspect of product management. In 2024, as in the past, delving into the intricacies of customer decision-making is essential for crafting offerings that resonate and meet the expectations of a discerning customer base.</p><p><strong>How Customers Adopt</strong></p><p>While technology advances, the challenge of getting customers to adopt a product remains a pivotal concern. Whether introducing innovative features or refining user experiences, product managers must continue to strategize on overcoming adoption barriers, removing friction, and ensuring that their offerings become an indispensable part of the customer’s toolkit.</p><p><strong>Stakeholder Management and Alignment</strong></p><p>Regardless of technological advancements, the art of managing and aligning stakeholders remains critical. In 2024, product managers must continue to secure buy-in and foster effective collaboration across diverse teams. The ability to navigate stakeholder dynamics ensures a unified approach toward achieving product success.</p><p><strong>Your Competition</strong></p><p>Competition is not fading away; on the contrary, it’s intensifying. As the cost of building diminishes and AI simplifies development, the SAAS landscape is becoming more crowded. In 2024, product managers must prepare for heightened competition, emphasizing innovation and differentiation to stay ahead.</p><p><strong>Effective Collaboration with Engineers and Designers</strong></p><p>Amid technological advancements, the core principles of working collaboratively with engineers and designers to create exceptional products remain constant. In 2024, as in the past, successful product management requires fostering effective collaboration, clear communication, and a shared vision among cross-functional teams.</p><p>The short conclusion of the above points is that all of these deal with two things that no technology will ever be able to change</p><ul><li>Human minds</li><li>Resource constraints</li></ul><p>The human mind will evolve but at a snails pace compared to these rapid technology advancements. Your product will certainly include the most cutting edge tech. But how customers think, how you react to competition, how you work with stakeholders will still need empathy and judgement.</p><p>And our resource constraints are not going to change overnight — budgets, manpower, materials, time. No amount of AI is going to make these resources abundant. So how you prioritize your work and create the right amount of product will be based on your cumulative experiences and judgment.</p><p>As a PM, don’t overlook the enduring importance of investing time in learning and mastering these critical aspects that bridge the gap between innovation and practical implementation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fdeaeb2f71f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-is-not-changing-in-2024-for-product-managers-9fdeaeb2f71f">What is not changing in 2024 for product managers?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maximizing Product Success through Effective Stakeholder Management]]></title>
            <link>https://medium.com/design-bootcamp/maximizing-product-success-through-effective-stakeholder-management-237f59c51b09?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/237f59c51b09</guid>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Thu, 21 Dec 2023 17:49:21 GMT</pubDate>
            <atom:updated>2023-12-21T23:11:23.991Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WEs8r7IAFFYEHn6s.jpeg" /></figure><p>Stakeholder management is a key skill for all B2B SAAS product managers. We work closely with engineering and design in order to design, build and launch our products. But there are many other stakeholders that we must work with closely.</p><p>In my experiences, I touched almost every organization when launching products including legal (changing our terms and conditions because we are capturing PII) and finance (needed a new SKU for a new product).</p><p>The most critical stakeholders that you as a Product Manager should engage with are :</p><ul><li>Product Marketing</li><li>Sales</li><li>Customer Service and Support</li><li>Customer Success</li></ul><p>While it is important to create alignment on your product strategy with these stakeholders, it is equally important to collaborate with them to shape your product strategy.</p><p>In order for you to maximize your product success, here are some examples of how you can better engage with stakeholders. These are not exhaustive, rather indicative of how you can collaborate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y1jv7cgwjfFXHAnE879hw.png" /></figure><p><strong>Product Marketing</strong></p><p>Product management and product marketing should really be joined at the hip. They need to work together to make sure the messaging and positioning is aligned. This means that they must have a good understanding of each other’s roles and responsibilities. Product management should provide product marketing with a deep understanding of the product roadmap, features, and benefits. On the other hand, product marketing should provide product management with customer insights, market trends, and competitive analysis. By working together, they can ensure that the product is developed with the customer in mind and positioned correctly in the market.</p><p>Here are some other areas the two should work together</p><ul><li><strong>Competitive analysis</strong></li></ul><p>Marketing often does competitor analysis so they can better arm their sales teams with playbooks and how to respond in a competitive situation.</p><p>A key aspect is to understand how competition is positioning their products. A common adage is not to focus on competitors but delight your customers. That’s true. The point is that your competition is doing the same, and maybe they are doing it better than you. So understanding how your competition is challenging you is important. You don’t have to focus on all competitors. Just the few who you see in the field or are more active in the set of customers you are targeting. Let’s say, one of your key competitors is telling customers that their workflows are superior and very flexible compared to yours. That means, you need to get ahead of that messaging when presenting to prospects and customers. Otherwise, a doubt is created in the minds of the customers for whom workflow is critical. You need to prevent that doubt in the first place and play offense. It could be a new feature you can build or it could just be better messaging in sales demos.</p><p>Work with product marketing to understand these competitive headwinds and help your company stay ahead.</p><ul><li><strong>Industry Analyst sentiment</strong></li></ul><p>In B2B, product marketing has good relationships with key analysts from Gartner, Nucleus, Forrester etc who are monitoring your space. It’s invaluable to get in front of these analysts and get the industry landscape and more importantly, how you are responding. While marketing has a good handle on working with the analysts, product managers should also be involved with them. This helps you understand the industry direction and provide a critical input to your own product strategy.</p><p><strong>Sales</strong></p><p>Sales is where the rubber meets the road. Product marketing provides the playbooks, demos and scripts to sales team so that they can be effective sellers.</p><p>Here are some areas on how you can help sales.</p><ul><li>Friction in demos or handling sales objections<br>Attend some of the prospect demos that salespeople present to see how they are received. Are the prospects gaining a good understanding of the product? Ideally, prospects should understand the product after one meeting, so the next meeting can focus on the sale. You can assist the sales team by identifying which parts of the product need improvement to shine during a demo.<br>During demos, customers may have a lot of questions. It is important to provide sellers with the right information so they can respond effectively to these objections. Handling objections is a critical part of making a successful sale. It increases your probability of a sale and makes the sales cycle more predictable.<br>In a growth startup, it is critical to build that repeatable sales motion. A product managers role is invaluable in helping shape that repeatable sales process. They can help with the right materials, talking points and FAQs, in addition to create a rocking demo with real life data.</li><li>Win-Loss Analysis<br>Another way for product managers to collaborate with sales (typically sales ops) is by analyzing win-loss data. Such data can provide valuable insights into why deals were won or lost and help identify areas for product improvement. It can also refine the ideal customer profile (ICP) and avoid pursuing prospects for whom the product is not well-suited.<br>Understanding where sales are gaining the most traction, such as in specific customer segments, industries, or domains, is critical. By doubling down on these areas, product managers can maximize success and shape product strategy.<br>Typically sales operations should be able to help with analyzing this data.</li></ul><p><strong>Customer Service and Support</strong></p><p>In B2B environments, customer support is essential to the success of customers. Support is responsible for making sure that issues faced by customers are resolved in a timely manner to their satisfaction.</p><p>One area to work with support for a PM, is to understand the patterns of incoming requests. Are their specific areas of the product that generate more tickets? Are there any friction points when a customer is using your product?</p><p>Some bugs will eventually move through your JIRA backlog, but as PM you should look at all incoming requests. A lot of requests are simply questions from customers — “How do I do this?”, “ I cannot find this action” etc These are invaluable inputs to help you improve your product experience so that customers don’t have to ask these questions and are able to resolve these on their own. Or perhaps there is an opportunity to create some FAQs, or Videos or Help articles. Maybe an in app guide to help the user.</p><p>Another area in working with support is streamlining your triage and escalation processes. In B2B environments, engineering will get a lot of high priority requests. But you can work with support teams to establish a cadence and prioritization framework. Not everything can be a priority.</p><p>Finally, involve your support team in your launch process. They will be the first to bear the brunt of your customers when something new is released. It is critical to help arm this first line of defense.</p><p><strong>Customer Success</strong></p><p>Finally, customer success is a key stakeholder in maximizing the success of your product. Their job is to ensure customers are onboarded and are using the product and getting the value. Mature CS organizations are involved with the customer at every step of their journey, not just at the end when renewal is coming up. A product manager needs to ensure that they set them up for success.</p><ul><li>Onboarding process<br>Sit through a customer onboarding process. See how much time it takes. Are their specific steps that have friction e.g. integrating with another application? or setting up reporting templates?</li><li>The faster you onboard, the better customer experience you create. As a PM, you can remove any friction during onboarding. Perhaps you can automate a few things so that customer success does not need multiple meetings with customers.</li><li>Usage monitoring<br>There is a high correlation between customers who have low usage of your product and churn. Customer success should be on top of customer usage patters. But as a PM, you need to understand the root causes of low usage. Maybe the feature is not important, or the feature is not adding value or even worse, maybe this is the wrong customer.<br>Usage monitoring and fixing the root causes are critical to make sure your product will be adopted across your customer base.</li><li>Churn analysis and mitigation<br>Find out why customers are churning. Is there a specific pattern on the type of customer who is churning? At what point do they churn? What can be done to to reduce churn?<br>These are exactly the key success criteria for a customer success organization. As a PM, you can help analyze the reasons for churn and help improve the product experience. This could imply adding new features in your product, or providing better training or materials to customer success teams.</li></ul><p><strong>Conclusion</strong></p><p>Personally, I establish connections with all stakeholders because they are a primary source of input for my product. In addition to talking to customers, I rely on the insights from my internal stakeholders. They are much more present with customers and have to deal with their frustrations.</p><p>It’s important to get to know your stakeholders, understand their motivations, and help them become better at their jobs. The product you build has a direct impact on their success as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=237f59c51b09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/maximizing-product-success-through-effective-stakeholder-management-237f59c51b09">Maximizing Product Success through Effective Stakeholder Management</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A BandAid is better than bleedi]]></title>
            <link>https://medium.com/design-bootcamp/a-bandaid-is-better-than-bleedi-070775e035f0?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/070775e035f0</guid>
            <category><![CDATA[product-management-tool]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Sun, 10 Dec 2023 13:59:39 GMT</pubDate>
            <atom:updated>2023-12-21T23:11:25.114Z</atom:updated>
            <content:encoded><![CDATA[<h3>A BandAid is better than bleeding</h3><p>I was watching Season 3- Episode 5 of “Halt and Catch Fire”. The two startup co-founders are arguing about a software issue which requires a quick decision. Should we leverage the code already built by someone (a company they recently acquired) that processes credit card payment or should we build our own payment processing. The main founder is a hard core techie (Mackenzie Davis) and she argues their code is in a different language and will not fit. The other cofounder (Kerry Bishe), also an engineer but handles business, suggests it will take time to build it and in the mean time we are bleeding. Let’s put the band aid now by integrating the 3rd party code, and then we can figure out how to improve on it later. We need a band aid now to stop the bleeding.</p><p>For those not familiar, <a href="http://www.amc.com/shows/halt-and-catch-fire">Halt and Catch Fire</a>, is an AMC TV series about the early days of the PC industry. Season 1 starts in the early 80’s and shows the transition of an analog electrical company in Dallas, TX into the PC business. And how the protagonists (the engineers and the visionary) split up to found their own companies selling PC clones, video games and the early packet switching networking. For those who lived through the early days of personal computing, might see themselves as one of the shows characters. The writing, direction and art is brilliant. If you liked <a href="http://www.hbo.com/silicon-valley">Silicon Valley</a> (HBO), then you will surely like this series.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*p91Xf0ahFKZER82j.jpeg" /></figure><p>Back to the bandaid. There are opposing forces when you are trying to build out your software. On the one hand, you need speed. Quick and dirty code could do the trick in order to build the customer base. On the other hand, you need your code to be scalable, foolproof, extensible etc etc. Most, not all, but most engineers would always want to build for the long term so that you don’t have to go back and retool your software the expensive way later. And they can do it better than anyone else. And they also don’t want to waste time later peeling off the band aid. Hence the quest to build the right solution from the get go.</p><p>There are no easy answer to these questions. The solution lies in your goals. If the goal is to get as many customers quickly so that you can be quick to market, then yes, band aids might be the best solution. Especially, if there are areas of your product that are not so core. By all means, apply a band aid, get off the shelf tools or software. Whatever it takes to ship the software. It’s a much harder decision when it comes to the core of your software. You may decide to write code on your own and not rely on band aids. Of course, it may cost you time and customers. But you will be prepared for the eventual deluge of customers, whenever it happens. But if getting customers is key so that you can get to the next round of funding, say, then the band aid approach will need to be on the table for discussion.</p><p>When I was in a smaller startup, speed was important. We kept our eye on the long term solution because we were confident of the long term growth. But wherever needed, we applied band aid or leveraged something that we could have built on our own if we had the time. Later I worked for a larger software company. Band aids become expensive very quickly. Not to mention, that with new code being added on a regular basis, the band aid never actually gets removed. It takes years of effort to retool. Hence the need for the right solution in the first place and avoid a much larger future bleeding.</p><p>In Episode 5, the eccentric techie founder went AWOL for a week to get married. But in that week, she was able to produce code the way she wanted and it was better integrated with the core. No need for band aid.</p><p>If you can find a way to get around a band aid quickly enough, then that should be the starting point. You should always start with the longer term solution, the right solution. Understand the costs associated. Only then bring the band aid approach if the long term solution does not meet your goals.</p><p>Whatever your approach, make sure everyone in the team is aware of the decision and all pros and cons understood.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=070775e035f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-bandaid-is-better-than-bleedi-070775e035f0">A BandAid is better than bleedi</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 revenue killers in B2B SAAS]]></title>
            <link>https://medium.com/design-bootcamp/top-10-revenue-killers-in-b2b-saas-35fe76e43b01?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/35fe76e43b01</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[b2b-saas]]></category>
            <category><![CDATA[revenue]]></category>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Tue, 24 Oct 2023 20:17:24 GMT</pubDate>
            <atom:updated>2023-10-25T00:23:38.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wKgeVamPPb0A_d-Fc70ltw.png" /></figure><p>Revenue is the lifeblood of any business, and as PMs you are ultimately responsible for delivering delightful products that brings in revenue. You are probably thinking that if you do the right discovery, you will build a great product and sales will follow.</p><p>Unfortunately, in B2B building a good product is just the beginning of the story. There are many more hurdles to go until the sale is made. Most of the time sales and marketing teams will take care of making sure the deals get closed. And customer success teams will ensure the renewals go through.</p><p>But as PM you can help grease the wheels a bit for them.</p><p>How?</p><p>Let’s look at the top 10 revenue killers companies face and how you as a PM can help mitigate these.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OP-dxornHCe2wUSx.png" /></figure><p><strong>1. Unclear Value Proposition:</strong> A hazy value proposition wastes precious sales cycles. When potential customers cannot easily grasp the unique benefits of your product, they are more likely to move on or explore other options.</p><p>A product manager can help by working closely with the marketing team to craft a compelling and clear value proposition that highlights the unique benefits of the product which resonates with the target audience. As a PM, you were involved in the initial discovery and validation of the product. Which means you have the best view to provide what value proposition will resonate the most.</p><p>Success is when sales and marketing messages resonate so well that prospective buyers are ready to start closing a sale early in the sales cycle, and sales is not spending frequents cycles with prospect to explain the product and why they should consider.</p><p><strong>2. Ill-defined ICP:</strong> An improperly defined Ideal Customer Profile (ICP) can lead to churn. When your product does not align with the specific needs and characteristics of your target customers, you risk losing those customers at the time of renewal.</p><p>A typical symptom of this lack of clarity is that sales will close deals with any type of customer, without too much regard if the product actually is a fit for them.</p><p>Imagine you have created a pain killer. Your sales will now target anyone with any kind of pain. Obviously not all pains are the same. A headache is different from a knee joint pain. But you define an ICP, e.g. a pain killer specifically for back ache then you only target those types of customers. And because your medicine works for back ache, most of the customers will find value and buy it again if needed.</p><p>If you see customers churning, check if they were really your ideal customer in the first place. There are many reasons for churn, but a primary one is to ensure your customers are a fit. As a PM, ensure you define your ICP clearly and work with sales and marketing to target those.</p><p><strong>3. Positioning Pitfalls:</strong> This is similar to #1 above. A well positioned message allows a customer to understand the value prop and self select. When positioning is done right, the prospects will gravitate towards your solutions.</p><p>If you’re not positioned right in the market, you risk potential clients who will choose no decision. Misaligned positioning can result in a missed opportunity to showcase your product’s value and uniqueness.</p><p>The best example is Netflix. When they started in late 90s, their positioning was “no late fees”. That resonates with a lot of people who were sick of paying hefty late fees to Blockbuster. (myself included). Now the value proposition is lot of selections, convenience, personalization etc. But it was the positioning that attracted the buyers.</p><p>How you create positioning is a topic by itself. In a nutshell, what is that one differentiated value that will attract your prospect and convince them that this is the solution they have been looking for. If they do not find that, they will end up with no decision, thus losing the sale.</p><p><strong>4. Messaging Misalignment:</strong> Misaligned messaging with internal stakeholder that fails to showcase your product in the best light can lead to confusion. Clarity and consistency in your messaging are essential for building trust.</p><p>Your internal stakeholders like marketing, channel management and others have their set of priorities. It is essential that the messaging they are relaying to prospects and partners is in line with the reality of the product capabilities.</p><p>If your web site or marketing copy does not highlight the real capabilities of the product, that could result in missed sales opportunities. As a PM, you have to ensure that stakeholders are aligned to the real value and positioning and not miss sales opportunities.</p><p><strong>5. Friction-Filled Onboarding:</strong> High friction during onboarding often leads to churn. Complex or time-consuming onboarding processes can deter new users from fully adopting your product, increasing the likelihood of abandonment.</p><p>Once I lost a customer as they were not able to connect my app to their Outlook for sending emails. As a PM, map the entire boarding process and remove any friction. Replace manual steps with automation where possible. Reduce the number of steps. Get them to the AHA moment as soon as possible.</p><p>This will help reduce churn due to reasons of poor onboarding.</p><p><strong>6. Reactive Retention Management:</strong> When customers don’t use the product as much as they would like, they risk being lost to churn. Which means you have to constantly monitor product usage data and proactive identify customers who may churn due to lack of usage.</p><p>Many times customer success will get to know about lack of usage towards renewal, which is already too late.</p><p>If you analyze past data of churned customers, you might see patterns. Then use that pattern to proactively identify which customer segments exhibit that pattern. Customer success can then do early intervention to prevent the churn.</p><p>As a PM, you can help proactively manage churn.</p><p><strong>7. Lack of Upgrade Paths:</strong> Usage data can also be your treasure map to upsell and cross-sell opportunities. When you don’t offer clear paths for customers to scale their usage or explore additional features, you miss out on potential revenue growth.</p><p>As a PM, identify high usage customers who offer the opportunity to expand usage across persona or use cases. Work with sales and marketing to promote additional products or add ons.</p><p><strong>8. Competition Oversight:</strong> Failing to keep an eye on the competition can result in losing customers. In a competitive market, neglecting to stay informed about competitors’ offerings and innovations can lead customers opting to switch.</p><p>As a PM, not only you have to watch new product capabilities from competition, but also how they are positioning. You may have a better product, but if a competitor comes with a better positioning message, then the customer will likely try to engage or get a demo. Your job is to ensure that the customers do not entertain the messages from the competition.</p><p><strong>9. Distrust-Building Mistakes:</strong> Mistakes like missed deadlines, data breaches, or inaccurate reports erode trust. Trust is fragile, and any missteps, whether they involve meeting customer commitments, protecting sensitive data, or ensuring data accuracy, can damage your customer relationships.</p><p>As a PM, do not ignore the small things that create distrust from the customer.</p><p><strong>10. Customer Neglect:</strong> Not giving due attention to customer needs, such as performance, roadmap clarity, or responsiveness, can lead to churn. Customer satisfaction and loyalty require ongoing effort, and neglecting their concerns or needs can result in attrition.</p><p>Remember, a vigilant B2B Product Manager can identify and mitigate these revenue killers effectively. By addressing these issues proactively, you can not only protect your existing revenue but also uncover new opportunities for growth.</p><p>Stay vigilant, stay proactive, and stay successful in your role as a B2B Product Manager. If you have any questions or need further insights into any of these revenue killers, please don’t hesitate to reach out.</p><p>Subscribe to my weekly newsletter on B2B SAAS: <a href="https://bit.ly/3mwHALq">https://bit.ly/3mwHALq</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35fe76e43b01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/top-10-revenue-killers-in-b2b-saas-35fe76e43b01">Top 10 revenue killers in B2B SAAS</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Churn to Earn — products role in managing retention]]></title>
            <link>https://medium.com/design-bootcamp/churn-to-earn-products-role-in-managing-retention-bb5b3c9dd1cb?source=rss-524d3c775f17------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb5b3c9dd1cb</guid>
            <dc:creator><![CDATA[Deepak Deolalikar (B2B SAAS PM)]]></dc:creator>
            <pubDate>Mon, 16 Oct 2023 21:50:10 GMT</pubDate>
            <atom:updated>2023-10-17T10:06:30.349Z</atom:updated>
            <content:encoded><![CDATA[<h3>Churn to Earn — products role in managing retention</h3><p>How B2B Product Management Drives Business Growth by Improving Customer Retention</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7Jcv_X5_MxHQXPzchj6vw.png" /></figure><p>In a separate article, I had discussed the <a href="https://productsos.substack.com/p/growth-strategies-for-product-managers">6 levers of growth</a> that a product manager has at their arsenal. When we say growth, we mean the growth of your business i.e revenue. Which lever is relevant depends on the stage of your company and your competitive position in the market.</p><p>In this article, we will focus on one such lever, <strong>retention</strong>. We will :</p><ul><li>understand the importance of retention</li><li>identify the root causes of churn</li><li>define retention (GRR and NRR)</li><li>strategies for PMs to manage retention</li></ul><p><strong>Why is retention important?</strong></p><p>One of the most important principles in a SAAS business is that acquiring new customers is more expensive than retaining existing ones because it involves substantial upfront costs associated with marketing, advertising, sales efforts, and customer onboarding. These expenses can be significant, especially in competitive markets. In contrast, retaining customers often requires comparatively lower investment as it involves nurturing and maintaining relationships with the customer base you’ve already acquired and ensuring product provides value. Existing customers are already familiar with your product or service, which means they are more likely to make repeat purchases and can provide a steady stream of revenue over time.</p><p>Let’s look at it mathematically.</p><p>Imagine your company has a target of 30% growth year over year. If your starting ARR (Annual Recurring Revenue) is $ 10 M per year, then by the end of the year ARR should be $ 13 M.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8QYXlpABf9K7mxCW.png" /></figure><p>The easiest would be to keep the existing customers who will continue to contribute $ 10 M in ARR and you add $ 3 M ARR from new customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZIcsQunZq8BVGw-Z.png" /></figure><p>However, during the course of the year, any of the following can happen -</p><ul><li>Customers cancel subscription</li><li>Customers reduce the usage of your product (e.g. less seats)</li><li>Customer downgrade to a lower tier plan</li></ul><p>Which means that the existing customers that started out with $ 10 M in ARR will have lower revenue. If churn is say 10%, then the ARR from existing customers will be $ 9 M. Now you have to get $ 4M from new customers to get to $ 13 M and meet your growth target. Getting new customers is costly and will eat up in profitability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I5SVDNKZtJ2HAHzG.png" /></figure><p>What if churn is 30%? <br>Then existing customers will bring in $ 7 M, and you will need to get additional $ 6 M from new customers. That’s a worse scenario than the above.</p><p>As you can see, retention is extremely important. Retention is the holy grail of SAAS business.</p><p>As a PM, your job is ensure that retention remains high. Each industry has it’s own set of retention benchmark. Marketing automation apps typically hover around 70% while CRM/ERP track at 90% and over. Your product should have retention rates similar or higher than your industry.</p><p>This is all financial mumbo jumbo. How is this related to my job as a PM?</p><p>Your company’s ability to retain customer lies in the product and the experience you provide. Your customers will continue to use your product as long as they get value. As a PM, it is your responsibility to ensure that retention is managed. Whatever level you are in the PM organization, understand the retention rates and be proactive in determining action plans.</p><p>There are several things you can do as a PM to manage retention.</p><p>Let’s go step by step.</p><p><strong>Gross Revenue Retention (GRR)</strong> <br>In our example above, we started with $ 10 M ARR and by the end of the year, ARR from existing customers dropped to $ 9 M. The retention is 90%. This is called gross revenue retention or GRR.</p><p>GRR can drop due to any of the following reasons.</p><p>Customer cancels subscription — The root causes for this could be :</p><ul><li>Product does not meet their needs</li><li>Customer goes out of business</li><li>They opted to go with a competitor app</li><li>Customer profile is not ideal</li></ul><p>Customer lowers usage — The root causes for this are :</p><ul><li>Customer is facing some business issue and not able to sustain usage levels</li><li>Customer is not using the product as much or not needed as much</li></ul><p>Customer downgrades their pricing tier — The root causes for this are :</p><ul><li>Customer bought a higher tier than needed</li><li>Customer does not need high level features</li><li>Customer is tightening their spend</li></ul><p>A high gross retention means customers are happy and want to keep using your product. A lower gross retention means customers are not finding the product useful. This is where product management need to step in and analysis the root causes. Most of the root causes for churn are in the list above. Narrow down to the reasons that are contributing to the churn.</p><p>As a PM, you can do the following to manage retention.</p><ul><li>Analyze the customer base and identify pockets of customers who are churning more often. E.g. Overall retention is 90% but a specific type of customer is retaining at 70%. Just managing this type of customer could get you additional retention points.</li><li>Analyze past usage patterns of customers who eventually churned. Then look at existing customers with similar patterns and take proactive action before they churn. e.g. customers who use only feature churn more than those use 2 or more features in your product. Or, customers in Asia churn more etc.</li><li>Map the customer journey and the onboarding process, and identify any paths that are causing friction. Work with customer success to make sure that onboarding is smooth, and the customer gets to the aha moment sooner in their onboarding. The fast the customer realizes value, the better they retain.</li><li>Make sure that your ICP is well defined and that sales and marketing are able to attract customers who fit that profile. Otherwise, sales may close a deal with a non ideal customer, but they will not retain.</li><li>Make sure your feature sets and pricing tiers are well aligned, so that customer get the value for the tier they are paying for.</li><li>Watch the competition and ensure they are not stealing your business. Sometimes you don’t have to add a feature to combat competition, it could just be a change in your messaging and positioning.</li></ul><p>As you can see, there are many ways you can help as a PM to manage retention from existing customers.</p><p>There is another strategy that can help manage retention.</p><p><strong>Net Revenue Retention (NRR)</strong></p><p>In our example above, we started with $ 10 M ARR and by the end of the year, ARR from existing customers dropped to $ 9 M. However, any of the following can also happen during the year.</p><ul><li>Customer add new users or new usage to the product</li><li>Customers upgrade their pricing tiers</li><li>Customers buy addon products from you</li><li>Customer buy a separate product from you</li></ul><p>Let’s say existing customers added a net total $ 3 M from any of the above reasons.</p><p>Now the ending ARR will be $ 12 M ($ 9M + $ 3M). The retention is 120%. ($ 10 M to $ 12M) This is called Net Revenue Retention. Sometimes also called NRD (Net Retention Dollar).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xyKTZrCNpBKp-x1I.png" /></figure><p>In order to meet our target of $ 13M, we only have to get $ 1M from new customers. This is much better scenario than trying to get $ 3M.</p><p>A NRR &gt; 100% means the overall base is expanding for future growth. If NRR&lt;100% it means your base is not growing and eventually your ARR will shrink. Which means you will acquire additional new customers.</p><p>A high net retention means customers are happy and want to keep not just using but expanding your product in their organization. This is a good sign that your product and messaging both are working.</p><p>As a PM, you can do the following to increase expansion revenue.</p><ul><li>Increase usage — Expand use cases for your product across your customers organization. Let’s say you have a product for sales people, maybe you can add dashboard and reporting for executives which would require additional subscriptions. Or let’s say you have an AI App for content marketers, then you could expand the uses to HR content. This requires a PM to understand adjacent use cases that can be easily sold to customers.</li><li>Upgrade — Find segments of customers who are ready to be upgraded. Typically, these are customers who have been onboarded for over a year, getting value and using the product increasingly. You could have a higher tier package that offers more features that will fit this type of customer.</li><li>Create new add ons -Creating add ons is a good way to create revenue from existing customers. Add ons typically work on top of the core product the customers are already using. When I was at SugarCRM, I created a product called Sugar Hint which would need to be installed on top of the platform as an add on. This was sold to the sales persona, and allowed us to get some additional revenue.</li><li>Create new products — When a company has started penetrating the market with one product, it becomes increasingly difficult to grow. The strategy then is to add a new product. The new product provides a new set of value proposition, possibly to a new set of users. SugarCRM was primarily a sales tech application. We created a new product Sugar Serve which was targeted to customer service users. This was a different product that customers could buy standalone.</li></ul><p>In the early stages of a startup, you are likely focused on Gross Revenue Retention. Once you have the structure and processes in place to maximize your GRR, you need to focus on Net Revenue Retention. The expansion that your existing customers provide today, becomes the starting ARR for next year. Then new customers this year, will contribute to expansion revenue next year at a much lower cost than acquiring brand new customers. And this effect compounds.</p><p><strong>Summary</strong></p><p>Monitor GRR and improve product and experiences for existing customers. Monitor NRR for expansion opportunities from existing customers.</p><p>As a PM, you won’t be going it alone in your mission to boost retention. Teams like Customer Success, Account Management, and Support all have roles to play in this endeavor. Many of the tasks I’ve discussed, such as refining onboarding processes or swiftly guiding customers to value, may indeed involve collaboration with others.</p><p>However, it’s essential to understand that retention is not exclusively the responsibility of the Customer Success team. As a PM, your role is pivotal in understanding the root causes of churn, resolving friction points, identifying new use cases, and even envisioning new products. It’s far from accurate to suggest that retention is solely within the domain of Customer Success; Product Managers are instrumental in driving this essential growth imperative. By ensuring the satisfaction and loyalty of our existing clients, we, as Product Managers, hold the power to not only boost revenue and cut costs but also gain priceless insights and forge enduring brand loyalty.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb5b3c9dd1cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/churn-to-earn-products-role-in-managing-retention-bb5b3c9dd1cb">Churn to Earn — products role in managing retention</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>