<?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 Kwan Ho Chan on Medium]]></title>
        <description><![CDATA[Stories by Kwan Ho Chan on Medium]]></description>
        <link>https://medium.com/@kwanhochan?source=rss-e4b5575e8b94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*2DKqZOVl4r8NC_DclTCOAw.jpeg</url>
            <title>Stories by Kwan Ho Chan on Medium</title>
            <link>https://medium.com/@kwanhochan?source=rss-e4b5575e8b94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:10:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kwanhochan/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[Key takeaways as a Not-For-Profit Product Manager]]></title>
            <link>https://medium.com/product-power-tools/key-takeaways-as-a-not-for-profit-product-manager-9b36efc1d47e?source=rss-e4b5575e8b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b36efc1d47e</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[not-for-profit]]></category>
            <category><![CDATA[social-impact]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[purpose]]></category>
            <dc:creator><![CDATA[Kwan Ho Chan]]></dc:creator>
            <pubDate>Mon, 21 Sep 2020 12:00:00 GMT</pubDate>
            <atom:updated>2020-09-21T12:00:00.603Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*ikAoozCcygQtSiyfRfSOtQ.jpeg" /></figure><p>It has been 3 years since I started my journey as a product manager at <a href="https://au.reachout.com/">ReachOut</a>, an NFP created to improve youth mental health in Australia. Compared to commercial business, product management at an NFP have a few key difference in characteristics, usually anchored around creating social impact.</p><p>As I am about to close this chapter of my career and embark on a new adventure, I thought it would be a good opportunity to reflect on things I have learnt along the way.</p><h3>1. Deeply knowing your beneficiaries and always placing them first.</h3><p>Beneficiaries are a group of people that your organisation exists to serve. We know that as a PM you need to empathise with your users however, this is tenfolds when you work at an NFP. Most importantly <strong>always</strong> place their interest first regardless of losing potential funding opportunities, reducing product growth or partnership opportunities.</p><p><strong>Things you should know intimately about your beneficiaries:</strong></p><ul><li>Who are your beneficiaries and what is the problem they are experiencing?</li><li>What is the problem they are experiencing?</li><li>How big is this problem in their life?</li><li>How do they currently experience this problem?</li><li>How do they current try and solve this problem?</li><li>Why are we best in place to serve them?</li></ul><h3>2. Are your users and beneficiaries the same people?</h3><p>As your organisation grows, some of your products in the ecosystem may not be targetting your beneficiaries as its users. The big, audacious social impact goal that your organisation is trying to achieve may not be possible by serving your beneficiaries alone. For example, <a href="http://au.reachout.com/">ReachOut</a> exists to serve young Australians however, we have products dedicated to <a href="https://parents.au.reachout.com/">parents</a> and <a href="https://schools.au.reachout.com/">schools</a> due to these users being a core part of young people’s support network.</p><p><strong>Assess the impact your other audiences have on your beneficiaries:</strong></p><ul><li>How do they impact the beneficiaries life, how big is this impact?</li><li>How likely are they to have a positive impact?</li><li>How do they interact with each the beneficiaries?</li><li>Is the impact they have on the beneficiaries repeatable?</li></ul><h3>3. Success can be measured by a combination of growth metrics + social impact.</h3><p>Measuring success is inherently different when compared to a commercial organisation which is usually anchored around revenue. For most NFPs, success is measured around the positive impact your product has made towards your beneficiaries and the growth of the product. Essentially we want to ensure that our product inherently will have a positive impact and that it is reaching and engaging our beneficiaries.</p><p>One of the key differences between an NFP and commercial business is our focus on impact measures. It’s an area where I believe having a dedicated research team is critical in ensuring that we are deliberate, accurate and scientific with our evaluation. At ReachOut, we have dedicated research and evaluations that run various annual surveys and complex cohort studies to evaluate whether our products and services are improving young people’s mental health.</p><p>However, there are also similarities in measuring success compared to commercial business. Success measures still ladder up to the organisation’s vision and strategy, ensuring that we are heading towards the same direction. As we are still providing a product to our beneficiaries and users, we would still set measures based on reach, usage and engagement metrics.</p><h3>4. Using retention as a counter metric.</h3><p>Retention is an interesting metric in NFPs, as our end goal is for our beneficiaries to hopefully not needing to return often. If our beneficiaries are returning often and are showing signs of more severe symptoms, then have we truly succeeded? Retention metrics should absolutely be monitored closely, however, I would challenge that it should be used as a counter metric. Counter metrics are numbers that prove your hypothesis to be wrong and identify where the gap is. They are commonly used as opposition to success metrics to prevent false positives. In the context of NFPs, its purpose is to evaluate whether our growth metrics actually translate to having a positive impact on our beneficiaries.</p><h3>5. Should we optimise for reach or impact?</h3><p>The never-ending debate at an NFP is whether we should be focusing on reaching more of our beneficiaries or deepening the impact we have. The short answer is you want <strong>both</strong>. However, that usually requires a very complex product or multiple products to achieve this and is likely to be a long-term outcome.</p><p>Understand what impact your product has to your beneficiaries and assess whether it is focused on reach or impact. An example of a reach focused product would be a website with information about youth mental health. It can reach millions of young people but is limited to providing support by increasing knowledge and reduces stigma. On the contrary, impact products like a one-on-one digital counselling service won’t service millions but would be able to provide hyper-personalised support.</p><h3>6. Using ‘reach’ products as a pathway into ‘impact’ products.</h3><p>The main advantage of reach products is that they are attractive to a huge segment of your beneficiaries with a low barrier to entry. It acts as a great acquisition pathway into impact products which may seem too intensive without prior support and education. This is commonly used in commercial space in the form of content marketing blogs. These blogs provide useful information to the users, hoping to convert them into paying customers by using their product.</p><h3>7. Free is a powerful unfair advantage.</h3><p>Social enterprises and NFPs as a section have been experiencing exploding growth. It is very easy to focus solely on how to create the most impact to your beneficiaries, however as an organisation, you have to be competitive.</p><p>In the eyes of your beneficiary whether you are a for-profit social enterprise or an NFP doesn’t matter. What matters to them is how well you solve their problem and how much it cost. Most of NFP’s income comes from government or corporate grants and community donations. The unfair advantage NFPs have is that it can often offer its product free to their beneficiary.</p><h3>8. Being attractive to funders matter.</h3><p>The flipside of this unfair advantage is that your income is based solely on securing funding contracts or donations. A for-profit social enterprise can generate profit from the beneficiary and grow at lightning speeds, NFPs are often stuck in-between funding cycles. To combat this NFPs have to be competitive in securing funding continuously through various streams. What tends to be attractive to funders are innovative products with some traction to prove its worth. A lean MVP rolled out to a small audience is a great way to do this, especially if you can craft a case study around the impact your product has.</p><h3>9. Growth, but at what cost?</h3><p>I want to reiterate the importance of always putting your beneficiaries first. Serving them is the reason your organisation exist. There will be funding opportunities that you will have to turn down. As counter-intuitive as that is if the funder isn’t aligned to your organisation’s vision the funding won’t push your cause forward.</p><p>The other hurdle that you will come across is trading off growth against your duty to your beneficiaries. There will be many product decisions that could result in massive growth for the product at the expense of potentially causing harm. For example, when you are building an MVP you could reduce scope by removing security and privacy features in order to go-to-market faster. However, if there is a security breach your beneficiaries privacy could be heavily affected. As an NFP PM you need to make the right trade-off, ruthlessly optimising for growth is not an option.</p><h3>10. Your purpose is electrifying, use it to rally your team.</h3><p>One of the advantages of any organisation with a strong reason to exist is the power it has on motivation. Not everyone in your organisation will not agree on every decision, but they will all agree that the cause is worth chasing after. This creates a sense of comradery and trust in fighting for a common cause.</p><p>As a PM you can leverage this through the storytelling of how the product or feature will have a real-world impact on your beneficiaries. Celebrate the small and big wins by sharing your beneficiaries experience with your product and the impact that it had on their lives. The key to a healthy and motivated team is to build a culture around placing the beneficiaries first and that we are making a difference, no matter how big or small.</p><p>Curious what working in a NFP or for-purpose organisation as a PM is like? Get in touch, always happy to answer any questions or chat about product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b36efc1d47e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-power-tools/key-takeaways-as-a-not-for-profit-product-manager-9b36efc1d47e">Key takeaways as a Not-For-Profit Product Manager</a> was originally published in <a href="https://medium.com/product-power-tools">Product Power Tools</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Tips on finding problem/solution fit.]]></title>
            <link>https://medium.com/product-power-tools/5-tips-on-finding-problem-solution-fit-dac3c1113a3c?source=rss-e4b5575e8b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/dac3c1113a3c</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[solutions]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[problems]]></category>
            <category><![CDATA[problem-solution-fit]]></category>
            <dc:creator><![CDATA[Kwan Ho Chan]]></dc:creator>
            <pubDate>Sun, 11 Aug 2019 12:00:43 GMT</pubDate>
            <atom:updated>2019-08-15T05:05:44.040Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bf-uoOdJqldZFDv7" /><figcaption>Photo by <a href="https://unsplash.com/@robschreckhise?utm_source=medium&amp;utm_medium=referral">Rob Schreckhise</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Problem statements are vital to good product development and a tool that every product manager should master. A well-defined problem statement is vital in ensuring that you are providing value to customers, and it’s the very first step in developing features that actually gain traction. I won’t go in-depth on how to write a great problem statement in this article, as it has been covered by this <a href="https://productcoalition.com/how-to-write-a-good-customer-problem-statement-a815f80189ba">excellent piece</a>.</p><p>However, knowing which problem to solve is only half of the equation. Implementing the wrong solution could have both short and long term negative impact on your product. What you end up shipping could have less customer value than expected, not scalable, incur a lot of technical debt, or introduce risk to your customers. Below are some key things to look out for, and tips and tools to help you find problem/solution fit.</p><h3><strong>1. Make sure your problem statement is validated.</strong></h3><p>Before looking into the solution space, validate that the defined problem statement still holds true. To deliver value to your customers, you need to be solving the right problem for them. Even if you have the shiniest solutions, if you are solving the wrong problem, it won’t deliver the results you are expecting. Take the time to understand which pieces of research, data, and insights the problem statement came from. A problem statement that has been inherited may be based on assumptions, outdated insights or simply not be as much of a pain point for your customers now.</p><p>A great way to do this is to speak to your customers directly through phone or in-person interviews. This is a great methodology to truly understand your customers, the root cause behind their problem, their motivations to solve it and how they are currently solving it. You can find a simple step by step guide on running customer interviews <a href="https://www.atlassian.com/team-playbook/plays/customer-interview">here</a>.</p><p>You may be tempted to use a ‘quicker’ methodology like surveys, as it is often perceived as an easy, low-cost research method that produces quantitative outcomes.</p><p>Surveys are a valid methodology, and great for asking questions that will warrant a factual response for example:</p><blockquote>‘What did you eat for breakfast?’</blockquote><p>It is also a great way to understand a customer’s habits and past behaviours, such as:</p><blockquote>‘How many times do you go for a run in a week?’.</blockquote><p>Beware of questions that warrant a subjective response as the participant may respond in favour of your question to please you. For example:</p><blockquote>‘What do you like or dislike about this feature’</blockquote><p>Avoid questions that ask participants to predict the future such as:</p><blockquote>‘Do you think you will use this product when it launches’</blockquote><p>The participant hasn’t performed the action yet, they simply don’t know. You can find out more from this <a href="https://medium.com/mule-design/on-surveys-5a73dda5e9a0">great article</a> that goes in-depth on the fallacy of using surveys incorrectly. Understand where your problem statement derives from, and validate any assumptions with it through appropriate research methodologies.</p><h3><strong>2. Be wary of being swayed by stakeholders.</strong></h3><p>This is a common problem when running ideation workshops with your/other teams, or with externals. Co-designing is an effective method to receive valuable input from different experts in their field. However, it can lead to a solution that everyone in the room is happy with, but not your customers. It is important to listen, understand and absorb all the information from your team and other stakeholders (input), but keep in mind that they aren’t the customer and likely won’t be using the feature (output).</p><p>Manage expectations during the ideation session by communicating that all the ideas discussed in the session will be considered. However, more definition work will need to be done before the solution can be finalised. Put in the work to explore all the ideas from the session, especially focusing on whether it truly solves the customer problem and understanding how it competes in the market. If there are multiple solutions that came out of your discovery phase, you can prioritise the solutions based on factors that are important to your product (i.e strategic alignment, customer value, and technical feasibility). Once you have finalised solution, communicate back to your stakeholders explaining your process and how you landed on the solution. Be prepared to answer any questions and defend your solution.</p><blockquote><strong>If you aren’t confident in shipping the problem/solution fit, ask yourself why.</strong></blockquote><p>As a PM it is your job to discern which pieces of information is valuable to the problem you are solving and which are interesting, but irrelevant. Being the person with the most overall knowledge on the feature you need to trust your gut. If the solution doesn’t sit right with you, take the time to reflect on why, and address it. I find it effective to come back and assess the problem/solution fit after a few days, to remain more objective. It’s always better to go back and explain to your stakeholders why the solution has pivoted from the ideation session, than ship a feature that you know won’t solve the customer problem.</p><h3><strong>3. Balancing between shipping fast vs shipping right.</strong></h3><p>When problem statements are validated and defined, product teams have a tendency to focus on shipping it to customers as soon as possible. This tends to lead to a speedy solution based on the first idea that comes to mind or the simplest to build. This is a costly mistake to make, especially when so much time has been invested in discovery in the problem space already.</p><blockquote><strong>Finding the right solution to your problem takes time and validation.</strong></blockquote><p>The first solution we come up with is very unlikely to be the right one. It is often based on preconceived notions of how the problem should be solved, rather than the discovery process involving customer research and concept testing. However, the reality is that not every feature you work on will have the luxury of time to fully explore the solution space. There are times when shipping fast is non-negotiable and may be the right decision to make (i.e to meet a specific strategic goal), however, keep in mind that it will likely incur a cost down the line (i.e tech debt).</p><p>When time is on your side validate your solution through concept testing, with customers who are experiencing the problem. One way to do this is to build a functional prototype and give it to customers to use in their natural environment. The benefit of this is two folds; you de-risk the concept by validating with customers, and you de-risk the build by resolving any technical assumptions. If the concept testing results indicates that it doesn’t solve the customer problem as expected, you can either pivot to find a solution that fits or scrap it and stop any further investment into it. The key is to keep the scope of the functional prototype tight, only building the minimum to validate the value of your solution.</p><p>Shipping fast vs shipping right is a decision you will likely need to make often and it can be one of the toughest. Understanding the factors (i.e time, budget, scalability) that influence your decision making and how much importance they weigh is vital to making the right decision. <a href="https://www.atlassian.com/team-playbook/plays/trade-off-sliders">Trade-off sliders</a> will help you understand the relative importance of all the factors you need to consider before making that decision. This tool really shines when it is used with your team and key stakeholders so that the decision being made is aligned and can be rallied on.</p><h3><strong>4. Question pre-defined constraints.</strong></h3><p>With any feature you are working on, it will likely be associated with constraints such as time, budget, resources, and dependencies. Constraints can commonly come from your seniors or the person who you report to. It can be daunting to question the constraints that have been placed but as the PM driving this feature it is vital to understand which constraints are negotiable and which aren’t.</p><p>One way to work through this is to organise a meeting with your seniors with a clear agenda on the constraints you want to better understand and discuss. The goal of this meeting is to understand where the constraints came from, and how much flexibility it has. You can do this by rephrasing the constraints into questions for example:</p><blockquote>‘Do we need to optimise this feature for mobile and tablet for the MVP?’</blockquote><p>If there are conflicting constraints (i.e ship quality code fast) <a href="https://www.atlassian.com/team-playbook/plays/trade-off-sliders">trade-off slider</a> can be a great tool to make a decision on which is more important. Record how negotiable each constraint is in a ‘<a href="https://docs.google.com/spreadsheets/d/1XpWZHpu4joxL8i9JWAkIMVPyhx93hDFSVRYrbqwniR8/edit?usp=sharing">Decision log</a>’, and keep it updated throughout the project. This will help communicate to stakeholders why decisions have been made, and how you came to the conclusion.</p><p>Constraints aren’t necessarily a bad thing and can act as guardrails to de-risk the feature you are working on. The key is to understand why the constraint exists, and how negotiable it is to help you make a considered decision.</p><h3><strong>5. Prioritising the right bugs.</strong></h3><p>Even if the problem/solution fits, poor implementation will kill a feature. Finding bugs during the testing phase is inevitable, especially when you are building something new or integrating with a 3rd party platform. To be able to ship on time it is vital to prioritise what to fix now and what to leave for later. As a PM you need to stay focused on the problem you are trying to solve with this feature and only prioritise bugs that prevent it from delivering value to the customer.</p><p><a href="https://www.guru99.com/what-everybody-ought-to-know-about-test-planing.html">Test plans</a> are a systematic way of testing that mitigates some of the chaos, as it forces the team to plan and prepare well in advance. Depending on how big the release is, book out half a day in your team’s calendar to conduct testing together. When a bug is discovered, immediately logged it into Jira. Once testing is completed, the PM will prioritise which bugs need to be fixed before the release based on <a href="http://softwaretestingfundamentals.com/defect-severity/">severity</a>. Critical bugs must be fixed before the release, whereas majors bugs will likely need to prioritise against how it affects the feature delivering its value.</p><p>A problem can be solved in many different ways, but realistically only a few solutions are appropriate based on factors such as strategic alignment, customer value, technical feasibility, and fixed constraints. Finding the right problem/solution fit more often than not requires iterations. <strong>Be patient, put in the work and most importantly trust your gut.</strong></p><p>Product management is a very complicated and subjective craft with very few universal truths to it. It fascinates me to navigate through the different problem /solution spaces and is one of the reasons why I decided to start writing about it. Hopefully, this article adds a little value to your craft.</p><p>Got some great tips of your own? Leave a comment below and let’s discuss!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dac3c1113a3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-power-tools/5-tips-on-finding-problem-solution-fit-dac3c1113a3c">5 Tips on finding problem/solution fit.</a> was originally published in <a href="https://medium.com/product-power-tools">Product Power Tools</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>