<?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 Chiranjib Bhattacharjee on Medium]]></title>
        <description><![CDATA[Stories by Chiranjib Bhattacharjee on Medium]]></description>
        <link>https://medium.com/@chiranjib1979?source=rss-f58ba97df6f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*88BF606zcZw5r4ygeJAASg.jpeg</url>
            <title>Stories by Chiranjib Bhattacharjee on Medium</title>
            <link>https://medium.com/@chiranjib1979?source=rss-f58ba97df6f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:42:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chiranjib1979/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[MVP tests — the litmus tests for product ideas]]></title>
            <link>https://medium.com/design-bootcamp/mvp-tests-the-litmus-tests-for-product-ideas-f5b65b66b75b?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b65b66b75b</guid>
            <category><![CDATA[minimum-viable-product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Sun, 08 May 2022 18:21:01 GMT</pubDate>
            <atom:updated>2022-05-10T04:34:03.207Z</atom:updated>
            <content:encoded><![CDATA[<h3>MVP tests — the litmus tests for product ideas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P55JIQ4WHRm3HOVHyz44Cw.jpeg" /><figcaption>Image credit: Freepik.com</figcaption></figure><p>Product Managers (PMs) are responsible to own and manage risk. One such risk is spending a lot of time and money on building something without validating whether that is the right thing to build. This is true for the entire product or any specific feature. This applies to startups as well as established enterprises. Startups risk the limited resources that they have accumulated through funding. Established enterprises risk their reputation and brand image. However, succumbing to this risk is so very common and at times unavoidable hence worth a mention.</p><h4>Avoiding the pitfall</h4><p>A PM can avoid this pitfall through the Minimum Viable Product test. Once the value proposition is articulated clearly the next step is to get some form of validation from the users themselves to ensure whether the users truly find the proposition valuable enough to invest their time and money into it. This is because the value propositions should be strong enough to overcome the psychological bottlenecks of attention, perception, memory, disposition, motivation, social influence, and physical bottlenecks of access, effort, and other competing priorities of the user.</p><p>MVP tests help to:</p><ol><li>Define what is the risky assumption that PMs want to validate</li><li>Test a product hypothesis with minimum resources by choosing the right MVP type</li><li>Get the product to early users as quickly as possible</li><li>Reduce engineering waste and accelerate learning</li></ol><h4>MVP Candidate</h4><p>To start with, PMs identify the core valuable components that constitute the minimum functionality. Instead of building out the full value proposition, which might take a long time to develop, PMs identify the MVP candidate to validate that things are heading in the right direction. This is also a good time to validate the ideas that have high risks associated with them. The sooner these risks are validated the lesser the impact of those risks to cost, time, and effort. The goal at this stage is to create an MVP <em>candidate</em> based on the hypotheses.</p><h4>Transitioning from Problem space to Solution space</h4><p>PMs and the product teams brainstorm on each of the value propositions and come up with feature ideas that will maximize the impact, minimize the effort and simplify the design. This is where PMs transition from the <a href="https://bootcamp.uxdesign.cc/how-to-get-objective-feedback-and-prioritize-them-5d244ee32894"><em>problem space</em></a> to the <a href="https://bootcamp.uxdesign.cc/how-to-get-objective-feedback-and-prioritize-them-5d244ee32894"><em>solution space</em></a><em>. </em>The goal is to generate as many ideas, not only individually, but also as a group, and build upon others’ ideas as well. This is how the most creative and extraordinary ideas come into existence as a concept. PMs and their respective teams should steer away from judgment and evaluation to keep the ideas freely flowing.</p><h4>User stories</h4><p>The feature ideas are written such that the corresponding customer benefit remains clear. One of the ways to do this is by following the template:</p><p><strong><em>As a [type of user], I want to [do something], so that I can [desired benefit]</em></strong></p><p>This clearly articulates <strong><em>who is the beneficiary, what is the benefit</em></strong>, and <strong><em>why the benefit is useful to the user</em></strong>.</p><p><em>Please refer to the article — </em><a href="https://xp123.com/articles/invest-in-good-stories-and-smart-tasks/"><em>INVEST in Good Stories, and SMART Tasks</em></a><em> by Bill Wake for writing good user stories.</em></p><p>Once user stories are identified each of them is mapped to either an activity or a task that a user performs in her journey. This helps PMs to keep an eye on the big picture while also detailing the individual activities in the user journey. The story map makes it easy to pick and choose user stories from different features that together will provide a meaningful value to the user necessary to validate the hypothesis. From the bigger story map, smaller pieces of “feature chunk” (functionality) are broken out to reduce the scope and build only the smallest yet valuable pieces of each feature. The intent is to work in smaller batch sizes to increase velocity to enable faster feedback. This reduces risk and waste significantly. The idea is to have frequent iterations of validation of the progress by the team every day or two which prevents a large disconnect to creep in. The feedback from these frequent iterations results in course corrections that are much smaller and more manageable, reducing waste and improving productivity.</p><h4>Return on Investment(ROI)</h4><p>At this stage, the feature chunks that are initially prioritized based on how much customer value each feature will create, are passed through a second-pass prioritization that accounts for both the value and the effort. This is determined to ensure the feature chunks deliver a minimum Return on Investment (ROI) which is measured in a “ratio scale” by dividing customer value (typically on a scale of 0–10) by development effort (typically developer-weeks). Great product teams take ideas and break them down into chunks, trim off less valuable pieces, and identify creative ways to deliver customer value with less effort than initially scoped. The goal of this estimate is not to figure out actual ROI but to derive a comparative value that helps to focus on the highest ROI features first and avoid the lower ROI features.</p><p>Estimated ROI helps to create a rank-ordered list (which is a good starting point) to help decide which feature chunks should be part of the MVP candidate. However, sometimes strict rank order does not create a “complete” MVP candidate and PMs may need to skip a few and include some other meaningful features. It is not always easy to estimate the value and the effort. In such events, PMs use their best guesses and change them going forward when they learn more about it while iterating on this.</p><p>Once PMs have organized the list of feature chunks by benefit and ROI and prioritized them, they make some tough decisions to decide on the minimum set of functionality that will resonate with the target customers. They refer to the product value proposition and ruthlessly prioritize to determine the MVP candidate. Keeping Kano’s model in reference, the MVP candidate should have all the ‘must haves’, some ‘performance benefits’ which will create a deferential positioning, and the top ‘delighters’ to absolute “wow” the user. At this stage, PMs decide whether the feature is a “pain killer” or a “vitamin”. Pain killer solves immediate needs, whereas, vitamins do not solve obvious pain points but appeal to users’ emotional needs. PMs use the MVP test to validate whether the pain killer is effective. Once the list of MVP candidates (a collection of feature chunks based on some hypothesis) is ready, PMs create a solution space representation of the MVP candidates so that they can be shown to the customers to get their feedback.</p><h4>Creating the MVP prototype</h4><p>MVP prototype has limited functionality, it should be meaningfully “complete” by addressing a bit of reliability, usability, and delighter attributes. The type of prototype depends on the type of test PMs want to conduct with users. It is neither a shoddy user experience nor a buggy product. It consists of just the right functionality to be considered viable by a user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*3R8aRI6nASv8pGd3ro9SEA.jpeg" /><figcaption>Credit: <a href="https://twitter.com/jopas/status/515301088660959233">https://twitter.com/jopas/status/515301088660959233</a></figcaption></figure><h4>MVP test categories</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*J1sWMALwW1IvVwssTOVfww.jpeg" /><figcaption>Credit: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p><strong><em>Qualitative marketing tests</em></strong> involve showing users marketing materials that are used to explain the product and soliciting feedback. Marketing materials are things that are put in front of a user such as a landing page, a video, an advertisement, an email, etc. These help PMs understand the benefits that best resonate with users and user reactions to the articulations of the benefits, the description of the product, and how compelling the users find the product value proposition. PMs even show users competitor’s marketing materials to learn what they’ve explained well and what they haven’t and to test product differentiation. e.g. <em>Five-second test </em>— users make decisions within the first few seconds so users are shown the home page or landing page for just five seconds and then are asked to tell what they remember and what they liked. This gives PMs a clear understanding of how well the messaging conveys what the product does and why someone would want to use it.</p><p><strong><em>Landing Page or Smoke Test</em></strong> is a popular test where PMs create a live web page to which traffic is directed. The landing page describes the product and asks customers to express some level of interest, which is usually a “sign up” button or a link to the “plans and pricing” page. It’s called a smoke test because there is no real product for use yet. Instead, there is a “coming soon” page to thank the users for their interest. The key metric to measure is the conversion rate. Tools like <strong><em>Optimizely</em></strong> and <strong><em>Unbounce</em></strong> make landing page testing and optimization faster and easier with less development effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*xJqfc50x6MCPa7wlAkIkmw.jpeg" /><figcaption>Source: <a href="https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/">Minimum Viable Product Types</a> by <a href="https://mvpworkshop.co/">https://mvpworkshop.co/</a></figcaption></figure><p><strong><em>The explainer video</em></strong> relies on a video to explain the product and is a variant of the landing page test. The conversion rate measures the effectiveness of the video. This is particularly useful for products that are difficult to explain.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7QmCUDHpNzE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7QmCUDHpNzE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7QmCUDHpNzE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/da23d3fc8d336c4ee9f3a173813546d9/href">https://medium.com/media/da23d3fc8d336c4ee9f3a173813546d9/href</a></iframe><p><strong><em>Advertisement campaign</em></strong> test experiments with different search terms and advertisement copy that try to increase clickthrough rate, giving PMs quantitative feedback on what words and phrases, display advertisement campaigns, messaging, and imagery users find most compelling.</p><p><strong><em>Marketing A/B Testing</em></strong> also called split testing, is used to test different versions of marketing materials, such as two or more different versions of a landing page, advertising, videos, and emails — with different messaging, pricing, images, colors, or other design elements — to see which converts better. Popular A/B testing tools include <strong><em>Optimizely</em></strong>, <strong><em>Unbounce</em></strong>, <strong><em>KISSmetrics</em></strong>, <strong><em>VWO </em></strong>(formerly Visual Website Optimizer), and <strong><em>Google Content Experiments</em></strong> (part of Google Analytics).</p><p><strong><em>Crowdfunding</em></strong> is a way to test whether or not people are willing to pay for a product and to quantify demand. Platforms like Kickstarter let people who want to make and sell a product promote it and accept money from customers who want to buy the product when it comes out. Kickstarter has reportedly received more than $1.9 billion in pledges from 9.4 million backers to fund 257,000 creative projects. e.g. Pebble, raised funding of over $10M.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*RbmGDClhLsgDlRxBq-P53Q.jpeg" /><figcaption>Source: <a href="https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/">https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/</a></figcaption></figure><p>Crowdfunding provides direct access to consumers and is a natural fit for consumer products. PMs provide a rich description of both the offering and its benefits with high-quality videos and FAQs. It is a channel to engage with users and learn about their needs and preferences, and incorporate their feedback thereby improving the product.</p><p><strong><em>Hand sketches</em></strong> are a great way to visualize ideas in the early stage of design. It is of the lowest fidelity and the lowest interactivity, however, easy to share and discuss with teammates and other internal stakeholders and allows for quick design iteration.</p><p><strong><em>Wireframes</em></strong> are low to medium fidelity representation of a product that gives a sense of its components and how they are arranged showing relative size and position. They are often grayscale and use placeholders for images and are devoid of any visual design details such as colors, images, and fonts. This is done to avoid distracting reviewers with visual design elements. They typically use real copy (or a preliminary draft) from the start to identify potential design issues early. Wireframes can be static and clickable or tappable and can be made device-specific to provide a realistic experience. Popular tools include Figma, Balsamiq and many more.</p><p><strong><em>Mockups </em></strong>(sometimes comps) have higher fidelity and look much more like the final product than wireframes. Mockups convey visual design details such as colors, fonts, and images. Some are intended to be “pixel-perfect” while others may only represent the approximate size and position of design elements. Mockups can be static or clickable. Static mockups can yield very valuable feedback from users. Popular tools include Figma and many more.</p><p><strong><em>Interactive prototypes</em></strong> are the next step up in fidelity and interactivity from clickable mockups and provide a level of interaction that goes beyond clickable mockups such as drop-down menus, hover effects, input forms, and audio or video players. e.g. proto.io, Figma, Dorik, and many more.</p><p><strong><em>Wizard of Oz</em></strong> allows PMs to actually test using a live product or service, however instead of the final version, it uses manual workarounds. The Wizard of Oz MVP appears to users as a real live product to the user. The goal is to validate the manual steps that are required and the market response before making the investment to build out an automated solution. e.g. <a href="https://www.groupon.com/">Groupon</a> — a platform founded by Andrew Mason that connects billions of people and processes thousands of transactions every day, started with a simple WordPress site where he posted deals for a local pizza shop each day. He generated PDFs manually as he received orders and emailed them via his own personal email. All of the work was done manually with the help of third-party resources.</p><p><strong><em>Concierge MVP tests</em></strong> are very involved tests with a small number of early adopters to really understand the target market, their needs, and preferences, and how to tailor the product to best meet them. Concierge MVPs work best with services, especially those with processes that require a fair amount of interaction with and input from the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*9X8evkuw_0MxEzv4BP-apw.jpeg" /><figcaption>Source: <a href="https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/">https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/</a> (Food on the Table)</figcaption></figure><h4>Live product</h4><p>Although the design artifacts are tested along the way, actual MVP is tested once it’s built because a lot of change occurs between the design and development phases. As the live product is the highest fidelity possible, PMs always learn new things from customers that were not uncovered during lower fidelity tests. The live product can be tested in a moderated or unmoderated fashion. In moderated testing, customers use the product in presence of the PM either in-person or remotely using Zoom session, whereas with unmoderated testing the customer is alone while using the product.</p><p><strong><em>The fake door or 404-page</em></strong> test is a good way to validate the demand for a new feature that is being considered for building. The idea is to include a link or button for the new feature and see what percentage of customers click on it. This lets PMs gauge whether customers actually want the feature before they spend the resources to build it. Since the feature or the page is not built yet, the users usually see a page acknowledging them for their interest and explaining that the feature is not built yet when they click on the link or button. PMs can add a form asking the user to share why they would find this feature valuable. Typically fake door tests are live for a limited period of time and PMs take them down when the desired sample size is achieved.</p><h4>Wrapping up</h4><p>Once a PM has selected the MVP test that she wants to conduct, she must design the user experience for testing with the users. Good user experience design helps MVP tests to be more successful. To read my write-up on user experience please refer — <a href="https://bootcamp.uxdesign.cc/user-experience-for-product-managers-part-1-6fd3cc276fbf">User Experience for Product Managers — Part 1</a></p><h4>References</h4><ol><li><em>The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback</em> by Dan Olsen</li><li><a href="https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/">https://mvpworkshop.co/blog/minimum-viable-product-mvp-type/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b65b66b75b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/mvp-tests-the-litmus-tests-for-product-ideas-f5b65b66b75b">MVP tests — the litmus tests for product ideas</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[Product metrics glossary]]></title>
            <link>https://medium.com/design-bootcamp/product-metrics-glossary-f7420f3b41ce?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7420f3b41ce</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Wed, 06 Apr 2022 16:15:38 GMT</pubDate>
            <atom:updated>2022-04-09T02:13:48.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yf7B_rBOY1Hyn6a4uzLEBw.jpeg" /><figcaption>Image credit: Freepik.com</figcaption></figure><p>In my earlier post <a href="https://bootcamp.uxdesign.cc/metrics-for-a-product-manager-79026f57bfda"><em>Metrics for a product manager</em></a>, I have shared my learning on how a Product Manager (PM) derives insights from the user interaction with the product and uses that to deliver more value to the user and the business. This post takes a deep dive into some of the critical metrics that are applicable to specific product types. This blog is compiled from different sources and the list of metrics is quite exhaustive. However, in reality, PMs create an optimized list of metrics that most support the growth strategy of the product. The idea is to start small and then gradually build on top of that.</p><h4>Types of consumer business apps</h4><p>Consumer apps are designed to meet specific target customers’ unique needs and wants. The goal is to strengthen the relationship with customers which leads to upsell and cross-sell.</p><p>The 5 major types of such businesses are:</p><p><em>Subscription — trial-based (e.g. Netflix)</em></p><p><em>Subscription — freemium (e.g. Duolingo)</em></p><p><em>Ad-based (e.g. Twitter)</em></p><p><em>Marketplaces (e.g. Amazon)</em></p><p><em>DTC (e.g. Country Delight)</em></p><h4>Subscription — trial-based</h4><p>Key success factors: <strong><em>low acquisition costs, a high conversion rate (post the trial period), and high retention.</em></strong></p><p><strong>Trials growth</strong>: New trials per period,</p><p><strong>Conversion</strong>: % of trials that convert to customers after the trial period ends,</p><p><strong>Customer retention</strong>: Month 1/3/6 cohort retention ( retention curve in <a href="https://bootcamp.uxdesign.cc/metrics-for-a-product-manager-79026f57bfda"><em>Metrics for a product manager</em></a>)</p><p><strong>Revenue</strong>: Monthly recurring revenue (MRR)</p><p><strong>CAC</strong>: Cost of acquiring a trial. MRR and conversion become very critical metrics to track when the acquisition is through paid channels.</p><p><strong>Payback period</strong>: This is also known as the growth spend efficiency which is the time taken to recover the CAC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*m2wGnGErQsryekzjQD-sxw.jpeg" /></figure><p>The general benchmark for startups to recover CAC is 12 months or less. High-performing SaaS companies have an average payback period of 5–7 months. Great B2C businesses have a payback period of less than 1 month. 6 months is considered good, and 12 months is average. And in exceptional cases, payback of acquisition costs happens on the very first transaction. B2B businesses that have small and medium businesses as their consumers 6 months of payback can be considered as great, 12 months as good, and 18 months as average. For enterprise customers less than 12 months of payback period is great, 18 months is good, and 24 months is average. Larger enterprises with greater access to capital can afford a longer payback period.</p><h4>Subscription — freemium</h4><p>Key success factors: <strong><em>Ability to build large pools of free users through word of mouth or virality (growth generated from existing users), sustained conversion rate from free to paid, and high retention</em></strong>.</p><p><strong>User growth</strong>: New signups</p><p><strong>User retention</strong>: Week 1/2/12 cohort retention</p><p><strong>Customer growth</strong>: New paying customers</p><p><strong>Customer retention</strong>: Month 1/3/6 cohort retention</p><p><strong>Conversion</strong>: % of free users that end up converting to paying customers after a finite time period (1–3 months is typically good)</p><p><strong>Engagement</strong>: Key action each day/week/month</p><p><strong>Revenue</strong>: Monthly recurring revenue</p><p><strong>Payback period</strong>: <em>Explained above</em></p><h4>Ad-based</h4><p>Key success factors: <strong><em>Sustained and inexpensive virality-driven user growth, high engagement, and high retention</em></strong>.</p><p><strong>User growth</strong>: New signups</p><p><strong>Engagement</strong>: DAU, WAU, or MAU</p><p><strong>Intensity</strong>: DAU/MAU, WAU/MAU, or L7/L30. While DAU divided by MAU is a common metric for measuring engagement, it has its shortcomings because it gives a single number whereas L30 (coined by the Facebook growth team) or the activity histogram gives a detailed view of a product’s engagement. It provides a richer understanding of user engagement. This is also called the <strong><em>“Power User Curve”</em></strong>. It is a histogram of users’ engagement (whatever action is important to measure the top-level activity) over the total number of days they were active in a month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*tvFqzvBmsX5XVVtE4wBZ9Q.jpeg" /><figcaption>The Power User Curve smiles when things are good [Source: <a href="https://future.a16z.com/power-user-curve-engaged-users/">The Power User Curve: The Best Way to Understand Your Most Engaged Users</a>]</figcaption></figure><p>The Power User Curve has the following advantages over the DAU by MAU value:</p><ol><li>It shows if the most engaged segment is coming back every day</li><li>It shows the variability among different users. Some are less engaged, whereas others are highly engaged</li><li>Power User Curves can be shown for different user actions and not just for a specific action. This matters if the core activity that matters for the product is deeper in the funnel.</li><li>When mapped to cohorts, Power User Curves shows if user engagement is getting better over time — which in turn helps assess product launches and performance of other feature changes</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*Blb1oqxSgbL7XPQxCDtbBA.jpeg" /><figcaption>[Source: <a href="https://future.a16z.com/power-user-curve-engaged-users/">The Power User Curve: The Best Way to Understand Your Most Engaged Users</a>]</figcaption></figure><p><strong>Retention</strong>: Week 2/4/8 cohort retention</p><p><strong>Activation</strong>: % of new users who “activate,” whatever that means for your product</p><p><strong>CAC</strong>: Cost of acquiring a new user</p><h4>Marketplaces</h4><p>Key success factors: <strong><em>Efficient acquisition costs, high-enough buyer conversion, high average order value which is the average dollars spent per transaction, and high purchase frequency</em></strong>.</p><p><strong>Match rate or Fill Rate</strong>: The job of any marketplace is to facilitate the matching of supply with demand. It is the rate at which buyers or consumers can find sellers or producers and vice versa. It varies from industry to industry. e.g. for a ridesharing company, the driver utilization time or what % of the time are drivers driving around with a passenger, vs. empty? A related metric is to measure unsuccessful matches. For ridesharing, what percentage of users open the app but drop off without requesting a ride? It could be due to long wait times, surge pricing, etc. when the marketplace was unable to meet the demand. Marketplace PMs should investigate and identify reasons why matches don’t happen and eliminate or reduce these blockers. If the core issues are not addressed quickly, multi-tenanting (which may be there already) will increase and users will naturally be incentivized and flock to competitor products.</p><p><strong>Bookings growth</strong>: Number of completed transactions per week/month. Bookings tell directly whether marketplace usage is growing or shrinking. e.g. for Uber and Ola, it is the number of rides. For Airbnb, it is the number of nights booked.</p><p><strong>Supply growth or Market depth</strong>: New active supply per week/month. It is important to measure and optimize market depth because it directly impacts the user experience. One of the primary goals of any marketplace is to reduce search costs by making it easy for participants to find and match with the other side. However, too much supply can cause challenges in discovery which may result in negative network effects. Consumers experience decision fatigue or a paradox of choice. Conversion rates could fall in such cases. Generally, for heterogeneous (each supplier is different) supply marketplaces like Airbnb, where a user’s tastes may be quite specific, every additional listing on the platform is useful to see. Whereas, for homogeneous (all suppliers are similar) supply marketplaces like Yulu, market depth impacts ease of use, e.g., if there were 6 Yulu scooters in my vicinity, this is no more valuable than if there were only 4 scooters available for me to use — user value plateaus despite the addition of more supply. So it is recommended to track “activated supply” (supply that has reached some value milestone) and not just raw new supply.</p><p><strong>GMV growth</strong>: Dollars going through the system per week/month. GMV or <em>Gross merchandise volume</em> is the total sales dollar volume of merchandise in a specific period. It’s the real top line, what the consumer side of the marketplace is spending. It is a measure of the size of the marketplace.</p><p><strong>Revenue</strong>: This is different from GMV, even though, GMV and revenue are frequently used interchangeably. Revenue is a fraction of GMV that the marketplace “takes.” It consists of various fees that the marketplace earns from the participants for providing its services; such as transaction fees based on GMV successfully transacted, advertisement revenues, sponsorships, subscription fees, etc.</p><p><strong>Buyer retention</strong>: Month 1/3/6 purchaser retention</p><p><strong>Supply retention</strong>: Month 1/3/6 supply cohort retention</p><p><strong>Conversion</strong>: % of visitors who end up purchasing</p><p><strong>Time to fill</strong>: How long it takes to fill a customer request (e.g. Uber request)</p><p><strong>Average order value (AOV)</strong>: Average dollars spent per transaction</p><h4>DTC</h4><p>Key success factors: <strong><em>Efficient acquisition costs, sustainable margins, and high AOV</em></strong>.</p><p><strong>Customer growth</strong>: Number of new purchases/subscribers</p><p><strong>Customer retention</strong>: Month 3/6/12 cohort retention</p><p><strong>Revenue</strong>: Monthly (recurring) revenue</p><p><strong>Growth spend efficiency</strong>: Payback period, and/or contribution margin, and/or ROAS</p><p><strong>Gross margins</strong>: Net sales revenue minus the cost of goods sold (per purchase or from an annual subscription)</p><p><strong>CAC</strong>: Cost to acquire a customer</p><p><strong>AOV</strong>: Average order value</p><h4>Key considerations while selecting the right set of metrics</h4><ol><li><em>How do you know you are acquiring new users sustainably?</em></li><li><em>How do you know that your users are experiencing the value that they expected?</em></li><li><em>How do you know your users are ready to pay?</em></li><li><em>How do you become certain that your users still want to pay for using the product?</em></li><li><em>How do you know that the product is making a profit for the business?</em></li></ol><h4>Acknowledgments</h4><p><a href="https://www.linkedin.com/in/shravantickoo/">Shravan Tickoo</a> — <em>Breaking into Product Management powered by </em><a href="https://www.airtribe.live/"><em>Airtribe</em></a></p><h4>Sources</h4><ol><li><a href="https://www.lennysnewsletter.com/p/payback-period?s=r">https://www.lennysnewsletter.com/p/payback-period?s=r</a></li><li><a href="https://www.lennysnewsletter.com/p/the-most-important-consumer-metrics?s=r">https://www.lennysnewsletter.com/p/the-most-important-consumer-metrics?s=r</a></li><li><a href="https://future.a16z.com/power-user-curve-engaged-users/">https://future.a16z.com/power-user-curve-engaged-users/</a></li><li><a href="https://future.a16z.com/power-user-curve-engaged-users/">https://future.a16z.com/power-user-curve-engaged-users/</a></li><li><a href="https://www.lennysnewsletter.com/p/the-most-important-marketplace-metrics?s=r">https://www.lennysnewsletter.com/p/the-most-important-marketplace-metrics?s=r</a></li><li><a href="https://future.a16z.com/marketplace-metrics/">https://future.a16z.com/marketplace-metrics/</a></li><li><a href="https://www.lennysnewsletter.com/p/the-most-important-consumer-subscription?s=r">https://www.lennysnewsletter.com/p/the-most-important-consumer-subscription?s=r</a></li><li><a href="https://www.geckoboard.com/best-practice/kpi-examples/cac-payback-period/#:~:text=The%20general%20benchmark%20for%20startups,have%20greater%20access%20to%20capital">https://www.geckoboard.com/best-practice/kpi-examples/cac-payback-period/#:~:text=The%20general%20benchmark%20for%20startups,have%20greater%20access%20to%20capital</a>.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7420f3b41ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-metrics-glossary-f7420f3b41ce">Product metrics glossary</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[Solving big problems in 5 days using Sprint]]></title>
            <link>https://medium.com/design-bootcamp/solving-big-problems-in-5-days-using-sprint-ed28901570bc?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed28901570bc</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 10:16:30 GMT</pubDate>
            <atom:updated>2022-04-01T23:56:23.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fKmzl1dqdhDkbji8yli9jQ.jpeg" /><figcaption>Image credit: Freepik.com</figcaption></figure><p>In <a href="https://bootcamp.uxdesign.cc/user-experience-for-product-managers-part-1-6fd3cc276fbf"><em>User Experience for Product Managers — Part 1</em></a>, I have talked about <strong>elements of great UX</strong>, <strong>UX design iceberg</strong>, and how the <strong>design is handed-off</strong> from Product Manage(PM) to UX designer and visual designer. A great product begins with a great vision. However, not all great vision turns into reality because it gets stuck into a myriad of problems, issues, questionable assumptions, and endless meetings. The path to real-world success remains elusive. Design Sprints can be leveraged to solve such problems by validating a new idea in a faster way that is absolutely fun.</p><h4>The plan</h4><p>To idea is to first assemble the perfect sprint team. (The meaning of “sprint” is different from the meaning in “agile”). The magic number is seven. The roles are listed below. It may not be possible to include all of them but a mix is better.</p><p><em>Decider — the decision-maker for the team, maybe the CEO, the founder, the product manager, or the head of design.</em></p><p><em>Finance expert — can explain the revenue streams and expenses easily. e.g. CEO, CFO, business development manager</em></p><p><em>Marketing expert — can craft company’s message. e.g. CMO, marketer, PR, community manager</em></p><p><em>Customer expert — who has a deep knowledge of customer pain points and challenges from daily interactions. e.g. user researchers, sales, customer support</em></p><p><em>Technology expert or Logistics expert — who understands what can be built and delivered. e.g. CTO, engineers</em></p><p><em>Design expert — such as UX designer, product manager</em></p><p>On Monday, the team will map out the problem and identify an important point to focus their attention on. Competing solutions will be sketched on Tuesday. Wednesday will be used to critique solutions to identify which solution is best to meet the long-term goal and create a corresponding storyboard. On Thursday, a prototype will be created. And finally, on Friday, the prototype is tested with real customers to understand and learn from their feedback.</p><h4>The three challenging situations where sprints can be very helpful</h4><p><strong>High stakes</strong> — <em>there is a big problem ahead and the solution will require a lot of time and money</em></p><p><strong>Not enough time</strong> —<em> time is short and a good solution is needed very fast</em></p><p><strong>Plain stuck</strong> — <em>initiatives that have lost momentum can use sprint to look at everything with a fresh perspective that acts as a booster rocket to success</em></p><h4>Points to note before jumping right into it</h4><p><strong>Someone should be identified as a facilitator</strong> — <em>who remains unbiased in decisions, who is confident in leading meetings, managing time, summarizing discussions and conversations and telling the team when it’s time to stop talking and move on.</em></p><p><strong>Including the troublemaker in the process</strong> — <em>it’s always prudent to include the smart person who has a strong and contrary opinion and who can see problems differently from everyone else.</em></p><p><strong>Block all five workdays in the week</strong> — <em>five working days are just right to sharpen focus and cut down useless debate and build and test a useful prototype without burning out the team.</em></p><p><strong>No device allowed</strong> —<em> No laptops, phones, etc. that causes distraction</em></p><p><strong>Whiteboards and stationery supplies</strong> — <em>whiteboards increase the visibility of information and allow creative synthesis of ideas. Office supplies such as sticky notes, markers, and pens aid the process</em></p><p>Sprint gives an excuse to free up the calendar to address the most important issue and work as a team for the next five days. With chances of context switching and random distractions put away, the team is ready to start with the five-day sprint week.</p><h4>Monday</h4><p>On Monday, a long-term goal is set. Like where do we want to be in 6 months, or 1 year, or 5 years from now? It may take 30 seconds to 30 minutes or more. Teams may not agree on a goal and there may not be clarity on it initially. That is fine. It is worth the time to get a clear understanding of the goal because it will bring confidence to the week’s effort.</p><p>Next, the team lists the sprint questions like,</p><p><em>What questions do we want to answer in this sprint?</em></p><p><em>What hypothesis needs to be true to meet long-term goals?</em></p><p><em>What could be the reasons for which the initiative might fail?</em></p><p>The trick is to rephrase the assumptions and obstacles into questions. By doing so, answering become easier with sketches, prototypes, or tests. Also the uncertainty shifts to curiosity. The number of questions does not matter at this time. The list may be daunting but comforting at the same time as it will give a clear picture of the direction and challenge that lies ahead.</p><p>Next customer-centric maps (flowcharts showing how customers interact with the product) are created with the list of key actors on the left and completed goals on the right. The interactions are the customer journey represented using simple boxes, connecting arrows, and text in 5 to 15 steps.</p><p>At this stage, validations from experts and guests (decider if he is not joining the team all the time, customer experts from customer research, sales, customer support) are needed. Feedback is discussed and changes are incorporated as needed on the long-term goal, questions, and maps. Questions that need to be validated are, what are the unique advantages or opportunities? What are the biggest risks? The experts help the team understand what the team didn’t know or missed from the previous exercise. Based on the information from the experts, notes are taken and organized. Identified problems are rephrased as opportunities using the “How might we” (HMW) statements. These HMW statements help to decide which part of the map to target. The related HMW statements are grouped together and themes start to emerge gradually. Next, the HMW statements are prioritized using dot voting. By now, the team has clarity on the challenge, the opportunity, and the risk. At this point, the decider chooses one target customer and one target event which will be the focus of the rest of the sprint.</p><h4>Tuesday</h4><p>Tuesday is for coming up with competing solutions. The search for ideas can be from other products, other companies, or other industries. However, it can be from within the organization as well. Ideas that were abandoned and unfinished from previous initiatives. It’s like getting Lego components that can be assembled to build something new. This is done through the “Lightning demo”. Big ideas are captured in the form of simple diagrams and notes. Now the team has the following inputs:</p><p><em>Monday’s maps</em></p><p><em>Sprint questions</em></p><p><em>How might we notes</em></p><p><em>ideas from “Lightning demos”</em></p><p>Next, the team divides up and tackles different parts of the problem or they might choose to focus on the same thing. It is prudent to split up to tackle the important parts. Next is to create sketches of the solution. Sketching is the fastest and easiest way to transform abstract ideas into a concrete solution. These sketches will be driving the rest of the sprint. However, they are not work-of-art. Each team member works alone by following a 4-step process. 20 minutes <strong><em>boot</em></strong><em> </em><strong><em>up</em></strong> with all the notes, opportunities, inspirations. 20 minutes to <strong><em>write down</em></strong> rough ideas. 8 minutes of <strong><em>rapid sketching</em></strong> exercise with the strongest idea. 30+ minutes of <strong><em>solution sketch</em></strong> with all the details worked out. The solution sketch should be self-explanatory, anonymous, may not be fancy, use actual copy, have a catchy title.</p><h4>Wednesday</h4><p>In the morning, goal is to decide which solution to prototype. This involves a 5-step process (<strong><em>Sticky decision</em></strong> as all the steps involves something sticky). <strong><em>Art museum</em></strong> — sticking the solution sketches to the wall. <strong><em>Heat map</em></strong> — looking at all the solutions in silence and use dot stickers on the interesting ones. 3 minute <strong><em>speed critique</em></strong> — discussing highlights and capturing big ideas in sticky notes. <strong><em>Straw poll</em></strong> — one vote per person to choose a solution. <strong><em>Supervote</em></strong> — decider making the final decision. Sticky decision is not perfect. However, it gives speed and helps in meeting the goal of the sprint — preparing fast to get real customer validation which will lead to the best decision.</p><p>Next, winners are picked up. Decisions are made on whether the winners can fit into one prototype or if conflicting ideas stand out as different prototypes. Prototypes are given fake brand names to identify them distinctly. Next, the team prepares a storyboard to plan the prototype. This will capture how you want the customer to interact with the product starting with a simple opening scene and then following on the customer journey till the customer goal is met. Generally, this should involve 5 to 15 steps.</p><h4>Thursday</h4><p>On Thursday, the storyboard is turned into a realistic prototype. Prototypes are disposable and built just enough to learn. They should be of “Goldilocks quality” — just enough quality to evoke honest customer reactions. 4-exercises that set the team on the right path are — picking the right tools, dividing and conquering, stitching it together, and doing a trial run. The team members could pick respective roles —at least <strong><em>2 makers</em></strong> who create individual components (screens, pages, interactions, etc.), a detail-oriented <strong><em>stitcher </em></strong>who combine the components to create a seamless experience, <strong><em>writer </em></strong>who creates the copy for the prototype with realistic texts, asset collector who scour the web, image libraries, etc. to get photos, icons, etc. that will be used in the prototype, and finally, the interviewer who prepares the interview script for Friday’s customer interview. Once the prototype is ready, the interviewer trial runs the prototype to become comfortable and ready for the next day’s interview.</p><h4>Friday</h4><p>Friday is the day for the test that makes the entire sprint worthwhile as the team interviews the customer and learns by watching the customer’s interactions with the product. After 5 customer interviews, patterns will emerge. The team watching together learns together from the interview and this helps in drawing better conclusions. Whether the prototype is a success or failure, the team learns exactly what they need to do as a next step. During the interview, the interviewer shows an authentic curiosity mindset by asking open-ended questions (who/ what/ where/ when/ why/ how…) and follow-up questions that help the customer to think aloud. The interviewer avoids leading questions and avoids prompting the customer on what to do next.</p><h4>Wrap-up</h4><p>The key is to build a habit of listening to customers. Strong bias to the customer problems helps in bringing the team closer to the people who use the product to solve a problem in their life.</p><h4>Acknowledgments</h4><p><a href="https://www.linkedin.com/in/shravantickoo/">Shravan Tickoo</a> — <em>Breaking into Product Management powered by </em><a href="https://www.airtribe.live/"><em>Airtribe</em></a></p><p>For a more detailed understanding of Sprint please refer to — <strong>Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days</strong> by Jake Knapp, John Zeratsky, Braden Kowitz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed28901570bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/solving-big-problems-in-5-days-using-sprint-ed28901570bc">Solving big problems in 5 days using Sprint</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[Metrics for a product manager]]></title>
            <link>https://medium.com/design-bootcamp/metrics-for-a-product-manager-79026f57bfda?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/79026f57bfda</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Tue, 22 Mar 2022 11:37:55 GMT</pubDate>
            <atom:updated>2022-03-25T00:17:33.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k8iVsJH5ZIDk8XaFpcaioQ.jpeg" /><figcaption>Image Credit: Freepik.com</figcaption></figure><p>Product Managers (PMs) are responsible for delivering great products. Knowing how to measure the success of a product is equally critical and important for a PM. It does not matter how good a product is or how great the user experience is or how strong the hypothesis is, all of these will not deliver the expected impact unless the PM figures out a way to master the art and science of getting the right telemetry and metrics from the different interactions of the product with its target user group. Product metrics command a significant impetus and very careful thinking so that the PM gets an accurate insight into user behavior while they use the product. Metrics help in identifying quantitatively how good or bad certain features are performing and how impactful they are.</p><p>For a PM, the two kinds of analytics that are very important are marketing analytics and product analytics. Marketing analytics provide information on traffic source, demographics, etc. and it typically refers to the quality of traffic from a specific channel at the top of the funnel. Any change in the quality of traffic from the respective channels can have a significant impact on the key product metrics. Typically, PMs rely upon Google Analytics to understand marketing analytics.</p><p>On the other hand, product analytics give PMs a systematic understanding of how users are interacting with the product while they are on their respective user journeys in the product itself. Typically this is achieved by instrumenting events in a product. As an example, for a sign-up page on a website or for a registration screen on the app, PM could leverage tools such as CleverTap or Mixpanel to define event triggers for the various actions that are to be performed by the users while they visit the website or uses the product. PMs typically define the user data tracking requirements in the PRD and the engineering team incorporates the necessary javascripts that capture the information when the respective events are triggered through user interactions such as a mouse click or a finger tap on a button etc.</p><p>How trivial it may sound, user interaction data trackers are the most critical component of the product when it comes to metrics. This helps in the ingestion of the data that can be analyzed to identify how the users are using the application, problems they are experiencing in their respective user journeys, and how the user experience may be improved to amplify the impact. This is the holy grail for the PM as it gives a clear understanding of the user behavior at every step of the user journey. It answers questions like how many users came to the landing page, how many users clicked on a specific button, and whether they completed an intended action or they dropped off in between. This data also helps to understand where could be effective marketing insertions and based on that users are nudged urging them to perform a desired action on the product.</p><p>For any product, there could be a large number of metrics that could be tracked to understand how it’s performing. As there are so many different metrics that could be improved, a holistic analytics framework that encompasses the entire business comes in handy. This helps to clearly articulate how the various metrics fit together and can help PMs identify where to focus. Every business wants to make its prospects aware of its product which is <strong>Acquisition</strong>. It wants to convert those prospects into customers or in other words <strong>Activation</strong>. It wants to retain as many of its customers as it can in the long run which is <strong>Retention</strong>. Post that, it wants to make money from its customers which is <strong>Revenue</strong>. And finally, it wants its customers to spread positive feedback to their peers, friends, and family about the product to generate more and more prospects which is <strong>Referral</strong>. Simply put this is the typical user journey through the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*1Gxfcejatie8aVvSKkkLWw.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p>However, the important part in this journey for a PM is to identify which part of the journey (<strong>Acquisition, Activation, Retention, Revenue, Referral)</strong> is more important than the rest which can be optimized for maximum impact. Hence, this becomes the “metric that matters most” (MTMM). It is the metric that offers the highest ROI opportunity for improving the business at a specific point in time. Initially, when a PM focuses on optimizing a particular metric, it is easy to find ideas that can lead to significant improvements without much effort. Once the improvements are made, the ROI continues to decrease as PMs optimize on the same metric. Optimizing another metric at this stage delivers higher ROIs. Typically, MTMM starts out as retention until product-market fit (PMF) is achieved. When there is a strong PMF then PMs change focus to conversion, and finally to acquisition. At the acquisition stage, for products that acquire users organically, revenue can be delayed to a later stage. However, for products with paid acquired users revenue becomes very critical at an early stage.</p><p>PMs constantly monitor what percentage of users keep coming back to the product to understand what’s going on across all users and what percentage of users are actively using the product. This is measured using retention rate which is the number of active customers by the total number of customers. When this is plotted over time, this gives the retention curve. The value for each point on the curve is calculated based on sign-up and usage data for a population of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-V0QoRoEutdhfF_Zp3Z_cA.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p>Lower initial drop-off rate with a low rate of descent, and the higher terminal value indicates stronger product-market fit. When calculating the retention rate, it is critical to distinguish between new and returning users. New users are customers who use the product for the first time (during a certain time period). Returning users are customers who use the product during a certain time period who first became users before that time period. Tracking returning users over time is valuable. This is because the trend in active user growth could be due to modest new user growth with decent retention as well as for very high growth in new users and very poor retention of returning users. By only tracking active users, it would be difficult to differentiate between these two scenarios. A group of users who share similar retention characteristics are called a cohort. Typically, Cohort based analysis of metrics for different cohorts over time proves as a powerful tool in this context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TCJk1snb5zuw5Ahl4WSc0g.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p>Cohort retention curve of Cohort C has the highest initial drop-off, the lowest rate of decay, and the highest terminal value hence this would be more preferable for PMs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*UkVqRU4OxvTzf_WFqyFR4w.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p>As PMs improve a product based on user feedback, the product-market fit improves over time. Consequently, cohort retention curves start moving up along the y-axis, with higher terminal values for newer cohorts.</p><p>The next step is to construct a quantitative representation of the business from the set of chosen metrics so that the business outcomes can be optimized. To do this, all businesses can be expressed by the foundational equation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*aHnxhJcHxyM2TNy7ERoRGQ.jpeg" /></figure><p>The next step is to break revenue down into actionable metrics to a “per user” basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*OLwGXN5N1wHEw6EcMA_N2w.jpeg" /></figure><h4>For an advertising-based business model it is expressed as:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Pe-59IQssIAkcJfS44TDjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*iBxP0n4YMkDd30ptFpH7dQ.jpeg" /></figure><p>Where, CPM is the cost per thousand impressions</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*OGT939NDZfPrYVKzbhUUzA.jpeg" /></figure><p>Visits can be influenced by content and notification to the visitor. Page visits can be controlled by distributing content across multiple pages. Impressions can be controlled by putting more ads per page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*w7coVx0Cbjkzls0yeG6iMQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63pCp04P2g2FLukSxIboBg.jpeg" /></figure><h4>For a Subscription-based model</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*fAJ2AKgHfz8dSSPZqYJctA.jpeg" /></figure><p>In a subscription-based model, a subset of users are paid users in case there is a trial period available to the users. For a freemium business model, there could be both free and paid subscriptions available to the users. Assuming all subscriptions are paid,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*JXGickdFi1a4KoJTy84Rpw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vzZSCk0RecnHDkbCMiJfxg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qCgU15MqnrT5-9pRrxA9iA.jpeg" /></figure><p>Once a business achieves product-market fit, the goal shifts towards making the business profitable. The focus shifts from understanding the business on a time period basis to understanding the business on a per-customer basis. Before PMF is achieved the focus is completely on revenue, while after PMF is achieved the focus shifts to improve the profitability and reduce the cost to run the business. However, in this context the focus is centered around reducing the costs associated with acquiring a revenue-generating customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*kcVLkSFLYyiPlNQmAtnHMQ.jpeg" /></figure><p>This can be also written as</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e-e2jrkE-ACdu9XtuH6gLA.jpeg" /></figure><p><strong>Customer lifetime value</strong> (LTV) is the revenue that a customer generates for the business without taking into account the cost to acquire the customer.</p><p>LTV = ARPU X Average Customer Lifetime, where,</p><p>Average Customer Lifetime = 1 / Churn rate</p><p>LTV = ARPU / Churn Rate</p><p>LTV can be increased by increasing ARPU. ARPU can be increased by raising prices for existing products or by cross-selling and upselling. LTV can also be increased by increasing the average customer lifetime, which can be done by decreasing the churn rate. Churn rate can be improved by providing excellent customer service and support, by ensuring the product continues to meet customer needs without compromising on the quality and reliability standards.</p><p><strong>Customer acquisition cost </strong>(CAC)is the average amount of money spent to obtain a new customer.</p><p>CAC can be determined assuming that the number of new customers added in a given time period is known and sales and marketing costs for the same time period are also known. A better way to determine CAC is using the cost per acquisition (CPA) which is the cost on average for each prospect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*AcIHJZ44_6XSmd-YjSnMgQ.jpeg" /></figure><p>CPA could be reduced by using low cost marketing programs and channels, or by using alternate keywords with lower CPCs, or by using inexpensive advertisement inventory, or by improving the effectiveness of the advertisements.</p><p>To generate a profit, LTV should exceed CAC, a general thumb rule for successful SaaS businesses is that LTV-to-CAC ratio should be greater than 3.</p><p>So far, we have identified the key metrics for the business. But knowing what to measure is half the task, the other half of it is to get customer validation for the experiments and respond to the feedback very quickly with improvements. This is accomplished by an effective A/B testing framework. It is very important to quickly iterate these experiments and learn from the customer analytics and optimize the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*QjpdNAKEO0pL_Qs6rjNS2g.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen</figcaption></figure><p>First PMs define key metrics. Next, PMs establish a baseline for each to know the starting point. Next, to ensure that the metrics data that are collected are those that are intended to be collected and are accurately reported. Finally, to set up analytics dashboards that make it easy for everyone to monitor how each metric is performing over time.</p><p>PMs use an A/B testing framework to roll out the improvement to a fraction of users while the rest of the population acts as a control. Tools like Optimizely, Unbounce, KISSmetrics, etc. could be leveraged. Generally, these tools let the PMs specify one or more variations and then distribute traffic among the variation and the control environment. They keep track of the results for the metric and show how the variation is performing, along with statistical confidence levels based on the sample sizes.</p><p>This brings to the end of a seemingly large post and I thank you for your patience and will look forward to hearing your feedback.</p><h4>Acknowledgements</h4><p><a href="https://www.linkedin.com/in/shravantickoo/">Shravan Tickoo</a> — <em>Breaking into Product Management powered by </em><a href="https://www.airtribe.live/"><em>Airtribe</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79026f57bfda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/metrics-for-a-product-manager-79026f57bfda">Metrics for 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[User Experience for Product Managers — Part 1]]></title>
            <link>https://medium.com/design-bootcamp/user-experience-for-product-managers-part-1-6fd3cc276fbf?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fd3cc276fbf</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 18:13:32 GMT</pubDate>
            <atom:updated>2022-03-16T02:40:56.046Z</atom:updated>
            <content:encoded><![CDATA[<h3>User Experience for Product Managers — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1OPJRlEdzh4grrySQe7f0Q.jpeg" /><figcaption>image credit: Freepik.com</figcaption></figure><p>Product Managers (PMs) are the greatest enablers. PMs necessarily do not design anything but they encourage and enable the design team to build a great design. To do this PMs need not be world-class designers themselves, but they should have an overall understanding of UX design and the key concepts. This helps PMs to have focused discussions with the UX designers and to contribute effectively to the design process that creates better products.</p><p>Great PMs ensure that a product not only meets customer needs in a much better way than the existing solutions but also delivers a great experience to the users. Using the product, the user should be able to derive value seamlessly.</p><p>Having a great UX means that the product feels easy to use. The users will be able to complete a specific task without any distraction, effortlessly and efficiently. The user should be able to intuitively figure out the next steps of a journey flow. While the user uses the product, the user interface hides behind the task at hand and the user conveniently completes the task at ease without any distraction from the interface. That is an example of great UX which can be a strong product differentiator.</p><h4>Elements of great UX</h4><p>A great UX should focus on reducing the cognitive load of the user and consists of majorly six elements.</p><p>Usability — This is the measure of how easily and conveniently a user is able to accomplish a task using the core flow. This is identified by usability testing, where users are given to complete core tasks and PMs observe what the users do. Usability helps answer the question, “Can customers use the product easily?” The higher the usability, the better it is. An example of good usability could be <strong>GPay</strong>.</p><p>Efficiency —This measures the time it takes for the user to complete a task using the core flow. Using different designs PMs measure how much time it takes users to complete the core task. The lesser the time, or the clicks, or the taps, or the keystrokes taken, the better it is. PMs measure and compare efficiency metrics to evaluate and improve a given design.</p><p>Perceived effort — It is the perceived effort that a user has to undertake to complete a task using the core flow. It is the consequence of any clutter that is there or that slowly creeps into a product over time by showing them too much information or giving them too many choices. The lesser the perceived effort the better it is. A very good example of low perceived effort is the Google home page.</p><p>Law of usability — The more effort that a user has to put in to achieve an outcome, the less number of people will actually achieve that outcome.</p><p>Delight — This is making the user happy in an unexpected way to increase the stickiness. It helps to answer “Do customers enjoy using the product?” e.g. <strong>Duolingo </strong>with the concept of using “mistakes” as a way to “mend” the broken heart into a gold heart. Using the delight component, several need-based products can gamify user experience thus lifting themselves from mere usefulness towards habit formation.</p><p>And lastly, Simplicity — This is delivering the intended value to the user in the fastest and the most simplified way.</p><h4>UX Design Iceberg by Dan Olsen</h4><p>A product with a great UX is not an accident but it requires consistent effort in different faculties. A good UX is similar to an actual iceberg, only a small portion of UX design is visible and obvious, however, much of it remains beneath the surface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*1TdDrZfISMTbs9SCArpeMA.jpeg" /><figcaption>Source: <em>The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback</em> by <strong>Dan Olsen</strong></figcaption></figure><p>Starting from the bottom, the layers of conceptual design, information architecture, and interaction design, remain not so apparent. However, the top layer of visual design is the part that sticks out of the water and this only remains visible to the user. This is because humans are visual creatures and it is the main way human brains processes information.</p><p>But a product with just good looks and screens is not enough to create a great user experience. Outstanding UX design requires a lot of careful work at all four layers as well as a good design workflow that progresses from conceptual design, information architecture, interaction design, and visual design.</p><p>Conceptual design is the soul of the design and the high-level function of the features that create value for the user. A good conceptual design is easier to create with a deep understanding of the target customers and their needs. Inputs from user research using the target personas become critical at this stage. The next layer from the bottom is information architecture. It defines how the information in the product should be structured. Tools like sitemap become useful at this point. The next layer, interaction design determines how the product and the user interact with one another. Tools like flowcharts, wireframes, and combo flowcharts become useful at this point. Visual design is the aesthetic visual part that contributes to the ease of use. Three major components of visual design are color, typography, and graphics.</p><h4>Handoff from PM to UX/Interaction designer to Visual Designer</h4><p>A PM is responsible for understanding what the market needs are, whether fulfilling those needs are in the scope of product strategy, and how the needs are aligned with overall business strategy, and translates the hypothesis into product requirements. Once these questions are answered, PM identifies what the real needs are and what are the associated features, and puts together the requirements. Then it is passed on to the UX designer to develop the information architecture. Then UX designer develops the interaction design. This includes user flows that may navigate across multiple pages and defines the various inputs that the user provides in those flows. This includes both the visual and audio interactions like that of <strong>Paytm </strong>voice notification after payment is received.</p><p>Then the UX designer develops the information design. The creation of great UX design requires different skills. In a great product company PM works closely with the UX/interaction designer and provides feedback, and validates decision choices. Finally, the visual designers add the visual design aspects like the final looks, fonts — colors, styles, sizes, and other graphical elements, and incorporate any feedback from the PM.</p><p>Then this is handed over to the engineering team for development. Based on the type of product and industry, engineers can also be involved earlier in the process to validate the feasibility aspects. Some organizations have a pre-sprint feedback process where engineers are given a lead time to clarify their doubts and ask their questions before they officially enter into the development sprint. The organizations not realizing these intricacies do not have the right skillsets in their team. Consequently, they fall victim to the design gap which might negatively impact the product and the business.</p><p><em>In the next part of this blog, I will discuss the type of design tools that are typically used and also talk about design sprint that helps to test new ideas in just five days.</em></p><p>Acknowledgments:</p><p><a href="https://www.linkedin.com/in/shravantickoo/">Shravan Tickoo</a> — <em>Breaking into Product Management powered by </em><a href="https://www.airtribe.live/"><em>Airtribe</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fd3cc276fbf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/user-experience-for-product-managers-part-1-6fd3cc276fbf">User Experience for Product Managers — Part 1</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[How to get objective feedback and prioritize them?]]></title>
            <link>https://medium.com/design-bootcamp/how-to-get-objective-feedback-and-prioritize-them-5d244ee32894?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d244ee32894</guid>
            <category><![CDATA[user-feedback]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[segmentation]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Tue, 08 Mar 2022 13:09:56 GMT</pubDate>
            <atom:updated>2022-03-12T04:09:28.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="image: Freepik.com" src="https://cdn-images-1.medium.com/max/1024/1*_SgKZhLesgH35O9eQbU6dA.jpeg" /></figure><p>During the product lifecycle getting objective user feedback is very critical for any product manager (PM). For a PM, it is very important to get user feedback that is actionable and easily comprehensible. Product decisions based on inaccurate and ambiguous feedback can lead to disastrous impacts. However, it is a little tricky to get the user to tell what is it that they expect from a product. It takes some work from the PM to identify the right target group (TG) and then ask the TG the right questions in the right way to get an actionable response.</p><h4>Identifying the target user group</h4><p>There are multiple ways to zoom in to the TG. However, one of the ways that this could be done is described in <a href="https://www.wiley.com/en-us/The+Lean+Product+Playbook%3A+How+to+Innovate+with+Minimum+Viable+Products+and+Rapid+Customer+Feedback-p-9781118960875">The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback queue</a> By Dan Olsen [ A summary of Dan Olsen’s book in his own words is available in YouTube — <a href="https://www.youtube.com/watch?v=m_c-B_MrxQU">https://www.youtube.com/watch?v=m_c-B_MrxQU</a>]</p><p>Getting to TG is like zooming in across customer attributes traversing from <strong>Demographic</strong>, <strong>Psychographic</strong>, <strong>Behavioral</strong>, and finally <strong>Needs based </strong>segmentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XMmw0ah6ZcfcyCTVFqlyhg.jpeg" /><figcaption>Getting to the TG is like peeling an onion. Even though the size of the market reduces, the value proposition increases significantly</figcaption></figure><h4>Understanding customer needs</h4><p>Once TG is identified, the next hurdle is to understand what are the unmet needs, or challenges, or pain points specific to a task or an activity that the customer is doing. This is done either by interviewing the customers in the TG or observing them while they use an existing product. Now, the focus is to identify the needs that the TG has that the existing product could not satisfy. This is the <strong>problem space</strong> — where all the customer needs reside. However, in the interview, customers find it difficult to articulate their needs very clearly without a reference point. This is because some needs remain unarticulated or unexpressed and the customer doesn’t discuss them during the interview. Moreover, there could be unknown needs and the customer doesn’t realize that they value something until that interview.</p><p>Thus having a reference point, which could be an existing solution that meets their need partially, could make a lot of difference. This reference point which could be an existing product, or a product design such as a mockup, or a wireframe, or a prototype, all of them exists in <strong>solution space</strong>. In general, customers do not give great feedback when asked a very abstract question like what are top 3 features you like in a car? Responses of such questions could be very generic or vague and there would not be much insight in there. This is because the customer is responding from a problem space context and they could not be sure what are the major problems they face. Interestingly, the same customer when asked a question from a solution space standpoint like, What are the features you like or dislike in a car of make A? they would give very pointed feedback and very insightful response. This is because they have a reference point in their mind and very quickly can playback their past experiences in their mind and give accurate response. PM with good interviewing skills listen actively to customer responses, repeating their statements back to ensure the understanding is clear. While doing so they validate their understand by asking additional clarifying questions to get a deeper understanding of the problem space.</p><h4>Prioritizing the needs before addressing them</h4><p>At this point, the PM has explored the problem space and identified the various customer needs that the incumbent product could not address and the new product could meet. But all of these could not be met at once. So, the PM uses a prioritization framework to prioritize the different needs — and prioritizing based on customer value is a good approach. A simple way to determine customer value is using a 2X2 matrix. X-axis represents user satisfaction with a current solution with a value low to high. This indicates how well an existing solution meets their needs and is related to the solution space. Y-axis represents the importance of user need with a value low to high. For a customer, different needs will have different levels of importance and this is related to the problem space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-NiVMFVcwhWaCeL2vdwTQ.jpeg" /><figcaption>Source: The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback queue By Dan Olsen</figcaption></figure><h4>Pitfalls to avoid</h4><p>There are a few pitfalls and PMs need to steer clear from them:</p><p><em>Surveying the wrong people; can be avoided by identifying the TG</em></p><p><em>Asking the wrong questions and asking leading questions</em></p><p><em>Trying to help the interviewer may not give the right result as this is the only place when the PM needs to only observe and provide a commentary and ask clarifying questions</em></p><p><em>“Product blindness” or blind spots for the issues that a new user will readily encounter but otherwise remain hidden from the PM</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d244ee32894" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-get-objective-feedback-and-prioritize-them-5d244ee32894">How to get objective feedback and prioritize them?</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[Lateral Thinking and Vertical Thinking in Product Management]]></title>
            <link>https://chiranjib1979.medium.com/lateral-thinking-and-vertical-thinking-in-product-management-475b3edd729e?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/475b3edd729e</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[lateral-thinking]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Sun, 27 Feb 2022 21:00:05 GMT</pubDate>
            <atom:updated>2022-02-28T05:45:48.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ubm_nEjsUrA3cWQqYBK6kA.jpeg" /><figcaption>Photo created by freepik — <a href="http://www.freepik.com/">www.freepik.com</a></figcaption></figure><p>Product Management, more than anything else, is a responsibility charter and a Product Manager (PM) is accountable for delivering a product that addresses a market need. At the same time this should present a viable and sustained business opportunity. It goes without saying that a good PM identifies opportunity for value that might not be clear to others.</p><p>This value discovery, however, does not happen in vacuum. It is not that PMs accidently stumble upon a breakthrough idea that can change the current customer paradigm and comes up with a grand idea to build a product that delivers a 10x value to the end customers.</p><p>On the contrary, true product discovery happens when a PM remains loyal to the problem and identifies a void in the market. There could be an unmet need or an unaddressed pain point that could not be met by any of the incumbents and a good PM is able to identify that opportunity and capitalize on that. However, this does not come easily. Good PMs rely on their vertical thinking and lateral thinking abilities along with customer empathy and knowledge to identify such opportunities.</p><p>Vertical thinking is a step by step sequential process which is more analytical and is backed up by evidences and data. It is a kind of thinking which PMs uses to bring frequent delta changes in a product based on some evidence and over time these delta changes compound to a significant drift in a positive way. In this case, the bets are small and there is always an option to fall back on the safety net. Though these small changes are like baby steps but these baby steps actually serve three purposes:</p><ol><li>It helps to maintain or improve the product-market fit</li><li>If the product is in the growth stage, it helps to delay the onset of maturity stage of the product by extending the growth stage of the product</li><li>It helps to maintain the value differential over the incumbents</li></ol><p>Few metrics that could be leveraged to understand the impact of the incremental changes are Net Promoter Score (NPS), Daily Average Users (DAU), Monthly Average Users (MAU) and Customer Churn Rate. PMs with a good understanding of the customer can design experiments that yields quick feedback which helps to build solutions that improves these metrics over time.</p><p>On the other hand, lateral thinking, a term coined by psychologist Edward De Bono, is the thinking process that creates new solution alternatives altogether that were previously considered inconceivable. It is about approaching a problem from a different direction altogether and identify a solution which is path breaking. Lateral thinking accompanied with deep customer and market learning can bring magical outcome. The profound customer insight leads to a “pivot” which may bring about a hockey stick growth. Founded in 2014, Swiggy, a hyperlocal food delivery organization brought in a paradigm shift which has led to magic for Swiggy to keep unlocking new business opportunities with ease. It decided to venture into new business verticals i.e. Swiggy Stores and Swiggy Genie. It has successfully enabled services like Instamart, Stores, Genie, etc. and has multiple offerings in the pipeline aimed towards the vision of delivering unparalleled convenience for consumers. [Source: <a href="https://bytes.swiggy.com/re-architecting-swiggys-logistics-systems-ddf301a29fa0">Re-Architecting Swiggy’s logistics systems</a>]. However, adopting lateral thinking to solve a problem is risky and requires more meticulous validation and accurate understanding of the market. It is a high risk — high return proposition and requires a strong feedback cycle to arrive at the right conclusion. As it is a non-linear approach to problem solving, it needs a strong validation process. Implementation of such change takes time and is far and few.</p><p>While vertical thinking helps to narrow in and focus, lateral thinking, on the other hand brings innovation and disruption. Nevertheless, both vertical thinking and lateral thinking are indispensable skills for a PM. PMs equipped with the right insights on the customers can exercise them based on what is at stake and what are the desired outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=475b3edd729e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Notes on Product Market Fit]]></title>
            <link>https://chiranjib1979.medium.com/my-notes-on-product-market-fit-5fedee47ebee?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fedee47ebee</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-market-fit]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Sun, 20 Feb 2022 17:35:40 GMT</pubDate>
            <atom:updated>2022-02-20T17:42:51.641Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RfwNmruIzlFPLeOwHqgGA.jpeg" /></figure><p>Product Market Fit or PMF is undoubtedly the most sought after thing for any product management (PM) team regardless they are part of a start-up or an established company. And because the market is always changing, it is more like a constant pursuit. Many teams identify PMF through several iterations of customer experiments and they spend lot of energy and time to do that and they become successful. However, there are still many PM teams who gives up the chase for so many reasons and PMF remains illusive to them.</p><p>The few definitions of PMF that I came across are:</p><p><em>“Product/Market fit means being in a good market with a product that can satisfy that market.”</em> [from Marc Andreessen’s essay <strong>The only thing that matters</strong> <a href="https://pmarchive.com/guide_to_startups_part4.html">https://pmarchive.com/guide_to_startups_part4.html</a>] This is a remarkable read for any PM or an entrepreneur.</p><p>In another YouTube video <strong><em>David Rusenko — How To Find Product Market Fit </em></strong>[<a href="https://www.youtube.com/watch?v=0LNQxT9LvM0">https://www.youtube.com/watch?v=0LNQxT9LvM0</a>] explains in a very practical sense how he and his fellow founders, Chris Fanini and Dan Veltri got to PMF for <a href="https://weebly.com/">weebly.com</a>. The journey was exciting and the way David narrates it with a timeline makes it very interesting. Slowly unfolding one milestone at a time and after 18 months finally the “Aha” moment.</p><h4>How do you know if you have product market fit?</h4><p>If you have already a version out there and the customers are not quite appreciating the value of the product that matches the expectation of the PM team and there is not much pull from the market, the PMF is still not there. Activation is not picking up or customers are not returning as often and revenue is trickling intermittently. Customers are still not lining up to get the product are some of the evident signs of not getting the PMF right.</p><p>On the other hand, if the word of mouth is spreading faster than expected and activation is pointing north and NPS is higher than 50% with revenue starting to flow faster and customers is queuing up at the door points to getting the PMF right.</p><h4>How the journey to PMF looks like?</h4><p>Again referring to the same YouTube video, David Rusenko explains this journey very practically from his firsthand experience with Weebly. At this stage of the journey, rapid experimentation with short customer feedback loop is very important. However, solutions proposed by the customers may not be as valuable. It is important to pay attention to:</p><ol><li>What problem are they trying to solve?</li><li>How are they solving it presently?</li><li>What change will happen in their lives if that specific problem is solved?</li></ol><p>This has to be done iteratively using prototypes. To reduce stress on the limited resources, focus should be on getting a prototype as fast as possible to collect feedback. Scaling and monetization is not the focus at this stage. The number of iterations could be more than expected. Also feedback should be taken from the target customer and not just any customer. Moreover, the PM team also needs to understand that their learning from these feedback sessions may change their understanding of who their target customer is. It may also change their understanding of the problem they are trying to solve.</p><h4>What happens if you come across a roadblock in the journey?</h4><p>In the course of finding PMF, PM team may need to “pivot” a few times. Pivot, as explained by Eric Ries in The Lean Startup [<a href="http://theleanstartup.com/">http://theleanstartup.com/</a>], is a “structural course correction to test a new fundamental hypothesis about the product, strategy and engine of growth”. In the YouTube video <strong>Eric Ries explains The Pivot</strong> [<a href="https://www.youtube.com/watch?v=1hTI4z2ijc4">https://www.youtube.com/watch?v=1hTI4z2ijc4</a>] with great examples to explain the concept in a nutshell.</p><p>In another YouTube video, <strong>Hiten Shah on The Art of Pivoting Towards Product-Market Fit at Lean Product Meetup</strong> [<a href="https://www.youtube.com/watch?v=idm__alXZ5w">https://www.youtube.com/watch?v=idm__alXZ5w</a>] talks about three pivot types:</p><ol><li>Product pivot (when a part of the product is stickier than the other parts of the product)</li><li>Customer pivot (when a new customer segment is pulling the product more than the customer segment targeted initially)</li><li>Problem pivot (when the PM team realizes there are bigger problems that are worth solving)</li></ol><p>The pivots are essentially rooted in customer learning. It is also very important to communicate these learning to the stakeholders in a structured way much early in the process to avoid last minute surprises. Pivots can be painful at times because the team has to let go some amount of work but this is worth it because the team can focus on a more relevant problem or more challenging and fundamental pain or finds a shorter way to PMF or unlocks an alternate way to a larger reward.</p><h4>How it looks like when the team got PMF?</h4><p>As Marty Cagan puts in his essay <strong>Product Market Fit</strong> [<a href="https://svpg.com/product-market-fit/?utm_source=sendfox&amp;utm_medium=email&amp;utm_campaign=top-50-resources-on-productmarket-fit-sachin-rekhi">https://svpg.com/product-market-fit/?utm_source=sendfox&amp;utm_medium=email&amp;utm_campaign=top-50-resources-on-productmarket-fit-sachin-rekhi</a>] PMF for B2B product is the point when there are 5 or so referenceable customers. For platform products, it is a threshold number of applications successfully built and deployed using respective API or platform services. For consumer products, this is the point when the engagement metrics such as NPS or DAU or WAU heads northwards consistently, however, appropriate metrics for PMF may be based on the unique situation.</p><p><em>I plan to come back and update the post further as I read more about PMF. Meanwhile, please feel free to add a comment or a link which can make these notes robust.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fedee47ebee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to prevent feature bloat?]]></title>
            <link>https://chiranjib1979.medium.com/how-to-prevent-feature-bloat-7673aa06792a?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7673aa06792a</guid>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[feature-bloat]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Sun, 13 Feb 2022 12:37:03 GMT</pubDate>
            <atom:updated>2022-02-13T13:06:28.509Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="&lt;a href=’https://www.freepik.com/vectors/brain&#39;&gt;Brain vector created by freepik — www.freepik.com&lt;/a&gt;" src="https://cdn-images-1.medium.com/max/1024/1*OqvImcWj1DcgS2zbDoZnFQ.jpeg" /><figcaption>PC — Brain vector created by freepik — <a href="http://www.freepik.com/">www.freepik.com</a></figcaption></figure><p>When a product has too many features that do not solve the core problem of the user, it is likely that the product is suffering from what is called feature bloat. For any product, user feedback is most important. However the product team also needs to carefully choose what to consider and what not to consider in the product backlog.</p><p>Feature bloat can very easily come into the product without the product team’s realization if they are not very tightly coupled with user needs and the core problem they are trying to solve. I remember renting a car some time back because my regular drive was away for repairs. The moment I sat on the driver’s wheel, I was overwhelmed with so many indicators and lights and controls. I was certain I was not flying an aircraft and I found so many dials, lights, and indicators a bit distracting. I am sure some people may have preferred them but they are clearly not my persona. I have changed my car a few times after that but stayed away from that Make all the time I choose my next car. Not that I could not afford them but more so because I knew they are not my type of car.</p><p>Many companies get into the trap of feature bloat due to competitive pressure, in search of creating the best of everything. They want to create their product unique, with a differentiation that will give them an edge over their competitors. To make their customers happy they keep on adding that extra feature. This is the point where there needs to be a check that can validate whether that extra feature is at all necessary. There are many products you could find that do an excellent job at it. However, you will come across many products that kind of gives in to it.</p><p>And just to remind you that feature bloats are not cheap in any terms. Any added feature takes a huge cost of addition. Feature bloat adds to the cognitive load and confuses the users. It impacts negatively on customer satisfaction in the short run and brand value over the long run. It also increases the opportunity costs in terms of lost time and effort to build and unbuild these features into the product.</p><h4>How to identify that feature bloat is creeping into the product?</h4><p>Once the feature bloat creeps in, customer engagement will start suffering. Metrics like DAU or daily active user count and WAU or weekly active user count will be impacted negatively. NPS and CSAT scores will also suffer due to it. After any release, if these metrics steers south and cannot be attributed to any other reason then that is an amber flag already.</p><h4>How do you prevent it?</h4><p>When you sense a potential feature bloat, the best way to validate is to go back to the problem that you just solved and validate it against the persona. Also validate it against the core problem and how close it is aligned to it. Is it helping to converge to the core objective? If not, there has to be some bit of course correction that may be needed to come out of it.</p><p>Moreover, the goal is also to ensure the product team does not fall into the same trap again. And mind it, there are ample traps out there in terms of a defect fix or customer feedback or simply a directive from the top management.</p><p>A very useful template as outlined by <a href="https://www.linkedin.com/in/mattlemay">Matt Lemay</a> in his book <a href="https://www.oreilly.com/library/view/product-management-in/9781491982266/">Product Management in Practice</a> puts it in simple terms.</p><p>Identify what is the issue? — define the problem statement as clearly as possible for everyone to comprehend it. This needs to be clear so that it can be validated with the core problem without any ambiguity.</p><p>Who reported the issue? — it helps to identify what is the source and the following course of action. Depending on the source there need to be different strategies to validate it. How you plan the next actions will vary if it has come directly from the top like a senior sales partner versus if it has come from a customer versus if it has come from a support team representative.</p><p>How many users is it affecting? — this helps to align it to the persona and whether that is the target persona for the product. It also helps in prioritization decisions in the backlog discussion.</p><p>Is there revenue directly tied to this issue? if so how much? — response to this is question is critical and has to be validated early and as accurately as the constraints permit.</p><p>What would happen if this issue were not addressed in the next two weeks? and, What would happen if this were not addressed in the next six months? — Now these questions are important to answer because there can be a revenue impact but there can still be some time to actually fix that problem. This obviously depends on the industry and the problem that the product is trying to solve however this check also helps to understand the severity of the issue very precisely. Also answer to these questions helps to strengthen your defense incase the directive has come from the top.</p><p>And lastly, who is the contact person for further discussing/resolving this issue? — this helps to identify the next steps and sets you in the path of closure which is very important.</p><p>I have found this very useful and my shout-out to <a href="https://www.linkedin.com/in/mattlemay">Matt Lemay</a> for this simple yet effective tool.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7673aa06792a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ABCD of Product Lifecycle Mistakes]]></title>
            <link>https://chiranjib1979.medium.com/abcd-of-product-lifecycle-mistakes-226412dc5a73?source=rss-f58ba97df6f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/226412dc5a73</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-management-skills]]></category>
            <dc:creator><![CDATA[Chiranjib Bhattacharjee]]></dc:creator>
            <pubDate>Wed, 22 Dec 2021 15:00:56 GMT</pubDate>
            <atom:updated>2021-12-23T18:26:34.083Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmePnYJGgzqKmuycpvMmDQ.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/geralt-9301/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=776670">Gerd Altmann</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=776670">Pixabay</a></figcaption></figure><p>There are many things that companies do to make their customers happy. Every company wants to see happy customers who go gaga about their products or services. Rightly so that is the way to create a leadership position in the market.</p><p>While having a killer product or service is the key however many companies can fall prey to their own over-confidence in the customer insight they have. This over-confidence creeps in from assumptions about customers that are not validated. There could be gaps in persona creation or inaccurate customer journey mapping for the persona and there could be many more.</p><p>Once the gap goes unnoticed, mistaken assumptions are taken forward in the design and build decisions. There are gates like prototyping and value discovery where such gaps could be discovered before the product is taken to the market, however, as I mentioned earlier over-confidence can be a sticky blindfold that is very difficult to remove.</p><p>Once such a product or feature ends up in customers’ hands, obviously customers might have problems. Some customers will run away at the earliest opportunity. There will be few customers who are loyal and can come back to voice their problems. Some companies will listen to them patiently and they will go back to their notes and papers to understand what went wrong. Other companies, at this point, fall victim to the first mistake which is to “<strong>avoid</strong>” customer interactions. This is mostly cultural and the notion is the customer is always looking for features or changes. This missed opportunity is not validating the golden assumptions that are actually responsible for this situation.</p><p>Even for the ones that have taken time to listen to the customer, some of the companies may actually fall victim to another adversary which is “<strong>blame</strong>”. Some companies will blame it on the customers’ lack of knowledge or low techno-savviness. This tells a lot about the maturity of usability validation in the design process. But some companies take this feedback positively and accept the gap and try to correct it.</p><p>Once companies accept the gap, they take a few steps back and try to mend their ways forward. They come back with alternatives and options for the customers they love to help. It is in no way an easy task and they have to work very hard for that. Nevertheless, if they have not validated the incorrect assumption and corrected it in the first few steps, they come up with options that tend to “<strong>confuse</strong>” the customer. This can be a costly mistake as this can result in the churn of some loyal customers who voiced their concern with the hope that their problems might get solved. Iteratively discovering value is a prevalent practice but the trick is to go back to the basics and fix the fundamentals (correct the erroneous assumptions in this case) and then pivot rather than taking a pre-mature call at the face value.</p><p>Companies who have come this far by fixing the fundamental assumptions can successfully mend the dented customer trust by delivering a workable solution without further “<strong>delay</strong>” which the next adversary. The delay could be for so many reasons but mostly it may be due to operational reasons. Companies that have not implemented agile and continuous delivery in the true sense may find it difficult to turn the fix around within the expected time.</p><p>The issues may seem very trivial, however, some of them can cause serious bottlenecks and may impact the product’s growth trajectory significantly. The issues can be effectively eliminated with proper alignment of organization goals and practice of an open culture that celebrates experimentation and learning from them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=226412dc5a73" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>