<?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 Theresa Lusiana on Medium]]></title>
        <description><![CDATA[Stories by Theresa Lusiana on Medium]]></description>
        <link>https://medium.com/@theresamvlr?source=rss-4f4dc95e6499------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JbgrYEHQFxhlr0wMbB_qXw.jpeg</url>
            <title>Stories by Theresa Lusiana on Medium</title>
            <link>https://medium.com/@theresamvlr?source=rss-4f4dc95e6499------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:07:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@theresamvlr/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[Almost. Almost Finished is Never Enough.]]></title>
            <link>https://theresamvlr.medium.com/almost-almost-finished-is-never-enough-179eb22d4534?source=rss-4f4dc95e6499------2</link>
            <guid isPermaLink="false">https://medium.com/p/179eb22d4534</guid>
            <category><![CDATA[poetry-on-medium]]></category>
            <dc:creator><![CDATA[Theresa Lusiana]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 14:22:51 GMT</pubDate>
            <atom:updated>2024-02-16T14:22:51.998Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer: this article is more of a personal reflection. And it’s a painful yet liberating one.</em></p><p>“Yes it is decided.“</p><p>We are going for it — full. speed.</p><p>Almost there.</p><p>STOP!</p><p>.</p><p>.</p><p>Let’s turn left (not right) now.</p><p>.</p><p>Okay, let’s repeat the last round 3, <em>uh no</em>, 4 more times.</p><p><em>How could someone bear the inconsistency of directions, while being judged by the inconsistency itself? Delivering at the most of one’s capability, at the most unfortunate circumstances?</em></p><p><em>Not trying to be abstract but abstract is at its core.</em></p><p><em>Perfection is what everyone thrives for. Yet, the clumsy, slippery hands are bestowed with praise.</em></p><p><em>Leads someone to lose their fire once burning brightly. Staring at the perfect dream yet consistently being disappointed at the clumsy reality.</em></p><p><em>Let everyone rejoice in the small perspirations made in abrupt endings, let everyone forget the long endurance made during the thoughtful process.</em></p><p><em>She refuses to give in to this meaningless pursuit in her once-upon-a-time La-la-land.</em></p><p><em>“Oh praise the small leap she made along the drive”,</em></p><p><em>Yet never been fully admired for her endurance amidst the sunken road.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=179eb22d4534" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflection on my internship]]></title>
            <link>https://theresamvlr.medium.com/reflection-on-my-internship-e67a1e185b07?source=rss-4f4dc95e6499------2</link>
            <guid isPermaLink="false">https://medium.com/p/e67a1e185b07</guid>
            <dc:creator><![CDATA[Theresa Lusiana]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 07:07:10 GMT</pubDate>
            <atom:updated>2020-11-02T08:56:47.510Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reflection on my internship during WFH</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qaf0Pw3cS_WIg5On9QWSrg.jpeg" /><figcaption>from <a href="https://unsplash.com/photos/-TQUERQGUZ8">https://unsplash.com/photos/-TQUERQGUZ8</a></figcaption></figure><p>In June 2020, my internship had arrived at an abrupt, yet anticipated end. My supposed to be six-month internship had to be forcefully cut down to four months due to decisions from the management to cease operation completely (I mean, we are not the only one heavily affected by the big elephant in the room — the c that should not be named).</p><p>After a solid four months of reflecting on what I had done right and wrong, I finally am able to pen down my thoughts on the valuable learning points from the internship. So here are my valuable takeaways (to which I had made my fair share of mistakes) I would like to repeat on my current and next career journey.</p><h4>Develop a genuine friendship with your supervisor</h4><p>I had the opportunity to be coached under a product manager who doesn’t have that big of an age gap from me. This definitely helps me to ease myself on initiating conversations with him, be it professionally or personally. I am such a people-person, I try to be nice to people I know well. Thus, the friendship forged between me and my supervisor is the quintessential of building trust and teamwork in my work life. With the friendship at stake at all times, I always try my very best to manage up to my supervisor’s standards. Also, the good thing about building a personal friendship with your supervisor is that you are never too afraid to report when you are faced with troubles in need of urgent solution.</p><blockquote>I took this internship program with a very, very optimistic mindset that helps me to see this opportunity as <strong>a (<em>read: the</em>)</strong> golden opportunity to build my knowledge and experience of real-life product management. With that in mind, initiating conversations with my colleagues is easing on my nerves.</blockquote><h4>Learn how to say “I am not sure yet” when you are not 100% sure</h4><p>This is BIG for me. It is more difficult to say “I am not sure yet” than “I know how to solve it”. If I say “I know how to solve it”, then I will be considered very good. This was my mindset when coming in to my internship. But guess what? I do not need to be a genius here. I am here to learn. I learnt humbly to have a learning mindset. With that in mind, I learnt to take time to gain contextual knowledge before giving proper answers to the problems at hand.</p><h4>Focus on one task at a time</h4><p>Especially in a role like mine, tasks can be overwhelmingly … a lot. It was like an exponential increment of tasks to do — from changing font sizes to projects in need of proper, thorough discussions. Of course, with that continuous stream of heads-up, I (eventually) got distracted. The distraction leads to a major context switching momentum (<em>to explain more on context switching, read the next section please!</em>). And with that momentum came the ultimate death — “um… where was I?” while looking at your laptop screen. And fun fact, it needs approximately 25 minutes to get you back in the “zone” (<em>read </em><a href="https://blog.rescuetime.com/context-switching/"><em>this article</em></a><em> on how context switching is killing our productivity</em>). On top of that lag, it was inherently so hard to revisit my trailing thought process. And then unknowingly, the 25 minute period ends. And there, I need to go on another meeting. Major learning lesson learned here: 25 minutes of skimming through another project is 25 minutes <strong>wasted</strong> to be better off spent on checking one more task from checklist.</p><h4>Context switching is a threat to my productivity. Hence, set aside time to be completely distracted for house chores please!</h4><p>During WFH (Work from Home), I am more susceptible to distractions (a.k.a. ticking off the very few house chores that I can barely set aside time for, random yelling from my parents, random favours from my parents, random appearance from my parents). They are all seemingly normal at first. Yes of course, because you are in the house. They <strong>are</strong> expected. But, these are precisely the reasons why workplace and house should be separated.</p><p>The rows of colleagues typing on their computer, the random, whispering crazy explorations on certain products, the random work updates to my supervisor really help live up the “work” spirit. The thought of “we are all in this together” — quoted from one of the famous High School Musical songs — really amped up my energy to focus on finishing the job at hand. But, with the random house distractions… It seems comforting at first, knowing that you are in absolute comfort of your home (on PJs and bed whenever I’m feeling stressed), knowing that I do not have to wear uncomfortable, thick work clothes, unlimited supplies of tissues, pens and proper makeup (<em>the horror! the burden!</em>). But, this, this was shortcoming, yet <em>unintended</em> — I don’t want to work for the next one hour. *goes to nap* (<em>the horror! he burden!</em>).</p><p>So, how does one balance the ultimate productivity and the inevitable house distractions? I honestly should say, I still don’t know yet. I can humbly say that it is definitely an art to master. My MVP solution now is to really set aside time to be distracted each day. Other than those timings, <em>sorry mom</em>, I am all ears to my professional life.</p><p>I also had an enjoyable time reading this <a href="https://blog.rescuetime.com/context-switching/">blog</a> on how context switching is killing our productivity (not in just the context of WFH, but working in general). Do give it a read if you have the time!</p><p>My internship experience was full of exciting pursuits and learning points that I would definitely carry throughout my professional career, and I want to know more of your most memorable takeaways from your internship, too. Do drop me a message if you would like to share some of your tips on dealing with people in work life. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e67a1e185b07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM Interview Series: Product Management in a Nutshell]]></title>
            <link>https://theresamvlr.medium.com/pm-interview-series-product-management-in-a-nutshell-6de3db5cd56f?source=rss-4f4dc95e6499------2</link>
            <guid isPermaLink="false">https://medium.com/p/6de3db5cd56f</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management-skills]]></category>
            <dc:creator><![CDATA[Theresa Lusiana]]></dc:creator>
            <pubDate>Sat, 26 Sep 2020 04:47:04 GMT</pubDate>
            <atom:updated>2020-09-26T04:47:04.356Z</atom:updated>
            <content:encoded><![CDATA[<h3>PM Interview Series: Product Management in a Nutshell with Clement Kao</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uXHq65URgGr9CE7x-AuH-g.jpeg" /><figcaption>Taken from Unsplash <a href="https://unsplash.com/photos/nPy0X4xew60">https://unsplash.com/photos/nPy0X4xew60</a></figcaption></figure><p>My encounter with Mr. <a href="https://www.linkedin.com/in/clement-kao/">Clement Kao</a> from <a href="https://blend.com/">Blend</a> started from his LinkedIn connection invitation. I gladly accepted his invitation and we chat a bit about his career at the moment. I was quite delighted to know that Mr. Clement Kao is an avid writer and co-founder of <a href="https://productmanagerhq.com/">Product Manager HQ</a> (PMHQ). Mr. Clement published 70+ product management best practice articles on the PMHQ website.</p><p>I would not want to miss the chance of getting product knowledge from an avid writer like him. As a professional contributor to PMHQ, I will embed links of his thoughtful articles throughout the interview transcript so you can also have some context!</p><p>For a better reading experience, I will list the topics discussed in this interview:</p><ul><li>Product Manager</li><li>People</li><li>Ideation Until Launch (Product Roadmap, Priotization, User Research, Project Management)</li><li>Competitors</li><li>Performance (Product Life Cycle, Metrics, Apps Interface, A/B Testing)</li><li>What distinguishes Great PMs from Good PMs</li></ul><h3>Product Manager</h3><h4>Q: Product Managers are often being confused with Project Managers. In your opinion, what is/are the stark difference(s) between the two?</h4><blockquote>At a high level: product managers maximise upside (and therefore expose themselves to risk) whereas project managers minimise risk (and therefore cannot kick off exploratory experiments). I have a PMP (project manager professional) certificate, so I speak from experience.</blockquote><p>To elaborate more on this topic for the curious souls, Mr. Clement also shared one of his insightful articles on <a href="https://productmanagerhq.com/product-manager-vs-project-manager/">Product Manager vs. Project Manager</a> on <a href="http://productmanagerhq.com/">PMHQ</a>. Do give it a <em>full</em> read if you can! :)</p><h4>Q: “To be a great PM, one must be from a tech background.” Do you find this statement to be true as per your personal experience?</h4><blockquote>No.</blockquote><h4>Q: What do you think is the most crucial criteria, in terms of hard skills (aside from leadership, management, etc), a great PM must possess?</h4><blockquote>The most crucial thing is to have <strong>empathy for stakeholders</strong>, and that includes empathy for engineers.</blockquote><p>You can see his article here on <a href="https://productmanagerhq.com/empathizing-with-engineers/">empathising with engineering</a> (and why you don’t need a technical background).</p><h3>People</h3><h4><strong>Leadership &amp; Attitude</strong></h4><h4>Q: What does it take to be a convincing, persuasive Product Manager?</h4><blockquote><a href="https://www.productmanagerhq.com/2018/10/stakeholder-empathy/">Stakeholder empathy</a> is the one thing that we need the most. Until we understand what makes our stakeholders tick, there’s no way to persuade them. This includes executives, managers, cross-functional partners (e.g. sales / marketing / legal), and podmates (e.g. engineering, design, QA).</blockquote><h4>Q: What do we need to do to earn the respect of our team?</h4><blockquote>Demonstrate that you care about them — set up 1:1’s and gain stakeholder empathy. Then, keep your commitments. I like to use a running 1:1 doc so they can see everything that I’ve tasked myself with on their behalf, and provide status updates on whether I knocked those out or not. That creates a historical record of my accountability.</blockquote><h4>Team &amp; Stakeholders</h4><h4>Q: What is the typical size of a team managed by a PM?</h4><blockquote>Depends on the company and the product maturity. Sweet spot is 5 engineers, but I’ve worked with only 1 engineer before, and I’ve worked with 24 engineers before.</blockquote><h4>Q: For the success of your product, who do you usually collaborate with? (Finance, Legal, Sales, Designer, Testing, etc)</h4><blockquote>This will sound trite, but it’s “everyone”. Finance, legal, infosec, sales, account management, deployment leads, customer support, marketing, design, QA, engineering, management, etc.</blockquote><h4>Q: What do you usually share in a PM meeting?</h4><blockquote>Depends. You can either meet to share context, or you can meet to drive to a decision and next steps.</blockquote><p>Read more on <a href="https://productmanagerhq.com/effective-meetings-for-product-managers/">Effective Meetings for Product Managers</a> by Mr. Clement for a better review regarding PM meeting.</p><h4>Q: How often do you need to collaborate with other PMs from other teams?</h4><blockquote>Depends on the product. Sometimes every single feature requires collaboration, other times none of the features ever need input from other PMs.</blockquote><h3>Ideation until Launch</h3><h4>Product Roadmap</h4><h4>Q: Where do backlog ideas usually come from?</h4><blockquote>Customers and internal stakeholders.</blockquote><h4>Q: How do you differentiate pain points from raw insights?</h4><blockquote>“I wish you build this solution.”, customer said. We should not really go into this feedback without understanding the actual pain points.</blockquote><blockquote>How do we attempt to understand the actual pain points?</blockquote><blockquote>1. Ask why. be better listeners to your customer.</blockquote><blockquote>2. What problem does it solve for you?</blockquote><blockquote>3. Try to better understand why they ask for such a request, because a feature request means there is a hidden pain behind it. And it is our job to identity this hidden pain.</blockquote><blockquote>But there comes a problem, pain is too abstract. but in an umbrella term of pain, it is usually referring to “more money to have or less money to spend.”</blockquote><blockquote>Weave in the discovery process into the sales process.</blockquote><h4>Q: What do you usually do to validate your ideas?</h4><blockquote>We do user research.</blockquote><h4>Q: What decides which product/initiative should be put in the product roadmap? What does a typical idea usually go through in order to be on the product roadmap?</h4><blockquote>The PM is the ultimate decision maker, but they take input from customers, cross-functional stakeholders, and leadership.</blockquote><h4>Q: How flexible is your product roadmap? How often do you go back to your product roadmap to revise your roadmap?</h4><blockquote>Very flexible. I edit every week.</blockquote><h4>Q: What are the protocols in finalising or revising a product roadmap?</h4><blockquote>I write the roadmap, I share with stakeholders asynchronous, if someone has objections then I talk through them what their concerns are and continuously edit the roadmap. Roadmaps are organic, living documents; they are not meant to stay in stone.</blockquote><h4>Q: If a company decides to change their business growth vision, how is the adjustment going to be?</h4><blockquote>We perform quarterly planning (rolling 12 months) from both a top-down perspective and a bottoms-up perspective, and then we realign all roadmaps and all metrics to the new quarterly plan.</blockquote><h4>Q: Do you use decision making framework/tools?</h4><blockquote>Yes.</blockquote><h4>Q: What decision making framework/tools do you usually use?</h4><blockquote>Three questions to ask:</blockquote><blockquote>Is this a reversible decision?</blockquote><blockquote>What is the ROI? Is this the highest ROI thing we could do?</blockquote><blockquote>Is there a window of opportunity, or is this opportunity evergreen?</blockquote><h4>Q: With the three questions asked before, what is the next best thing to do then?</h4><blockquote>The challenges with any kind of prioritisation, or any decision making framework, is that decision making is an art, it is not a science. and so, there is some amount of cost that you are spending in trying to understand whether this decision is good enough. So, if you spend 6 weeks trying to understand whether a decision is correct or not, that is much worse than if you spend two days to make a decision, spend two weeks building this, and come to a conclusion that this is not a good decision.</blockquote><blockquote>There is a part one: if it is a <strong>reversible</strong> decision and it doesn’t cost you a lot, it doesn’t commit you to anything, you might as well just go into it, because then, there is no long lasting pain.</blockquote><blockquote>but, part two, if it is an <strong>irreversible</strong> decision, it costs you a lot of time that you can’t get back, then you would have to ask, is this the best way to use our time? One way to ask: what is the ROI (return on investment) that you are going to get? This applies in a case where there are two initiatives: the first initiative costs us 100 dollars and ROI of 1,000 dollars meanwhile the second initiative costs us 100 dollar and ROI of 5,000 dollars. We should go with the second initiative instead. So that helps you to identify the sequence.</blockquote><blockquote>But then, there comes another problem of: a lot of opportunities just don’t last forever. Product is always in an evolving landscape with competitors (shifting market demands, and etc.). So, there are many times that you just need to go with the smaller ROI project first, because there won’t come an opportunity like that later on. There are going to be times when you are forced to do the projects with smaller ROI, but it is urgent. There won’t come any other time where you can do it, which this will hinder you in the long run.</blockquote><blockquote>So, the reason there is no one right answer is the answers to the 3 questions above fundamentally changes the landscape of how you are making a decision. It depends on what your executive thinks is important, and what you think is important.</blockquote><h4>Q: Cost of delay. Do you use this as a method to identify which feature/product to prioritise?</h4><blockquote>not always, because cost of delay is ultimately, a cost in the cost-benefit analysis. There are two component of a product:</blockquote><blockquote>benefit component (to your customer and to you) and cost component (which is not just the cost of delay, but the cost of building it).</blockquote><blockquote>If you optimise simply on the cost of delay, then you will be building a lot of short-sighted features that are not going to ladder up to a broader product roadmap, and you are going to build a lot of features that are urgent, but not important (projects that might not have ROI to begin with). Just because it costs you a lot to get your foot in the door of some tiny market, doesn’t mean that you are going to want to go to that tiny market in the long run. But if you are trying to keep your door open to everyone, that is something that a product team <strong><em>might</em></strong> do. If you are trying to get into all 50 markets by building tiny projects, then there is the broader question to ask: should you actually be in those 50 markets?</blockquote><blockquote>If you are only use the cost of delay, you are not going to build a good product. but if you don’t use the cost of delay, you are also not going to build a good product. So it is an art of balancing.</blockquote><blockquote>So if there is a huge cost of delay but no ROI to begin with, then you should not be doing that feature.</blockquote><h4>Q: How to manage product discovery and delivery?</h4><blockquote>For discovery: meet with customers regularly, demo / ship on a relentless cadence, get feedback and talk through tradeoffs.</blockquote><blockquote>For delivery: this is project management, stay on top of Jira and standups.</blockquote><h4>Prioritisation</h4><h4>Q: How do you prioritise features / projects and cut out the noise?</h4><blockquote>I work in B2B. The factors are:</blockquote><blockquote>how large is the aggregated customer demand? How deep is the impact? This gives me a benefit number.</blockquote><blockquote>Then, what is the engineering cost?</blockquote><blockquote>Divide benefit by cost to get ROI. Evaluate ROI vs. all other initiatives, and sequence based on highest ROI.</blockquote><h4>Q: Which one will you prioritise first: developing new products / features to attract bigger markets which require high-level cost of resources, or developing a feature that tackles risk assessment of our application first?</h4><blockquote>Depends on the lifecycle of the product. If there’s fundamental missing capabilities that would unlock significant new markets, then we tackle those. Otherwise, we try to avoid refactoring just for refactoring’s sake.</blockquote><h4>Q: Does every prioritisation need to be calculated objectively?</h4><blockquote>No, not all of them need to be objective. If it’s a low cost (less than 1 dev-week), and is clearly a better UX for the majority of users (e.g. cannot just be an edge case), we’ll invest there even if we can’t measure it.</blockquote><h4>User Research</h4><h4>Q: Which process do you usually act on first: idea or surveys?</h4><blockquote>Surveys are not generally valuable in B2B. I’ve never used a survey in my time as a product manager. I always jump straight to conducting user interviews, and presenting multiple alternative ideas in a neutral way. That way I can get their reactions to various perspectives and understand how they’re thinking about the problem.</blockquote><h4>Q: How frequent do you conduct user research?</h4><blockquote>Every day. Every sales conversation and feedback report is user research.</blockquote><h4>Q: What method(s) do you find is/are the most effective in identifying customer’s pain points &amp; feedback?</h4><p>He suggested me to read on his article for user interview, which you can also read here: <a href="https://www.productmanagerhq.com/2018/08/effective-user-interviews/">conducting effective user interviews</a>. But for the purpose of the wholesome learning points for myself, I will write a short summary (which will contain mostly quotation from the real article for better interpretation) on his article:</p><p>This guide is structured the following way:</p><p>Before the Interview:</p><ul><li>Plan</li></ul><blockquote>Determine what your <strong>objective</strong> is for conducting the user interview. Are you trying to better understand a particular problem? Do you have a hypothesis in mind that you’re trying to prove or disprove? Is there a product decision that you’re trying to make?</blockquote><blockquote>Based on your objective, come up with questions that will help you achieve your objective.</blockquote><blockquote>Note that most user interviews shouldn’t go past 60 minutes, since interviewees tend to run out of energy and focus by then.</blockquote><ul><li>Source</li></ul><blockquote>To conduct interviews, we need interviewees. I realise how dumb that sounds, but finding interviewees is honestly one of the hardest parts about user research.</blockquote><blockquote>We need to find willing participants. One great way to jumpstart your pool of interviewee candidates is to start with family, friends, and colleagues as initial interviewees, and to ask them to refer others to you.</blockquote><blockquote>As you look for participants, consider both unpaid (word-of-mouth and postings) &amp; paid channels.</blockquote><blockquote>In cases where you’re finding lots of difficulty in recruiting, considering hiring a third-party professional sourcer.</blockquote><ul><li>Screen</li></ul><blockquote>You need to ensure that the users you interview are not biased. Biases come in two broad categories: beliefs and demographics. To account for these biases, you need to ensure that the sample you take is representative of the market that you want to tackle.</blockquote><blockquote>But, it is also important to take note that similarly, we shouldn’t exclusively limit ourselves to a particular geography unless that’s the specific geography we want to tackle.</blockquote><ul><li>Schedule</li></ul><blockquote>Be sure to leave time between interviews so that you’re not rushed from one to another. You want to ensure that you have some amount of buffer time in between interviews, especially where you find a thread of inquiry that’s particularly insightful but requires additional time from what you had originally scheduled.</blockquote><p>During the Interview:</p><ul><li>Contextualize</li></ul><blockquote>Provide context to your interviewee. Who are you, and what are you generally looking to learn about?</blockquote><blockquote>Stay high level and keep your product out of the discussion for now. What is she trying to accomplish, and why is she trying to accomplish it? What’s blocking her from being more effective?</blockquote><ul><li>Dive</li></ul><blockquote>Your most important objective is to<strong> learn how to think the way your interviewee thinks </strong>— try to understand what they are feeling, make them feel included and actively listened.</blockquote><blockquote>First, ask questions in an <strong>unbiased way</strong>. Instead of asking, “Why is it so painful for you to shop for groceries?”, ask “How do you feel about shopping for groceries?”</blockquote><blockquote>Second, don’t ask a ‘yes’ or ‘no’ question. Do not ask “are you the one who is buying the groceries for your household?” but ask “who are the one buying the groceries for your household?”</blockquote><blockquote>Third, ask “why” to any answer that you get back. You may feel embarrassed, or you may feel the answer is complete — but many times, you’ll find that going one level deeper will yield new insights or ways of thinking.</blockquote><ul><li>Replicate</li></ul><blockquote>Close out the interview by running through hypothetical scenarios with your user, or by running through wireframes and prototypes. Now is the time to see whether their behavior is the same as their stated thought process!</blockquote><p>After the Interview:</p><ul><li>Retrospect</li></ul><blockquote>Once you complete the user interview, reflect on the experience immediately. Use whatever downtime you have until the next interview to reflect on what you’ve learned. Are there other areas of inquiry that you should going after instead? Are particular questions not working the way you expected them to?</blockquote><blockquote>With these insights, continuously hone your user interview guide.</blockquote><ul><li>Document</li></ul><blockquote>Gather all of your notes and recordings in one centralized location.</blockquote><blockquote>Create a spreadsheet or table, and enter in attributes about each of the interviews that you’ve conducted so far.</blockquote><blockquote>Then, provide a direct link to the raw interview itself. That will help you synthesise the data at a later point, and enable you to quickly navigate all of the interviews you’ve conducted thus far.</blockquote><h4>Q: What do you usually want to investigate during a user research?</h4><blockquote>You cannot get feature feedback without digging deeper into the pain that is kick starting the feedback. If you get feedback and you don’t ask why, why, why, then you won’t actually understand what the root problem is. Everyone will give you different and conflicting feedback, but the root cause pains generally converge into a single problem statement.</blockquote><h4>Project Management</h4><h4>Q: What project management framework do you use in your company?</h4><blockquote>None. We’re in charge of coming up with how we want to manage the work.</blockquote><h4>Q: If your team’s speed is low, what do you usually do to boost their speed up?</h4><blockquote>Identify the bottleneck. Is it lack of context, lack of skill set, or lack of people? Then, attack the bottleneck.</blockquote><h4>Q: Do you clash ideas with your engineers? Is it a common thing that a PM will be critically attacked in the technical realm by their engineers?</h4><blockquote>We collaboratively talk through tradeoffs. I expect my engineers to push back and tell me that there is a better technical solution available. And, my engineers expect me to push back and tell them that their idea cannot be implemented because our customer or our business has a real constraint.</blockquote><h3>Competitors</h3><h4>Q: Is it important to keep up with competition (since our competitors do it, then we should do it)?</h4><blockquote>We do not chase competitors. We identify what our customers truly need.</blockquote><p>Read this <a href="https://www.widerfunnel.com/blog/how-to-create-an-awesome-value-proposition/">article on value propositions</a> by Mr. Clement, and why it’s dangerous to chase competitors.</p><h4>Q: When do you know that it is time to find new verticals, not to expand the horizontals?</h4><blockquote>We ask our customers to make the tradeoff — what do they see as the highest priority? We aggregate the responses to identify how much to invest in new verticals vs. expanding existing capabilities.</blockquote><h4>Q: Do you ever get caught in tough competition? What do you do to attempt to stay ahead of the competition?</h4><blockquote>We purposefully find tough competitors and go tackle them. To beat them, we use pilots. Read my presentation on <a href="https://docs.google.com/presentation/d/1332f5-2axHV5QckQxEaiXyhE2MxSHSdP9tcTIx6PiX8/edit">how to use pilots</a> to create product/market fit and stay ahead of competitors.</blockquote><h4>Q: According to the book “Art of Opportunity”, it is said that today’s business model can no longer depend on being the cheapest offerings. What is your take on that? How do businesses/products stay relevant in today’s world?</h4><blockquote>Agreed. Cheap doesn’t matter. ROI matters the most. If you provide the most value for your customer (benefits divided by costs), you will always win.</blockquote><h3>Performance</h3><h4>Product Life Cycle</h4><h4>Q: When do you know that your product has reached the Decline Stage?</h4><blockquote>Based on user feedback and usage statistics.</blockquote><h4>Metrics</h4><h4>Q: Retention, Engagement &amp; Conversion. Which metric do you emphasise on the most?</h4><blockquote>Depends on the product. For example, you can’t possibly retain a borrower when they’re applying for a mortgage, since they either apply or they don’t apply — they don’t come back after the mortgage is done.</blockquote><h4>Q: In relation to Product-Market Fit. How do you find your product’s North Star?</h4><blockquote>See this set of articles I wrote for Gainsight: <a href="https://www.gainsight.com/blog/stop-using-the-wrong-product-metrics-valuable-metrics-framework-part-1/">part 1</a>, <a href="https://www.gainsight.com/blog/stop-using-the-wrong-product-metrics-unlocking-business-value-part-2/">part 2</a></blockquote><h4>Q: Do different sectors require different sets of metrics? If so, what did you use in the past?</h4><blockquote>Yes, they do. Each vertical has a different need. In real estate, I focused on funnel metrics such as “time to convert a lead into a sale”. In fintech, I focus on engagement metrics such as MAU.</blockquote><h4>Q: How would you analyse a change in a metric?</h4><blockquote>See my article here on <a href="https://productmanagerhq.com/product-manager-interview-analyze-a-metric-change/">analyzing metric changes</a>.</blockquote><h4>Apps Interface</h4><h4>Q: How often do you change your interface? When do you know it is time to change?</h4><blockquote>I work in B2B, so I do not engage in UX changes unless the underlying functionality itself has changed. I’ve never done a redesign before.</blockquote><h4>Q: Do we, as PM, need to be adept in user experience?</h4><blockquote>Yes, you must understand what makes good UX, though you don’t need to design it yourself.</blockquote><h4>Q: What are the bullet-proof tips you can give in identifying the most pleasant user experience?</h4><blockquote>Things to do: <a href="https://www.productmanagerhq.com/2018/08/effective-user-interviews/">conduct effective user interviews</a>, <a href="https://productmanagerhq.com/shadowing-your-sales-team/">shadow your sales team</a>, <a href="https://productmanagerhq.com/customer-support-for-a-day/">shadow your customer support team</a>. The general goal is “get the user’s voice into your head” so that you can talk design through “why XYZ decision is good” or “why XYZ decision is bad”. You own the customer’s voice in the room when you work with design and engineering.</blockquote><h4>A/B Testing</h4><h4>Q: What does an A/B testing mean to your product development? Does it possess a high importance even for small products?</h4><blockquote>No. I work on B2B products. You cannot A/B test those because businesses are running their processes on you, so you cannot introduce variants. See this presentation on <a href="https://docs.google.com/presentation/d/1gJujPJdwxhbV0RqTjd-coA_3Q40Yo-8QuGbTuV5o8_o/edit#slide=id.p">Nuances of B2B Analytics</a>.</blockquote><h3>What distinguishes great PMs from good PMs</h3><h4>Q: What is your key learning point of being a PM?</h4><blockquote>Identifying the correct problem to solve is 90% of the complexity. The rest is straightforward.</blockquote><h4>Q: What was your most difficult trial during your career as a PM (be it personal, professional, or relational)?</h4><blockquote>Relationships are hard. I’m an introvert and I’m not good at politics, so it’s always awkward for me to talk to someone about performing poorly.</blockquote><h4>Q: What do you think differentiate great PMs from the good PMs?</h4><blockquote>See this Quora post on <a href="https://www.quora.com/What-distinguishes-the-Top-1-of-product-managers-from-the-Top-10">1% PMs</a> from Ian McAllister. Basically: be T-shaped, be good at everything.</blockquote><h4>Q: What are some of your suggestions and pro tips on resources to watch/listen/read to be a great (not just a good) PM?</h4><blockquote>Focus on a specific PM and absorb their mindset through all of their blog posts. Good people to understand — <a href="http://sachinrekhi.com/">Sachin Rekhi</a>, <a href="https://caseyaccidental.com/">Casey Winters</a>, <a href="https://adamnash.blog/">Adam Nash</a>, <a href="https://www.kennorton.com/">Ken Norton</a>, <a href="https://andrewchen.co/">Andrew Chen</a>, <a href="https://svpg.com/">Marty Cagan</a>. Once you absorb their blogs posts, you know how they think, and their voices will speak to you while you tackle product management.</blockquote><p>The interview experience with Mr. Clement had definitely opened my eyes to how delicate of an art product management is. Though there are certain framework (in mathematical language — formulas) to certain cases, but it should be balanced with a certain amount of rationality and sensibility. With every other case varies ever so slightly, there is a sizeable amount of qualitative and quantitative consideration we need to take into account until we conclusively make a decision as a product manager.</p><p>With a very formulaic background of mine (maths..), there will be a gradual shift of way of thinking when I am carving my career into product management. The questions I have crafted were worded in a more formulaic stature. On the other side, the answers that I had gathered were mostly a balancing act between a “yes” or “no”. If this was illustrated as colours, it was initially black and white, and now it is all a definitive shades of grey.</p><p>I would like to thank Mr. Clement for setting aside time to discuss questions with me over on an online meeting. I was very pleased with the many insights I have gathered throughout our interview.</p><p>To read more on how I came up with this PM Series, check out my article <a href="https://medium.com/@theresamvlr/pm-interview-series-introduction-d5df1f3ca2ef">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6de3db5cd56f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM Interview Series: Introduction]]></title>
            <link>https://theresamvlr.medium.com/pm-interview-series-introduction-d5df1f3ca2ef?source=rss-4f4dc95e6499------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5df1f3ca2ef</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-manager-interview]]></category>
            <dc:creator><![CDATA[Theresa Lusiana]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 19:19:52 GMT</pubDate>
            <atom:updated>2020-10-26T16:32:00.408Z</atom:updated>
            <content:encoded><![CDATA[<h4>The PM Interview Series might be more suitable for peeps who have a little bit of a context understanding of Product Management.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*id1XGdV-ruaV4xwh0y6SFg.jpeg" /><figcaption>Picture is taken from <a href="https://unsplash.com/photos/0GBxtiFvzXE">https://unsplash.com/photos/0GBxtiFvzXE</a></figcaption></figure><p>Hi! I am Theresa. I am eagerly learning how to “<em>properly PM</em>” and hence, this series was born.</p><p>Note: This article is written in a casual, inquisitive (as what my friend would say) way of mine.</p><p>In this series, I have a myriad (read: <em>a lot</em>) of PM-related questions for some experienced PMs who I have acquainted over the making of this series or who I have <em>disturbingly</em> annoyed before the making of this series. I would like to share the interview results with them over the course of this series. :)</p><blockquote>The making of this series has definitely made me come out of my comfort zone. Remembering how jittery my speech was when asking questions, clenching my jaws and grinding my teeth to remain calm every so often (read: spasmodically!) and clenching my hands so that I won’t be freezing due to nervousness. It definitely took a lot of effort just to not do silly random things while interviewing. I really hope my series provide the different perspectives and empathy PMs should acquire. — Yours truly</blockquote><h4>Now, let’s start with how I came up with this crazy idea.</h4><p>No university department nowadays covers Product Management and even people sometimes say project manager instead of product manager, thinking that they are the same thing! Very little resources to look at on how to “<em>properly PM</em>”.</p><p>Product Management (PM) is a very<strong> experience-based</strong> study field, at least it was to me. Even if there are resources out there on how to <em>“properly PM”</em>, PM theories are all <strong>ideal</strong> cases. The <strong>REAL</strong> problem kicks in when you are actually trying to implement those theories and then realised, “oh no, now what?”</p><p>It was very hard for me to learn how to “<em>properly PM”</em>, especially in this tragic time of COVID19. I cannot go out to mingle with fellow product enthusiasts in conferences and meetups. Henceforth, I strategised my “ PM Interview process” by writing up 25+ (D<em>isclaimer: not exhaustive!</em>) PM-related questions from Ideation to Metrics and Prioritisation.</p><h4>Okay, questions. Then, what?</h4><p>Somewhere deep inside my inkling mind tells me: “I needed to reach out to professionals to help me answer some (<em>read: all</em>) of my questions!”. <strong>I really wanna dub myself as Theresa the PM Explorer, but it might sound too corny.</strong></p><p>And boy, I turn to <a href="https://productschool.com/slack-community/"><strong>Product School Slack Community</strong></a>. I am very lucky to be a part of such an eager community where passionate aspiring and professional PMs gather. My wildest thought at the time is to cold call in one of the channels. I waited for the responses. [<em>Cold Call </em>might not be the most appropriate word to write here, because, context (business), but it is definitely the most suitable way I can explicitly describe what I did to attract some of the very professional PMs in the slack community.] It was definitely the most nervous moment I have ever been stuck in.</p><p>Where can I reach out to other PMs? My lightbulb moment was <strong>LinkedIn</strong>. YES! I made several connections with and roll out another round of cold calls, but this time, personal messaging them one-by-one (<em>read: the horror of being ignored!</em>). My God, the anticipation for the responses is worse. I will either look like a crazy MLM stalker if they ghosted me, or a very amateur learner if they welcomingly receive my messages.</p><h4>Now, let the PM Interview Process start.</h4><p>I will be sharing my interview transcripts with product managers I have successfully arranged interview with. I will make a list of the respective links for each interview I have ever done. As this is an <strong>non-exhaustive</strong> series, I will be constantly adding to the list below:</p><ol><li><a href="https://medium.com/@theresamvlr/pm-interview-series-product-management-in-a-nutshell-6de3db5cd56f">Product Management in a Nutshell </a>with Clement Kao, Product Manager at Blend, USA</li><li>From Ideation to Metrics and Prioritisation with Barry Matthew Meyer, Product Manager at DANA Indonesia (transcript is coming soon!)</li><li>Validation and Roadmapping with Prasetyo Andy Wicaksono, Senior Product Manager at Bukalapak Indonesia (transcript is coming soon!)</li><li>Product Management is a delicate art to master with Gohan Parningotan at Cicil.co.id Indonesia (transcript is coming soon!)</li><li>Product Manager for Funnel Optimization with Samuel Widjaya at Tokopedia Indonesia (transcript is coming soon!)</li><li>Interview with Bahni Mahariasha, Product Manager at GOJEK Indonesia (interview is coming soon!)</li><li>Product Management through the lens of business with Jeremy Joseph Hanniel at Shopee Indonesia (transcript is coming soon!)</li><li>Interview with Nigel Chrisman Santosa, Product Manager at Mekari Indonesia (interview is coming soon!)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5df1f3ca2ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>