<?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 Ishaan Suri on Medium]]></title>
        <description><![CDATA[Stories by Ishaan Suri on Medium]]></description>
        <link>https://medium.com/@ishaansuri16?source=rss-c1c5055d5356------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5xSo6WyQ_mkYwCZ36dzoLQ.jpeg</url>
            <title>Stories by Ishaan Suri on Medium</title>
            <link>https://medium.com/@ishaansuri16?source=rss-c1c5055d5356------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:47:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ishaansuri16/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[A&W and Pret-a-Manger Strategic Partnership: Masterclass of learnings for Growth Product Leader]]></title>
            <link>https://ishaansuri16.medium.com/a-w-and-pret-a-manger-strategic-partnership-masterclass-of-learnings-for-growth-product-leader-39f504e79487?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f504e79487</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 19:31:06 GMT</pubDate>
            <atom:updated>2025-01-06T19:31:06.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fvh17LKg2kmQBI_B_d566g.jpeg" /><figcaption>Image Courtesy : Ishaan Suri</figcaption></figure><p>Let me start by telling you that I’m a coffee enthusiast who loves visiting places in search of that perfectly brewed cup. Whether it’s the Columbian coffee beans, Robusta, Liberica or even Excelsa to the what is the right degree of roast or that “<strong>18.2g dose for that perfect expresso extraction”, </strong>to experiencing brands &amp; especially the local gems around the world. In the past few years, I have studied a lot about this amazing ‘source of energy’ — to the extent that my fascination has led me to visit coffee museums to learn more about its history, geography (and more subjects…..)</p><p>So, recently when <em>Pret A Manger</em> announced that they are finally entering Canada, I was certain that I have to give their famous coffee a go and let my taste buds make a judgement about the nodes and tastes, in comparison with some other notables from this region. When I started to research more about their launch, that’s where came the surprise — “<em>A&amp;W has announced an exclusive agreement to serve Pret A Manger’s Classic Blend coffee in all its Canadian restaurants”. </em>So now I just had to find the nearest A&amp;W outlet to actually get hold of that cup for that <em>aha </em>moment. But wait, if you’re here for that coffee ratings stay tuned till the end because first the Product Manager in me kicked in with a lot of questions around the ‘WHYs’ and ‘WHATs’. So let’s dive in:</p><p>The collaboration between A&amp;W and Pret a Manger is a fascinating case — a one that could be termed as a strategic growth case that provides a lot of learnings as a Growth Product Manager.</p><h4><strong>Potential Problems</strong></h4><p>Both A&amp;W and Pret a Manger, while successful in their respective markets, are facing similar challenges such as sustaining growth and also building a potential market differentiation.</p><p>A&amp;W, a traditional fast-food chain specializing in burgers faces a stiff competition from their local rivals. They have been trying to improve their brand image overall and get a sizeable chunk from the ever growing QSR customer base. Pret a Manger, on the other hand, a premium coffee-food chain, aimed with their objective of expansion have been trying to open its market reach and penetrate in Canada to increase brand awareness. Here enumerating some of the potential partnership considerations to build a case:</p><ul><li><strong>Strategic Fit: </strong>A&amp;W&#39;s extensive network and decent brand recognition in Canada, coupled with Pret&#39;s premium coffee offerings, were both complementary strengths which were identified as a perfect blend. Both companies probably focus on quality, innovation, combined with customer experience, which builds synergies within their brand values while ensuring a smooth collaboration.</li><li><strong>Business Modelling : </strong>a mutually suitable revenue-share model would have been established to distribute the profits from coffee sales while assessing the initial investment required for infrastructure, training, and marketing by leveraging the A&amp;W network</li><li><strong>Risks &amp; Assessments:</strong> to gauge the market potential a thorough market analysis would have been conducted to assess the potential demand for quick coffee in various A&amp;W&#39;s locations across regions. The partners would have also evaluated the logistics and operational requirements to ensure a seamless integration.</li><li><strong>Shared Infrastructure: </strong>a game changer technique for quicker yet exanded reach. Leveraging A&amp;W’s extensive network of restaurants provides a convenient platform to introduce Pret’s offerings to a wider audience. Additionally, both companies collaborated to streamline the operations, reduce costs, and improve efficiency with this new introduction. Oh and not to forget launched joint marketing campaigns to increase brand visibility and attract new customers.</li></ul><h4>Smart Advantages of this partnership over giants</h4><p>The A&amp;W-Pret partnership offers several strategic advantages over coffee giants like Tim Hortons and Starbucks:</p><p><strong>Niche positioning and Unique offering:</strong></p><ul><li><strong>Premium, Affordable and Quick appeal:</strong> Pret’s focus on fresh, <em>localized </em>menu and high-quality ingredients aligns with growing user preferences with A&amp;W food offerings. This differentiates them from the more traditional offerings of Tim Hortons and Starbucks.</li><li><strong>Unique Experience:</strong> By offering a unique coffee experience, A&amp;W can attract a new customer segment that values quality and innovation.</li></ul><p><strong>Synergy and Cross-Promotion:</strong></p><ul><li><strong>Complementary Offerings:</strong> A&amp;W’s food menu can easily complement Pret’s coffee and food offerings, creating a more comprehensive experience for their customers</li><li><strong>Joint Marketing Campaigns:</strong> The two brands could collaborate on marketing campaigns to increase brand visibility and drive more <br>traffic with relatable traffic.</li></ul><p><strong>Agility and Innovation with Customer Loyalty</strong></p><ul><li><strong>Faster Decision-Making:</strong> As relatively smaller new companies in the region, A&amp;W and Pret could make decisions and adapt to market changes quickly than other similar players. Also they may be more willing to take risks and experiment with new products and services.</li><li><strong>Personalized Experience:</strong> By understanding customer preferences and tailoring their offerings, A&amp;W and Pret could build stronger customer relationships.</li></ul><p>Capitalizing on these advantages would help A&amp;W and Pret carve out a positioning in the Canadian coffee market and challenge the dominance of larger chains.</p><h4><strong>Tracking and measuring the impact</strong></h4><p>To measure the success of the partnership, A&amp;W and Pret likely employed a combination of potential KPIs such as:</p><p><strong>Sales Metrics </strong>such as<strong>:</strong></p><ul><li><strong>Increased Revenue:</strong> Tracking the incremental revenue generated from coffee sales in A&amp;W locations.</li><li><strong>Average Transaction Value (ATV):</strong> Monitoring the average amount spent per customer visit.</li><li><strong>Upsell Conversion</strong>: measuring how many users now buy a coffee with their meals and tracking the week-on-week impact</li></ul><p><strong>Customer Satisfaction &amp; Brand Impact Indicators : </strong>collaborating with a trusted partner can help mitigate risks associated especially with new market entry or expansion especially by evaluating metrics and techniques like:</p><ul><li><strong>Customer Surveys</strong></li><li><strong>Social Media Monitoring:</strong> Tracking online reviews and social media sentiment per channel</li><li><strong>Net Promoter Score (NPS)</strong></li><li><strong>Brand Perception Score:</strong> conducting surveys to measure changes in brand perception</li><li><strong>Social Engagement</strong>: Tracking social media metrics, such as likes, shares, and comments.</li></ul><p><strong>Operational Efficiency: </strong>an imp factor for<strong> </strong>both companies is to track the impact of the partnership</p><ul><li><strong>Staff Training:</strong> Assessing the effectiveness of training programs for A&amp;W staff.</li><li><strong>Supply Chain Optimization:</strong> Evaluating the efficiency of the supply chain for coffee beans and other ingredients.</li></ul><h4>Key Takeaways for Growth Product Managers</h4><p>As a growth product manager, there are several key lessons that can be drawn from this partnership:</p><p><strong>Leverage Strategic Partnerships: </strong>Partnering with complementary businesses can help businesses tap into new customer segments and geographical markets. A&amp;W, with its extensive network, can introduce Pret’s premium coffee to a broader audience. By associating with a premium brand like Pret, A&amp;W can position itself as a more upscale, modern fast-food chain.</p><p><strong>Priority on Customer Experience: </strong>Both A&amp;W and Pret are committed to providing high-quality products and exceptional premium customer service. This shared focus on customer experience can lead to increased customer satisfaction and loyalty. By listening and understanding customer problems, gaps in the market to then tailor the product offerings, businesses can create more engaging cohesive experiences for their users</p><p><strong>Innovate and Adapt: </strong>Both companies are constantly innovating and adapting to changing consumer preferences. This type of agile mindset is crucial for staying ahead of the competition. Additionally, the partnership also allows both brands to experiment with new formats and business models.</p><p><strong>Data-Driven Decision Making:</strong></p><ul><li><strong>Utilize Data Insights:</strong> By leveraging data analytics, businesses can gain valuable insights into customer behavior, market trends, and the effectiveness of their strategies.</li><li><strong>Measure and Optimize:</strong> Continuous monitoring and optimization of key metrics can help businesses identify opportunities for improvement and maximize their ROI</li></ul><p>All in all this <em>A&amp;W-Pret partnership</em> serves as a vital case study for growth product managers. By leveraging strategic partnerships, focusing on customer experience, and embracing data-driven decision-making, businesses can achieve significant growth and market leadership.</p><p>Now, back to main topic — how was my coffee :D For that I would say I’m willing to go back twice a month for their coffee. If you are a coffee person, do give it a try</p><p><strong><em>PS: these are just my views/thoughts as a Product Manager and how I dissect this partnership.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f504e79487" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Success: A Guide to Product Metrics for Leaders & Managers]]></title>
            <link>https://ishaansuri16.medium.com/unlocking-success-a-guide-to-product-metrics-for-leaders-managers-f9318fe45ce3?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9318fe45ce3</guid>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-metrics]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 22:55:08 GMT</pubDate>
            <atom:updated>2024-01-24T22:55:08.688Z</atom:updated>
            <content:encoded><![CDATA[<p>Metrics are crucial for leaders and product managers to gauge the performance of their products and make informed decisions. Measuring the performance is a key requirement and responsibility across the product department hierarchy — whether you’re starting as Associate Product Manager right upto the Chief Product Officer (CPO) position. They provide valuable insights into user behaviour, product adoption, and the overall health of the product.</p><p>Throughout the years, I have been a part of numerous organizations where a lot of focus is placed on the North Start (NS) or primary performance metrics — which is not wrong. However, a key element which is actually missed by a lot is that the <strong><em>NS is a guiding metrics which has to then be broken down into working metrics to attain</em></strong></p><p>As a product leader, navigating the sea of data to find valuable insights can feel overwhelming. Yet, understanding and measuring product metrics is paramount to making informed decisions and driving success. This guide will equip you with the knowledge to unlock the true potential of your product metrics.</p><h4>Breaking Down the North Star: Key Metrics to Track</h4><p>While North Star metrics provide crucial direction, they often require further analysis. By delving into these 4 key categories, we can break down the North Star into actionable insights:</p><p>1. <strong>Organizational/Business Metrics:</strong> These metrics focus on the overall financial performance of the product and its impact on the organization. They provide insights into the product’s contribution to the company’s revenue, profitability, and growth.</p><ul><li>Revenue: Total income generated through sales/subscriptions.</li><li>Profit: Net income after accounting for expenses.</li><li>Customer Acquisition Cost (CAC): Average cost of acquiring a new customer.</li><li>Customer Lifetime Value (LTV): Total revenue generated from a customer over their lifetime.</li><li>Monthly Recurring Revenue (MRR): Recurring revenue generated from subscriptions each month.</li></ul><p>2. <strong>Product Usage Metrics:</strong> These metrics measure how users are interacting with the product. They provide insights into user engagement, feature adoption, and pain points.</p><ul><li>Active users: Users who interacted with the product in a specific period.</li><li>Daily Active Users (DAU): Users who use the product daily.</li><li>Monthly Active Users (MAU): Users who use the product within a month.</li><li>Average Session Duration: Time users spend per session.</li><li>Feature Adoption: Percentage of users using a specific feature.</li></ul><p>3. <strong>User Metrics:</strong> These metrics focus on the satisfaction and loyalty of users. They provide insights into how users perceive the product and their likelihood of recommending it to others.</p><ul><li>Customer Satisfaction (CSAT): Measures user satisfaction with the product.</li><li>Net Promoter Score (NPS): Measures user likelihood to recommend the product.</li><li>Churn Rate: Percentage of users who stop using the product in a specific period.</li><li>Retention Rate: Percentage of users who continue using the product over time.</li></ul><p>4. <strong>Product Health Metrics:</strong> These metrics measure the overall health and stability of the product. They provide insights into technical issues, performance bottlenecks, and bugs.</p><ul><li>Uptime: Percentage of time the product is available for use.</li><li>Mean Time to Resolution (MTTR): Average time to resolve technical issues.</li><li>Number of Bugs: Total number of bugs reported.</li><li>Customer Support Tickets: Number of tickets received regarding product issues.</li></ul><p>5. <strong>Marketing Metrics (Optional)</strong>: These metrics can help product managers to understand how effective their marketing campaigns are and how they are attracting new users.</p><ul><li>Website Traffic: Number of visitors to your product website.</li><li>Conversion Rates: Percentage of visitors who take a desired action.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*08jWbA68VVud8OqQgA3Xng.png" /><figcaption>Image Credit — Ishaan Suri</figcaption></figure><h4>Beyond Numbers: The Power of Data-Driven Decisions</h4><p>Remember, metrics are more than just numbers; they tell the story of your product’s performance. By actively tracking, analyzing, and communicating these insights, you can:</p><ul><li>Define clear goals and measure progress effectively.</li><li>Prioritize features and allocate resources strategically.</li><li>Identify areas for improvement and optimize product performance.</li><li>Make informed decisions based on real data, not assumptions.</li><li>Communicate results and share findings with your stakeholders</li></ul><p>Understanding the metrics that matter most will not only help you make better decisions but also drive product success. Remember, effective product leadership lies in not only tracking the numbers but also in harnessing their power to drive success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9318fe45ce3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Product Feedback Loops as a Product Manager]]></title>
            <link>https://medium.com/design-bootcamp/building-product-feedback-loops-as-a-product-manager-b1c2bffedc1c?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1c2bffedc1c</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[user-feedback]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Wed, 23 Nov 2022 17:15:22 GMT</pubDate>
            <atom:updated>2022-11-30T05:02:32.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*FYD94pVksskmJjSqERWrrQ.png" /></figure><p>We always build products for problems faced by a specific set of customers. However, sometimes we overlook checking back with them to see whether what we built and launched is solving their problem or if it is just another tool sitting in their repository failing to solve its purpose. This kind of situation sheds light on a very well-known problem. The problem of customer feedback. Let’s unpack this and try to understand why it’s a key, important arsenal for the product manager</p><h3>What is ‘Product Feedback’</h3><p>Product Feedback is a continuous loop that allows the users of the product to submit what they ‘feel’ about and how they use the product. It is <em>hearing everything</em> about the product but from the actual regular users. They share their likes, dislikes, suggestions, and much more about your product, for you to decipher and map it to the created product vision. Since we roll out multiple iterations of the product in the market, feedback is more of a continuous circle instead of a one-off situation, therefore becoming a feedback loop</p><h3>How to devise a Product feedback loop strategy</h3><p>Feedback for any product is always a continuous and recurring cycle. As a product manager, the feedback strategy for your product will not only help you measure and analyze but also learn and get the prime answer to ‘<em>What Next’.</em></p><p>However, to obtain these answers we first need to develop a way to create a process and build a strategy that collects this continuously from our customers. Here’s a well-known accustomed feedback framework that I use in my product journey:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*A9PVDYMX4ConpnAPdsHfxA.png" /><figcaption>Image Credit — Ishaan Suri</figcaption></figure><ol><li><strong>‘Talk’ and gather: </strong>the start of anything new in a product is with gathering customer inputs and insights. Talk, hear and gather what the customers are saying about your product. This could be done in multiple ways (which I have highlighted in the Arsenal section of this article) however, keeping your industry type &amp; customer type in mind is a very important identification to make here. Identify them carefully to select your tools.</li><li><strong>Bucket the feedback: </strong>once you have collected your customers’ inputs and feedback, carefully categorize them into various buckets to help you understand the importance of each. The heavier the bucket, the easier for you in deciding the relevance and importance</li><li><strong>Pick your battles: </strong>here is the fun part. From the previous step, you will have multiple buckets available. Choose the bucket(s) which are most impactful both for your customers and also align with your business goals, priorities &amp; roadmap. Here you will need to have some conversations with your stakeholders, analyze the available datasets and then pick your most important battles. Remember not all battles are worthwhile to be fought.</li><li><strong>Implement the feedback: </strong>once you have identified the right categories, proceed forward with making those updates and changes which customers suggested and are highly impacting the business thereby IMPROVING THE PRODUCT FOR ALL PARTIES</li><li><strong>Follow up: </strong>since every change brings opinions, always follow up with your customers to know their feedback</li></ol><h3>Why is it important to have a feedback loop, and what are the benefits?</h3><p>For any changes or updates, there needs to be an appropriate value identified and answer ‘what will be the impact’. The same is the case with the feedback loop as well. A streamlined feedback loop strategy helps in:</p><ol><li><strong>Improving the potential of the product</strong>: we always build for customers and create a business opportunity by solving their problems. Your customers are always able to identify the edge cases of using the product which we might have missed while building the product or a new feature within the product. A continuous feedback cycle helps you to evaluate those suggestions and recommendations as a potential in improving your product</li><li><strong>Build your value and data-driven product roadmap: </strong>as product managers, we are required to have a roadmap of our product to bring out the product vision &amp; direction for the execs. Customer feedback acts as one of the necessary tools for getting the inputs and ‘data’ required for building your product roadmap.</li><li><strong>Manage your organizational goals: </strong>finally, businesses survive in the market when they are fulfilling and solving a pain point. Hearing from your customer about their experiences with the product defines and helps the organization create both the short-term and long-term goals that they want to achieve.</li></ol><h3>Arsenal for creating feedback loop strategy</h3><p>While by now we understand what is a feedback loop and how to create a successful strategy. During my years in product, I have found out that having the right set of tools to help get things done is very important for a product manager. Here is a list of the necessary tools to help us build the right feedback loop strategy:</p><p><strong>Explicit Feedback</strong>: those feedback methods where we openly approach and ask the customers for their feedback. This method generally requires us to have some kind 3rd party tool integrated into our system to collect and gather the responses from the users. What I recommend here is the following set:</p><ul><li><strong>Feedback surveys</strong>: Use Typeform or SurveyMonkey to create and send a set of questions to your customers to get their feedback</li><li><strong>User Interviews</strong>: One of my personal favourites, I use UserInterviews to talk to customers and get their direct feedback. The trick here is to have a well-written pitch and agenda within the questions you want to ask your users so that you get their honest replies</li><li><strong>Usability testing</strong>: This involves testing the product with either your existing or potential new users to simply understand how easy or difficult the usage of our product is for them. This is mostly done in 2 ways, either by integrating an in-app feedback system or by getting on users on call to test the product live and share their experiences. My approach is always to use the former method here as a) it helps you reach the masses b) doesn’t require someone to specially connect and block their times for you c) the most important one, you collect a lot of data which you can then analyze with all the collated responses. I prefer to use HotJar here</li></ul><p><strong>Implicit Feedback</strong>: those kinds of feedback methods where we hear from the customers ‘indirectly’. Though we do not reach out to the customer to share their feedback, for every product this kind of feedback always exists in the surroundings. For this, we just need to be aware of where to look for these as product managers. What I prefer as the modes are as follows:</p><ul><li><strong>Customer Support Tickets</strong>: there’s no dearth of the number of tickets which are raised as requests by our customers to the support team. Simply dive into all such tickets and identify the feedback.</li><li><strong>Online Ratings and Reviews</strong>: users (especially those who are not happy) are very active about posting their ratings and feedback on the online stores. Product Managers should start looking into these to get honest customers’ feedback without asking them directly to share one. Yes, reaching out to them to get a better understanding of their viewpoints is secondary but this tool</li><li><strong>Social Media</strong>: an extension from the last one, users are very vocal about their experiences on different social media channels. You can start leveraging those posts, comments, and other available media types to hear what customers have to say about your product and its usage</li></ul><p>Can you think of more ideas of how we can improve getting the customers’ feedback — please share it in the comments section below as I would like to learn more and use them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1c2bffedc1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/building-product-feedback-loops-as-a-product-manager-b1c2bffedc1c">Building Product Feedback Loops as a Product Manager</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[Debugging Churn as a Product Manager]]></title>
            <link>https://ishaansuri16.medium.com/debugging-churn-as-a-product-manager-30b0c0b4324b?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/30b0c0b4324b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[churn]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-analytics]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Fri, 21 Oct 2022 19:09:49 GMT</pubDate>
            <atom:updated>2022-10-21T19:09:49.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-mcIhAGtZ6bg-tEzgq7HFg.png" /><figcaption><a href="https://webengage.com/blog/5-effective-proven-strategies-to-reduce-your-customer-churn-rate/">Image Courtesy</a></figcaption></figure><p>Churn rate — a crucial metric that product managers often use from their arsenal while working on improving their products and businesses. While churn rate is used by the majority of the organizations, like any other approach it has its merits, shortcomings, and some misconceptions.</p><h3><strong>However, first let’s consider what churn signifies:</strong></h3><p><strong>Churn</strong> is referred to as the number of customers that leave and stop using the product during a given period. Any fluctuations in the churn for the product could shed some great insights about the business ← → customer interactions, competition &amp; their services, customer’s overall satisfaction, pricing, services offered and much more. As a Product Manager there’s a need to measure and keep an eye on this rate, as it also refers to the loss in overall business revenue because of such exits by their product users.</p><h3><strong>How to calculate your product churn rate</strong></h3><p>Typically churn rate can be classified into 2 major heads: Customer Churn rate and Revenue Churn rate. Both these churn rates are important for the business to measure the health &amp; acceptability of the product.</p><ul><li>Let’s first talk about the <strong><em>Customer Churn rate</em></strong>: this is calculated simply as (Canceled Customers in the last X days ÷ Active Customers X days ago) x 100</li></ul><p>On the face of it this looks easy however the important factor here is identifying the value of X. Depending on your business type (B2B, B2C, etc…) product offering, target audience, customer session and active rate, the value of X can be ranging from 3–365 days. As a PM it is in our purview to work with the business and identify what is the best number which will help us define the activeness and churn rate of the customer</p><ul><li>The next here is <strong><em>Revenue Churn rate</em></strong>: similar to customer, the revenue churn rate is calculated as [X (time) Recurring revenue loss due to user exits ÷ X (time) total revenue] x 100</li></ul><p>The value of X and the time is depending on the actual revenue metrics acceptability by the business. In most of the cases this is for a month to help the organization measure the health of the product.</p><h3><strong>Misconceptions about churn</strong></h3><ol><li><em>‘Standard churn’ number for every business</em>: most of the businesses generally calculate their churn on a 30 day basis and this is usually followed without understanding all the underlying factors that go into identifying the right time frame. Hence it becomes one of the biggest misconceptions that a churn rate should be calculated for 30 days and should remain standard forever. As the business evolves and the conditions change with time, the time frame is something which first needs to be identified, implemented in the tracking, followed by regularly adjusting this factor based on the customer acceptability, repeat returns on the platform and more industry specific factors.</li><li><em>Most Ideal acceptable churn</em>: ok, let’s take a pause to think a bit more about this. Most businesses and product managers operate on the premise that their offerings are unique (which is essentially true since your product is earning a revenue so you would be offering something different from your competitors) If we all agree with this statement, how can we say that there is a ‘most ideal’ and general churn rate of X% and since it falls in this range, my product is healthy. Since every product in the industry is different, so should be the churn rate for each of them. Pick a churn rate for your product based on what’s the most suited for your product and business type.</li><li><em>Every churn is bad for the business</em>: I’m sure all of us would have seen alarm bells ringing when there’s a word about churn in the organization. But let us think rationally and see if it is really a fire kind of a situation or not. We start analyzing churn primarily by checking the data sets and trying to talk to the churned users. This helps us in getting the bucket categories of reasons as to why they left our product. While these are the initial steps, are they good enough? The answer here is NO. Since a great product solves the problem for a specific set of users and not for everyone, in the same way not <strong>EVERY</strong> churn can be termed as a bad one.</li></ol><h3><strong>Now let’s check out some ways to to manage churn</strong></h3><p>To better manage the churn rate for your product and its relevance while calculating the rate, I follow a simple framework of use case vs audience plot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*z9nU-vKvbCG0v7De0tEILQ.png" /><figcaption>Image Credit — Ishaan Suri</figcaption></figure><ol><li><strong>Identify the right churn user: </strong>to better manage your product churn, the first and foremost step is to identify the exact current users who are your target audience. In our previous diagram every user can be identified into a quadrant by bucketing them in the right one and the ability to do this correctly is an art which PMs should learn.</li><li><strong>Review your full customer experience and lifecycle: </strong>in my view a lot of times users drop off and never return because of 2 major reasons, either the product is too complex to use or the experience they have had with the product is not pleasant. As a business the onus lies on us to regularly review the customer experience and ease out every pain in their journey or lifecycle to keep them hooked and engaged with our product.</li><li><strong>Focus on the right user retention: </strong>this might sound like a paradox but instead of focussing on your churn or bounce, always focus on user retention. A retained user is highly likely to jump into the next higher tier pricing and engage more with your product. From the qualitative side, they act as our product promoters and manage more leads followed by conversion. But the catch here again is the ‘<em>right user’</em></li></ol><p>Finally, <em>the hard fact</em>: even if you employ the best of the best strategies and brains behind attaining a zero churn for your product, churn is inevitable and unavoidable. There will ALWAYS be some amount of churn customers for your product therefore manage your product churn effectively. Remember the biggest danger in this game is always <strong>not fighting hard to reduce churn.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30b0c0b4324b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Considerations — 2]]></title>
            <link>https://ishaansuri16.medium.com/product-considerations-2-746a89e494c0?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/746a89e494c0</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[go-to-market]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-launch]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Mon, 03 Oct 2022 13:46:28 GMT</pubDate>
            <atom:updated>2022-10-08T13:29:04.737Z</atom:updated>
            <content:encoded><![CDATA[<h3>The importance &amp; depths of a Go-To-Market Plan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2Wz9N_T2B0ssk3NUmo3Rw.jpeg" /><figcaption><a href="https://www.leadfuze.com/go-to-market-strategy/">Image Courtesy</a></figcaption></figure><p>Building a great product is half the battle won,<strong><em> then what is the other half of the battle?</em></strong></p><p>Usually, each product launch is followed by a sigh of relief along with the expectation that the product will be a success and it will land safely in the hands of the customers. During the preparation for the launch cycle, we as product managers collaborate with the development teams, data analysts, and designers to get the product in the state of readiness and launch in the market. Is our role limited to just features, stories, grooming, wireframes, and announcing “let’s go live”? Well, that was something I thought during my early days as a PM. However, over the years, I have learned that a product needs to be ‘packaged, dispatched, and marketed’ correctly to make it a success. I’m sure all of us would have encountered issues like the following:</p><ul><li>Sales executives facing challenges in understanding the product, customer value proposition for existing users and pricing of the product.</li><li>The Marketing Team is struggling to develop the right positioning, and messaging statement. They may also not be able to identify the right channels which should be used for this product promotion</li><li>New queries about the product or feature launch flooding the Customer Support members and the knowledge gap amongst their team about the product preventing them from addressing these queries and helping the users.</li><li>Customer Success team is not able to position and faces difficulties in pitching the new product to it’s existing customers.</li></ul><p>All of a sudden the hard work which was put into launching the product and the euphoria, go in vain with these tethering issues since now we are rambling to sort these for the business to deliver value to its customers — a problem statement very common. So how do we mitigate the whole vicious cycle with:</p><h3><strong>Go-To-Market Plan</strong></h3><h4>What of Go-To-Market Plan</h4><p>Go-To-Market essentially is a blueprint document of how the business <em>AS A WHOLE</em> will work and collaborate together to make the product/feature launch a success. The GTM Plan is a method of ‘programs’ which helps bridging the potential gaps by building a clear understanding across the business of how the value will be delivered to the customers, with the new product/feature release in the market. Be cautious of not confusing this with the product strategy, marketing strategy, or business strategy, as all of these are more of <em>planning</em> strategies whereas the GTM is more of an <em>execution short-term </em>type strategy</p><h4>Why is there a need for the GTM Plan</h4><p>The GTM plan is needed mainly for <em>reducing the risk of a failed product launch</em> and at the same time <em>clear all the doubts clouding the launch</em> across the business. Since the GTM plan is intended for all the stakeholder teams involved in the product, the plan needs to be created keeping in mind their needs and the level of understanding. This ensures smooth functioning and support from these departments at the time of the launch.</p><p>As we have identified the struggles faced by different teams of the business with a new launch and the importance of a GTM plan in solving these struggles, let’s now try to plot a scheme of how to create a successful GTM plan for the product launch with these steps.</p><p><strong>Need Identification</strong>: first and foremost as a PM you need to identify if you need a GTM plan or not. Generally speaking, there are 3 most common types of product releases, ranked in the order of importance as follows:</p><ul><li><strong><em>A new product release</em></strong> is more like the first version of the product which will be released in the market for the very first time. The product never existed before this.</li><li><strong><em>A new product version</em></strong> release is a combination of big features clubbed together to be released for your existing product. This is more like big problem- solving solutions and features being added to the existing product</li><li><strong><em>A new product fix release</em></strong> is an incremental product release for an existing feature which has been improved and fixed to better suit the user’s needs</li></ul><p>With the new product fix release all our stakeholders and users are aware of the what and the how of the existing feature, so it does not require a special plan and time to invest in building a GTM plan. When we talk about a new product release and a new product version release, this is somewhat a blind spot for all the members of the business and users. Hence it becomes very important that this type of release to be explained across to help everyone understand what is this release going to be all about</p><ol><li><strong>Product Objective: </strong>once we have identified the need for the GTM, it’s now time to plan the GTM. This starts with the product or release objective. A right product objective establishes a clear understanding of what our efforts are directed towards and why. A PM is the bridge between the current business and what the future of the business could potentially look like, so reiterating the product objective sets up the right tone in our teams internally.</li><li><strong>Problem: </strong>since every product or release is targeted at solving a particular problem for the customer, a well documented pain point that we are trying to solve for, iterates and brings back the focus into the launch.</li><li><strong>Determining the target audience</strong>: we always solve for a specific target audience segment and not the complete population so identifying the most affected user’s profile which will drive value from this product or release, is crucial.</li><li><strong>Solution &amp; the USP</strong>: this is the space to showcase the actual developed solution with the key differentiators that the product or release provides to its users, in comparison to your competitors. Highlight every big product detail about the release in this section. It is important to have the differentiators clearly structured as this will be the selling proposition for the sales and marketing teams for the identified user segment.</li><li><strong>Pricing Mix: </strong>now this is a tricky territory. A lot of factors go into building the right pricing strategy for the product including and not limiting to multiple stakeholder discussion spanned over numerous sessions. However once finalized, it needs to be articulated to bridge any gaps which may arise when talking to the potential users.</li><li><strong>Marketing &amp; Sales Plan</strong>: an important piece of the plan is preparing for the product marketing and articulating the required information for generating sales leads. Although, as the product manager you would not have direct control over these activities per say, however as the SME for the product, helping the marketing team identify the channels for distribution and supporting the sales team in making the plans of upselling to the business clients, ensures the success of the GTM plan.</li><li><strong>Support Plan</strong>: since the support team is the first responders for any and every customer queries, a support structure to manage these with all the relevant information is a vital part here. This includes preparing new &amp; updating the existing FAQs in addition to a live customer support channel setup like support email channel, chat engines, voice calls and many more. In the end, remember we are here to solve for the business and for our customers so having this setup puts us in the right path forward.</li><li><strong>Key Business Metrics: </strong>Here’s the most critical piece of the plan in my view. With any product launch or version launch, we need to clearly articulate the key metrics which we will track to identify the success. These key business metrics should be well communicated so that every domain of the business works towards impacting that positively and driving towards the path of progress with the launch itself.</li></ol><p>One of the most widely asked questions is when is the right time to be working on the GTM plan. Although there is no set-in-stone as to when this should be created, I recommend a ‘Parallel Approach’ — once the stories have been handed over for development to the technical team and the coding begins, we can start working on the GTM Plan in parallel /in tandem. This helps us manage our capacity and most importantly bring the alignment across the business, well in advance.</p><p>Though every organization is different and every release is unique, the above is a more generic approach in what a Go- to market plan could potentially look like. Although there might be some nuances based on the type and nature of the business or product, if we aim to have a GTM plan in full force, we would be able to guide the product in the right direction for the end goal. Finally, here’s a snapshot of what could be an example of the Go-to-market plan which I have been using for a number of years (this is a sample case and the contents here are for illustration purposes only)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoGu4viZCNnG1HOqiG9NuQ.png" /><figcaption>Image Credit — Ishaan Suri</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*lA4AlTQPsITFGvWhqDZElQ.png" /><figcaption>Image Credit — Ishaan Suri</figcaption></figure><p>Let me know your thoughts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=746a89e494c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Review]]></title>
            <link>https://ishaansuri16.medium.com/product-review-55062188d9ab?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/55062188d9ab</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Thu, 22 Sep 2022 17:18:53 GMT</pubDate>
            <atom:updated>2022-09-22T17:20:28.569Z</atom:updated>
            <content:encoded><![CDATA[<h3>Omnipresence of Whatsapp</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*UlyzzhuWsbH1U2hCUfRl-Q.jpeg" /></figure><p>Chatting has been and still is the most common form of communication in the world. Today it is an unparalleled tool to share our thoughts with friends, family, and peers. Communication has become an indispensable and integral part of our daily lives, something we are so hooked on without even realizing.</p><p>Let’s talk about the digital world today. One of the most popular communication platforms (if not the biggest) is Whatsapp. Before we go too deep, some numbers hereto digest (as per <a href="https://www.businessofapps.com/data/whatsapp-statistics/">Business Of Apps</a>)</p><ul><li><strong>Revenue for 2021</strong> : $8.7bn</li><li><strong>Number of countries</strong>: 180 in 60 languages</li><li><strong>Active users in 2021</strong>: 2.2 bn</li><li><strong>Percentage of internet users using WhatsApp</strong>: Excluding China, 69%of internet users use WhatsApp (GlobalWebIndex)</li><li><strong>Daily activity on WhatsApp</strong>: Over 100 billion WhatsApp messages are sent and over two billion minutes are spent on WhatsApp voice and video calls per day (Facebook)</li></ul><p>Whatsapp, right from its inception has been on a mission to <em>help people have the next best experience to an in-person conversation</em> when they want to communicate with anyone. And their recent presence and updates allows them to dominate this space. Let me deep dive more about how they are slowly crawling into daily unconventional conversational streams.</p><ul><li><strong>Professional ← → Chat Experience</strong> : while browsing my Whatsapp recently I stumbled upon a very small change to their homepage layout. An icon somewhat similar to their groups feature. At first I thought it was for groups and now they probably had more clear and dedicated space. Curious to explore more, I clicked onto it and woahhhh, this was something new. Communities. Whatsapp (in specific regions) now allows to group users of common interest into one community and provide them blanket updates. This is a very useful feature especially in the post covid era when digital communication reached a brand new level. Given more thought, you will realize that this was something which was always available but now allows a localized yet commercial approach. Think about the use cases: Classroom communities to distribute homework, talk about attendance records, Parent teacher updates and meetings. This is like a way to organize and <em>group </em>groups — something on the likes of Slack Workspace but now on Whatsapp. While Slack allows search for groups by non-members and users joining those groups, groups in communities will be more secure/private as people will not be allowed to discover other groups in their community. They have also taken care of the privacy issue here, as none of the contact info of members in a group is accessible for other groups in the same community. Now, this is one of the prime examples of Product-Led-Growth and product extension using the core existing capabilities of the product, shown here by Whatsapp while opening a whole new (now official) target audience</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*KNifaR9TCVEhj7MPWL60VQ.png" /><figcaption><a href="https://about.fb.com/news/2022/04/our-vision-for-communities-on-whatsapp/">Image Courtesy</a></figcaption></figure><p><strong>Commerce ← → Chat Experience</strong>: very recently I read that Whatsapp and Reliance JioMart (from India) have come together to allow users to have a full buying experience on Whatsapp for their grocery needs without leaving the app. Browse products, add to cart, pay and get it delivered — all within Whatsapp without opening any other app. This opens their avenues for entering directly into the chat commerce space. No need to install another grocery delivery app or browse to find the required items. Simply send a Hi to a dedicated Whatsapp number and your whole experience will be available within the chat window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfwJpncqfnITtwzoGIcYLQ.jpeg" /><figcaption><a href="https://indianexpress.com/article/technology/tech-news-technology/whatsapp-announces-partnership-with-jiomart-in-india-for-end-to-end-shopping-experience-8118779/">Image Courtesy</a></figcaption></figure><p>This was the user side of the story. Now let us see what’s in store for Whatsapp. Based on these updates, Whatsapp will now be able to know what happens in your household apart from the regular conversation. They are able to collect data about your preferences, what is happening around you and what is affecting you the most. Apart from this, the average session time on the app would increase by multiple folds which is an important aspect and metric of its operations. However, the big picture play here is collection of Users Behavioral Data, Personal information and becoming the master warehouse of this data. The more time you spend on their system, the more you will inadvertently ‘share’ about yourself, your likes and preferences.</p><p>When you think about this, Whatsapp is slowly becoming what you call a super app. By introducing these features, the app is slowly becoming an indispensable part of our life. Who knows what’s next: get results of your child’s tests on whatsapp — no need for physical report cards or those bulky non sophisticated school portals all including product recommendations based on the child’s performance.</p><p><strong>Key learnings from a Product Managers’ perspective</strong></p><ul><li><strong>Product Led Growth</strong>: let your users experience and test your product. They will get hooked and adopt only by choice and not by force.</li><li><strong>Use existing capabilities to unlock new avenues</strong>: one of the prime ways of acquiring new users and helping in increasing the product adoption QUICKLY is by utilizing the core of your platform to open new segments</li><li><strong>Listen for problems</strong>: always solve for a real world customer pain point and build a case of how your product or offering can solve that for them. Your customers will always highlight what concerns they have. Just listen and ‘read between the lines’ to identify your solution</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55062188d9ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Considerations]]></title>
            <link>https://ishaansuri16.medium.com/product-considerations-46dddc4fd231?source=rss-c1c5055d5356------2</link>
            <guid isPermaLink="false">https://medium.com/p/46dddc4fd231</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Ishaan Suri]]></dc:creator>
            <pubDate>Wed, 07 Sep 2022 21:12:39 GMT</pubDate>
            <atom:updated>2022-09-08T03:27:21.210Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quick Wins — from the lens of a Product Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*drgAwk2MEf1KzvIsRXx_kQ.jpeg" /><figcaption><a href="https://blog.searchmetrics.com/us/content-optimization-5-quick-wins/">Image Courtesy</a></figcaption></figure><p>Over the years, I have been a part of several ‘Quick Win’ conversations as a Product Manager. Stakeholders across various businesses or organizations I have worked with, often come up with requests like:</p><p>- Let’s change the button colour</p><p>- How about we add this or remove that</p><p>- Let’s change the image size</p><p>- We should add this section on the homepage</p><p>In the early days of my PM career I was always quick to respond that ‘It does not look complex’ or ‘It’s fairly easy and simple, I’ll get going with this’. However, over the years I have learned the art of asking my own set of questions to any such requests. Let’s just dive straight in.</p><p>Quick wins can be defined as solutions which are easy, fast and economical to implement, easily reversible and deliver a positive impact to the business following the core vision. Let’s break each and every element of this definition now:</p><ul><li><strong>Fast and economical to implement</strong>: an idea would be considered a quick win when it is simple and yet cost effective to implement so that it does not interrupt your long term plans and committed items. If it does hamper the long term goals, then you’re venturing into a whole new universe where you could end up be chasing and reacting instead of envisioning &amp; pro-acting. And anything that takes you away from this, ends up making your domain futile, since its core purpose is to solve problems in the first place.</li><li><strong>Easily reversed</strong>: Let’s admit we cannot always be right with whatever we do for a product. Whether it is an internal idea or an external one, things may and at times tend to go downhill. It’s crucial to evaluate that when such ‘wins’ are rolled out, they can be easily rolled back as well without hampering the product overall.</li><li><strong>Deliver a positive impact to the business following it’s core vision</strong>: every idea which is brought to the table is brought assuming that this will positively impact the business or business metrics. However, the key element which is sometimes overlooked is that most of these ideas can result in the product deviating from the core vision for the business.</li></ul><p>Now once you have established the answers to these 3 key elements, the next step is to finalize - understanding the why and the how’s. It is not always about the difficulty &amp; estimates of the ask but the background and the immediate anticipated results from the same. The questions (rightly to be answered) here are:</p><ul><li><strong><em>How big this change will be</em></strong></li><li><strong><em>Will there be an impact on the revenue or metrics</em></strong></li></ul><p>Don’t hesitate to reach out to your stakeholders for these questions and help them figure out these answers as well</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*j4r53p77-uZlY6WRBivWuA.jpeg" /><figcaption><a href="https://documentmedia.com/article-3081-Quick-Wins-or-Big-Winshellip.html">Image Courtesy</a></figcaption></figure><p>Our product backlog will always consist of tasks big and or small. My two cents regarding this is that we should not be against the idea of a Quick Win till we can ascertain how impactful it would be and how much it aligns with the organizational vision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46dddc4fd231" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>