<?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 Kavya Rastogi on Medium]]></title>
        <description><![CDATA[Stories by Kavya Rastogi on Medium]]></description>
        <link>https://medium.com/@Kavya135?source=rss-6123bb07c6c9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2AHt-_KQooYY-_9sTH9YOg.jpeg</url>
            <title>Stories by Kavya Rastogi on Medium</title>
            <link>https://medium.com/@Kavya135?source=rss-6123bb07c6c9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:30:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Kavya135/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[First-Run Experience : Best Practices]]></title>
            <link>https://medium.com/design-bootcamp/first-run-experience-best-practices-bfac94195dde?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfac94195dde</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sun, 28 Aug 2022 16:45:59 GMT</pubDate>
            <atom:updated>2022-08-29T07:44:03.840Z</atom:updated>
            <content:encoded><![CDATA[<h3>First-Run Experience: Best Practices</h3><p>Imagine you begin learning a new language and are bombarded with so much information that you get overwhelmed and drop the idea of being multi-lingual altogether! This is exactly what a new user experiences when he/she opens your app for the first time and is shown irrelevant content about your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*TaVqJuv5h_zFxxE3TVyI2w.png" /><figcaption>Source : Twitter</figcaption></figure><p>Revisiting the previous <a href="https://bootcamp.uxdesign.cc/first-run-experience-an-introduction-e13f99d2b070">post </a>: <br>“<em>An FRE is designed keeping in consideration the following:<br>-What should the user know at this point in time?<br>-What do you want the user to do in the first few instances of using the app?<br>- What value the user wants from the product? </em>“</p><p>In this edition, we broadly look at a few pointers on creating an engaging user onboarding flow.</p><ul><li>The FRE should be as brief as possible. Information overload should be avoided at all times. <br>Answer the question “ <strong><em>Why should people use my product</em></strong> “ and emphasize delivering this value in a crisp manner, as early as possible. This keeps consumers hooked and they tend to stay for longer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*uNQgkG2pw4IpESxBy4NCXg.png" /><figcaption>FRE for Watch App on iOS</figcaption></figure><ul><li>Find what makes users “stick around“ : Identify which actions differentiate an active user from a churned one. The onboarding flow should involve getting users to complete those tasks and attaining their AHA ! moment early on in the process.<br><em>Example: As shown below, data suggests that when users connect with 10 friends in a week, they are likely to stay longer on Facebook. Hence, the initial steps should focus on getting new users to connect with as many friends as possible.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rPlSg_4dwpALoJuE.png" /><figcaption>Source: Apptimize.com</figcaption></figure><ul><li>Focus on engagement: The user should want to engage with the experience and not be forced to complete it. There should always be a provision to skip the FRE and revisit it later.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQoi3gSvKWcvQDQkHWjXPw.png" /><figcaption>Headspace App FRE (iOS)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2AOEsxbtyImn9LwH9OmfYA.png" /><figcaption>Calm App FRE (iOS)</figcaption></figure><ul><li>Utilise in-context education: If a feature/add-in is only used occasionally, users might be unfamiliar with it. In such situations, demonstrating another FRE with the concerned add-in might be more beneficial for the end user.</li><li>Adopt visual indicators: Use progress bars/dots to motivate users to complete the onboarding. This aids them in achieving a sense of accomplishment and keeps them from feeling restless.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*gGRJR8x3EisoMv66KTNlcA.png" /><figcaption>Examples of progress indicators</figcaption></figure><ul><li>Emphasise the ongoing education bit: This ensures that users can focus on one learning moment at a time. Conclude by directing users to your “help” section so they can revisit when in doubt. <br><em>Example: As shown below, Keynote App is educating the user on new features in the latest update.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*n02ELSPQQ5-Oxulj8GTWwg.png" /></figure><ul><li>Adapt and improvise: Creating an impactful onboarding flow may require multiple iterations. Constantly utilise data to determine at which stage of the conversion funnel, you are losing customers. Change the onboarding flow as your product evolves.</li></ul><p>Crafting a good user onboarding flow should focus on the experience you want to create for the user and the sentiments you wish to elicit from the user. Hoping this article gave you some food for thought!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfac94195dde" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/first-run-experience-best-practices-bfac94195dde">First-Run Experience : Best Practices</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[First-Run Experience: An Introduction]]></title>
            <link>https://medium.com/design-bootcamp/first-run-experience-an-introduction-e13f99d2b070?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e13f99d2b070</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Tue, 26 Jul 2022 18:54:52 GMT</pubDate>
            <atom:updated>2022-07-29T09:04:32.962Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever wondered why in the era of (seemingly) similar products, only a few offerings stand out while the rest suffer from a high churn rate, even before the user is able to realise the value offered by the product? As they say, the first impression is the last impression, the first few steps of the user experience either make or break your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*XrCOQVjIc16O7vR9U8ssNg.png" /><figcaption>Reasons for high churn rate among Mobile Apps</figcaption></figure><p>Today we delve deeper into a first-run experience (FRE )/ first-time UX : A well-crafted user onboarding flow which decides whether you will have returning users or not. Your FRE can help users realize the benefits of your product in the very initial steps of interacting with the app. The sooner consumers reach their AHA! moment, more likely that they will use your product over others.</p><p><strong>What</strong>: An FRE includes all aspects of user experience when the user interacts with the product for the 1st time: how they feel, think, what emotions it evokes in the user’s mind and how well they understand the product.</p><p><strong>Why</strong>: An impactful first impression paves the way for consumer retention, ensures that the user engages with the product and utilizes its benefits. It has a significant impact on the churn rate as well.</p><p><strong>When</strong>: Ideally begins after the user opens your app for the first time/lands on your site. In some cases, it starts when the user tries to download your app.</p><p><strong>Who</strong>: First-time users are exposed to this onboarding flow.</p><p><strong>How</strong> : A good FRE is backed by data. It should be designed in alignment with the target audience: who they are, their needs and wants, their behaviour and their expectations from the product.</p><p>Let’s consider the following example :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BtwDtz_PzBNtO9hL.png" /><figcaption>Image source :CleverTap</figcaption></figure><p>Product: Clarity Money App.<br>What works for the flow: Product benefits are instantly visible, visual progress indicator to demonstrate flow, usage of examples to reinforce learning , no information overload and adequate use of visuals.</p><p>An FRE is designed keeping in consideration the following:<br>-What should the user know at this point in time ?<br>-What do you want the user to do in the first few instances of using the app ?<br>- What value the user wants from the product ?</p><p>More on how to design a contextual and impactful FRE in the next post. Stay tuned !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e13f99d2b070" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/first-run-experience-an-introduction-e13f99d2b070">First-Run Experience: An Introduction</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 Management : Lessons I have learnt and relearnt]]></title>
            <link>https://medium.com/@Kavya135/product-management-lessons-i-have-learnt-and-relearnt-16dd626e5a62?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/16dd626e5a62</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sat, 29 Jan 2022 19:34:49 GMT</pubDate>
            <atom:updated>2022-01-29T19:34:49.229Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Management : Lessons I have learnt and relearnt</h3><p>As I traverse through my corporate journey, working on diverse projects requiring disproportionate time and efforts , there have been times when it has become increasingly difficult to stick to the basic principles of Product Management . Easier said than done, right !<br>Presenting few seemingly simple lessons/principles which have made it to the <em>Product Management Hall of Fame</em> and need to be imbibed like the ABCDs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*mHsyHfCFO4nsartI.jpg" /></figure><p>-Requirements should be as clear and disintegrated as possible. Its imperative to have concise functionalities which map to specific requirement(s). This mapping can be shared with concerned stakeholders to ensure no surprises post development phase. My secret sauce is to include crude system diagrams in the BRD, encapsulating connectivity and basic needs from each system.</p><p>-Avoid big bang releases at all costs. Its better to have multiple releases covering a span of features than a single release encumbering development and testing. Incremental development followed by thorough UAT is the key to avoid unnecessary delays in the SDLC and confusing the user.</p><p>-Interdependencies among modules and/or systems should be established right at the start of the project. This is especially relevant for projects involving multiple systems with independent working teams . This has been a new personal lesson which I learned the hard way.</p><p>-Time management is an underrated PM skill which needs to be mastered. As PMs we tend to work on multiple projects at a time, and with only limited number of working hours, burning the midnight oil tends to be a common occurrence. I find that making a daily issue tracker for projects helps in conducting concise meetings, to a certain extent. Additionally, we can schedule “x” hours for each concurrent project, depending upon the current stage the project is in.</p><p>-Timely communication goes a long way to help timely deliveries. Periodical check-ins among all systems’ stakeholders ensures everyone is on the same page vis-à-vis connectivity ,requirements and timelines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16dd626e5a62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Roadmaps : An Introduction]]></title>
            <link>https://medium.com/@Kavya135/product-roadmaps-an-introduction-ce4055955da?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce4055955da</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sun, 10 Oct 2021 20:23:46 GMT</pubDate>
            <atom:updated>2021-10-10T20:23:46.047Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Roadmaps : An Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3NzA9YEETtNc35_h.png" /><figcaption>Source : Roadmunk</figcaption></figure><p>For this week’s rendezvous, let’s deep-dive into Product Roadmaps, the seemingly complicated yet interestingly simple tool which serves as a guiding light for shipping desirable products which meet customers’ expectations and needs.</p><p><strong>W</strong>hat : It communicates the strategy and focuses on “<strong>what</strong>” is in the company’s pipeline in the coming future, ranging from a few months to a few years. It maps out the strategic direction of the product over time.</p><p><strong>W</strong>hen : Created after the vision and high-level strategic planning are in place. A roadmap is required to convey <strong>what </strong>will be delivered and <strong>when </strong>: right from launching a new product to shipping enhancements. It can evolve through the lifecycle of the product, based on market demand and consumers’ needs.</p><p><strong>W</strong>ho : The concerned PM team/Product Owner is primarily responsible for the creation and upkeep. The org’s and product’s strategic objectives set by the executive team, form the cornerstone of a product roadmap.</p><p><strong>H</strong>ow : The company’s vision leads to formulation of company strategy. The vision defines the “<strong>why</strong>” while the strategy encapsulates the “<strong>how</strong>”. A roadmap draws from the strategy and represents strategic product development over time.</p><p><strong>W</strong>hy : A shared roadmap conveys the vision to facilitate buy-ins from stakeholders. It aligns stakeholders on the “<strong>where</strong>” and “<strong>how</strong>” and provides a loose time segment to keep the concerned stakeholders informed. It can also help the business align with the customer’s expectations.</p><p>Few notable characteristics of a good product roadmap:</p><ul><li><strong><em>Adaptable </em></strong>: It should be able to accommodate changes in feature prioritization, as per market trends and the company evolving strategy.</li><li><strong><em>Easily available</em></strong> : A roadmap shared with public can help with user engagement, ensure alignment with customers’ needs and help create a more successful , useful product. <br>example : Microsoft 365 <a href="https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=">roadmap </a>, <a href="https://github.com/github/roadmap">GitHub</a></li><li><strong><em>High-level</em></strong> : It should contain only high-level overviews of feature improvements and/or additions without very specific delivery timelines.</li><li><strong><em>Communication</em></strong>: It should have an active user feedback loop which leverages consumer’s expectations and helps make educated decisions to ship best-selling products.</li><li><strong><em>Components</em></strong> : A roadmap should highlight strategic features, new modules, integrations and significant tactical improvements, based on factual evidence.</li></ul><p>Tip : It helps to share a “light” version of the roadmap with the sales teams to discuss with clients. This can contain features and customer benefits to assist with closing deals and generating interest in the customers’ mind. Be wary of detailing release dates in the roadmap to avoid breaking promises !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce4055955da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking]]></title>
            <link>https://medium.com/@Kavya135/design-thinking-5d4425ba3fcb?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d4425ba3fcb</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sun, 26 Sep 2021 18:00:57 GMT</pubDate>
            <atom:updated>2021-09-26T18:00:57.198Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, Apple is synonymous with perfection in design.Ever wondered how Apple evolved into a market disruptor ? Steve Jobs had a laser-focused mentality for products with an obsession for simple and empathetic user experience. Let’s decode design thinking , the (not so silent ) hero behind Apple’s stellar success using the familiar 5Ws and 1H framework:</p><p><strong>W</strong>hat: Design thinking is an iterative approach to solve complex problems in a user-centric manner. It helps us develop empathy with the target user and understand his/her needs better.This helps businesses create more meaningful consumer experiences ,leading to happy consumers and a healthier bottom line.</p><p><strong>W</strong>hen to prefer design thinking: It is apt for problems wherein:<br>-Very little relevant data exists to be analyzed<br>-Deep understanding of users is involved<br>-The problem needs further exploration<br>-There are many unknowns leading to uncertainty.</p><p><strong>W</strong>hy: It forces us to challenge our assumptions of what we know: about the user, about the problem and find newer ways to solve our problems. Ambiguity is considered an opportunity to remain curious.</p><p><strong>W</strong>ho: Leading brands like Apple, Google, Microsoft, Samsung and <a href="https://blogs.intuit.com/blog/2021/01/21/why-every-company-should-be-doing-a-follow-me-home/">Intuit</a> have adopted this approach to ship products that attain mass market success.</p><p><strong>W</strong>here: Design thinking thrives at the cusp of viability, feasibility and desirability. It combines what is desirable from a human point of view with what is technologically feasible and economically viable to make.</p><p><strong>H</strong>ow: Identify the unarticulated needs of the user by having them interact with your product. This immersion in customer experience provides deeper actionable insights which form the criteria for brainstorming solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZniUIWAvaNWupGWJ.png" /><figcaption>Source : Nielsen Norman Group</figcaption></figure><p>The phases include, in any order :<br>- Empathising with your user and understanding what is valuable to them.<br>- Defining the needs and problems of the user<br>- Challenging known assumptions and identifying alternative solutions<br>-Prototyping using techniques like storyboarding, wireframing among others.<br>- Testing what works and scaling based on iterative feedback</p><p>Hoping to elaborate on detailed implementation phases and industry examples in the next article. Please let me know what you want to read more about !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d4425ba3fcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Metrics: An Introduction]]></title>
            <link>https://medium.com/@Kavya135/product-metrics-an-introduction-553eb65cba21?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/553eb65cba21</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sat, 18 Sep 2021 07:35:03 GMT</pubDate>
            <atom:updated>2021-09-18T07:35:03.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*19B-RCM2V3Ua-a1D.jpg" /><figcaption>Image Source : Salesforce</figcaption></figure><p>In the era of digitization, customers today are mindful of where they spend their money, efforts, and data. Owing to minimal switching costs and a plethora of available alternatives, it is becoming increasingly imperative to evolve as per customers’ expectations and demands. How do we decide which customers to cater to? How to convert a website into an experience? What works best for my users? Metrics help find answers to all these queries. They are seemingly simple, yet intricate data points that aid in tactical and strategic decision-making.</p><p>Metrics assist companies in deciding what to do, how to do it and measure how successful they are in doing it. Using metrics helps attain more clarity of userbase and what works for them, ensure alignment with business goals, and aid in prioritization of which features to build. Let’s dive deeper using the 5Ws and 1H framework :</p><p><strong>W</strong>hy do we need metrics? <br>Product Metrics helps focus on what actually matters. Without proper metrics, any company’s actions are reactive in nature, instead of being proactive.</p><p><strong>W</strong>hat do we track? <br>Events and Properties are tracked. <br>Events: Recorded when a user performs an action on our product. <br>Properties: Provide additional information tagged to users/events.</p><p><strong>W</strong>hen do metrics come into the picture?<br>Right from the planning stage.</p><p><strong>W</strong>ho decides the metrics to be tracked?<br>PMs, after discussion with the project stakeholders. However, during later stages, Data governance is a collaborative effort among all team members.</p><p><strong>W</strong>here do we use metrics?<br>Each stage of decision-making, right from deciding what to launch to measuring the success of a launch.</p><p><strong>H</strong>ow do we decide which metric(s) to use? <br>Ascertaining the primary metric is straightforward and starts with determining the desired outcome of a business/feature/object and mapping it to a quantifiable and meaningful metric. <br>Examples: Spotify / YouTube: Time spent in consuming content<br>Airbnb: Number of nights booked.</p><p>These real-time insights empower companies to take timely decisions and stay relevant in consumers’ minds, thus accelerating business and growth potential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=553eb65cba21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prioritization Series: RICE Framework]]></title>
            <link>https://medium.com/@Kavya135/prioritization-series-rice-framework-3c0df1c2275a?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c0df1c2275a</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Sat, 31 Jul 2021 10:30:31 GMT</pubDate>
            <atom:updated>2021-07-31T10:30:31.109Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*D79jzh9CuKVo-w9FHunH9g.png" /><figcaption>Image source: Marketing91</figcaption></figure><p>A perennial question haunting PMs is “How to decide what to work on first?“ The RICE scoring technique helps determine which initiatives to put on the roadmap by scoring options against four factors: <strong>R</strong>each, <strong>I</strong>mpact, <strong>C</strong>onfidence, and <strong>E</strong>ffort. It helps minimize personal biases which might creep in while decision-making and make better decisions objectively, by identifying the relative importance of different ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zIBylDEsJUDkFeTszUbZQ.png" /></figure><p><strong>R</strong>each: Measured in events/people per time period. Advisable to utilize measurements from the product metrics itself.</p><p><strong>I</strong>mpact: Can signify a qualitative or quantitative goal. Difficult to measure. <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">Intercom</a> recommends using a multiple-choice scale to estimate impact.</p><p><strong>C</strong>onfidence: Higher if we have data backing our estimates. <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">Intercom</a> has devised a tiered model using percentages to avoid confusion.</p><p><strong>E</strong>ffort: Represents a cost to the initiative. Typically measured in person-months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*IuYQ1Q1G218VxkwDL4vR0A.png" /></figure><p>Post initial scoring of features, PMs evaluate the order in which features are tackled. The framework works best with SMART goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c0df1c2275a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prioritization Series:MoSCoW Analysis]]></title>
            <link>https://medium.com/@Kavya135/prioritization-series-moscow-analysis-bd3d6d0606c5?source=rss-6123bb07c6c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd3d6d0606c5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Kavya Rastogi]]></dc:creator>
            <pubDate>Mon, 26 Jul 2021 14:11:35 GMT</pubDate>
            <atom:updated>2021-07-26T14:11:35.138Z</atom:updated>
            <content:encoded><![CDATA[<p>More often than not, PMs can find themselves in deep waters while dealing with the opinions of multiple stakeholders and managing feature requests to be incorporated in a sprint. Using the <strong>5Ws and 1H</strong> technique, let’s try to decode the MoSCoW technique, a popular mechanism to manage requirements :</p><p><strong><em>What</em></strong>: Helps stakeholders segment the requirements into different priority buckets.</p><p><strong><em>Why</em></strong>: With limited time and resources at hand, it’s imperative to take a call on what requirements to be embedded in a particular sprint.</p><p><strong><em>When</em></strong>: Happens during foundations and ideally should be continually reviewed to prevent scope creep.</p><p><strong><em>Who</em></strong>: The product team and key stakeholders are generally involved.</p><p><strong><em>Where</em></strong>: Can be applied predominantly to user stories/requirements but can also be used for tests, acceptance criteria, use cases, and tasks.</p><p><strong><em>How:</em></strong> Requirements can feature in any of the following priority bucke</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*dv2yeOutYZKJgOOhlTUhzQ.png" /><figcaption>Image Courtesy: Crrux on Twitter</figcaption></figure><p><strong>M</strong>ust have: This requirement is critical for delivery. This serves the identified need for the product. If not included, the product will be deemed as a failure.</p><p><strong>S</strong>hould have: These include feature benefits that are important but not time-sensitive. It may be painful to leave these requirements out, but the release is still possible.</p><p><strong>C</strong>ould have: These are desirable features that can be included if time and resources permit.</p><p><strong>W</strong>ish/Will not have: These are the least critical items that offer low payback and might not be appropriate at the time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd3d6d0606c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>