<?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 Wildiyanto Yawin on Medium]]></title>
        <description><![CDATA[Stories by Wildiyanto Yawin on Medium]]></description>
        <link>https://medium.com/@wyawin?source=rss-11e2423a384------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rUj--qucShdcyh-AOJ3Ong.jpeg</url>
            <title>Stories by Wildiyanto Yawin on Medium</title>
            <link>https://medium.com/@wyawin?source=rss-11e2423a384------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:35:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wyawin/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[3 Product Prioritization Techniques]]></title>
            <link>https://medium.com/@wyawin/3-product-prioritization-techniques-bb7f976e6ca6?source=rss-11e2423a384------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb7f976e6ca6</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Wildiyanto Yawin]]></dc:creator>
            <pubDate>Sat, 03 Oct 2020 17:24:08 GMT</pubDate>
            <atom:updated>2020-10-03T17:24:08.970Z</atom:updated>
            <content:encoded><![CDATA[<p>Prioritization is one of the most important parts in product management. Deciding on when and what to do next is a critical part.</p><p>If you’re someone who transitioned to product from another role, before, you prioritize tasks by choosing which task to work on first, which tasks need to be done above all others and what are the orders. Keep in mind that prioritization in product management is at a whole new level. You must be able to prioritize which problems to solve first and which can wait.</p><p>If you’re completely confused about prioritization and how to make it work, There are 3 most common and popular frameworks to do a prioritization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*sMr4Z-trc8OKBOMwgx8T5A.jpeg" /></figure><h3>1. MoSCoW Method</h3><p>MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique used in Agile PM to understand what’s important and what’s not. The method is commonly used to help key stakeholders understand what the product team is working on and why.</p><p>The acronym, MoSCoW, stands for 4 prioritization categories: <strong>Must have, Should have, Could have, </strong>and <strong>Won’t have</strong>.</p><h4>Must Have</h4><p>As the name suggests, this category consists of initiatives that are “musts” for your team. Non-negotiable product needs that are mandatory for the team, you absolutely should not launch without it.</p><p>If you’re unsure about whether this initiative belongs in this category, ask yourself the following questions.</p><ul><li>What happens if you release without this initiative?</li><li>Is there a workaround or a more simple way to accomplish this?</li><li>Will the product work without this initiative?</li></ul><p>If the product won’t work without this initiative or you can’t picture success without it, then it’s a Must have!</p><h4>Should Have</h4><p>This category is just a step below must have. They are important to the product but it’s not like you can’t release without it. It’s things that would be better to include in the product.</p><p>Should have initiatives are different from must have. They can be scheduled for a future release without impacting the existing things. For example, it could be like improving performance, bug fixes or new functionality. Without them, the product still works.</p><h4>Could Have</h4><p>Could have things would be nice to include, another way of describing “could have” initiatives is nice to have. Could have and should have only had a slight difference. Compared to should have, they have much smaller impact on the outcome if they are left out. It’s not really necessary for the product to succeed.</p><p>To define what initiatives belong here, think of how each requirement will affect the product and customer. The lesser impact, the priority goes down further.</p><h4>Won’t Have</h4><p>Won’t have doesn’t mean this initiative is useless or it never can be included in your product. That just means not this time. You will do this later. It’s not a priority for this specific timeframe.</p><p>Placing initiative in this category is one way to help prevent the product from being widened from the initial solution we decide.</p><h3>2. RICE Scoring</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X782_bZedr88X_a0bN_6MA.png" /><figcaption>RICE Scoring</figcaption></figure><p>The RICE scoring model is a prioritization framework designed to help product managers determine which products, features, and other initiatives to put on their roadmaps by scoring these items according to several factors which again has four categories. These factors then form the acronym RICE, which is <strong>Reach, Impact, Confidence,</strong> and <strong>Effort</strong>.</p><h4>Reach</h4><p>The first factor is Reach, It is to get a sense of how many people you estimate that will be impacted by your initiative in a given timeframe.</p><p>You can measure this in the number of people impacted in a specific timeframe. Example you can ask yourself, “how many customers will this impact per quarter?”</p><h4>Impact</h4><p>Impact can reflect a quantitative goal, such as how much will this project increase conversion rate when users encounter it. This time you will think about how they’ll be affected as individuals.</p><p>There’s no real scientific method for measuring impact. <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/"><strong>Intercom</strong></a> recommends a multiple-choice scale:</p><ul><li>3 = massive impact</li><li>2 = high impact</li><li>1 = medium impact</li><li>0.5 = low impact</li><li>0.25 = minimal impact</li></ul><h4>Confidence</h4><p>Although in product management things, data should be used as much as possible as the foundation for decision making, but sometimes you have no choice but to rely on intuition and gut-feeling.</p><p>For example, if you are lacking data to prove the initiative importance, a confidence score will help you account this.</p><p>As Intercom did to impact factor about measuring initiatives, Intercom also created a tiered set of classification percentages to score confidence, so that product teams wouldn’t get stuck or take too much time here deciding the exact percentage number between 1 and 100. When determining your confidence score for a given project, your options are:</p><ul><li>100% = high confidence</li><li>80% = medium confidence</li><li>50% = low confidence</li></ul><p>If you arrive at a confidence score below 50%, maybe you will want to assume your priorities to be elsewhere.</p><h4>Effort</h4><p>All of the factors we have discussed to this point such as reach, impact and confidence represent the numerators in the RICE scoring equation. Effort represents the denominator.</p><p>In other words, if you think of RICE as a cost-benefit analysis, reach, impact and confidence represent the potential benefits while effort represents the costs.</p><p>To score this effort, you will need to involve everyone for the project success like engineer, designer, QA, etc for the information about how much effort to finish the project.</p><p>Estimate how much work it’ll take each team member working on the project. The more time it takes to finish, then the higher reach, impact and confidence you need in order to make it worth it.</p><h4>How is a RICE score calculated?</h4><p>Now you should have four numbers representing each of the 4 factors. To calculate your RICE score, simply multiply Reach by Impact, and then by Confidence. Then divide by Effort.</p><p>Your final score represents ‘total impact per time worked.’ The higher the score, the closer you are to high impact with low effort.</p><h3>3. Kano Model</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMElE11FKoud0vFZVoIkOw.png" /><figcaption>Kano Model</figcaption></figure><p>The Kano Model is a prioritization framework which helps prioritising features on a product roadmap based on the order to which they are likely to satisfy customers the most.</p><p>The utility of the model is to divide the problems into 3 relevant categories, which is<strong> Must have</strong>, <strong>Delighter</strong> and <strong>Performance</strong>.</p><h4>Must Have</h4><p>The minimum feature that is expected by customers to solve their problems. Without these, the product is basically useless to your customers.</p><p>Customers expect these features and take them for granted. For example, as a car manufacturer, you cannot work on solving your customers’ problem if you don’t provide car’s turn signal, seat belts, etc.</p><h4>Delighter</h4><p>Delighters provide extra benefits that exceed expectations and improve the experience. It’s okay if you don’t have these features, customers might not even think about it, but if you include them and continue to invest in them, you will create dramatic delight to your customers.</p><p>These delighter things might be the things that will differentiate you from your competition.</p><p>Example some people never like waiting while their car is being serviced as the waiting lounge offered by the service provider is in a bad shape. I wish it had VIP lounge facilities with Wi-Fi services, food, massage services, etc.</p><h4>Performance</h4><p>The more performance needs you add, the better your product is. In general, customers give a very good response to high investments in performance features.</p><p>These are also features that your customers might be used to deciding whether to choose your product or your competitor’s.</p><p>Example of performance need is number of kilometres covered by the manufacturer’s warranty.</p><h3>Summary</h3><p>MoSCoW method is an effective prioritization method when you want to include both customers and stakeholders in the process. The MoSCoW method is often used for time-boxed projects only.</p><p>Another reason you might want to use the MoSCoW method is it allows your team to determine how much effort goes into each category. However, there’s nothing stopping you from putting things into ‘Must have’ and it might overextend your resources.</p><p>The RICE scoring can help product teams quickly create a consistent framework for objectively evaluating the relative importance or value of a number of different project ideas. It will help you make better-informed decisions about what to work on first and defend those decisions to others.</p><p>The Kano Model can be a helpful framework for product teams with limited time and resources who want to make sure they are prioritizing the appropriate mix of features to work on next.</p><p>Of course, these aren’t the only three prioritization techniques out there, and many talented PMs have their own ways of doing things. All you can do is keep testing and evaluate!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb7f976e6ca6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Product Analytics]]></title>
            <link>https://medium.com/@wyawin/introduction-to-product-analytics-2788f3dc654d?source=rss-11e2423a384------2</link>
            <guid isPermaLink="false">https://medium.com/p/2788f3dc654d</guid>
            <category><![CDATA[product-analytics]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Wildiyanto Yawin]]></dc:creator>
            <pubDate>Fri, 02 Oct 2020 05:20:34 GMT</pubDate>
            <atom:updated>2020-10-02T05:20:34.356Z</atom:updated>
            <content:encoded><![CDATA[<p>Product Analytics can be used to analyze how users interact with our product and understand better about our user behaviour.</p><p>With Product analytics, It can help us decide which is the right approach we must focus on, why our product doesn’t perform as expected after we release it to market, because at the end we must focus on the customers.</p><p>Product analytics also help Product Managers in evaluating pain points of the product, identifying opportunities or improvement for the product roadmap and identifying patterns in product usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3bua9ACC2-5YAFZP32S2ig.jpeg" /></figure><h3>How does it work?</h3><p>It tracks the actions of our users in our product, such as clicks per events, pageviews, heatmap and other activities that are involved when event action, navigating, etc.</p><h3>Why is it important?</h3><p>Product analytics provide vital information to optimize performance, diagnose problems, and correlate customer activity with long-term value.</p><p>It is important to analyze product usage data to get a better understanding about our customer behaviour and customer happiness.</p><p>It is also important to measure the performance of our product and evaluate the data as often as possible, because customer preferences and behaviour change over time.</p><p>Using the data we analyze, measure and evaluate before, it will help us come up with a decision for us to focus on, it is to solve issues or choose the right new opportunity.</p><h3>Qualitative and Quantitative</h3><p>Qualitative enables you to examine and get better understanding about the actual “whys” behind your numerical data. While quantitative focuses on aspects of your app that can be measured by numbers.</p><p>Qualitative data is a little more “touchy-feely”. It comes from open-ended questions on surveys, customer interviews, sales call feedback, reviews section, and support tickets. Example is looks like “they prefer mobile apps because not all parents have access to a computer” or “it takes too many steps to reach the finish.”</p><p>Quantitative data is “hard data” that puts everything in terms of number, it comes from analytics, surveys with significant sample sizes. Examples might be number of active users per month, number of transactions per week, bounce rate, conversion rate, how many people clicked on this section, etc.</p><h4>When to use Qualitative?</h4><ul><li>When we try to explore users’ habits and potential problems</li><li>When we want to improve or provide, but need deeper understanding about the customers</li><li>Observe immediate reactions and emotional responses to an experience</li><li>Evaluate and gather feedback and insight from a relatively small group of users</li></ul><h4>When to use Quantitative?</h4><ul><li>When we want to validate the assumption or hypothesis</li><li>Evaluate and gather feedback and insight but the size and range of the user group can be expanded</li><li>Reduce bias with bigger scale</li><li>Measure satisfaction and usability with standard measures</li></ul><h3>How can it help?</h3><p>You can imagine the product analytics is having three main layers:</p><h4>1. Data</h4><p>First, we focus on collecting data that we need, process and management of the raw data.</p><h4>2. Analysis</h4><p>In this layer, product teams will define parameters of analysis and transform the raw data into meaningful information.</p><h4>3. Reporting</h4><p>Finally, after creating the report, it allows product teams to see the report as a chart or table from the data, see if there are any issues or opportunities.</p><p>There are several main areas where product analytics can help the product team, such as:</p><ol><li>Tracking product metrics</li><li>Whether our users is using our product</li><li>What pattern can be seen in our user behaviour &amp; personas</li><li>How are our users using it</li><li>What are the pain points</li><li>Which are the most popular feature</li></ol><h3>Summary</h3><p>Through product analytics, product teams have access to the data about how customers engage with their product. So we can analyze, measure and evaluate the product. Using that data we can get a better decision making about how to solve the product issues or even choosing a new opportunity to approach. Then using product analytic, it also can help the product teams tracking their metrics.</p><p>We must always use data to make a decision in every product development process and balance usage of qualitative and quantitative data.</p><blockquote>If you can’t measure it, you can’t improve it.<br>— Peter Drucker, Father of modern management</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2788f3dc654d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Phases of Product Development]]></title>
            <link>https://medium.com/@wyawin/7-phases-of-product-development-165f72afc8a2?source=rss-11e2423a384------2</link>
            <guid isPermaLink="false">https://medium.com/p/165f72afc8a2</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-lifecycle]]></category>
            <dc:creator><![CDATA[Wildiyanto Yawin]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 17:48:58 GMT</pubDate>
            <atom:updated>2020-10-02T16:38:11.419Z</atom:updated>
            <content:encoded><![CDATA[<p>There are 7 phases of product development and have a series of steps that they go through. Each one of them is a crucial step to achieve success in a product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*gKz928xG8jyVdeR1JxaSnQ@2x.png" /></figure><h3><strong>1. Discovery and Conceive</strong></h3><p><em>Objective: Find a problem to solve</em></p><p>Product discovery or idea generation is the initiation phase where Product Managers talk to customers, listen to their feedback, trying to find their problems, why they have the problems and what is the main reason they cannot outcome the problems.</p><p>Besides talking to customers, ideas may also come from different sources, such as co-workers, competitors, etc.</p><p>After we are done identifying the product or idea problems, then brainstorming a solution and identifying the focus areas to work on.</p><h3>2. Plan and Define</h3><p><em>Objective: Determine the MVP</em></p><p>In this phase, we do market research, we already got the idea and we do the research on those ideas.</p><p>Then after carefully evaluating all possible ideas, then we decide which ideas we want to focus on and roadmap out what we think we could make, how long it might take, and at what point we should have a particular feature, if we are actually going to do this.</p><p>The goal is to have a product that has the minimum set of features to test our ideas. In this phase, we try to determine the MVP that gives the biggest impact using our market research data we did before.</p><h3>3. Develop</h3><p><em>Objective: Release the MVP</em></p><p>Now we have the solution to a problem. It’s time to get our hands dirty. This is the phase where we list down all the requirements for our MVP and start designing the mock.</p><p>After that, We start making user stories, and we are going to talk to the development team about estimations on very specific details of how long this particular thing needs to take to be developed.</p><p>By the time while developing, the requirements should be set, and they really shouldn’t change until we evaluate and get some sort of validation on the early parts of the completed product.</p><p>Don’t forget to install any analytic technology to track our user behaviour.</p><h3>4. Iterate and Validation</h3><p><em>Objective: Get early feedback</em></p><p>This is a phase when we finish our MVP, we get early feedback from the internal users and selected users, usually this step is done with releasing alpha and beta testing. We test the assumptions that we made with the original idea of the product.</p><p>We don’t wait until we are all the way done, because we want to get the testing as early as possible and iterate if needed.</p><h3>5. Launch</h3><p><em>Objective: Send product to market</em></p><p>In this phase we work with other stakeholders like the marketing team, PR team, sales team, legal team, etc in order for success of the product.</p><p>We want to develop a Go-to-Market Strategy, such as how the campaign looks like, how we plan to engage with customers, create value, and hit that strategic objective we just explained, which top 2–3 target persona we want to focus on, what is our unique value proposition that differs us from competitors, etc.</p><p>Deciding which Go-to-Market strategy will determine how big is the impact of our product we release. This may determine the success of the product.</p><h3>6. Post Launch</h3><p><em>Objective: Evaluate the product</em></p><p>During this time we collect metrics on how people use it, we analyse the product using the analytic we install before, analyze our current data and optimize our metrics.</p><p>We try to keep optimising our product, either from the performance of the product or the user journey based on the analysis done. We try to get the maximum return for investment on it.</p><h3>7. Maintain or Kill Product</h3><p><em>Objective: Deciding the product fate</em></p><p>Now we are at the final phase, At this point we decide, It’s either we keep iterating or kill the product.</p><p>We use all the data we have collected, analyze the product and see the metrics, is it still worth it compared to the cost? How frequently are people using or purchasing this? What is the return of investment?</p><p>If it’s not doing so well, then there’s not much we can do, so maybe we decide to kill it. On the other hand then we want to iterate and increase the metrics.</p><h4>Any Thoughts or Comments</h4><p>Well, that’s it for today. I would love to get any thoughts or comments.</p><p>Do share your feedback, and let me if this article was of any help. See you all next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=165f72afc8a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>