<?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 Ishant Juyal on Medium]]></title>
        <description><![CDATA[Stories by Ishant Juyal on Medium]]></description>
        <link>https://medium.com/@ishantjuyal?source=rss-69ea2aa5a8ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rn7FF3ysFtbXViRDmi4Ukg.jpeg</url>
            <title>Stories by Ishant Juyal on Medium</title>
            <link>https://medium.com/@ishantjuyal?source=rss-69ea2aa5a8ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:05:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ishantjuyal/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[Practicing Product Management interview questions the right way!]]></title>
            <link>https://ishantjuyal.medium.com/practicing-product-management-interview-questions-the-right-way-d4ee10a65b9b?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4ee10a65b9b</guid>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[ai-product-management]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Sun, 24 May 2026 05:53:12 GMT</pubDate>
            <atom:updated>2026-05-24T05:53:12.027Z</atom:updated>
            <content:encoded><![CDATA[<p>Yes, there’s a wrong way to do it.</p><p>If you have been a regular reader of my content, then you must know that I am writing after a very long time.</p><p>So, where was I? What was I doing?</p><p>I was working on something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24UYhqHDODfT9EzaE4zlOQ.png" /></figure><h3>Introducing: PM Quest 🚀</h3><p>PM Quest is a <strong>LeetCode-style practice ground for Product Managers</strong>.</p><p>It’s a place where you can regularly answer <strong>product thinking problems</strong> — the kind you get in:</p><ul><li>PM interviews</li><li>Case rounds</li><li>“how would you think about this?” real-work scenarios</li></ul><p>Not only that, you can see other people’s answers and learn from them. And now, you can even get instant feedback from AI and see an “expert answer” to improve your product thinking.</p><p>The goal is simple: <strong>get faster, clearer, and more structured</strong> in how you think and communicate about product.</p><p>Currently, we are at 75 users and are looking for more so that we can get feedback and make a product that every PM and aspiring PM wants to use.</p><p>Here are some of the most interesting problems you can solve:</p><h3>Investigating Dip in Track Completions for New Spotify Premium Converts</h3><p>Imagine you’re the PM for Spotify’s Premium subscription. How would you investigate a sudden 8% dip in daily track completions (listening to a track fully) specifically for users who recently converted from a free trial?</p><p><a href="https://www.pmquest.live/problems/0c0bc206-0dc9-4ee9-af09-770d75123d9f"><strong>Solve it here</strong></a></p><h3>Optimising Delivery Navigation for Complex Locations in Google Maps</h3><p>Design a new product or feature for Google Maps that specifically addresses the challenges delivery drivers face when navigating complex apartment complexes or large corporate campuses, aiming to improve efficiency and reduce frustration.</p><p><a href="https://www.pmquest.live/problems/9d6d4a4a-663d-4e64-b86f-dce9cbd67b14"><strong>Solve it here</strong></a></p><p>And so many more…</p><p>And not only this, there is so much else you can do. We have added some interesting things.</p><p><strong>Karma</strong></p><ol><li>Earn karma points for each question you answer and see yourself on the leaderboard.</li><li>For each upvote you get, you earn karma points, showing how much you have contributed to the community.</li><li>Karma is not competitive. It’s a measure of you being better than others, it’s a measure of your contribution.</li></ol><p><strong>Public Profile</strong></p><ol><li>What’s a platform without social profile. So, we added a social profile for you.</li><li>Here’s my public profile: <a href="https://www.pmquest.live/u/ishantjuyal">Ishant Juyal</a></li><li>You can select your own username, so go on, claim the one you really like.</li><li>There’s a lot of work needed to make these public profiles useful and something that shows the work you have put, so if you think there’s something we should add, let me know.</li></ol><h3>AI Feedback</h3><p>BUT, recently I realised that the platform has a big flaw. When the user solves a problem, they submit the answer but they don’t really know if it’s a good solution or not.</p><p>Unlike programming, there is no objectivity to the right answer in product management. The only thing they have is another answer from a peer or from an AI export we have to compare.</p><p>So, I built a feedback feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*669w0fMFWjr5OxwN8jtZtg.png" /></figure><p>From now on, whenever you submit an answer, you also get the option to get feedback about what you did well and what you could have done better.</p><p>Just click on “Get Feedback” button and you will have a report in front of you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0TMo-W3WgQT5Ema6JOvTXw.png" /></figure><p>Not just that. If you want to see the gold standard of how the answer should have been, then you have an improved expert — AI PM also answering the question that you can only see after you submit your answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i18tfiD59Sl5PQhDZQ2Auw.png" /></figure><p>So now, you don’t have to wonder what you could have done well. Get feedback, learn what to improve and ace your next PM interview!</p><p><strong>Try it out now: </strong><a href="https://www.pmquest.live/"><strong>https://www.pmquest.live/</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4ee10a65b9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jobs-To-Be-Done Framework for Product Managers]]></title>
            <link>https://ishantjuyal.medium.com/jobs-to-be-done-framework-for-product-managers-ad5de5de6f41?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad5de5de6f41</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Tue, 09 Jul 2024 10:11:14 GMT</pubDate>
            <atom:updated>2025-05-31T17:28:52.596Z</atom:updated>
            <content:encoded><![CDATA[<p>When was the last time you bought something?</p><p>Why did you buy it?</p><p>Now think deeper, why did you really buy it?</p><p>Whenever a consumer buys something, they don’t just buy it, they hire that product to do a job for them.</p><p>If you hire a fry pan, why do you do it? You don’t buy it only because you want a fry pan, you need a fry pan to cook stuff.</p><p>Cooking is a job that needs to be done, and you hire the pan to do it for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*c-m-Df1qrqK4chuuaaz7DQ.png" /><figcaption>Why did Peter buy the snickers?</figcaption></figure><p>Below is an excerpt from a HBR article:</p><blockquote><em>After decades of watching great companies fail, we’ve come to the conclusion that the focus on correlation — and on knowing more and more about customers — is taking firms in the wrong direction. What they really need to home in on is the </em><strong><em>progress that the customer is trying to make in a given circumstance</em></strong><em> — what the customer hopes to accomplish. This is what we’ve come to call the </em><strong><em>job to be done.</em></strong></blockquote><p>JTBD framework tells us that users use products in certain situations when they want to achieve a specific outcome because of some reason that acts as their motivation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*Np0kheE96_4rdWRz3Tee_A.png" /><figcaption>Writing a JTBD statement</figcaption></figure><p>The core value of this framework is that it provides an approach to gathering an understanding of who your user is, and what their motivations and hopes are.</p><h3>How to implement this framework?</h3><p>Building better products start with a great JTBD statement. A jobs to be done statement concisely describes the way a particular product or service fits into a person’s life to help them achieve a particular task, goal, or outcome that was previously unachievable.</p><p>Here’s a JBTD statement template that is commonly used amongst Facebook and Instagram product teams:</p><p>When I…… (context)</p><p>But…… (barrier)</p><p>Help me…. (goal)</p><p>So I….. (outcome)</p><p>With those principles and end goal in the background, follow these four steps to gather all the info you’ll need to fill out your JTBD template:</p><ol><li><strong>Start by defining your audience clearly:</strong> Think about the defining characteristics that help you develop a crystal-clear image in your head of your audience. Without a clear definition, you risk going too broad or gathering signal from the wrong kinds of people.</li><li><strong>Ground yourself in market research:</strong> Understand as much as possible about this audience’s behavior: what they currently are using to solve this specific problem and where they feel the most pain in the customer experience.</li><li><strong>Talk to your users:</strong> Using surveys and interviews, get a firsthand account about your user’s mindset and decision process (related to what you are building).</li><li><strong>Prioritize:</strong> There are many customer jobs your product could tackle, but focus is paramount here. From user interviews, look for themes that emerge in jobs to be done. Narrow down jobs and prioritize those with the most demand and the largest gap to be filled.</li></ol><p>How to think about which jobs to tackle in the JTBD framework? This image might help you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*iqcT6nzwyHWlTkZHh40mFQ.png" /><figcaption>How to prioroitize problems</figcaption></figure><h3>Examples of JTBD Statements — Discord JTBD</h3><blockquote><em>When I want to jump into my favorite game, but I don’t know if there are people around to play, help me safely coordinate with a group of like-minded gamers, so I can easily find a way to enjoy my favorite multiplayer game.</em></blockquote><p>This suggests that we should make it easy to find people through public or private servers and switching easily from text to voice chat as the users organize and jump into a game.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad5de5de6f41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to answer Product Metrics Questions in a PM Interview]]></title>
            <link>https://ishantjuyal.medium.com/how-to-answer-product-metrics-questions-in-a-pm-interview-94fdc0088f0b?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/94fdc0088f0b</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 12:00:06 GMT</pubDate>
            <atom:updated>2025-05-31T17:28:39.634Z</atom:updated>
            <content:encoded><![CDATA[<h3>Choose your metrics!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4sr9HFu1IfR-dwgoL283iQ.png" /><figcaption>Important product metrics you should know</figcaption></figure><p>As a Product Manager, metrics play a pivotal role in assessing the performance, success, and impact of the products and features that you ship.</p><p>A team might ship a lot of features but it’s the responsibility of the PM to determine if they are shipping the right thing or not. Metrics help you do that.</p><p>If you are asking “how do they help in that?”, you should check out our resource on Product Metrics <a href="https://www.crework.club/resources/product-analytics">here</a>.</p><p>In a PM interview, you will be asked questions related to metrics either as part of a case study or a random question out of nowhere. Here are some examples:</p><ol><li>You might be asked a product design question — “Build a LinkedIn for blue collar workers.” and then you might be asked to come up with metrics that you would use to track the success of the feature/ product.</li><li>You might be asked — “What is the north star metric for Uber and why?”</li><li>You might be asked — “You have to perform an A/B Test for a feature. How would you do it?”</li></ol><p>All of these questions are testing your understanding of metrics and how they tie up with the product success. As a PM, it’s a must have skill.</p><p>Metrics serve as the compass guiding product managers in their journey towards success. They provide valuable insights into user behavior, product usage, engagement, retention, conversion rates, and other key performance indicators (KPIs). By leveraging analytics tools and methodologies, product managers can gain a deeper understanding of user needs, identify opportunities for improvement, and optimize product strategies for maximum impact.</p><p>Now, you know the questions that are asked and why they are asked but don’t know how we approach these questions. So, let’s talk about that.</p><h3>Let’s talk about the “How”</h3><p>When faced with metrics and analytics questions in a product management interview, it’s essential to demonstrate a structured approach and analytical mindset. Here are some steps to follow:</p><ol><li><strong>Understand the Feature/Product Objective</strong>: Begin by understanding the specific objective or goal of the feature or product. What problem does it aim to solve? What outcomes or improvements are expected? Understanding the purpose of the feature/product will guide your selection of relevant metrics.</li><li><strong>Identify Key Stakeholders</strong>: Consider the stakeholders involved in the success of the feature/product. This may include users, product managers, marketing teams, sales teams, and executives. Understand their perspectives, priorities, and expectations regarding the feature/product’s performance.</li><li><strong>Define Success Criteria</strong>: Clearly define what success looks like for the feature/product. What are the primary outcomes or KPIs that indicate its effectiveness? Success criteria may vary depending on the nature of the feature/product and the goals set by stakeholders. Examples of success criteria could include increased user engagement, improved retention, higher conversion rates, or enhanced user satisfaction.</li><li><strong>Brainstorm Potential Metrics</strong>: Based on the feature/product objective and success criteria, brainstorm a list of potential metrics that align with these goals. Consider both quantitative and qualitative metrics that provide insights into different aspects of user behavior, product usage, and business impact.</li><li><strong>Examples of potential metrics include</strong><br>- User Engagement: Metrics such as daily active users (DAU), monthly active users (MAU), time spent in app, frequency of use, or feature adoption rate.<br>- Retention: Metrics such as user retention rate, churn rate, repeat usage rate, or cohort analysis to track user retention over time.<br>- Conversion: Metrics such as conversion rate, click-through rate (CTR), sign-up rate, or completion rate of specific actions or funnels.<br>- Satisfaction: Metrics such as Net Promoter Score (NPS), customer satisfaction (CSAT) score, or user feedback ratings.</li><li><strong>Prioritize Metrics</strong>: Evaluate the list of potential metrics and prioritize those that are most directly linked to the success criteria and key objectives of the feature/product. Consider factors such as relevance, measurability, and actionability of each metric. Focus on selecting a manageable set of high-impact metrics rather than trying to track everything.</li></ol><p>Following all these steps, you will be able to answer any metrics question asked to you in the interview.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94fdc0088f0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to answer Guesstimate Questions in Product Management Interviews?]]></title>
            <link>https://ishantjuyal.medium.com/how-to-answer-guesstimate-questions-in-product-management-interviews-a188ffa12ffe?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a188ffa12ffe</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Sat, 29 Jun 2024 02:04:19 GMT</pubDate>
            <atom:updated>2025-05-31T17:27:44.264Z</atom:updated>
            <content:encoded><![CDATA[<h3>Guesstimates</h3><p>Guesstimates are basically approximations based on the available limited information. A guesstimate is an information-based guess, not an accurate answer.</p><p>For example, if I ask you how many people travel through IGI Airport Delhi daily, I am not expecting you to tell me the exact number but to estimate the number using your thinking and assumptions.</p><p>It doesn’t even matter what exact number you give to the interviewer, but the process and rational behind that number matters more.</p><p>Guesstimate questions can cover a wide range of topics, including:</p><ol><li><strong>Market Sizing:</strong> Estimating the size of a market, such as the number of potential customers or total addressable market (TAM) for a product or service.</li><li><strong>Volume Estimation:</strong> Estimating quantities or volumes, such as the number of golf balls that can fit in a school bus or the annual consumption of coffee in a particular city.</li><li><strong>Revenue Projection:</strong> Estimating revenue or financial metrics, such as annual sales of a product or the potential revenue from a new business venture.</li><li><strong>Time and Distance:</strong> Estimating time or distance-related scenarios, such as the number of pizzas sold in a city each day or the distance traveled by a commuter in a year.</li></ol><h3>Let’s talk about the “How”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bFriCUC3799JvWyW" /></figure><p>The process of solving a guesstimate problem is pretty simple: Look at the possible parameters that may affect the final quantity, and estimate its numbers. When faced with a guesstimate question, follow these steps to structure your approach:</p><ol><li><strong>Clarify Assumptions:</strong> Begin by clarifying any assumptions you need to make to proceed with your estimation. Clearly state these assumptions to ensure transparency in your reasoning. This might be the common steps in all type of PM interview questions.</li><li><strong>Determine Your Approach:</strong> Plan out your approach before diving into calculations. Ensure your method is clear and logical. Assign reasonable proportions for each segment based on your strategy. Keep communicating your thought process to the interviewer and seek their feedback.</li><li><strong>Break Down the Problem:</strong> Break down the problem into manageable components or sub-questions. Make an equation out of the problem as soon as possible and try to come up with the values of each part of that equation.</li><li><strong>Round Numbers and Approximate:</strong> Guesstimates don’t require exact calculations. Instead, focus on approximations and rounding numbers to simplify your estimations. This approach helps streamline your thought process and yield reasonable outcomes.</li><li><strong>Sanity Check:</strong> Finally, perform a sanity check on your estimation to ensure that your answer is within a plausible range and aligns with common sense. Revisit your assumptions and calculations if necessary to refine your answer.</li></ol><p>The best way to understand guesstimates better is via examples. So, let’s jump into some.</p><p><strong><em>Calculate the number of queries answered by Google per second.</em></strong></p><p>We’ll do a top-down approach.</p><p>Total searches per second= Total searches per day / 24 hours / 60 min / 60 sec</p><p><strong>Calculating total number of users who search on Google</strong></p><p>Global Population = say, 7.5B</p><p>Geographies excluded: China, Half of Russia (people here don’t use Google as their primary search engine); So, remove 1.5B population.</p><p>That leaves us with a population of 6B</p><p>Only 50% of people are connected to the internet, that leaves us with a population of 3B.</p><p>Google market share with Bing, AOL, and other regional engines: Let’s assume it to be about 70–80% = 75%.</p><p>So, we are left with 2.2B people who are potentially using Google search as their primary search.</p><p><strong>Usage Frequency</strong></p><p>We can segment them according to their frequency of usage. I would say there are 3 types of searchers:</p><ol><li>Aggressive</li><li>Active</li><li>Passive</li></ol><p>Passive searchers are those who don’t use the internet to search daily (like old people, kids, and the majority of the rural population). Assuming this type represents the majority of 50% = 1.1B people</p><p>Active people would search once a day. Assumed to be 25% of the population = 550M people</p><p>Aggressive searchers are super active searchers who might search 4–8 times a day (Take average of 6). Assumed to be 25% of the total population = 550M people</p><p>Total searches per day = Number of users who search * Number of times they search on Google</p><p>Total searches per day = 550M<em>1 + 550M</em>**6 = 3.8B searches per day</p><p>Total searches per second= 3.8B / 24 hours / 60 min / 60 sec = ~ 44,000 searches per second</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a188ffa12ffe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to answer behavioral questions in PM Interviews]]></title>
            <link>https://ishantjuyal.medium.com/how-to-answer-behavioral-questions-in-pm-interviews-c8ef81d0f8d1?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8ef81d0f8d1</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Wed, 26 Jun 2024 07:32:52 GMT</pubDate>
            <atom:updated>2025-05-31T17:27:29.399Z</atom:updated>
            <content:encoded><![CDATA[<h3>Behavioral Questions</h3><p>The Behavioral Round focuses on assessing your past experiences, behavior, and decision-making in professional settings.</p><p>During the Behavioral Round, interviewers are looking to evaluate several key attributes:</p><ol><li>Communication Skills</li><li>Problem-Solving Abilities</li><li>Leadership and Teamwork</li><li>Decision-Making</li><li>Adaptability and Resilience</li></ol><p>For example, you can be asked — “Tell me about the challenge you had with your co-worker and how you handled it?” Through this question, the interviewer wants to check your communication skills, your ability to take decisions and stakeholder management.</p><p>Here are a few sample behavioral questions you might encounter:</p><ul><li><em>Describe a time when you had to navigate conflicting priorities on a project.</em></li><li><em>Can you share an example of a successful product launch you were involved in? What was your role, and how did you contribute to its success?</em></li><li><em>Tell me about a time when you had to influence stakeholders who were resistant to your ideas.</em></li></ul><h3>Why it matters</h3><p>Seeing a list of skills is all well and good, but an interview also gives a company a chance to gauge how you behave in different situations. They want to know that you work well in high-pressure environments, that you’re able to influence without authority, and manage stakeholder expectations. Behavioral questions provide insights into your past behavior and experiences, offering valuable clues about your future performance as a Product Manager.</p><h3>Let’s talk about the “How”</h3><p>I know the question you have right now is — How can I prepare for this round then?</p><p>To excel in the Behavioral Round, follow these tips:</p><ol><li><strong>Prepare Stories:</strong> Identify key experiences from your past that demonstrate relevant skills and qualities. Structure these experiences using the <a href="https://www.themuse.com/advice/star-interview-method">STAR method</a> (Situation, Task, Action, Result) for clarity and coherence.</li><li><strong>Be Specific:</strong> Provide concrete examples and details in your responses. Use specific anecdotes, metrics, and outcomes to illustrate your points and make your stories memorable.</li><li><strong>Highlight Leadership:</strong> Emphasize instances where you’ve taken initiative, led teams, or influenced outcomes. Showcase your ability to inspire others, drive results, and navigate challenges effectively.</li><li><strong>Stay Positive:</strong> Even when discussing challenging situations or failures, focus on the lessons learned and your growth from the experience. Frame setbacks as opportunities for development and improvement.</li><li><strong>Practice Active Listening:</strong> Pay attention to the interviewer’s questions and cues. Listen actively, ask clarifying questions if needed, and tailor your responses to address the interviewer’s concerns.</li></ol><p>During the interview, make sure that you understand the INTENT of the question. Do not try to force-fit any of the prepared answers, but rather take 1 or 2 seconds to understand what the interviewer is trying to know.</p><p>Use your best judgment to think about what type of skill the interviewer is trying to evaluate here (leadership, problem-solving, etc.), gather your thoughts, and then speak.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DOWraM8No7Y5Sh8U" /></figure><h3>Common Behavioral Questions</h3><p>You must be sharing why am I not sharing the “how to solve it part” today. Because behavioral questions are stories and mostly test your communication skills. It’s hard to teach soft skills by telling you my story, it’s something you learn by practicing.</p><p>So, here are some of the most common questions:</p><ol><li>Tell me about a time you pivoted strategies and stakeholders disagreed.</li><li>Tell me about a time you had to make a decision to make short-term sacrifices for long-term gains</li><li>Tell me about a time you handled a difficult stakeholder.</li><li>Tell me about a time you made a mistake.</li><li>Tell me about a time you had a conflict with someone. How did you resolve it and what did you learn?</li><li>What product that you led are you most proud of and why?</li><li>Tell me about a time you’ve solved pain points for customers.</li><li>What was your biggest failure as a product manager?</li><li>Describe a situation where you negotiated a win-win situation.</li><li>Tell me about a time you used a specific metric to drive change in your department.</li></ol><p>Obviously these are just the most popular ones, and there can be multiple questions about you and your past work. But having a story bank covering all these questions should be more than enough for you to encounter any question.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8ef81d0f8d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to answer Product Design questions in a PM Interview]]></title>
            <link>https://ishantjuyal.medium.com/how-to-answer-product-design-questions-in-a-pm-interview-a042639086cd?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a042639086cd</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-interview]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Fri, 21 Jun 2024 10:05:13 GMT</pubDate>
            <atom:updated>2025-05-31T17:27:12.447Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Design Questions</h3><p>In every Product Management interview process, you will come across a product design question. A typical example of a product design question is something like this — “How would you build an Interview Preparation tool for LinkedIn?”</p><p>The interviewer asks you to build or design features or products for a target segment. Even thought it is called Product Design question, but you are not really supposed to “design” anything using any tool.</p><p>You must be thinking, “If I am not supposed to design, what am I supposed to do?”</p><p>Before we go into that, let’s talk about the “why” behind this round.</p><h3>What is your interviewer looking for?</h3><p>While interviewing a PM candidate, you look for the following things:</p><ol><li>Empathy — The interviewer wants to make sure that you can think about their customers, their needs and wants and really be in the shoes of the customer.</li><li>Design Thinking — Can you evaluate how well designed a product is? What are the ways in which a product is well designed and what are some gaps?</li><li>Passion — The interviewer wants to make sure that the candidate is passionate about the PM role and products in general.</li></ol><p>Cool, now we understand what the interviewer wants to assess. Let’s move on to how you will solve the product design problem.</p><h3>Product Design Process</h3><p>A simple but very effective framework for solving product design questions focuses on the users: Who are they? What do they need? How can we address that need?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iNzi7GSyoMYQgLTZ.png" /><figcaption>How you can solve product design questions</figcaption></figure><p>We can also think of this in the terms of the Design Thinking framework. If you don’t know what’s design thinking is, read this — <a href="https://30daysofpm.substack.com/p/day7">Design Thinking</a>.</p><p>Design thinking basically has 5 steps. We can walk through any product design question while following these steps:</p><p><strong>Ask clarifying questions</strong></p><ol><li>The purpose of asking clarifying questions is two-fold. These questions can help you:<br>a. Understand the problem you are supposed to solve<br>b. Buy time to think about how to approach the question</li><li>Your clarifying questions will vary based on the case so I won’t list too many.</li><li>Examples of clarifying questions:<br>- Why are we doing X? What does the company want to achieve through this?<br>- Who is this for? Why would they use it?<br>- Who am I in this situation? Google PM? New startup?</li><li>Don’t ask more than two or three clarifying questions. Interviewers want to see that you can make decisions based on logical assumptions, so be prepared to answer your own questions (interviewer can ask you: “who do you think we should build for?”).</li></ol><p><strong>Empathize — Identify the users</strong></p><ol><li>“Who is my user?”, “What matters to this person?”</li><li>Learn about the audience for whom you are designing. With any product question, the first step is always to identify the users.</li><li>No matter how simple the question seems to be, start by clearly defining who you think the main user group is. It’s fine if you think there are several core user groups — call them out!</li><li>For a lot of product design questions, it’s fine to have a broad user group. Perhaps it’s “millennials” or perhaps it’s “people who shop online”. It could be interest-focused, like “people who like to explore new restaurants”.</li><li>The user group can be defined by any number of factors, such as demographics, profession, background, experiences, or interest.</li></ol><p><strong>Define — Identify relevant user needs</strong></p><ol><li>“What are the user needs and product goals?”</li><li>Once you’ve declared the target user, identify the problem they have.</li><li>Remember that, when discussing a product, there’s usually one or a couple main pain points as well as adjacent needs the target users may have.</li><li>Discuss with your interviewer about the various use cases for the users and prioritize to focus on one of them.</li></ol><p><strong>Ideate — Identify product solutions</strong></p><ol><li>Brainstorm and come up with as many solutions as you can for the problem.</li><li>If you’re analyzing an established product, chances are that it does solve the needs of its target audience(s) — that’s what keeps it in business. But, users’ needs are rarely solved 100% of the time, so you should think about ways the product could improve.</li><li>Don’t be afraid to describe in plain language why you think a product fulfills the user’s need well, even if it seems relatively obvious. It’s fine to come up with only an incremental change.</li><li>The most important thing to do is to tie everything back to the target users and their needs. This sounds simple, but it’s easy to forget in the heat of the moment.</li><li>At this stage, it’s less about having a “right” answer and more about showing how much you think and care about the user and can come up with ideas to solve those problems.</li></ol><p>This basic framework will get you pretty far with a product design question. Often, there are next steps which would strengthen your answer or which the interviewer might request.</p><ol><li>You might be asked to draw some wireframes to communicate your solution visually.</li><li>One extension goes into product metrics. Given the user, user need and product, how do we know quantitatively how well the product solves the need? Read about product metrics here — <a href="https://30daysofpm.substack.com/p/day23">Product Metrics</a>.</li><li>Another direction that could be fruitful is considering the competitive landscape — is there a product out there that does something similar to what you’re describing? How well do they solve the user need? How can your product differentiate yourself? Or, you could discuss any business considerations here, like how you think your product could be monetized.</li></ol><p>Product Design questions can have a wide scope but the basics always come down to the same thing — identify the target user, their needs, and what does (or doesn’t) fulfill those needs. Think like a PM.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a042639086cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are Growth Loops and how can you use them?]]></title>
            <link>https://ishantjuyal.medium.com/what-are-growth-loops-and-how-can-you-use-them-0dd53f950b7e?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dd53f950b7e</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth-loop]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Sun, 16 Jun 2024 05:59:36 GMT</pubDate>
            <atom:updated>2025-05-31T17:25:52.715Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Growth Loop?</h3><p>Loops are closed systems where the inputs through some process generates more of an output that can be reinvested in the input. There are growth loops that serve different value creation including new users, returning users, defensibility, or efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*cIBxX7-PC03VlaX8mAM5Nw.png" /></figure><p>For example: The driving force behind Pinterest’s growth is the following loop:</p><ol><li>User signs up (or returns)</li><li>They activate you on the product with specific/relevant content</li><li>You save new content or repin existing content which gives Pinterest quality signals</li><li>Pinterest distributes the quality content to search engines</li><li>A user finds the content via search engines and either signs up/returns (see step 1)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FJmqiq0vWI_lGCesklEWqQ.png" /><figcaption>Growth loop of Pinterest</figcaption></figure><p>Or, let’s think of a newsletter that we created at Crework. It’s called 30 Days of PM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*nIKaW8L3kLq8AwCJ0Xqz8g.png" /><figcaption>Growth loop of “30 Days of PM” newsletter</figcaption></figure><ol><li>User subscribes to 30 Days of PM</li><li>They post about starting their journey learning with the newsletter on Twitter</li><li>Twitter user sees the tweet and gets curious about it and visits our website</li><li>This new user subscribes to 30 Days of PM (back to step 1)</li></ol><p>This little growth loop helped us reach 400 subscribers in 2 months without any sort of marketing. I am not even surprised.</p><h3>Loops Provide Sustainable Compounding Growth</h3><p>Loops force you to answer “How does one cohort of users lead to another cohort of users?” You focus on how you reinvest the output of one cycle of the loop into the next cycle of the loop to get more output. This creates a compounding effect that is more sustainable.</p><p>Not all loops are created equally. You’ll be tempted to draw a ton of loops for your product, but what that typically means is that you just have a ton of low-powered loops that aren’t sustainable. The fastest growing products are typically powered by 1- 2 major loops that transition over time. Measuring and understanding the power/health of your loops is critical to understanding where to focus.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dd53f950b7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How should Product Managers write problem statements?]]></title>
            <link>https://ishantjuyal.medium.com/how-should-product-managers-write-problem-statements-614c8dca52c8?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/614c8dca52c8</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-interview]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Thu, 13 Jun 2024 20:46:37 GMT</pubDate>
            <atom:updated>2025-05-31T17:25:39.221Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Problem Statement?</h3><p>A problem statement is a concise description of an issue to be addressed or a condition to be improved upon. It identifies the gap between the current (problem) state and desired (goal) state of a process or product. The first condition of solving a problem is understanding the problem, which can be done by way of a problem statement.</p><p>A good problem statement:</p><ul><li>Provides focus and frames the problem</li><li>Inspires your team</li><li>Informs criteria for evaluating competing ideas</li><li>Empowers your team to make independent decisions</li><li>Captures the hearts and minds of people you meet</li><li>Prevents you from creating concepts that are all things to all people</li><li>Should be discreet, not broad</li></ul><p><strong>Why is a problem statement important?</strong></p><p>A problem statement is important because it examines an issue from multiple angles. It identifies who the problem impacts, what the impacts are, where the problem occurs and why and when it needs to be fixed. This helps organizations determine the extent of an issue.</p><h3>How to write a problem statement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6Hvpxbi-Z4CaByYO.png" /><figcaption>How to write a problem statement</figcaption></figure><p><strong>Put the problem in the context</strong></p><ol><li>Before you write, you need to have a clear picture of the problem itself. At this stage, you want to discuss the what, where, when and who, regarding the problem.</li><li>Think about these additional questions to help you frame an impactful problem statement:<br>- Is the problem limited to a certain demographic or region?<br>- Which people have attempted to solve the issue?<br>- What do people already know about the issue?</li></ol><p><strong>Explain the relevance of the problem</strong></p><ol><li>The problem statement should address not only <em>what</em> the problem is but <em>why</em> it’s important to solve. You need to communicate why it matters to the business and the potential dangers if it goes unsolved.</li><li>To clarify why your problem is significant, address the following questions:<br>- Who will feel the consequences of the problem?<br>- What is the financial impact of the problem?<br>- Does the problem have any relevance to other areas of the business?<br>- Does the problem impact the wider society?<br>- How will solving the problem increase our understanding of the business?</li></ol><p><strong>Backup your claim</strong></p><ol><li>Quantifiable data ensure people understand the relevance and scope of a problem. Using evidence to back up your problem statement will make people take the issue seriously. Knowing your numbers also boosts your credibility.</li><li>For example, if a problem has diminished sales in the past few weeks, showing these statistics immediately communicates the extent of the issue.</li></ol><p><strong>Propose a solution</strong></p><ol><li>After doing a thorough investigation into the problem, you would have a solid grasp of <em>how</em> the problem occurred. Thus, you need to propose a practical solution or suggest several approaches to understanding and rectifying the issue at this stage.</li><li>State your objectives by suggesting well-thought-out plans for combating the issue.</li></ol><p><strong>Explain the benefits of your proposed solution</strong></p><p>Demonstrate why the solution will work with practical examples of how it will effectively address the problem. Explain how solving the problem will benefit the organization. Focus on the financial benefits of solving the problem and the impact on customer satisfaction.</p><h3>Problem Statement Template</h3><p>Problem statements usually follow the same general format, though they may fluctuate in length depending on the complexity of the issue. Here’s a basic template you can follow when writing your problem statement:</p><ul><li>Problem — Using one sentence, define the problem.</li><li>Background — In this section, use evidence to describe and explain the context of the problem.</li><li>Relevance — In this section, describe why the problem matters.</li><li>Objectives — In your conclusion, propose solutions to the problem based on your research and understanding of it.</li></ul><p>Or you can use this another template:</p><ol><li>What’s the real problem?</li><li>Who are the users facing this problem?</li><li>How do we know it’s a real problem?</li><li>What is the value generated by solving this problem?<br>- For the business<br>- For the target users</li><li>Why should we solve this problem now?</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=614c8dca52c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Segmentation vs User Persona]]></title>
            <link>https://ishantjuyal.medium.com/user-segmentation-vs-user-persona-ce887eaf8609?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce887eaf8609</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Tue, 11 Jun 2024 13:33:55 GMT</pubDate>
            <atom:updated>2025-05-31T17:25:16.416Z</atom:updated>
            <content:encoded><![CDATA[<h3>Doing Laundry</h3><p>Have you ever sorted your clothes before washing?</p><p>If you haven’t, maybe you should start doing it now. Separating dark colored clothes from whites or heavies from lights extends the life of your clothing and better preserves their color.</p><p>Setting loads of dirtier clothes to heavier settings gets them cleaner faster. A small amount of planning and effort before washing your clothes could save you the time and money required to frequently replace the ill-washed clothes.</p><p>But, why am I talking about laundry?</p><p>Because, if every article of clothing doesn’t responds well to the same washer settings, so why would different users all have the same experience with your product? Users of your product are at least slightly more complex than a polo shirt.</p><p>Hence, to serve the users well and to build the best product for their needs, we need to understand exactly what type and categories of users do we have. That’s why we have user segmentation.</p><h3>User Segmentation</h3><p>User segmentation is the product management equivalent to sorting laundry.</p><p>Grouping your users by shared characteristics reveals insights into how these segments are interacting with your product — and, most importantly, where your product can be improved to provide them with a better experience.</p><p>Instead of treating a single user experience as the most important, you should leverage user segmentation to identify and embrace the different ways customers use your product.</p><h3>How does user segmentation help?</h3><p>Let’s take an example. Say our product is a new community swimming pool. The top-requested features (and <strong>number of requests</strong>) are as follows:</p><ol><li>Starting blocks | <strong>17</strong></li><li>Ping pong table | <strong>15</strong></li><li>Lounge chairs | <strong>14</strong></li><li>Concession stand | <strong>12</strong></li><li>Swim lanes | <strong>12</strong></li><li>Branded swim caps | <strong>11</strong></li><li>Water slide | <strong>7</strong></li><li>Basketball court | <strong>4</strong></li></ol><p>We have the budget and capacity to choose <strong>three</strong> of these features by opening day so we choose the top three.</p><p>The opening day arrives and we eagerly await to see who subscribes for an annual membership to my pool with starting blocks, a ping pong table, and lounge chairs.</p><p>But to our accountant’s horror, no one subscribes!</p><p>Why aren’t people subscribing? Did they lie about their needs?!</p><p>The truth is that further analysis would have shown that in order to subscribe, each segment has a few dealbreakers — requirements that if not met, will ensure they take their business elsewhere.</p><ul><li><strong>Competitive swimmers</strong> need starting blocks AND swim lanes</li><li><strong>Teenagers</strong> need ping pong AND a concession stand AND a basketball court</li><li><strong>Parents</strong> need lounge chairs AND swim lanes for lap swim AND a waterslide</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*pp0tTgLVXVnSxY_fd_6gWg.png" /></figure><p>By delivering starting blocks, a ping pong table, and lounge chairs, we incidentally met one dealbreaker for each segment, but did not deliver sufficient functionality to be good enough for any segment.</p><p>So, by not understanding our user segments and their needs, we missed a chance to build a product that solves the needs of at least 1 segment of user properly.</p><p>What should have been done:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*j3Vw5P4CHiHSnbx1o6syhw.png" /></figure><p><strong>In this scenario, the chances of competitive swimmers being the subscribers would have increased.</strong></p><h3>How do we segment users?</h3><p>In theory, there are an endless number of characteristics with which you could segment your users. However, in practice, you cannot segment users on just any characteristic; you need to have data that enables the identification of if a user has a particular characteristic.</p><p><strong>These are some of the common segmentation model:</strong></p><ol><li>Demographic — Demographic segmentation uses demographic attributes, such as gender, language, race, and geography to divide up the user population.</li><li>Device — Device type segmentation is particularly useful for answering certain questions, such as:<br>- Do desktop users versus mobile users behave differently across device types?<br>- Are updates to your apps improving the experiences of the different groups of users? Or are updates introducing problems that you haven’t yet identified?<br>- Are there features or capabilities that you haven’t enabled on certain platforms that might meaningfully impact overall user retention?</li><li>Acquisition Source — This segmentation is used to analyze differences in users based on where they were acquired. Common sources include organic, google search, and facebook ads.</li><li>Usage Patterns — We can segment users by their usage patterns of the product. Users who give referrals can be very different from users who don’t. Users who do more than 1 payment a day can be very different from person who does none.</li></ol><h3>What is a User Persona?</h3><p>Once you are done with user research and are trying to make sense of whatever you have learnt about the user, you figure out the user segments that will be interacting with your product and then create user personas.</p><p>You can think of user personas as a representative of the segments that you have identified from your research.</p><p>A user persona is basically a fictional representation of your ideal customer. It’s fictional because you are imagining a person with various characteristics and that person is not real, but the characteristics that they have are a representation of the insights you got from your user research.</p><p>A persona incorporates the needs, goals, and observed behavior patterns of the target audience.</p><p>An example of a user persona:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MtE-lmVzFOGIQ3e_PkkyRA.png" /></figure><h3>Why do we need a User Persona?</h3><p>Understanding the needs of your users is vital to developing a successful product. Well-defined personas will enable you to efficiently identify and communicate user needs. Personas will also help you describe the individuals who use your product, which is essential to your overall value proposition.</p><p>Knowing your audience will help influence the features you choose, thus making your product more useful. A persona clarifies who is in your target audience by answering the following questions:</p><ul><li>Who is my ideal customer?</li><li>What are the current behavior patterns of my users?</li><li>What are the needs and goals of my users?</li><li>What issues and pain points do they currently face within the given context?</li></ul><h3>How can we make a User Persona?</h3><p>A well-defined user persona contains these pieces of information:</p><ul><li>Who is the user? You can mention the user’s demographic profile here.</li><li>End goals and aspirations of the users</li><li>Pain points and challenges to achieving the goals</li><li>Activities and experiences of the users</li></ul><p>Okay, to give you an example, let’s make a user persona of ideal user for this 30 Days of PM challenge.</p><ul><li>Sakshi, 23 years old Software Engineer working full time</li><li>Lives in Bengaluru, India</li><li>Wants to break into Product Management role</li><li>Don’t know how and where to start learning</li><li>Spends her time on LinkedIn and Twitter interacting with people in tech</li></ul><p>This could be a user persona for 30 Days of PM right? And I am sure a lot of you relate to this as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce887eaf8609" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idea Validation & MVP]]></title>
            <link>https://ishantjuyal.medium.com/idea-validation-mvp-2e44ada481c3?source=rss-69ea2aa5a8ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e44ada481c3</guid>
            <category><![CDATA[validation]]></category>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ishant Juyal]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 18:49:43 GMT</pubDate>
            <atom:updated>2025-05-31T17:25:03.115Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why should we care about validating ideas?</h3><p>One of the greatest product management sins is wasting your organisation’s time and money developing a product or feature that fails. As a product manager it’s your job to ensure that if you green light a product it has a good shot at success, which means it’s critical to ensure that you’re not frivolously hedging bets on something that’s doomed from the start.</p><p>When you take the time to validate, you’re reducing the odds of building a product (or adding a functionality) that fails by answering important questions such as:</p><ul><li>Are you solving the <strong>right problem</strong>?</li><li>Are you solving the right problem at the <strong>right time</strong>?</li><li>Is your solution the <strong>right solution</strong>?</li></ul><p>The trick is knowing how to find the answers.</p><h3>How can you validate your solution?</h3><ol><li>The first step in idea validation process is to identify the right problem to solve. The question should not be “Can this product be built?” but “Should this product be built?” and “Can we build a sustainable business around this set of products and services?”</li><li>If you’d like to stick with Lean Startup principles, an MVP would be a great place to find and know your early target audience. A simple landing page with a sign-up form is a highly-effective MVP when you’re looking to gauge interest in your solution and get in touch with interested parties.</li><li>So build a landing page; do keyword research on the problem you’re solving to see how people are looking for solutions (and how often they do) and put together something that looks nice and captures the email addresses or other information you need from potential customers.</li><li>Once you’ve amassed a collection “sign-ups” you’ll be able to start getting in touch and having conversations with folks that will help guide you in the right direction. If you don’t get any sign-ups or any interest, it may be a good idea to reassess your idea and how you marketed it.</li></ol><h3>What is an MVP?</h3><p>A minimum viable product, or MVP, is a product with enough features to attract early-adopter customers and validate a product idea early in the product development cycle.</p><p>It is the version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least amount of effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*UUGQusJ8R7SNHTfC.png" /><figcaption>How MVP works. It is useful in every stage.</figcaption></figure><p>If you’re wondering what this would look like in practice, let’s review how a couple of familiar brands launched successful MVPs.</p><p><strong>Airbnb</strong></p><p>With no money to build a business, the founders of Airbnb used their own apartment to validate their idea to create a market offering short-term, peer-to-peer rental housing online. They created a minimalist website, published photos and other details about their property, and found several paying guests almost immediately.</p><p><strong>Swiggy</strong></p><p>Swiggy was launched in 2014 using the MVP framework. They built an app using very little resources to fulfill the need of their customers.</p><p>The app only offered a way to place food orders from a restaurant. It did not have:</p><ul><li>Coupons</li><li>Extensive payment options</li><li>No delivery tracking options</li><li>No AI-based chatbots</li></ul><p>Most of their operations were done the manual way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e44ada481c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>