<?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 Samia Suys on Medium]]></title>
        <description><![CDATA[Stories by Samia Suys on Medium]]></description>
        <link>https://medium.com/@samiasuys?source=rss-bd5280386875------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MSFyKNtrD9AqQ6Ng0nV2WQ.jpeg</url>
            <title>Stories by Samia Suys on Medium</title>
            <link>https://medium.com/@samiasuys?source=rss-bd5280386875------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:11:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samiasuys/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[I’m Coming Out ️]]></title>
            <link>https://medium.com/swlh/im-coming-out-%EF%B8%8F-250d1c0e70ca?source=rss-bd5280386875------2</link>
            <guid isPermaLink="false">https://medium.com/p/250d1c0e70ca</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[feminism]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Samia Suys]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 13:21:13 GMT</pubDate>
            <atom:updated>2022-03-14T13:21:13.783Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*r0JYcgHtCC8FMSBjRGpwjQ.jpeg" /></figure><h4>Confession of a female product leader in tech</h4><p>Suppose I asked you to take a moment and think about the word ‘feminist.’ What would come to mind? If you’d asked my teenage self this very question, she would come up with many things. Like angry, man-hater, sloppy…Dramatic, perhaps. Throw in some sandals, and that’s pretty much how I envisioned a feminist. Somehow someway feminism has long had a negative connotation in my book. Being a feminist wasn’t something I aspired to be.</p><p>Things started to turn as little baby me set foot in the business world. “Remember,” said the fiercest female leader I ever had the privilege of working with, “nice girls don’t get the corner office.”</p><p>Honestly, I was too young at the time to truly grasp what she meant and where that came from. But over the years, I hit replay on that quote many a time. Once, I was just about to present a product strategy to a room chock-full of people. There I was, minding my own business, drinking a glass of water at the bar to get ready. A man came up to me and said, “I’ll have a coffee.” My spontaneous reaction was to laugh. Because this dude had to be kidding, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yPe9xp-GYL_sZuGD" /><figcaption>Photo by <a href="https://unsplash.com/@minimalattitude?utm_source=medium&amp;utm_medium=referral">Alberto Bogo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Check again, please.</p><p>He wasn’t.</p><p>Ouch.</p><p>You see, the thing with bias and sexism is that it’s hushed sometimes. And excruciatingly loud at others. It’s there when you assume “the doctor” is a man, or “the secretary” is a woman. It’s there when your male colleague says, “she must be on her period; she’s so cranky.” (By the way, it would be perfectly fine if she were, that s#!t would make anyone cranky.) It’s there when a man applies for a job he’s only 70% qualified for, and a woman only does so when she’s at least 100% qualified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*qBvNX5WTMy6tBnqg8jHx7w.jpeg" /></figure><p>Shortly after the coffee incident, I started to lean into feminism. I filled my bookcase with Roxane Gay, Chimamanda Ngozi Adichie, and Bernardine Evaristo (to name a few). I became more attentive to subtle and not-so-subtle displays of gender bias. I learned that feminism has been poorly marketed. That it comes in many shapes and colors. That everyone, across the entire gender spectrum, should be a feminist. And that, yes, (some) feminists are angry. And that’s a good thing. Chimamanda Ngozi Adichie splendidly explains why:</p><blockquote><em>“I am angry. We should all be angry. Anger has a long history of bringing about positive change.”</em></blockquote><p>I am a woman working in tech. Over the last decade, my colleagues, and especially leadership, have been mostly men. I’m lucky enough to have parents who raised me to believe I can be anything I want to be. Because if I had just looked around over the past 10 years, I wouldn’t have thought I could become a leader in tech.</p><p>Today I am a woman. Working as a leader in tech. It’s been a wild ride so far, and I’m sure it will continue to be. More on that later. I can’t give it all away at once.</p><p>Am I only defined by my womanhood? Of course not. Do I find myself being anti-woman at times? Girl. Nobody’s perfect, so yes. Do I refrain from singing along to songs because the lyrics are questionable at best? Also no. Sometimes the rhythm is just bound to get you. I’m a multifaceted person. But damn it, being a woman is an essential part of who I am. And that deserves to be highlighted.</p><p>So. Here I am. Officially coming out.</p><p>I’m a feminist.</p><p>And a proud one at that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=250d1c0e70ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/im-coming-out-%EF%B8%8F-250d1c0e70ca">I’m Coming Out 🗣️</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 Quirky Guide To Becoming A Product Person By Getting All The Words Right — Pt. 1]]></title>
            <link>https://medium.com/@samiasuys/a-quirky-guide-to-becoming-a-product-person-by-getting-all-the-words-right-pt-1-6c89691fb997?source=rss-bd5280386875------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c89691fb997</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[vocabulary]]></category>
            <dc:creator><![CDATA[Samia Suys]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 10:18:23 GMT</pubDate>
            <atom:updated>2020-01-20T10:18:23.547Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDCnUsCZ8s8OOWJwX2BCNA.jpeg" /></figure><h3><strong>A Quirky Guide To Becoming A Product Person By Getting All The Words Right — Pt. 1</strong></h3><h4>Not your average lexicon of commonly (mis)used jargon in the tech world</h4><p>“How do I become a Product Manager? Product Analyst? Or any kind of person involved in everything that surrounds making a product but not, you know, actually making it?”</p><p>The million dollar question that tends to pop up on forums, social media and in MeetUps.</p><p>I contemplated writing a half-smart and sophisticated answer after the last time I heard it. One that builds on <a href="https://medium.com/@sebastienphl/my-product-management-reading-list-2017-cb874975c635">books and articles to read</a>, <a href="https://www.mindtheproduct.com/how-do-you-become-a-product-manager/">courses to follow</a> and people to befriend. But I figured there’s already <strong>a lot</strong> of content doing that. And secondly: it seemed a tad dull to write and I’m in a lively mood.</p><p>So I decided to take a different approach. I took a moment to assess how I and people in my network managed to end up — and stay — in the field as some kind of product person. It seems to boil down to a few things:</p><ul><li><strong>Mindset &amp; Attitude</strong>— The most important element <em>by far</em>, in my opinion. One you cannot learn from a book, mentor or course. Being in Product takes a certain <em>je-ne-sais-quoi</em>. And I’m not talking about working your a$$ off 24/7. I’m talking about being obsessed with the “why” of things. About relentlessly chasing vision. Ceaselessly striving for improvement. I’m talking about resilience. The willingness (and ability) to constantly fail, try again, fail again etc. until you kinda sorta get it right. It’s a bumpy ride, and it’s not for everyone. Some days I’m not even sure it’s for me.</li><li><strong>Knowledge</strong> <strong>&amp; Skills </strong>— Obviously you’ll need <em>some</em> kind of knowledge and skills in your rucksack. Like it or not, investing time in reading books and blogs and following a few courses or workshops will be an important part of your journey. On this note I’m personally a huge fan of looking beyond the most obvious resources like <a href="https://svpg.com/inspired-how-to-create-products-customers-love/">Inspired</a>, <a href="https://www.nirandfar.com/hooked/">Hooked</a>, <a href="http://leanuxbook.com/">Lean UX</a>, <a href="https://www.mindtheproduct.com/">Mind The Product</a>, <a href="https://svpg.com/">Silicon Valley Product Group</a>…They are priceless, for sure. But venture further as well. Look for inspiration in unlikely places. Like sports, cooking, travelling…Whatever makes your heart grow fonder! Perspective keeps you sharp.</li><li><strong>Alignment of the stars </strong>— The truth and nothing but the truth: you’ll need a portion of luck. You’ll need for someone to acknowledge the potential wafting from your pores and give you an opportunity. Once it arises, grab it with both hands and make the most of it.</li><li><strong>Vocabulary </strong>— I’m almost literally deadly allergic to name and term dropping. If anyone tries to pull this baloney on me, I’ll end the conversation as prematurely as humanly possible. All of the sudden my grandma’s dog will be really ill or my neighbour will have fallen off the stairs. Be that as it may... If you wish to survive in the tech world, you’ll have to pick up at least some of the lingo.</li></ul><p>In the first team meeting I ever attended with my new software colleagues, I legit felt like Homer Simpson. Below is an exact image of what was going on in my head. (And some days it still is.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*i4taQ-6EtBV9tzy_Om8PXA.gif" /></figure><p>I’d hate for you to have to go through the same ordeal. That’s why I scribbled down this post. It’s the beginning of a series that will portray my take on frequently (mis)used terms you need to know as a Product Person to survive in the tech world.</p><p>Read. Weep. Curse. Laugh. Share. Add more terms in the comments to include in a next story…Whatever suits you.</p><p>I decided that two of the buzziest of buzzwords would be a good place to start. Let’s go!</p><h4><strong>Agile [ aj-<em>uh</em>l, -ahyl ]</strong></h4><p>This must really be the mother of all tech fuzzwords. If your development is not agile, you’re pretty much doing a shitty job and you’d be better off in a bottomless black hole. But what on earth does it mean?</p><p><strong><em>What the dictionary says</em></strong><em><br></em>Able to move quickly and easily.</p><p><strong><em>What it means in a software context</em></strong><em><br></em>In 2001 a group of software guys had a couple of beers together. They figured the way people were making software at the time was too slow, too bureaucratic and too rigid. So they came up with a set of principles that could improve the way software was made and jotted down the <a href="https://agilemanifesto.org/">agile manifesto</a>. The gist of it? People over process. Working software over documentation. Being willing to take the reality as it comes rather than rigidly following a plan. So basically, being as agile as the dragonfly as your core working ethics.</p><p>A <em>ton</em> of money has been made on the concept of “agile”. There’s books, certificates, workshops, full-blown courses, coaches…The whole shebang. But. As always, there’s theory. And then there’s practice and reality.</p><p><strong><em>How people are actually using it<br></em></strong>As stated earlier, agile is one of the greatest buzzwords of this time. Almost every development team will tell you they’re agile. The sad thing is: a lot of them are talking the talk but not walking the walk. It seems to me that agile is, in some (or many?) cases, being used as an excuse for not dealing with organisational chaos.</p><p>Under the pretext of ‘self-steering teams’ I’ve seen a total lack of alignment arise between squads, resulting in — amongst others — the same work being done twice (and then having to undo it, of course).</p><p>While pleading for people over process, I’ve seen hours of recurring meetings being organised because the text book says so.</p><p>I’ve seen people work on Wiki pages and user stories for 8 hours a day, every day, whilst advocating for working software over documentation.</p><p>Don’t be tricked into succumbing to the same temptation of using agile as a cover-up for things that are just not right. If you want to take home one learning about agile, let it be this: agile — as I see it — is above all, about flexibility. Being in touch with reality and working <em>with</em> it (not <em>against</em> it) in order to move ahead at the best possible pace in your particular situation. Agile is not a rigid process and it’s not a one-size-fits-all.</p><h4>User Experience (UX) [ <strong>yoo</strong>-zer ik-<strong>speer</strong>-ee-<em>uh</em>ns ]</h4><p><a href="https://jnd.org/">Donald Norman</a>, the godfather of UX, universalised this term towards the end of the 20th century. Since then it has become more popular by the day, meaning that it has obviously been misused a lot. Let’s try to clear the air.</p><p><a href="https://www.nngroup.com/articles/definition-user-experience/"><strong><em>What the definition says</em></strong></a><strong><em><br></em></strong>User experience encompasses <em>all</em> aspects of the end-user’s interaction with the company, its services, and its products.</p><p>It’s basically everything you — as a user — experience/feel/think while interacting with a product. All the yays, and all the yikes. If you work in product, you’ll probably want to strive for <em>good</em> user experience.</p><p>What makes for good experience, you ask? It depends ;-) On your users (duh), what you are trying to accomplish with your product and many other factors. However, if you want some kind of guidance, have a look at Peter Morville’s “<a href="http://semanticstudios.com/user_experience_design/">User Experience Honeycomb</a>”. It’s one of many tools that breaks down the various aspects of a good user experience. Even though it’s older than Beyoncé’s hit song “<a href="https://www.youtube.com/watch?v=Q1dUDzBdnmI">Check On It</a>” it’s still relevant today.</p><p>What makes for a bad experience? Look around! Erroneous experiences are e.v.e.r.y.w.h.e.r.e. I personally keep a bug list of things that annoy me on a daily basis. That list is depressingly long but hey, you never know when I’ll have a chance to make it right!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*XwpOtS81v1vuG6_iDXPDFw.jpeg" /><figcaption>A water bottle designed to soak yourself upon opening</figcaption></figure><p><strong><em>What it means in a software context</em></strong></p><p>There’s a 100% chance of people around you fussing about UX when you’re working on a product in a software context. While it’s great news that UX is getting the attention it deserves, the bad news is: some folks don’t really, nope,<em> really don’t</em>, understand what it means.</p><p>They might blurt out stuff like:</p><p><em>“I don’t think the user experience of this page is any good. Let’s make that blue button yellow.”</em></p><p>Or:</p><p><em>“We need to focus on usability this year. Let’s hire a UI designer.”</em></p><p>If you hear anything along these lines, you should either:</p><ul><li>Run, Forrest. Run</li></ul><p><em>Or</em></p><ul><li>Set them straight</li></ul><p>The field of UX actually consists of multiple working areas, and design is nothing more or less than merely one of them. Shocking, right?!</p><p>You see, before you (or anyone, for that matter) can even start <em>thinking</em> about design in its strictest meaning, there’s a bunch of other UX work that needs to be done. There’s no escaping it, for real! If you want to know more about the different working areas in UX, different UX processes, elements of UX, etc. I highly recommend subscribing to the <a href="https://uxdesign.cc/">UX Collective</a>. That’ll quench your knowledge thirst.</p><p>But I’m trying to be concise here. And the way I see it, there’s *just* one teeny tiny but sorta quintessential thing that needs to be done before you start designing your interface, interaction, or whatever. Are you ready to find out?</p><p>Wait for it.</p><p>Wait some more.</p><p>You have to get to know your (potential) end users.</p><p>Oh my! Mind = blown. Eyes are opened. Epiphanies are had.</p><p>It seems so darn trivial and yet there’s people out there forgetting this on the daily. If you want to offer a good user experience, you have to dig b@lls-deep into the needs, wants, likes and dislikes of the people that will potentially be (or already are) using your product, guys! This means you’ll have to walk out your door and go <em>talk</em> to people. Like, really talk to them. Observe them. Get to know them. However scary that may seem.</p><p>Only when you have a good feeling of who these people are, can you start working on flows, scenarios, wireframes, mockups, prototypes and other fancy stuff.</p><p>And don’t forget to never. Ever. Assume that you <em>are</em> the user. For you are <em>not</em>.</p><p>Good luck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c89691fb997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 911. — Hi, Uhm…Who’s Calling the Shots?]]></title>
            <link>https://medium.com/swlh/product-management-911-hi-uhm-whos-calling-the-shots-a309feb96b07?source=rss-bd5280386875------2</link>
            <guid isPermaLink="false">https://medium.com/p/a309feb96b07</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[women-in-product]]></category>
            <category><![CDATA[women-in-business]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Samia Suys]]></dc:creator>
            <pubDate>Wed, 27 Nov 2019 12:40:13 GMT</pubDate>
            <atom:updated>2019-11-28T12:21:30.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozTj8Ckob1hbLa_z2SkU7g.jpeg" /></figure><h3>Product Management 911 — Hi, Uhm…Who’s Calling the Shots?</h3><h4>An anthology of painful truths (and how to cope)</h4><h4>Rookie mistakes</h4><p>As with many Product Managers I know, the job was handed to me like a hot potato on a burning silver platter. By lack of other volunteers. By accident. And with little context. Moreover, I had just rolled into the tech world at the time. So obviously, I had no leads on what to think, feel and do. And then I stumbled upon Horowitz’ <a href="https://a16z.com/2012/06/15/good-product-managerbad-product-manager/">Good Product Manager/Bad Product Manager</a> article.</p><p>The infamous CEO phrase,</p><blockquote>a good product manager is the CEO of the product</blockquote><p>immediately got to me. I vividly remember a sudden feeling of pride and empowerment rushing through my veins when I read it…I was going to change the world!</p><p>If I could meet “past” me now, I’d slap her in the face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G4mLg_7-9yyWmcMT" /><figcaption>Woman slapping other woman</figcaption></figure><p>Because it wasn’t long before I started to struggle with empowerment, responsibility, authority and decision making (or the lack thereof). And thus came the inevitable black day when I found out that…well, <a href="https://www.mindtheproduct.com/product-managers-not-ceo-anything/">Product Managers are not the CEO of anything</a>.</p><p>I felt awfully forlorn when this hit me. Lied to. At loss. How was I supposed to change the world when I didn’t have the mandate to actually do so?</p><p>This just in: it’s not easy and there’s not one answer. At all. I learned there will just always be days when you’ll seem to be shovelling a big pile of p00p from left to right. But there will always be a silver lining too.</p><p>I’ve put together a list of painful realities about empowerment in Product Management that unraveled before my weary eyes. To soften the blow, I’ve injected some silver rays of hope. Just to make sure you’re not commuting home in tears with your resignation letter in your hands after you read this.</p><h4>The house always wins</h4><p>As a Product Manager you spend all of your time working on Very Important Stuff. Talking to customers, exploring and validating brilliant (or not so brilliant) new ideas, crunching numbers of analysis reports, trying to translate what the development guys are telling you, etc…All this knowledge you gather on a daily basis puts you in the perfect position to advise the decision-makers in the building. And luckily, people acknowledge this.</p><p>Therefore they invite you at the decision-making table to present your esteemed recommendations. So when the invite comes in, you go and pour your heart and soul into crafting an inspiring and convincing exposé. You work for days and nights and then some. Until <em>finally</em> the day comes when you get to showcase this masterpiece. You seize the moment. You speak with fiery passion. You ooze pride, confidence and vision and you paint compelling pictures.</p><p>And when you’re done everyone looks at you like you’re see-through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hiGrT8C2FxCsTA1A" /><figcaption>Invisible you</figcaption></figure><p>Uncomfortable silence fills the room. After a few awkward questions and dito answers the meeting goes on. At the end of it, the C*O, VP Ninja and Something Director all agree. We’re going to do exactly the opposite of what you just presented. High fives are given, fists are bumped, great meeting everyone! Let’s go get ‘em.</p><p>What on earth just happened?</p><p>When I first experienced this kind of folly, I thought it was me. I’m a rather petite woman. I also don’t wear pencil skirts or two-piece suits. Heck, a customer once even asked me to serve him coffee at an event where I was going to be presenting the product’s strategy because he thought I was the waitress. So obviously the first thing I did was question myself.</p><p>Guess what? It wasn’t me. And it isn’t you. It’s the system, stupid. No matter how hard we work on getting the facts straight; no matter how well we empathise with our stakeholders and <em>show instead of tell…</em>at the end of the day, it’s out of our hands. The house always wins. Some days we’ll land exactly where we wanted to and others we’ll have to suck it up and get in line.</p><p>Don’t worry though. We can (and should ceaselessly strive to) change the system from within. Just keep reading.</p><h4>“He knows nothing; and he thinks he knows everything. That points clearly to a political career.”</h4><p>George B. Shaw really nailed it with this quote. It took a while for me to admit, but it actually relates quite well to Product Managers.</p><p>One of the definitions of Product Management, as spelled out by Martin Eriksson, is “the intersection between the functions business, technology and user experience”. A.k.a the Venn diagram we’ve all once used to explain what we do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*YHV7Jrf2q1zMTQr-uC7NGw.png" /><figcaption>© 2011 Martin Eriksson</figcaption></figure><p>This diagram is not telling you we are experts in all those functions. It’s telling you we deeply care about each of them. That we surround ourselves with experts in the fields we are less experienced in. And that we don’t know about all the details, but we do see the overall picture.</p><p>So…Do we know everything? If we take it literally, we don’t. But speaking for myself: I sure like to think that I do, because I get the bigger picture…You got me there, G.</p><p>And then the politics. Oh, the politics. I personally <em>loathe</em> company politics. It drives me nuts. It’s bonkers. Overhead and just plain noise if you ask me. But love it or hate it, it’s the way the world goes round. While I’ve always tried to tell myself I steer away from it, I just have to admit it woud not help my career if I actually did.</p><p>As we found out earlier, us Product Managers have very little authority. Consequently we have to rely on others to make the decisions we want them to make. So we really have no choice but to dive knee-deep in the office politics. We can’t ever overlook or bypass people. Not even if we think they’re incompetent wankers. We have to play the game and work the folks in both the formal and informal organisation charts.</p><p>This all implies that — whether we like it or not —Product Managers are politicians in many ways. Diplomats. Tacticians. Mediators.</p><p>For me this was a bitter pill to swallow. Because let’s be real: no one likes politicians. Politics (especially the office kind) are exhausting. There’s nothing sexy about it. So to unburden myself from the woes of being a politician, I try to stick to some ground rules:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzhXFnX2N76hy8fR50OTZw.jpeg" /></figure><ul><li>Put your money where your mouth is</li><li>Don’t wear a suit (it would get dirty in the trenches when you’re spending valuable time with the civilians)</li><li>Don’t call your co-workers, users, or other valuable people civilians. We’re all in this mess together</li><li>Hold on to your beliefs for dear life</li><li>Call yourself an influencer. It has a millennial ring to it, so why not?</li></ul><h4>Cloudy with a 99.9% chance of having too many cooks in the kitchen</h4><p>Product Managers come in different colours, flavours, role descriptions and even job titles. Regardless of labels, there’s one thing we all have in common: we have to ‘manage our stakeholders’. There’s a lot of <a href="https://svpg.com/stakeholder-management/">great content</a> out there describing what that means and <a href="https://www.scrum.org/resources/blog/10-tips-product-owners-stakeholder-management">how to approach it</a>.</p><p>Truth of the matter is: if you’re in any type of Product role, chances are high you’re working on something very visible. Something <em>everyone</em> cares about. Stakeholders are the ones that can make or break your work. They are the ones we should focus on, internally. So let’s definitely not stop learning how to work with and alongside your stakeholders. Otherwise we might not succeed as Product Managers.</p><p>However.</p><p>However. (It’s a BIG however so I just had to put a second one here)</p><p>What I <em>rarely </em>read about is all those other people. The ones who are not stakeholders but who <em>all</em> feel they should have a say. I’m talking e-mail threads about the shade of blue of a button in which people are added and added until the “to:” field contains more text than the body. I’m talking people spreading vague product ideas (of their own) as facts and thus causing confusion, disarray and misalignment. I’m talking meetings with 10 people in the room while there should have been 4…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*PXdPOVoxzQBpj4Ll50RQmw.jpeg" /></figure><p>At one point I’ve felt like even the office dog was meddling with my stuff. And that her smelly input was more relevant than some of the e-mails I was deleting. I mean receiving.</p><p>This stuff happens on a nearly-daily basis and it sucks. Big time. But it’s something we have to deal with. If you’re like me, you’ll have days where you just want to take your coat and leave, not wanting to deal with this cr@p. Just remember:</p><ul><li>These people, however annoying, (mostly) mean well</li><li>Step up once in a while and call an end to the never-ending e-mail thread or meeting attendee madness. We’re perfectly positioned to notice when chaos is hurting the day-to-business. Use this position to kill the chaos. Everyone, especially you, will feel better.</li><li>If people <em>keep</em> interfering with your work instead of theirs, something else might be wrong. Take a pillow, place it over your nose and mouth and shout some profanities. Then start a few conversations to see what’s going on and how you can solve it together.</li></ul><p>If all of the above fails: take your coat and leave. Tomorrow is another day.</p><p>Soooo…who is calling the shots, you ask? It depends. One thing’s for sure: some days being a Product Manager is all about sporting a pair of big balls. Other days it’s about putting your ego in the fridge and going with the flow.</p><p>To quote one of my favourite TV shows of all times: “Welcome to Product Management. It sucks. You’re gonna love it!”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a309feb96b07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/product-management-911-hi-uhm-whos-calling-the-shots-a309feb96b07">Product Management 911. — Hi, Uhm…Who’s Calling the Shots?</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 Things I Learned (The Hard Way) About Being A Product Manager]]></title>
            <link>https://medium.com/@samiasuys/4-things-i-learned-the-hard-way-about-being-a-product-manager-b6356c7839e1?source=rss-bd5280386875------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6356c7839e1</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[women-in-product]]></category>
            <dc:creator><![CDATA[Samia Suys]]></dc:creator>
            <pubDate>Mon, 30 Sep 2019 15:31:02 GMT</pubDate>
            <atom:updated>2019-10-03T22:35:05.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An astronaut floating in outer space by himself. The resemblance with Product Management is uncanny." src="https://cdn-images-1.medium.com/max/1024/0*kX1IcUsNQPSGjFCq" /><figcaption>Photo by <a href="https://unsplash.com/@nasa?utm_source=medium&amp;utm_medium=referral">NASA</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>The School of Hard Knocks is the only Product Management School that exists.</h4><h4>It’s complicated</h4><p>Being a Product Manager is challenging. For one, no one really understands what exactly it is you do. Heck, half of the time you probably don’t even get it yourself. To make matters worse, there is not one magical recipe for being a great Product Manager. Oh no. Like ice cream, Product Managers come in many different colours and flavours.</p><p>When I first got thrown into the glorious world of Product Management, I too, had no clue what I was supposed to be doing. But along the way and years I managed to get some grip.</p><p>Below are a few insights I picked up by falling down, face-first. They may seem trivial, but I sure wish someone had laid them down on me back when I was a baby PM.</p><h4>1. Making a complex product is way easier than making a simple product</h4><p>I’m sure no Product Manager <em>intends</em> to confuse and frustrate users. And yet every few milliseconds someone somewhere is cursing. Perhaps over your product.</p><p>The pressure to add nifty new features is never-ending. The customer success and support teams bombard you with requests on a daily basis. The sales team needs that one feature to sign this or that <em>huge</em> deal. The CEO saw something at a conference once and thinks it would be a great addition to your product…Adding all the features everyone (and no one) asks for makes your product become rococo, and then rubble.</p><p>You could say it’s a natural process, what with the lifecycle of a product and all. But there’s certainly a few actions you can take as a PM to slow down the rubbling. Here’s my top 3:</p><ul><li>Question every request and hold it against high standards. Is it a <em>useful </em>change or addition? Could it potentially generate profit? Will it boost customer delight? Or to put it in one simple phrase: <strong><em>does it add value</em></strong>?</li><li>Don’t be tempted to rush anything into your product. Do your homework and do it every time, no matter how high the pressure is. <em>Always</em> ask the questions no one else dares to ask or answer.</li><li>Avoid unnecessary complexity. This may seem ridiculously obvious, but it’s actually really tricky. Sometimes people may even deliberately try to complicate things, to come across as smart. Newsflash, guys: you don’t. So please, my fellow PM’s, guide your team(s) to solving problems in a way your five-year-old son or eighty-six-year-old grandma could understand. And if you’re dealing with legacy products: <em>Marie Kondo</em> that s#!t.</li></ul><h4>2. Fire-fighting is a noble job, but it’s not yours</h4><p>As a Product Manager you (should) have a broad network in your organisation. Everyone knows you, even if they don’t understand what your responsibilities are. What they do understand is that you’re super motivated and that you’re a problem solver. So it’s very likely you’ll find yourself drowning in a sea of “urgent” e-mails, phone calls or Slack messages more than once.</p><p>It’s okay to feel flattered for a bit because people know and acknowledge you. And I’ll admit that sometimes it can be useful to put on your wellies and help your teammates slog in the mud for a while, just to keep in touch with what’s happening out there. However. Don’t be tempted to let a flood of (so-called) urgencies reign your agenda.</p><p>You are the lighthouse for your product. If you don’t guide the way, or if you’re not thinking a few steps further ahead of everything and everyone else, no one else will. Your number one priority is to be on top of market evolutions and needs and to provide vision and direction for your product. Sometimes this will mean you lock yourself up to let your creative juices flow. Sometimes you’ll be in your car, on your way to a series of customer visits or an important event. Sometimes it will mean you’re in a long (and likely tedious) meeting with your internal stakeholders, convincing them you know best. And other times you’ll be explaining your troops where you want to go next and why.</p><p>Just remember to always guide the way. Believe it or not, it’s one of your most important responsibilities.</p><figure><img alt="Chicken staring into the great wide open" src="https://cdn-images-1.medium.com/max/1024/0*ns4Evokmxqj-I5MO" /><figcaption>Photo by <a href="https://unsplash.com/@tarikulxraana?utm_source=medium&amp;utm_medium=referral">Tarikul Raana</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So do yourself and your colleagues a favour and take the time to check your agenda once in a while. Take a deep hard look and ask yourself this horrifying question: am I busy working on what matters? Or am I running around like a headless chicken, unintentionally neglecting my core responsibilities? If you are, that’s ok. Just don’t stop reading quite yet. We’re getting there.</p><h4><strong>3. When all else fails, take a nap</strong></h4><p>This must be one of my favourite quotes of all time. In this context, I obviously don’t mean you should <em>literally</em> take a nap when things hit the fan. (Or at least not every time.) When everything seems to go south, do what feels most unnatural: hit the pause button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XvH1kfVg86nDO8JW" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles 🇵🇭</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>That’s right. Drop whatever you’re doing and abandon your working station. Go for a walk. Grab a coffee in the coffee shop around the corner. Call your best friend or your mom to ask how their day is going. Or cry a little in the restroom. Whatever you do, switch your work-brain off for at least 30 minutes. Once your heart rate has slowed down, grab your problems by the nuts.</p><p>Don’t dive right back into the operational chaos you ran away from. Inspire yourself. Scroll through a few articles right here on Medium. Head over to the guys at <a href="https://www.intercom.com/blog/">Intercom</a> or <a href="https://www.atlassian.com/blog">Atlassian</a> (or any other product blog you find inspirational) for some product peptalk. Or read a few pages in the life-altering book that’s been sitting on your desk for months. Broaden your perspective. Then reflect that fresh perspective onto your current problems and try to pinpoint what’s causing the turmoil.</p><p>Is customer support flooded with calls and tickets? Don’t immediately assume your customer support team is understaffed. Or help them close tickets and take calls. Your job is first and foremost to figure out <em>why</em> your customers are so desperately trying to reach you. Are you building the right things? If not, you might want to consider blocking some (or even a lot of) time to freshen up your market and customer insights. If you’re absolutely sure you’re building the right things…are you sure you’re building them right? Have a good long chat with your engineering team. Perhaps they’re having trouble delivering quality because they don’t understand what they’re trying to build. What about your testing process? Are you sure you’re not sending poorly tested releases into the world? Etc…</p><p>Is sales riding you to add a ton of new features because they’re not closing enough deals anymore? Don’t bend over backwards to cram a load of novelties into your product. Rather, consider whether or not the sales team is well informed and trained on what’s already in the product? Or perhaps your product’s proposition has shifted, but the market the sales team is tapping into hasn’t? Or maybe you’re being the victim of some bad word-of-mouth marketing? In which case: are you building the right things? Etc…</p><p>Go find your <em>why’s </em>and fix them.</p><p>The daily struggle is real. Chaos is right around the corner. It creeps up on you like belly fat during cold winter months. Don’t let it get the better of you. Book a meeting with yourself every week and use that me-time for your figurative nap. Assess what’s going on on all fronts of your product and define what you can, nay, <strong><em>should</em></strong>, do to help prevent trouble and headache. I promise you this will turn out to be the single most important and useful meeting you have every week.</p><h4>4. Honesty trumps being liked</h4><p>When I’m not on the job I’m very much a people pleaser. I’m an introvert and at times socially awkward because of it, but I’m a nice person (mostly). And I enjoy being perceived as one too. In my early days as a Product Manager, I made the mistake of taking this aspect of my personality to work.</p><p>In my first week I asked one of the engineers if we could solve an issue in a way that seemed perfect to me. He told me he could do anything I asked for. Being a total rookie in the software business at the time, I eagerly brought this info into my first customer encounters. I soon realised he forgot the most important part of that sentence: “but it will cost you”. Needless to say, a few of those early visits came back to bite me over the following months and even years.</p><p>Of course anything is possible. Given limitless time and resources. In my experience though, both are always as tight as those mile-high super skinny jeans in your closet. Therefore, your life as a Product Manager consists of making impossible trade-offs and choices until hell freezes over. And then rationalising these to your colleagues, clients and stakeholders.</p><p>Gasp!</p><p>How was my soft-hearted, people-pleasing personality ever going to cope with breaking bad news to people all the time? It took some time (and a few beers) to come to terms with it, but it’s all for the best. Here’s why:</p><p>Scarcity, believe it or not, works in your favour. It helps to keep you sharp and focus on your long-term vision. If you would have all the time, money and people in the world, we’d soon be back to paragraph one: a rubbish product that does everything and nothing all at once. Check. And mate. Your product has now failed big time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*J6V5zRveGFFRFBnt25vVAg.gif" /></figure><p>When people come to you with a suggestion, they’re very often wrong (sorry folks). They don’t know what’s best for the product or the market. <a href="https://www.nngroup.com/articles/first-rule-of-usability-dont-listen-to-users/">They often don’t even know what’s best for them themselves</a> (once again sorry peeps). It’s <em>your</em> job to understand what your target audience <em>really</em><strong> </strong>needs, and to make sure a solution for their problem ends up in your product.</p><p>Even if you’re the most meticulous planner in the world, a roadmap is under constant pressure. Anything can and will be turned upside down. When you make a promise you probably won’t be able to keep it. That’s nasty. Being straightforward takes guts, but it sure beats not being trusted or respected by your most valuable connections. So find a way to deliver difficult messages that works for you.</p><p><em>Hot tip</em>: always provide context when you’re saying “no” to something, and explain what you’ll be working on instead. Transparency is gold!</p><p>And remember: all of this is in the best interest of your clients, your stakeholders <em>and </em>your product. So you’re actually pleasing everyone after all ;-)</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://usejournal.com/newsletter/noteworthy-in-tech/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6356c7839e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>