<?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 Lilly M. Dobreva on Medium]]></title>
        <description><![CDATA[Stories by Lilly M. Dobreva on Medium]]></description>
        <link>https://medium.com/@lilly.dobreva?source=rss-1fb8c89bd9e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UvwuAhLx8KLK5swF46LaBQ@2x.jpeg</url>
            <title>Stories by Lilly M. Dobreva on Medium</title>
            <link>https://medium.com/@lilly.dobreva?source=rss-1fb8c89bd9e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:48:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lilly.dobreva/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[The Missing Ingredient in Your Product Roadmap]]></title>
            <link>https://medium.com/swlh/the-missing-ingredient-in-your-product-roadmap-403d03b4de8e?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/403d03b4de8e</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Fri, 06 Dec 2019 14:03:14 GMT</pubDate>
            <atom:updated>2020-10-26T15:53:12.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WeFKvl1BF-yeLjbF" /><figcaption>Photo by <a href="https://unsplash.com/@gxjansen?utm_source=medium&amp;utm_medium=referral">Guido Jansen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Sunsetting: The Missing Ingredient of Your Product Roadmap</h3><p>As Product Managers, it’s our job to create value for our users and our company. And so we ask ourselves:</p><blockquote>How can we add more value to our product?</blockquote><p>What often follows is a laundry list of new features to address certain problems or improvements for already existing features. If we brainstorm some more, we’ll end up with even more new and additional things to build. And here is the problem. We often assume that the only way to increase the value for our users is to add something. Adding is seen as inherently positive. After all, intuition and experience tell us people won’t object to receiving more for the same amount of investment from their side. And while this is true in a variety of cases and I believe could be a sound strategy to delight users, it need not be the only one you should be considering.</p><p>We have all heard time and time again that ‘Less is More’ but if you simply look again at your roadmap, I bet there isn’t a single item focused on sunsetting a feature or service. Simply put, we don’t see removing code as a value-adding activity. Instead, we see it as less exciting because there isn’t something inherently new about it. The novelty factor, a major excitement ingredient, is zero. Your engineers want to build cool stuff. This makes it harder to get them or other stakeholders on board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z1QKycZICNP2E1TX" /><figcaption>Photo by <a href="https://unsplash.com/@prateekkatyal?utm_source=medium&amp;utm_medium=referral">Prateek Katyal</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sunsetting a feature could also be seen as a signal that building it in the first place was a mistake. Building the right products the right way is hard and we get plenty of learning opportunities along the way. However, sometimes Product Managers could find it difficult to admit failures and are unlikely to engage in the analysis and discussions needed to determine if sunsetting is a good option or not. This is especially true in companies where a ‘Fail-Safe’ culture isn’t present. After all, we tend to celebrate launches and we tend to mourn dead features. I know I would much rather be in a celebratory mode.</p><p>But when done right, sunsetting has its benefits. By eliminating sub-performing features or services, users are likely to benefit from the more streamlined experience. They can now fully have their attention on your well-performing features. You have less code to maintain and less complexity and that frees up time to focus on delivering value where it really counts. Removing code really could provide value for the user and the organization and I hope next time you’re thinking of what to put on your roadmap you remember this.</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=403d03b4de8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-missing-ingredient-in-your-product-roadmap-403d03b4de8e">The Missing Ingredient in Your Product Roadmap</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Trick to Make You A More Efficient Product Manager]]></title>
            <link>https://medium.com/@lilly.dobreva/a-simple-trick-to-make-you-a-more-efficient-product-manager-8af313ca0777?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8af313ca0777</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Fri, 29 Nov 2019 22:06:15 GMT</pubDate>
            <atom:updated>2019-12-09T15:12:28.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8NcOlGYrChMxKKzA" /><figcaption>Photo by <a href="https://unsplash.com/@prateekkatyal?utm_source=medium&amp;utm_medium=referral">Prateek Katyal</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are many ways to be more efficient as a Product Manager but I am going to trust your googling skills and won’t list them all here. Instead, I want to focus on a less obvious one. In fact, I just demonstrated it to you in the opening sentence of this article. Let me explain.</p><p>I recently attended a conference and had the pleasure of listening to some very engaging talks. One thing instantly caught my attention. One of the speakers was explaining that earlier in his career the vast majority of his time was spent answering the questions his development team had. Sounds familiar? I used to be in this situation as well when I started. I thought being attentive to the developers is no brainer and was happy to answer everything and anything that was thrown my way. And you should absolutely do so, no doubt. But it’s also true that often these discussions were actually proposals coming from the engineers on how to adapt the solution to make it better, faster, simpler or cheaper and after some back and forth I’d simply say ‘I agree’. I bet it’s something that often happens to you too. And then the speaker said:</p><blockquote>What if instead of ‘I agree’, you flip it and say ‘I trust you’?</blockquote><p>And it made me reflect. What if your team knows you trust them to make these calls and they just do so and simply inform you. What would happen then? I can tell you.</p><ul><li>Your team will be more empowered to deliver the best possible solution</li><li>Your team will also feel a stronger sense of ownership over the solution</li><li>You’ll be forced to always communicate clearly what is the problem and what is the goal so the team has enough information to make these calls</li><li>You free up time for yourself (👋 Hello, Efficiency! I was looking for you!)</li></ul><p>You get all of this plus the added benefit of fostering a trusting work environment. If all this sounds somewhat familiar, well, it should be. Product Managers are best equipped to own the Problem Space with knowing the Why and should leave room for the rest of the team to figure out the What and How in the Solution Space. It’s easy to forget that but now you know how to spot it: if you start saying ‘I agree’ a lot when discussing something with your team and you feel like there’s not much unique perspective you can add, let them handle it. You can trust them, they’ve got this. And now you’ve got some spare time too.</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8af313ca0777" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do You Keep Product Managers Happy?]]></title>
            <link>https://medium.com/swlh/how-do-you-keep-product-managers-happy-6d234bd765e1?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d234bd765e1</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Wed, 23 Oct 2019 14:20:05 GMT</pubDate>
            <atom:updated>2019-11-02T14:15:46.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YmcONd5Nli32aMBX" /><figcaption>Photo by <a href="https://unsplash.com/@alexblock?utm_source=medium&amp;utm_medium=referral">Alex Block</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What Makes Product Managers Happy?</h3><p>Today, I came across <a href="https://confidenceconf.com/product-managers-job-satisfaction-study?ref=producthunt">research</a> done by the folks at <a href="https://confidenceconf.com/product-managers-job-satisfaction-study?ref=producthunt">ConfidenceConf</a>, <a href="https://medium.com/u/5c8a41de7f95">Pavlo Pedenko</a> and <a href="https://medium.com/u/85c449caffb3">Yaroslav Stepanenko</a>. I think most PMs would find it insightful and thought-provoking. It covers job satisfaction among PMs in relation to how happy they are with different aspects of their job. Here is the summary:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gI3Gpt6TU_1PzzR4VJNsNQ.png" /><figcaption>Summary from ‘Product Managers’ Job Satisfaction’ Report 2019 by <a href="https://confidenceconf.com/">ConfidenceConf</a>. Get the full report <a href="https://confidenceconf.com/product-managers-job-satisfaction-study?ref=producthunt">here</a></figcaption></figure><p>It’s a well-structured and engaging read and frankly the most comprehensive research on this topic I have come across so far. Looking at the summary, some of the findings definitely drive home the point that autonomy, clear decision-making process and strong collaboration are key to PM’s happiness. But obviously, there’s more.</p><p>It made me think not only about what really influences my own satisfaction with my PM role but also how do I make sure that the PMs on my team are satisfied. I don’t have a very clear-cut answer but I think the most important step is to listen and adapt. Make sure you are always aware of what bothers the Product Manager and actively take steps to adapt the reality to fit their needs. Personally, when I see people take my pains seriously and act on them with urgency, then I feel content and even more motivated to perform. At the end of the day, as <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> put it, <a href="https://medium.com/@johnpcutler/15-things-you-should-know-about-product-managers-f488513d246">‘Product Managers are the canary in the coalmine’</a>. They’ll be the first ones to spot organizational dysfunctions and if you manage to keep them happy, you’re half-way there.</p><p><em>Note: I am in no way associated with or promoting ConfidenceConf, just wanted to share the report properly with all credit where credit is due :)</em></p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d234bd765e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-do-you-keep-product-managers-happy-6d234bd765e1">How Do You Keep Product Managers Happy?</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mental Cost of Being a Product Manager]]></title>
            <link>https://medium.com/swlh/the-mental-cost-of-being-a-product-manager-dd64e47fc73b?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd64e47fc73b</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Tue, 27 Aug 2019 07:35:10 GMT</pubDate>
            <atom:updated>2019-11-02T14:16:13.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7xTL9XqWlvfXSVX-" /><figcaption>Photo by <a href="https://unsplash.com/@nofilter_noglory?utm_source=medium&amp;utm_medium=referral">Tim Goedhart</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve been approached a lot recently by people who want advice on how to enter Product Management. And while you can read my enthusiastic take on ‘<a href="https://medium.com/swlh/why-you-should-consider-a-career-in-product-management-6366aabfa8a6">Why You Should Consider a Career in Product Management</a>’, all of these conversations made me want to be more transparent about being a Product Manager so people really know what they are getting into. If you are considering becoming one or are still new to the Product world, keep reading. The following few points illustrate how taxing the role can be when it comes to mental health and will hopefully help you acknowledge and move past them.</p><h3>The uncertainty is overwhelming</h3><p>The reality is that as a product manager you deal with a lot of uncertainty. This is certain. But you can’t know for certain what competition is up to or where the market will be in a year; if the innovative feature you’re betting on will be adopted by users as envisioned. Yet, you’re expected to have all the answers, fast. You are expected to make well-informed decisions, even when relevant data might be missing. Given the enormous responsibility that you have to make the product successful, the pressure to not mess it up is huge. It might be tempting to wait and avoid making the necessary decisions but the pressure will still be there from all sides to provide clarity and way forward. The way to deal with it is to acknowledge you can’t always be right and that’s alright. Rely on data as much as possible, listen to and trust your team’s expertise, talk to users often and if all else fails, be grateful for this learning opportunity. Next time you’ll do it better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MZXjDxfnFI-8q_PY" /><figcaption>Photo by <a href="https://unsplash.com/@bamagal?utm_source=medium&amp;utm_medium=referral">&quot;My Life Through A Lens&quot;</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Imposter syndrome is thriving</h3><p>Congratulations, you are a generalist in a pack full of specialists. The designers, the engineers, the marketeers… they all have their specific domain skills. We are supposed to be a jack of all trades but some days we feel like we have no trade at all. The role itself still causes confusion among many colleagues and people often don’t have a clue what we do all day. Imposter syndrome is alive and thriving among Product Managers but the good news is, it does get better with time. As you pick up more and more experience, it becomes easier to see the value you bring to the table. And with that, the feeling that we’re imposters goes away. On most days.</p><h3>Context switching is a killer</h3><p>If you read enough about Product Managers you’ll soon realize one of the common ways to describe them is as multiple hat wearers (Hi, <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> 👋). It’s a fitting analogy. Juggling between different departments and their needs, and the versatility of our own role, we need to switch between contexts and embody multiple roles within a single day sometimes. That can be exhausting at best and schizophrenic at its worst. In the end, it’s part of what makes Product people so valuable in a team and can be mitigated to some extent by making sure you are laser-focused on the top priority and saying ‘No’ to all the other distractions. Which leads me to my next point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*sd2A1mdFvDhlqYcOoLvgww.jpeg" /><figcaption><a href="https://www.departmentofproduct.com/blog/apis-explained-for-product-managers/">From DepartmentOfProduct.com</a></figcaption></figure><h3>It’s isolating</h3><p>People won’t like it when you tell them ‘No’. The reality is that in order to build a successful product, you’ll need to say it a lot. Other departments might not always understand your reasoning and that won’t bring you many new friends I am afraid. Not to forget the abusive feedback you sometimes receive from some of your users. For all the empathy requirements our there, it’s really difficult to ignore the fact that sometimes you’ll need to do something users might not like (think $$$). And when they tell you so, the feeling of betrayal is real. Overall, being a Product Manager could be lonely so make some friends in your team and remember there are users who do enjoy your product after all. Just take a look at all those five-star reviews! ❤</p><p>Overall, Product Management could be stressful but it’s also incredibly rewarding. If you take good care of yourself and your mind, the stress is managed. Send me a message if you need someone to chat with.</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd64e47fc73b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-mental-cost-of-being-a-product-manager-dd64e47fc73b">The Mental Cost of Being a Product Manager</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Common Misconceptions About Data-driven Product Management]]></title>
            <link>https://medium.com/swlh/4-common-misconceptions-about-data-driven-product-management-804abacc3b04?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/804abacc3b04</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Tue, 06 Aug 2019 21:11:42 GMT</pubDate>
            <atom:updated>2019-11-02T14:16:57.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4FNGzJt7J1cJiG3V" /><figcaption>Photo by <a href="https://unsplash.com/@franki?utm_source=medium&amp;utm_medium=referral">Franki Chamaki</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Data helps us build better products. With so many companies embracing the data-driven approach to product management, I was recently reflecting on what are some of the common misconceptions about this approach. Here’s what came to mind.</p><h3>1. Qualitative data is not needed</h3><p>One of the common issues I see is product managers who don’t use qualitative data. For some reason, ‘data-driven’ is being equated to ‘using numbers’ and so the words of consumers are not seen as data, which is simply not true. By ignoring such qualitative data, product managers miss the opportunity to fully understand the emotions of consumers, the why of their behavior which in turn could help explain some of the hard data. Not to mention words create empathy, a key ingredient for any team.</p><h3>2. ‘Looking’ at data is sufficient</h3><p>Sometimes when product managers run experiments, they say they’ll look into the data. The problem is, sometimes that’s exactly what they do. They look at the numbers and make conclusions. However, that’s a wildly ineffective way to do analysis. You need to have a hypothesis and then design a way to test it while making sure the data collected is of high quality and only then start to understand the data within the framework of statistics. To not do a thorough job in the first few steps of this process is to arrive at the wrong conclusions while you analyze the data.</p><h3>3. It happens overnight</h3><p>Well, it doesn’t. One day someone says ‘We need to be more data-driven’ and from that moment on not much has changed, frankly. It takes time to build up the mindset, the analytical skills and make sure all the required infrastructure to support it is in place. Not to mention, being data-driven requires practice. You might design an inconclusive experiment, or end up snowed under so much data that analysis-paralysis takes the best of you. You’ll get better over time and that’s normal. So start now.</p><h3>4. Data is free</h3><p>I am not sure where this one comes from, to be honest, but I see many companies wanting to be data-driven and not really investing in it. Being data-driven costs money. Qualitative data requires time and money to collect it first hand from your users. Do you want product usage data? You’ll need to invest in a good product analytics tool. Not to mention, high-quality data is not something that happens by accident and designing, implementing and maintaining a robust tracking system can be difficult and expensive. Do it anyway.</p><p>At the end of the day, data will help you build a better product but it’s not a panacea. You’ll still need all the other ingredients, the most important one being the right people in your team.</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=804abacc3b04" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/4-common-misconceptions-about-data-driven-product-management-804abacc3b04">4 Common Misconceptions About Data-driven Product Management</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Possibly the Best Question to Ask in Interviews]]></title>
            <link>https://medium.com/swlh/possibly-the-best-question-to-ask-in-interviews-c4dea59910ff?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4dea59910ff</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Tue, 23 Jul 2019 14:08:38 GMT</pubDate>
            <atom:updated>2019-11-02T14:17:20.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*afNW_1Osrhcs9PIh" /><figcaption>Photo by <a href="https://unsplash.com/@emilymorter?utm_source=medium&amp;utm_medium=referral">Emily Morter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>The Best Question to Ask in Interviews</strong></h3><p>It’s hard to know if a company will be the right place for you while you’re still interviewing. Sometimes, the interviews are over, and you get the offer only to realize you are unsure. It has happened to me in the past. It just means I didn’t take the opportunity to dig deeper. Or worse, you think you have a clear picture, but once you start at the company, surprises start emerging.</p><p>To avoid this, next time you are interviewing, ask the CEO or whoever is present from the management team to answer this question:</p><blockquote>Imagine it’s two years from now. The company has failed. What went wrong?</blockquote><p>This is the classic pre-mortem question. It seems simple and it is, and at the same time, it’s an incredibly complex question. Let’s unpack it.</p><h3>Illustrates knowledge and understanding</h3><p>First, it’s essential to ask this question because it will reveal if the person answering knows the ins and outs of the business. Any business can fail for many reasons, some out of our control. But that doesn’t mean the company should not be aware of such dangers and actively work to mitigate the risk. As a leader, if you don’t know what can bring down the company, it’s hard to believe you fully understand what really brings the cash. That, in turn, signals potential strategy shortcomings. You’ve been warned.</p><h3>Highlights problematic areas</h3><p>Second, it shows you where the weak spot of this company is. Is the answer related to competition stealing their market share? Likely the company in question feels that they are not innovative enough and not able to go fast in comparison to other companies in the field. Is the answer related to the product? Culture? Costs? The answer tells you what scares the people at the top and likely will inform the strategy in the next few years. Now you know better what to expect.</p><h3>Reveals character</h3><p>Third, you can observe how your potential new leader tackles what is indeed an unexpected and tough question. Able to think on their feet? Is humble and objective enough to acknowledge failure could happen? Communicates well so even an outsider can understand the explanation quickly? The person is convincing and inspiring enough that you still want to work there even if you just heard a plausible way this company can go bankrupt? Happy to be vulnerable and open with you? Well, congratulations, they aced your challenge.</p><h3>Bonus: It boosts your position</h3><p>There is one other reason why you might want to ask this question in your interviews. Basically, it’s none of the standard questions people ask and it is a thoughtful and revealing question. Often, when I ask this question, I get the surprised look and then acknowledgment that it is an excellent question and no one else has asked this before. As a result, you stand out from the other candidates and it shows you are analytical and creative. These are all fantastic things to achieve with just one question.</p><p>Once you get the answer, don’t stop there. Keep asking thoughtful and difficult questions to fully understand if this company is the one you want to join. If you’re going after a Product role, make sure you also check out <a href="https://medium.com/u/c82d30f86a02">David E. Weekly</a>’s awesome article on <a href="https://medium.com/hackernoon/acing-your-product-manager-interview-e4f163408cef">Acing Your Product Manager Interview</a> and <a href="https://medium.com/u/99aad3e53433">Andreea Nastase</a>’s <a href="https://medium.com/@diemkay/how-i-prepared-for-a-product-manager-interview-26122f2c80ba">How I Prepared for a Product Manager Interview</a>. Good luck!</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4dea59910ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/possibly-the-best-question-to-ask-in-interviews-c4dea59910ff">Possibly the Best Question to Ask in Interviews</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Junior Product Manager…]]></title>
            <link>https://medium.com/swlh/dear-junior-product-manager-3feefb3e872f?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3feefb3e872f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 13:10:13 GMT</pubDate>
            <atom:updated>2019-11-02T14:18:10.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R_T4PEXjbTiaEWha" /></figure><p>More and more, I get to talk to people who are just entering the Product Management field, and I find myself reflecting on my early days as well. I wish someone told me a few things. If you’re also new in the Product Management role, here are some things I wish someone told me at the beginning that aren’t so obvious.</p><h3>Befriend the Engineering Manager</h3><p>Often, people who find themselves wearing the Product Manager hat end up sticking with other PMs. At best, they might cozy up with the designer on the team. Actually, it’s essential to immediately befriend the Engineering Manager (or whatever that role is called in your team) as this is the person who can help you win the team over. Once you have a good relationship with the Engineering Manager, the other developers will become more comfortable with you and will be even more willing to help you out. You can then count on the team whenever you’re not sure how to tackle something, which will be often. Trust me; you don’t want to be in a situation where you don’t have a good relationship with the Engineering Manager.</p><h3>Start writing</h3><p>Your days will be chaotic, and your tasks will be wide-ranging. Structure is your friend, but it will be hard to structure your work. It’s even harder to structure your thoughts. Do it anyway. One way to achieve some clarity and structure for yourself is to start writing. You can read about <a href="https://medium.com/the-mission/the-psychological-benefits-of-writing-regularly-307bc9825373">the benefits of writing</a> in <a href="https://medium.com/u/515997e8c7e3">Gregory Ciotti</a>’s spot-on article, but in short, it forces you to structure what’s in your head, and it will help you see things more clearly. It’s such an understated practice for PMs. You can start by writing a recap at the end of the day or simply taking more detailed notes at workshops/meetings. There are different practices you can follow; just choose what works for you.</p><h3>Make that decision</h3><p>No matter how many times you might have heard this before, you’ll still be surprised by the number of choices you’ll have to make daily. It is a significant part of your role because it helps teams to make progress. Any decision is better than no decision as they say because it’s easy to lose track and wait for the perfect amount of information to make the decision, but you lost time and likely will still not get all the information you wish you had. Instead, get comfortable with making a decision based on partial data and smart estimations and learn from the outcome. It’s sometimes cheaper and faster to make the wrong decision, learn from it, and adapt than to wait and gather all data you need for the complete analysis. I can’t stress enough how vital decisiveness is for a product manager to be successful, so here’s <a href="https://medium.com/u/7137e34bb35b">Barry Davret</a> advice on how to <a href="https://medium.com/@Barry.Davret/how-to-sharpen-your-decision-making-skills-in-ten-minutes-a-day-874ec703cdb7">start practicing decision-making now</a>.</p><p>But above all, if you are new to Product Management, don’t stress too much, you’ll do just fine. Enjoy!</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3feefb3e872f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/dear-junior-product-manager-3feefb3e872f">Dear Junior Product Manager…</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Should Consider a Career in Product Management]]></title>
            <link>https://medium.com/swlh/why-you-should-consider-a-career-in-product-management-6366aabfa8a6?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6366aabfa8a6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-paths]]></category>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 14:46:49 GMT</pubDate>
            <atom:updated>2019-11-02T14:18:52.055Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zKYY3-rTaQou7B4I" /><figcaption>Photo by <a href="https://unsplash.com/@gautamlakum?utm_source=medium&amp;utm_medium=referral">Gautam Lakum</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve recently talked to a few people who are considering a career in Product Management. It was a very insightful and enriching experience for me to say the least, and I felt the need to structure a little my advice and make it more accessible. If you are also a fresh graduate or someone looking to switch careers, keep reading. A few years ago, I was in the same situation. After more than four years in the field, here is why I think a career in Product Management should be high on your list.</p><h3>It’s flexible.</h3><p>And I don’t just mean in terms of work-life balance. Yes, you can work remotely and from your own home. You can also choose whether you prefer a corporation, a startup, or maybe you want to freelance. Relocating abroad is also a possibility. In short, you have options, and so you can indeed find what fits best your desired lifestyle. Product Management gives you that flexibility.</p><p>But what is uplifting is that as a Product Manager, you get the ultimate flexibility — you get to define your role. It’s expected of you to come up with your backlog of things and then to prioritize it. Because the role itself is different from organization to organization, there are plenty of Product Management flavors out there. <a href="https://medium.com/u/bfaac52feb9d">Lucas Didier</a>’s aptly named article <a href="https://medium.com/mozza-io/the-99-types-of-product-managers-3b6dabe92a25">The 99 Types of Product Managers</a> is an eye-opener. You get the point.</p><h3>You’ll learn a lot</h3><p>Being a Product Manager, one thing that I am grateful for is the endless learning opportunities. Product Managers get to collaborate with several other roles daily, and while challenging, this also means we get to learn tons of new things all the time. Think engineering, design, research, marketing, sales, support. Overall, the variety of domain knowledge you’ll acquire in the Product Manager role is indeed remarkable.</p><p>Besides, you’ll hone quite a few soft skills as well. You’ll become a better leader. Your communication skills will improve. You’ll get more comfortable with making decisions since you’ll have to make a few every hour. You’ll sharpen your problem-solving and collaboration skills since that’s pretty much the essence of your role. All these easily come handy also outside of the office. Think about it; it’s a robust skillset to have.</p><h3>No need for a specific degree</h3><p>I spent a few years working in Research and Strategy before I realized it’s not a fit. I thought I need to spend time and money for another degree so I can switch career paths. Not so fast. Product management does not require a specific degree. It’s inspiring to see how people from very diverse backgrounds such as <a href="https://blog.usejournal.com/software-engineer-to-product-manager-5d1eddaa3678">Engineering</a>, <a href="https://medium.com/pathtoproduct/from-designer-to-product-manager-1fcb1acdea7e">Design</a>, <a href="https://medium.com/pmlesson/analyst-to-product-manager-emma-yee-senior-data-pm-goodrx-d0b2ed6f27b7">Data Science</a>, and <a href="https://uxdesign.cc/from-subway-sandwich-artist-to-facebook-product-manager-e425aae34f4e">more</a> end up in a product role. You can do it too.</p><p>To get your first job in Product Management, you’d still need to demonstrate several skills, though. <a href="https://medium.com/u/438402a57690">Brent Tworetzky</a> did a thorough job at listing these skills in his brilliant article <a href="https://medium.com/pminsider/product-manager-skills-by-seniority-level-a-deep-breakdown-cd0690f76d10">Product Manager Skills By Seniority Level — A Deep Breakdown</a>. The good news is that some of these skills you might already have. The reality is that as long as you have the right mindset and soft skills, you can learn all of the rest pretty fast on the job from your team, your fellow Product managers, mentors.</p><h3>It’s rewarding</h3><p>Hands down the most crucial reason why you should consider becoming a product manager is it’s utterly satisfying. It’s currently in demand, and so it’s well-paid, plus you have a rapid career progression unless you go to one of the multinational companies. Not to mention, due to the nature of the role, you get exposure to top management all the time, which has its perks.</p><p>But that’s only a part of the story. What is truly rewarding is observing how a user interacts with your creation, and you realize you’ve solved one of their problems. Whether it’s helping them do something faster, cheaper, in a more convenient way, or it’s a ground-breaking one-of-a-kind innovation, you helped create something that had a positive impact on someone’s life. The better you get at product management, the more often you get to experience this. It’s addictive.</p><h3>Beware the cost</h3><p>If I convinced you and you’re already browsing PM jobs, that’s great, but please stay with me for a little longer. While I love my role, and it’s the only one I can imagine myself doing with a smile, many of my fellow Product friends will agree that mentally, it’s a very demanding role. You can read my honest take in <a href="https://medium.com/swlh/the-mental-cost-of-being-a-product-manager-dd64e47fc73b">The Mental Cost of Being a Product Manager</a> and also make sure to <a href="https://medium.com/@johnpcutler/15-things-you-should-know-about-product-managers-f488513d246">check out this brilliant article</a> by <a href="https://medium.com/u/4c3f4fe11e6b">John Cutler</a> on some of the challenges you’ll face.</p><h3>Be honest</h3><p>While all this could sound very compelling, you have to be honest with yourself. This role, just like any other, is all about personal fit. If you’re looking for a well-defined, structured role with little uncertainty and no improvisation required, if you prefer to work alone, then product management is not for you. There are plenty of other excellent roles that would fit, keep looking.</p><p>Good luck!</p><p><strong>Let’s be friends! </strong><a href="https://medium.com/@lilly.dobreva"><strong>Follow me</strong></a><strong> on Medium for more articles on product management and startups.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6366aabfa8a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/why-you-should-consider-a-career-in-product-management-6366aabfa8a6">Why You Should Consider a Career in Product Management</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Books That Most Influenced My Product Career]]></title>
            <link>https://medium.com/series/books-that-most-influenced-my-product-career-e1ba11935c9b?source=rss-1fb8c89bd9e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1ba11935c9b</guid>
            <dc:creator><![CDATA[Lilly M. Dobreva]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 08:13:36 GMT</pubDate>
            <atom:updated>2019-06-22T12:34:54.980Z</atom:updated>
            <content:encoded><![CDATA[<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1ba11935c9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>