<?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 Anastasia Shakhaeva on Medium]]></title>
        <description><![CDATA[Stories by Anastasia Shakhaeva on Medium]]></description>
        <link>https://medium.com/@ashakhaeva?source=rss-f6b6e420aad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oL3psQYqzHHdQ3GlHQzVQA.jpeg</url>
            <title>Stories by Anastasia Shakhaeva on Medium</title>
            <link>https://medium.com/@ashakhaeva?source=rss-f6b6e420aad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:50:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashakhaeva/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[9 ways that being a client success manager made me a better product manager]]></title>
            <link>https://medium.com/agileinsider/9-ways-that-being-a-client-success-manager-made-me-a-better-product-manager-e19abb9d871e?source=rss-f6b6e420aad------2</link>
            <guid isPermaLink="false">https://medium.com/p/e19abb9d871e</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Anastasia Shakhaeva]]></dc:creator>
            <pubDate>Fri, 02 Jun 2017 14:15:00 GMT</pubDate>
            <atom:updated>2019-06-11T15:42:04.414Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZf0-0V6bkxd8iD-SVbKPA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ptrikutam">Pavan Trikutam</a></figcaption></figure><p><em>Lessons from a client success role, and how they translate into product management .</em></p><p>Today I am a product manager at Zoon.ru, a website that helps consumers find the best local businesses and service providers, and I couldn’t<strong> </strong>have landed this role without first gaining experience in client success. It’s common to hear about people transitioning to PM roles from marketing, design, and development, so I think it’s about time we talked about transitioning to product management from a customer support role. So here is my story: the lessons from my journey and the reasons I think there should be more people with my background in product management.</p><p>About 3 years ago I was working at a movie streaming company with the title of User Experience Manager and a role similar to that of a client success manager. The position meant being the advocate for user needs inside the company and supporting the users through various channels — email, phone, social networks, in-person interviews.</p><p>I was genuinely good at talking to customers, I could find a way to talk to anyone and get to the root of the problem, and make sure that even if we couldn’t fix the experience with the product the user knew that we cared and were doing everything in order to not make the same mistakes again. There were times when I asked our users to help us figure out what was going on with the product and test something, and convince them to help us time and time again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*VdmoQCwUm89OohVOcaQ9SA.gif" /></figure><p>I once spent an hour on the phone explaining step-by-step to a user how to pay for a movie and start watching it on a Smart TV. He told me he was old and it was hard for him, but he genuinely wanted to. From a purely business and profitability standpoint, one might have argued that this was not the most productive thing I could have done with that hour. <strong>But by taking the time to co-experience onboarding with the client, me and the whole team that witnessed it developed empathy for our users’ struggles.</strong></p><p>Helping people felt good, but I wanted to have more of an impact. I wanted to make it so that users stopped needing my help in the first place.</p><p>The goal set for me at the time was to create an efficient customer support system. As I was gathering the issues that users experienced, testing and categorizing them, it became clear that we did not need better support — we needed to make changes to the product.</p><p>That’s how I gained my first product experience. I went over the issues that I found and came up with a a big redesign of the Help section which we turned into a FAQ section and a few minor tweaks in product that would help the user contextually. I worked closely with our designer and developers. It was incredibly difficult but it also felt good. After the update, user inquiries reduced by about 50%, and I was absolutely ecstatic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*lpomychrWSCHjeo74nGcow.gif" /></figure><p>Fast forward and I see the posting for a PM position with Sports.ru (one of the biggest Russian-speaking sports media). The description seemed perfect — it was exactly what I wanted to do. On my application, I highlighted the experiences I had that were relevant to product management. That got me in the door. During the interview, I focused on how, through my daily interactions with users, I had already been doing key product management functions throughout my career. I guess, that was what got me the job.</p><p>My client success experience continued and continues to help me every day on the job. That’s not to say that I wouldn’t benefit from being more proficient in engineering or design, but here are 9 ways that my client success background helps me every day:</p><ol><li><strong>Empathy</strong>. The core of the CS job is to help the user and make her happy. It can’t be done without empathy. And good products can’t be created without understanding user needs. Feeling the pain is paramount.</li><li><strong>Advocacy.</strong> As a client success manager, you are far from a position of power or authority. I had to learn to advocate for change anyway, and that’s really applicable to product managers who find that they need to lead via influence instead of authority.</li><li><strong>Communication.</strong> Both customer support managers and product managers must communicate and collaborate all the time: explaining time and time again to different audiences, listening to the stakeholders, and getting to the root of their needs.</li><li><strong>Problem solving.</strong> Despite being an overused cliche during interviews, problem-solving is a critical skill to develop. It’s also pretty much the central focus of customer support and success, and is a daily aspect of product management.</li><li><strong>Learning.</strong> Accumulating information and building your knowledge base is central to client success — you can’t be caught on the phone with a user and not have the answer to their question. Similarly, the PM has to do the same. And not only accumulate that information but also leverage it to solve problems, plan ahead, and make decisions.</li><li><strong>No bullshit.</strong> When a user says something that doesn’t make sense or looks like a lie, believe it or not, it in fact may be a lie! I’m not saying that the users are untrustworthy, but they are people who make mistakes and sometimes they may say untrue things, or you may interpret what they say in the completely wrong way. The same goes for all people, including teammates. And that makes you learn to ask the questions: Why? And how so?</li><li><strong>Open-mindedness.</strong> With a CSM background, you don’t know what the perfect engineering or design solution looks like. And that is a good thing. Because CSMs primarily focus on the problem space rather than the solution space, they become product managers that are totally open to suggestions and new ideas.</li><li><strong>Saying no.</strong> In customer support, it’s important to understand that we cannot satisfy all user cravings. We learn to recognize when a user is asking way too much. And we learn how to say no clearly but without offending them. As the saying goes: the most important thing is not to know what to build, but to know what not to build.</li><li><strong>Resilience.</strong> It gets harder to stay strong and face criticism when you transition to product management, but you get a lot of experience doing it as a CSM. Rather than answering for a product someone else built, you’re now answering for something you did. As a customer support manager and as a PM you learn to differentiate between pain-inflicted feedback that you need to empathize with and the <em>haters gonna hate</em> feedback that you ignore. You learn not to take it personally. You feel pain and learn to turn it into fuel for change.</li></ol><p>It’s been two years since I transitioned into product management, and still not a day goes by where I don’t lean on my client success skillset. I believe that considering product managers from diverse backgrounds, among them customer success, is paramount for organizations that want to build a solid and balanced product team. And if you’re someone with a client success background and are interested in product management, know that you’re not far away. And every day in client success is incredibly valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zrSVkdjp1nTpVYwLQu7zdw.gif" /></figure><figure><a href="https://productmanagementinsider.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/531/1*yPRWnRlzXXe8hWuwg2xETA.png" /></a></figure><figure><a href="https://alphahq.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*d6feM7YM9xI2c0CPC8XhSA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e19abb9d871e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/9-ways-that-being-a-client-success-manager-made-me-a-better-product-manager-e19abb9d871e">9 ways that being a client success manager made me a better product manager</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a real PM: overcoming the pressure of unrealistic standards]]></title>
            <link>https://medium.com/agileinsider/becoming-a-real-pm-overcoming-the-pressure-of-unrealistic-standards-83a6084d4759?source=rss-f6b6e420aad------2</link>
            <guid isPermaLink="false">https://medium.com/p/83a6084d4759</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Anastasia Shakhaeva]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 11:31:31 GMT</pubDate>
            <atom:updated>2019-06-11T16:01:14.714Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zkF6dD9h278oCM6L5KbGw.jpeg" /><figcaption>Photo by Crason Arias</figcaption></figure><p>There’s a certain image in the media of what a Product Manager should look like, how they should behave, and what they should believe in. Similar to the way fashion magazines represent a retouched and unrealistic image of men and women, Medium posts about product management seem to translate a perfect and unattainable image of what our jobs and our products are. And since it’s not Vogue, but a free space where everyone can have a voice, we tend to stop critically evaluating the image of the PM and lose our grip on reality. While it’s helpful to familiarize ourselves with and try to incorporate best practices, they shouldn’t give us misconceptions about the realities of the job and our performances.</p><h3>Product management is not as glossy as the image, kind of like life in general</h3><p>Here is a list of some of the urban legends that drive me crazy and how they compare to reality.</p><p><strong>Legend #1:</strong> Tests always give results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*IBAGdqBsobBNqOmTplb-2Q.jpeg" /></figure><p><strong>Reality</strong>: Tests give statistically significant results about <a href="https://hbr.org/2014/12/yes-ab-testing-is-still-necessary">1 in 10 times</a>. The data-driven test-based approach cultivated by Netflix and other great companies is amazing and useful, but tests are not the magic bullet.</p><p><strong>Legend #2: </strong>A single keyword change will skyrocket app search rankings overnight<br><strong>Reality</strong>: Changes in App Store keywords or Google Play descriptions do impact the position of your app, but not immediately. Most of the time you won’t see much difference. The overnight success stories just lead to more survivorship bias.</p><p><strong>Legend #3:</strong> The users always give actionable feedback, and you always know why a user behaves the way she does.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*R3Cs0jupPk91qNanMQUE-Q.gif" /></figure><p><strong>Reality:</strong> About half the time, user feedback doesn’t even make sense. Sometimes they confuse products and companies, sometimes they describe how they use the features that aren’t even there, and sometimes their syntax prevents you from understanding their message. Some feedback is useless and that’s okay. In the real world you can’t always immediately make sense of why the users behave the way they do, why they use your product in certain ways, and why the data seems crazy.</p><p><strong>Legend #4:</strong> You’ll always have all the data you need, and decisions will therefore be obvious.<br><strong>Reality</strong>: More often than not, when you get together user feedback, business requirements and analyze the data, you end up with conflicting sets of data and few legitimate solutions to a problem you’re no longer sure is even real. Even when the data is adequate, you’re never sure what the best solution is.</p><p><strong>Legend #5:</strong> The main task of a PM is to generate ideas. Literally, to just sit there and come up with stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*mt4PdNQTNgeysesio__fTg.jpeg" /></figure><p><strong>Reality:</strong> Generating ideas is basically an activity to be done in the shower. The core job (read: the other 99% of the time) involves reacting to problems ranging from “how do we reach these users?” to “sales are declining — why and what do we do?” to “shall we hide this part of the form to decrease the cognitive load?” But having the solution isn’t enough, as the PM also must support the dev/design/marketing/sales/editorial team.</p><p><strong>Legend #6:</strong> The PM is the CEO of the product, so when she presents a new product or feature to the team, everyone excitedly goes: “OMG that’s genius, let’s get to it right away!”<br><strong>Reality</strong>: When a PM presents her ideas to the team, typically the reactions range from “well, that’s not total bullshit” down to opinions regarding why there’s no problem worth solving in the first place.</p><p><strong>Legend #7:</strong> A PM always has clear KPIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2L76cy654yKQdZAMmbWehg.gif" /></figure><p><strong>Reality</strong>: When you interview for a PM role and ask about the KPIs, few companies will provide exact metrics. Others will say something like “the performance of the product is important,” while the rest will admit they don’t have any at all.</p><p><strong>Legend #8:</strong> Everything goes according to plan. You just set the roadmap and follow it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*rkGOiyyGmmHcT55fwjZwiQ.gif" /></figure><p><strong>Reality</strong>: New technologies bring new opportunities and mess up the roadmap. Products underperform and get killed. New laws are passed. The CEO is fired and the new one has totally different mantras. Life happens: people get sick, make mistakes, and even leave.</p><p><strong>Legend #9</strong>: Everyone knows the product you work on. So when you tell it to someone new they ecstatically go: “OMG, I love [insert company name]. They are so cool!”<br><strong>Reality</strong>: There’s not just Apple, Google, Facebook and about 30 world’s largest companies + 10 or so local companies that people work for. There are many more. Many of them are B2B. So it’s only natural that when you tell people you work for company X on product Y they would go: “Huh? Never heard of it.”</p><p><strong>Legend #10:</strong> Your products are magical and amazingly innovative. And boy have you ever seen user retention be this high?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zQsO8hjpSYNlfYb-iVHETQ.gif" /></figure><p><strong>Reality</strong>: Not all products are created equally sexy. And most of the time, you aren’t really innovating. From time to time, you need to kill your product or features, because they underperform. But as long a you keep them real helpful to users and business you are doing a great job.</p><h3>It’s time to embrace reality</h3><p>So where do we go from here? When we’re out of pixie PM dust and there’s no unicorn in sight, all we’re left with seems to be an uncontrollable chaos that’s not so glamorous after all. The idea is to make sense and build tiny bits of order out of that chaos. To solve real problems for real users and real businesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*lrc-yBZXqW0J3KSw7uvicA.gif" /></figure><p>The only way to live your true and authentic PM self is to first embrace reality and attainable expectations. Let go of detrimental perfectionism, embrace impostor syndrome, welcome the uncertainty of everything. Pray to common sense, make fun of bullshitters, ruthlessly cut to the point. Trust your teammates, see business values and priorities clearly, challenge the status quo. Give straight feedback and welcome honest opinions. Do what makes sense, not what is fancy. Kill what’s no longer useful.</p><p>The fairy tales are all good and fun and important to read for self-development and stuff, but the real thing is better. Do more of what makes you real. Afterall <a href="http://mashable.com/2017/02/09/march-american-vogue-cover-embraces-diversity/#V3eCEHxMemqN">even Vogue is headed that way</a>.</p><figure><a href="https://productmanagementinsider.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/531/1*yPRWnRlzXXe8hWuwg2xETA.png" /></a></figure><figure><a href="https://alphahq.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*d6feM7YM9xI2c0CPC8XhSA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83a6084d4759" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/becoming-a-real-pm-overcoming-the-pressure-of-unrealistic-standards-83a6084d4759">Becoming a real PM: overcoming the pressure of unrealistic standards</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>