<?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 Tejas M Bhat on Medium]]></title>
        <description><![CDATA[Stories by Tejas M Bhat on Medium]]></description>
        <link>https://medium.com/@tejasmbhat?source=rss-ca3374ce7fdd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pLmm9YV-FCYo4Xos.</url>
            <title>Stories by Tejas M Bhat on Medium</title>
            <link>https://medium.com/@tejasmbhat?source=rss-ca3374ce7fdd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:54:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tejasmbhat/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[The Art and Science of Strategy in Product Management]]></title>
            <link>https://medium.com/@tejasmbhat/the-art-and-science-of-strategy-in-product-management-be05f5eb4c49?source=rss-ca3374ce7fdd------2</link>
            <guid isPermaLink="false">https://medium.com/p/be05f5eb4c49</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Tejas M Bhat]]></dc:creator>
            <pubDate>Fri, 08 Sep 2023 14:10:55 GMT</pubDate>
            <atom:updated>2023-09-08T14:10:55.971Z</atom:updated>
            <content:encoded><![CDATA[<p>Introduction</p><p>In the dynamic world of product management, success hinges on a well-crafted strategy. The role of a product manager is akin to that of a captain navigating a ship through treacherous waters. To reach their destination, they must chart a course, adapt to changing conditions, and keep their crew (the development and marketing teams) motivated and focused. This article explores the intricate art and science of strategy in product management, emphasizing its critical importance in bringing successful products to market.</p><p>Understanding Product Management</p><p>Before delving into the nuances of product management strategy, let’s first establish a clear understanding of what product management entails. Product management is a multifaceted discipline that involves overseeing the entire lifecycle of a product, from inception to retirement. It encompasses market research, idea generation, concept development, design, development, testing, launch, and ongoing maintenance and improvement.</p><p>Key Responsibilities of a Product Manager</p><ol><li><strong>Market Research</strong>: A product manager must have their finger on the pulse of the market. This involves studying competitors, understanding customer needs and pain points, and staying attuned to industry trends.</li><li><strong>Idea Generation</strong>: Product managers often play a pivotal role in brainstorming and generating innovative ideas for new products or improving existing ones.</li><li><strong>Roadmap Creation</strong>: Creating a product roadmap that outlines the vision and strategy for the product is crucial. This roadmap guides the development team in executing the plan effectively.</li><li><strong>Cross-functional Collaboration</strong>: Collaboration with various teams such as development, marketing, sales, and customer support is essential. Product managers act as the bridge between these departments to ensure alignment with the product strategy.</li><li><strong>Product Development</strong>: Overseeing the development process, setting priorities, and making key decisions about features and functionalities are integral aspects of the role.</li><li><strong>Product Launch</strong>: A successful product launch requires meticulous planning and execution. Product managers must coordinate efforts across teams to ensure a smooth launch.</li><li><strong>Performance Monitoring and Improvement</strong>: After launch, ongoing monitoring, analyzing data, and implementing improvements based on user feedback are crucial to a product’s success.</li></ol><p>The Importance of Strategy in Product Management</p><p>Strategy in product management is the North Star that guides every decision and action throughout a product’s lifecycle. Without a clear and well-thought-out strategy, a product is like a ship without a compass, drifting aimlessly in a vast sea of competition.</p><ol><li><strong>Setting Clear Goals and Objectives</strong>: Strategy starts with defining clear, measurable goals and objectives. These goals serve as the foundation upon which all subsequent decisions are based. They provide direction and purpose for the product team.</li><li><strong>Market Segmentation and Targeting</strong>: A well-crafted strategy involves identifying specific market segments and target customers. This ensures that the product addresses the needs of a particular audience rather than trying to be all things to all people.</li><li><strong>Competitive Analysis</strong>: Understanding the competitive landscape is essential. A solid strategy involves analyzing competitors’ strengths and weaknesses to identify opportunities for differentiation.</li><li><strong>Risk Mitigation</strong>: A good strategy anticipates potential risks and challenges and includes plans to mitigate them. Whether it’s technological hurdles, changing market conditions, or unexpected setbacks, a strategic approach prepares the product team to navigate these obstacles.</li><li><strong>Resource Allocation</strong>: Resources, including time, money, and manpower, are finite. A well-defined strategy helps allocate these resources optimally, ensuring that the most critical aspects of the product receive the necessary attention and investment.</li></ol><p>Components of an Effective Product Management Strategy</p><ol><li><strong>Market Research</strong>: A thorough understanding of the market is the foundation of a solid strategy. This includes studying market trends, customer behavior, and the competitive landscape. Tools like market research surveys, user interviews, and data analysis are instrumental in gathering this information.</li><li><strong>SWOT Analysis</strong>: Conducting a SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) helps identify internal and external factors that can impact the product’s success. It provides insights into where the product stands in the market.</li><li><strong>Value Proposition</strong>: A clear and compelling value proposition defines what makes the product unique and why customers should choose it over alternatives. This should be a central component of the product’s strategy.</li><li><strong>Product Roadmap</strong>: The product roadmap outlines the journey from concept to market. It includes timelines, milestones, and prioritization of features and enhancements. The roadmap should align with the product’s strategy and goals.</li><li><strong>Go-to-Market (GTM) Strategy</strong>: A successful product launch is contingent on a well-defined GTM strategy. This involves decisions about pricing, distribution channels, marketing campaigns, and customer support.</li><li><strong>Feedback Loop</strong>: Continuous feedback from customers and stakeholders is invaluable. A strategic product manager establishes mechanisms for gathering and incorporating feedback throughout the product’s lifecycle.</li><li><strong>Iterative Approach</strong>: In today’s fast-paced business environment, flexibility is key. A strategic product manager understands the need for iteration and is willing to adapt the strategy as new information emerges.</li></ol><p>Strategies for Different Stages of Product Development</p><ol><li><strong>Early-Stage Strategy (Concept to Development)</strong>:</li></ol><p>-Focus on validating the product concept through market research and user feedback.</p><p>-Develop a Minimum Viable Product (MVP) to test key hypotheses.</p><p>-Prioritize features that deliver the most value to early adopters.</p><p><strong>2. Mid-Stage Strategy (Development to Launch)</strong>:</p><p>-Define the product’s unique selling proposition (USP).</p><p>-Build a cross-functional team with a shared understanding of the product’s goals.</p><p>-Develop a comprehensive marketing and launch plan.</p><p><strong>3. Late-Stage Strategy (Post-Launch)</strong>:</p><p>-Monitor key performance indicators (KPIs) to assess the product’s success.</p><p>-Gather user feedback and prioritize feature enhancements.</p><p>-Consider expansion into new markets or customer segments.</p><p><strong>Conclusion</strong></p><p>In the world of product management, strategy is the linchpin that holds everything together. It provides direction, purpose, and a roadmap for success. Effective product managers are not just tacticians; they are strategic thinkers who understand the importance of aligning their product’s goals with market needs.</p><p>In today’s competitive landscape, where customer expectations are constantly evolving, the role of strategy in product management has never been more critical. It is the compass that guides the ship through stormy seas, the blueprint that shapes the product’s journey, and the key to delivering value to both customers and stakeholders.</p><p>As the product management discipline continues to evolve, those who master the art and science of strategy will stand out as the captains who steer their products to victory in a challenging and ever-changing market.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be05f5eb4c49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing dip in metrics as a Product Manager]]></title>
            <link>https://medium.com/@tejasmbhat/analyzing-dip-in-metrics-as-a-product-manager-eb5343a64e63?source=rss-ca3374ce7fdd------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb5343a64e63</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[revenue]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[hypothesis-testing]]></category>
            <dc:creator><![CDATA[Tejas M Bhat]]></dc:creator>
            <pubDate>Thu, 31 Aug 2023 20:56:39 GMT</pubDate>
            <atom:updated>2023-08-31T20:56:39.913Z</atom:updated>
            <content:encoded><![CDATA[<p>Often as a Product Manager, we find ourselves in a situation where the metrics we are responsible for dips and we get a few mail/slack messages from the top management seeking updates. I am pretty sure everyone has faced this situation at least in your time as a Product Manager. Today, let’s see what can be done in such a case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0lBhxAOSfVrBc34__OY7A.png" /></figure><p>Whenever you see a dip in a top line metric, the first thing you need to do is… not panic! Yes, data is your friend and you always make use of your friend.</p><p>Try to break down a metric into smaller sub-metrics.</p><p>For example, if you see a dip in revenue, try to split the revenue into granular metrics. In this case, revenue can be defined as Daily Active User x (Buyer / Daily active User) x (revenue / buyer), and compare this data with another period which was stable.</p><p>If the major difference is coming from say Daily Active User (DAU), then this is an indicator that players who logged in are lesser compared to how many logged in in the previous period.</p><p>Again, try to break down DAU further, which can be new install, lapsed returner and continuing players. Say, if you see the major difference coming from continuing users, then come up with a few hypotheses on why this might be happening.</p><p>One sample hypothesis can be that continuing players are not logging in because a content in the game is no longer running. Now that we have a hypothesis, you can easily validate with data and check if there is any missing content, and/or any similar pattern previously when the content was turned off.</p><p>To summarise, whenever there is a dip in data, always try to drill down the data to get to the bottom most layer, and then come up with hypotheses and validate.</p><p>A bonus tip would be to ask the Analytics team to build a dashboard with top to bottom metrics with a few filters, so that you can use the dashboard anytime and need not spend time waiting for an analyst to share data with you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb5343a64e63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A/B testing in Product Management]]></title>
            <link>https://medium.com/@tejasmbhat/a-b-testing-in-product-management-9e5a47afe316?source=rss-ca3374ce7fdd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e5a47afe316</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hypothesis]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Tejas M Bhat]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 15:01:41 GMT</pubDate>
            <atom:updated>2020-07-08T17:03:07.038Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of Product Management, the term A/B testing is heard in plenty. So today, let’s understand A/B testing better.</p><p>In simple words, A/B testing is a mechanism to test a hypothesis.</p><p>To do an AB test, there are always four parameters involved:</p><ol><li>A hypothesis</li></ol><p>A hypothesis is a statement which might or might not be true. It is a statement which can be proven or disproven with data.</p><p>For example, if you are a product manager at a firm and you want users to subscribe to a feature. So you add a ‘Subscribe’ button. Now you are trying to decide what color the button should be. Your goal (aka Metric more explanation to follow) is to get more people to subscribe to your feature. So, you will decide a color for your button which will be more appealing to the people. So now, your hypothesis would be — ‘Making the Subscribe button color blue will increase the click rate’. This statement will be the one you will be evaluating during your AB test.</p><p>2. Metric</p><p>A metric is a number. In our case, since we want users to click the button, the metric is click through rate (CTR). Sometimes, metrics can also change negatively. So it’s important to keep track of such metrics as well.</p><p>For example, if CTR improves, the time spent in a page might reduce as the user is more involved in doing actions faster. This is okay with us.</p><p>3. Number of users</p><p>This is our target user set with whom we will be working to validate our hypothesis. It is important to set 50% of users as Control and 50% of users as Test. A group with no change is called a Control group, and the group where the new change is exposed is called a Test group. The percentages can vary as per need, but it’s very important to divide the whole user base into buckets, as we only want our changes to reflect in users labelled as Test.</p><p>4. Time frame</p><p>With the number of users set, we also need to set a time frame so that we can measure the impact at the end of AB testing.</p><p>To get a statistically significant result, we need to use the AB test result calculator. Any AB test will give results with a level of confidence. With huge data, it’s easy to attain significance at 95% confidence. But, with a smaller data set, 90% is considered a good confidence level. One tailed test is generally used (a positive or neutral change can be detected), but if you want to detect negative impact as well, then two-tailed test can be used.</p><p>At this point you might be wondering as to why you can’t use pre and post data to check the impact. With this type of analysis, we will have lots of variations depending on time period, age of user, quality of user and the kind of features running in the two periods.</p><p>I hope you learnt a little about A/B testing today. So,now let’s get going and start doing A/B tests as a part of your product cycle!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e5a47afe316" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>