<?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 Cristina Trifonescu on Medium]]></title>
        <description><![CDATA[Stories by Cristina Trifonescu on Medium]]></description>
        <link>https://medium.com/@cristina.trifonescu?source=rss-3aa96da2ad03------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ix5fsdApXj5e4NyG.jpg</url>
            <title>Stories by Cristina Trifonescu on Medium</title>
            <link>https://medium.com/@cristina.trifonescu?source=rss-3aa96da2ad03------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:41:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cristina.trifonescu/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[Things they don’t talk about in school]]></title>
            <link>https://medium.com/@cristina.trifonescu/things-they-dont-talk-about-in-school-603070dbea1?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/603070dbea1</guid>
            <category><![CDATA[youngadult]]></category>
            <category><![CDATA[young-people]]></category>
            <category><![CDATA[graduate-students]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 20:12:17 GMT</pubDate>
            <atom:updated>2020-08-11T08:15:09.027Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*-V4rto0_omJZ79e9UOiKaQ.jpeg" /><figcaption>Young Cristina having finished first grade with honours</figcaption></figure><p>Hello! Welcome to the third article from the series <a href="https://medium.com/@cristina.trifonescu/i-hear-you-want-to-work-in-tech-256be2bc0783">“I hear you want to work in tech…”</a>. This week’s article is dedicated to all students and recent grads who are either doing internships at the moment or looking for opportunities. Imagine I am your big sister, telling you some things I wish someone told me when I was your age.</p><p><em>Massive disclaimer: I grew up in Eastern Europe, Romania, a developing country, and studied there from 3–21. I moved to the UK at 21 for a master degree and never left. So I only experienced 2 educational systems, in 2 very different countries. This article is solely based on my own experiences.</em></p><p>Ok, enough with the giggles, let’s do this…</p><h3><strong>Adapt your communication style (written and visual)</strong></h3><p>Reading the room, or better said, reading your audience is a super important skill to have. Why is that? Because in order to get your message across, you will have to deploy different communication techniques depending on who you’re talking to.</p><p>For example a C-level person is usually someone super busy, who doesn’t have a lot of time, so if you need to let’s say send them some analysis findings, I recommend you stay super concise, send a short summary, use bullet points and focus on key numbers. If you were to present the same thing to your wider team, probably you’d go into more depth, give more context and explain the steps you took to get to the results.</p><p><strong>Goes the same for visual aids:</strong> I use to have a manager who absolutely loved PPT decks, great visuals, and the use of photos/ gifs in the presentations- must say, they looked awesome. He was a visual dude and that worked for him. Problem was it didn’t work for his boss or other people around the business. Sadly, I witnessed several times, how his great points sometimes didn’t reach his audience as good as they should.</p><h3>Adopt the communication channels everyone else is using</h3><p>Each company has it’s own way to communicate, some rely super heavily on emails (like literally a thread looks like a WhatsApp group chat), some on tools like Skype, Slack, Teams, some value face-to-face conversations more (yes, that is a real thing that I have experienced in a company and it’s awesome). My advice is to make sure you suss out what they do early on and adopt the same method even if that might not necessarily be your cup of tea. Why is that when I clearly work more efficiently using Slack?…. well, for a similar reason I mentioned at point 1: in order to ensure your message gets across or people get your message in a timely manner you’ll have to do it.</p><p><strong>Goes the same for how people manage their calendars: </strong>some companies just LOVE MEETINGS and for every chat/ discussion/ decision people need to make they put a meeting in the calendar. You’ll have to start doing the same to ensure you’re getting what you need. Maybe showing up at your colleagues desks if your preferred method (it’s mine for sure), but that won’t work every time or with everyone. Some people might tell you to F off.</p><h3>Embrace the culture</h3><p>Last one on the communication topic, but I promise you it’s super important. It’s very relevant for people with background in different cultures, working in a new country or a company from a different country than theirs.</p><p>When I was doing my internship in the UK, my manager took me and a colleague (now one of my best friends) in a meeting room to explain us the importance of small talk in the kingdom. I am Romanian and she is German and let’s say that our communication styles were somewhat a bit direct :)) no questions about the weather, how’s was the weekend like etc. Everything was straight to the point and we considered ourselves VERY EFFICIENT . Turns out we were wrong and taking a bit of time to do small talk is not only nice, but also lucrative. I know not everyone likes it, but majority of the people in UK like to talk about the weather A LOT, so you have to read your audience, but also embrace the culture. Thanks for the advice, Richard, I know you’re reading this.</p><p>Obviously, my weather example was a massive simplification, there’s more to that, but the key point is that you have to embrace the way people communicate across different cultures for the exact same reasons mentioned above. This doesn’t mean you will lose your personality and the way you are- you shouldn’t look at it in that way. People will notice and appreciate small efforts to integrate from a culture perspective.</p><h3>Build your CV as early as possible</h3><p>OK, this is legit a problem, especially where I come from where the majority of students are not used to take summer jobs or do internships while they study. So you might end up at the end of your degree with zero work experience. DO NOT PANIC!!! This doesn’t mean you have no CV. It means you should focus on your soft skills and things you have learned during different school projects (e.g. your collaboration and interpersonal skills can really come though if you reference a group project) or hobbies, especially sports (they teach team work, discipline, endurance etc). Or you can set up a side gig like an e-commerce website. I promise it will be so, so much fun to do it and it will help with your CV too. Seek help: if you didn’t know this already, most universities offer free career advice with job applications, CVs, interview prep.</p><p>The real key message is to start building your CV as early as you can, by either volunteering, taking summer jobs, setting up small businesses etc. Not only you’ll be making some money, have fun, but also help yourself for what’s to come. If you don’t do that, you will probably going to take a hit in terms of salary, company prestige and career opportunities at the beginning.</p><h3>Healthy relationship with money</h3><p>We get little to NO financial education in schools and probably by the time you will realise that you would have wasted a lot of years in which you could have done things a bit differently (I used to think designer bags are good investments. LOL). Also, it shocks me how very few people actually talk openly about money in general as if it is a taboo subject or as if money is evil. Spoiler alert: IT’S NOT!!! Doesn’t mean you shouldn’t follow your passions or you should be obsessed with becoming rich- that’s not the point. My point is that as a young adult you should know a few basic things about finances like:</p><ul><li><strong>Taxes:</strong> how taxes work in your country</li><li><strong>Student loans:</strong> analyse some financing options for your degree, maybe write pros and cons for student loans. Or different options to pay for it once you graduated.</li><li><strong>Pensions:</strong> how pension works and if you should be on a net arrangement or not (if you already work in UK and have no idea what I just said, that’s a red flag, my friend- google it)</li><li><strong>Investments:</strong> don’t be afraid of the word “investments”. I am not here to give financial advice (that would be illegal), but probably keeping your savings in a current account won’t allow you to achieve your financial goals (depending on what they are). As I said, it’s not financial advice, it’s basic economics that if you keep your money in a place that gives you zero in return, let’s say in 3 years time that same money is going to be worth less.</li><li><strong>Set goals:</strong> doesn’t matter how big or small they are, you have to set some goals, either to buy something you really like, a holiday, buy a house, set up a business, or retire in your 30s (yes, it’s a thing people do: doesn’t mean they want to go on an island and do nothing, but to be financially independent aka don’t rely on a job for their existence).</li></ul><p>As I said, whatever beliefs you have about money (usually picked up from your family) you might want to review them and change your attitude towards them- if used wisely, they will help you or help others around you if that’s your calling.</p><h3>Don’t compare yourself with your friends</h3><p>The money point is a good segue into something that is easy to say, but hard to achieve. I grew up in a culture where how you did compared to others was massively ingrained into my brain. I would come home from school and say super happy “I got a 9 in maths” (grading system in Romania is from 1 to 10). My dad would say “Why not a 10, who got 10?”. Dude, 9 was like a massive achievement for me at that point, we should take a moment to compare this to the last time I came home and mentioned how much I got in maths… My point is you should always look at yourself and find ways to be better. If you start looking at grades, how much money you make, what job you have, what designer shit you have, what car you drive and compare yourself with others, I 100% guarantee you will be unhappy for the rest of your adult life. If you want to achieve something, do it because you really want to and that helps you in some way, not because you have to prove something.</p><h3>Your relationships are going to influence your life a lot</h3><p>Another smooth transition into this next advice: the relationships you build along the way can influence your life both ways- positively and negatively. Yes, there are some things that you should probably do and experience when you’re young, but you have to be really careful who you hang out with (I know I sound like an old lady now). Your friends can literally influence your future. I am not suggesting to ditch your group , what I am saying is that your values are probably aligned to theirs, but you might find yourself wanting different things later on. You could diversify the groups you hang out with to keep your options open.</p><p><strong>Goes the same for the workplace/ business life: </strong>don’t confuse this with nepotism, it’s not. You will have to invest time to build relationships with the people who can help you. I mentioned this before in a previous article — it’s a pretty transactional world out there and if your goal let’s say is to go up on the career ladder you will have to think about ways you can be useful to people who have the power.</p><h3>You have to decide what career you want</h3><p>OK, this is a total pile of steamy, hot, BS!!! You don’t!!! It’s pretty terrifying that we are asked to do that when we are so young- how can you decide what you want to do with your ENTIRE life when you’re, what 15–16? The high-school you pick will influence the uni you can go to and I already know parents in the Bay area think about their kids CVs for Stanford applications when the baby is still in the womb.</p><p>Spoiler alert: YOU DON’T HAVE TO. OK, there are a few exceptions like people who know what their ideal profession is early on, or situations where you kind of have to think hard about it early because the degrees are super long like med school. For the majority of people the key thing is to stay focused on your goals, but pivot your career if needed.</p><p>I studied and worked in Marketing because it seemed awesome on paper, but I didn’t like it as much as I thought I would, so I moved into Tech/Product and probably I will pivot again at some point. That is totally fine. As cheesy as it sounds, you should strive to be the best version of yourself, not to compare yourself with your friends. Everyone has their own story, path and decisions to make in life.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=603070dbea1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I am not a developer, but I want to work in tech. What can I do?]]></title>
            <link>https://medium.com/@cristina.trifonescu/i-am-not-a-developer-but-i-want-to-work-in-tech-what-can-i-do-1021f698afbe?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/1021f698afbe</guid>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Tue, 21 Jul 2020 19:01:01 GMT</pubDate>
            <atom:updated>2020-07-21T19:28:59.524Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@cristina.trifonescu/jobs-in-tech-b1bed06c3e98">The previous article </a>was an introduction to different non-engineering (software developers) roles for anyone who wants to work in tech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8Dwo_2BA3yKWX_25i4dkg.png" /><figcaption>@ Secret Escapes: happy people after a workshop</figcaption></figure><p>This week I want to show you what those roles will do in a real life scenario, applied on a product most of you will be familiar with. <em>Disclaimer: this is a simplified example aimed to give you an idea of what each role does in real life. I do not work for a food delivery company.</em></p><h3>Product definition</h3><p>A product can be a whole mobile application, a website (desktop or mobile), a web app etc. In majority of the cases a team owns specific features (e.g. search) or a part of the user experience (e.g payments journey). Also “the users” are not always just the customers.</p><h4>Let’s look at a food delivery app…</h4><p>Who are your “users”?</p><ul><li><strong>Internal</strong> users: people who are using any internal system (e.g.: manage photos, menus, prices, payments for restaurants and riders etc.)</li><li><strong>Customers</strong>: people who place the orders/ buy food from you</li><li><strong>Restaurants</strong>: people who cook the food for your customers</li><li><strong>Riders</strong>: people who deliver the food</li></ul><h4>Tech teams explained…</h4><p>The organisational structure differs from company to company, usually based on how much money they have. In most companies a “product team” is formed of a product manager, business analyst, designer and a few developers. <a href="https://medium.com/@cristina.trifonescu/jobs-in-tech-b1bed06c3e98">All the other roles</a> from the previous article are sometimes shared across multiple product teams. I will give examples of each role later.</p><p>For our food delivery app, let’s imagine we have product teams for each user type and supporting roles across all 4 teams:</p><ol><li><strong>Internal tools team: </strong>responsible for all systems and tools the employees use to manage the supply and content of your food delivery app</li><li><strong>Customer team: </strong>focused on the customer experience: the app where your customers order the food from</li><li><strong>Restaurants team: </strong>responsible for all systems and tools the restaurants employees use to manage the orders</li><li><strong>Riders team: </strong>focused on the riders experience: the app where riders manage the deliveries</li></ol><h4>Introducing a new feature…</h4><p>Let’s imagine that there is a new feature available in your food delivery app: REVIEWS!!! You can now see a score for each restaurant in the app, leave your own reviews and see other’s reviews too. Pretty cool, right? Now let’s go back to the <a href="https://medium.com/@cristina.trifonescu/jobs-in-tech-b1bed06c3e98">roles list</a> and see what each person had to do to make this happen….</p><h3>Feature development life cycle</h3><p>Diving into what each role does without context will be a bit unfair. The feature we are talking about was not released because the CEO said “let’s add reviews”, it probably started with a business goal in mind “Increase app engagement by X% in the next quarter” or “Increase orders per week by X%”. I will explain as briefly as possible the steps the teams could take to get to the feature you now see and use in your food delivery app. Bear in mind the steps below are not linear, some happen in parallel, or in some cases one has to happen before other- there’s not magical blueprint, everyone has to do what works for them, with the product and resources they have.</p><h3><strong>High level goal setting</strong></h3><p><em>Usually: product manager and data analysts</em></p><p>When it comes to setting goals/ OKRs for the team it’s usually the <strong>product manager </strong>who is heavily involved in this, with help from <strong>data analysts and the rest of the product team. </strong>This doesn’t happen in a silo, but by collaborating with key business stakeholders and other product managers in the wider team. Data analysts usually help with insights, crunching numbers, ensuring the goal is something the team can easily monitor on an ongoing basis.</p><p><em>Back to our scenario: let’s say our app goal for the Customer team was “Increase number of orders per week by 20%”.</em></p><h3><strong>Identify opportunities</strong></h3><p><em>Usually: product manager, design, developers, data analysts</em></p><p>Once you have a goal, there are multiple techniques that a product team can use to identify the things that will help them achieve that. A super popular framework is the <a href="https://www.product-frameworks.com/Opportunity-Solution-Tree.html">“Opportunity solution tree” by Teresa Torres</a>. Who usually takes part in this exercise: <strong>product managers, designers, developers, data analyst, and business stakeholders.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*XMSi7FOEXwR8EoIfYCI3ug.png" /><figcaption>From producttalk.org</figcaption></figure><p>As you can imagine, this exercise can produce multiple opportunities for our food delivery app like:</p><ul><li>loyalty schemes (get your existing customers to order more)</li><li>personalisation (target impulse purchases/ bring more people on the platform by using notifications/emails etc)</li><li>Conversion Rate Optimisation/CVR optimisation (boost the number of orders from people who are already on the platform)</li></ul><p>And for each opportunity you have a bunch of solutions and experiments you can lay out. It’s important that multiple disciplines come at the table to do this exercise to ensure ideas come from different angles: based on data (analysts), based on research (designers/ UX should represent the voice of the customers) and so on.</p><p><em>Back to our scenario: let’s say that during the opportunity solution tree exercise, “allowing users to see restaurant reviews” is one of the ideas that come up under CVR optimisation.</em></p><h3><strong>Prioritising</strong></h3><p><em>Usually: product manager with input from design, developers, data analysts.</em></p><p>This is the most frequent problem product teams have: we have a lot of GREAT IDEAS, WHAT DO WE DO WITH THEM???? The <strong>product manager</strong> is in charge or prioritising them to ensure no time and money are spent on things that won’t achieve the goal.</p><p>One of the <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">most popular prioritisation frameworks is RICE </a>, where you can lay out all ideas and give them scores that will give you a clear indication of what you should start with. This will also start to form your roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*cTlPav_L-tYyu75bw4hBdg.png" /><figcaption>Intercom <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">article</a> about RICE framework</figcaption></figure><p><em>Back to our scenario: let’s assume that during the RICE exercise the reviews concept gets a high score and it’s amongst the top 3 things that will help the team achieve their goal: “Increase number of orders per week by 20%”.</em></p><h3><strong>Validating hypotheses</strong></h3><p><em>Usually: design, user researcher, product manager, data analysts, developers.</em></p><p>Each idea that you have on the table can be turned into a hypothesis and that has to be tested (aka validated) to ensure that it’s the right thing to go forward with. This is pretty much the <strong>design arena</strong> (UX, design, user researchers) and there are a myriad of discovery activities a team can use to validate hypotheses: from surveys, user interviews, card sorting exercises, tree testing, user testing with prototypes, A/B tests etc. Usually the <strong>product manager</strong> is heavily involved in this and supports the design team. Similarly, <strong>data analysts</strong> can support with validating ideas with data/numbers. Developers can also participate by ensuring the ideas are feasible to be built or by running their own investigations (what we call tech spikes).</p><p><em>Back to our scenario: let’s assume that the team has done some surveys that suggest lack of reviews are the number one barrier to purchase from restaurants. The team can also start sketching how the first version for the solution could look like and run a remote, moderated user testing session. After these things we now have confidence in the solution, but we’re not convinced about how this will impact the number of orders on the app. So the next step could be to run an A/B test in the app.</em></p><h3><strong>Design</strong></h3><p><em>Usually: design, developers, product manager</em></p><p>At this point we have a solid idea and we have identified how the feature could look like for an A/B test, but from wireframes (low resolution sketches) to designs that can be used by the developers, there is a bit more work. The design phase is, as it says on the tin, the <strong>design arena, but with input from developers and product manager.</strong></p><p><em>Back to our scenario: the outcome of this step is that we will have designs that are ready to be turned into code.</em></p><h3><strong>Build</strong></h3><p><em>Usually: developers, business analyst, product manager, design, tester, delivery manager, project manager.</em></p><p>Turning designs into code that works and people can use requires a ton of work from different people, not just developers.</p><ul><li><strong>Developers:</strong> decide on the best approach to build the product and actually deliver the work aka write the code.</li><li><strong>Business analyst:</strong> work with developers and product manager to refine and define review features and ensure it’s ready for development. They are a crucial part into ensuring the developers have what they need (clear descriptions of how the functionality works).</li><li><strong>Product manager</strong>: at this stage they are prioritising the tradeoffs. Example for our scenario: do we build in house a mechanism to capture reviews, do we use a third party, what are the pros and cons for each?</li><li><strong>Designer: </strong>is still very involved in the process to ensure the developers have all they need and they do design reviews (aka making sure what it’s produced looks like intended).</li><li><strong>Tester: </strong>dedicated person who is there to ensure that what the developers have built functions the way it’s meant to- following the rules and logic the business analyst layed out.</li><li><strong>Delivery manager: </strong>will ensure the team is working at their best. It means they review and propose processes changes, unblock the team, ensure the team has everything they need. Usually they run a lot of ceremonies/meetings I haven’t really mentioned (maybe for another time).</li><li><strong>Project manager: </strong>will ensure things are being delivered on time, on budget (do we have enough people, do we need money for new tools). They could develop and plan new processes, training materials and the launch for the feature.</li></ul><p><em>Back to our scenario: the outcome of this step is that we will have an A/B test for reviews in the app ready to be launched. Means 50% of the app users will see restaurant reviews and 50% will see the app as it is. This will help the team assess if this feature will have the desired outcome and helps with achieving the goal. This is a simple idea, where the reviews are coming from a third party. So users can only see reviews, they can’t input their own YET.</em></p><h3><strong>Test &amp; Measure</strong></h3><p><em>Usually: product manager and data analysts</em></p><p>We are closing the loop with the same people- once you’re feature is out, in the hands of the users you want to constantly monitor how it’s doing against the goal you set. For the purpose of this article I had to massive simplify things. In real life you will probably iterate (try more options) or try different ideas until you reach your goal.</p><p><em>Back to our scenario: let’s assume the A/B test was a massive success and users who saw reviews in their app ordered 3 times more than users who didn’t saw reviews in the app. The next steps are to work with the team to figure out how this can be turned into a permanent feature in the app and improve it in the long term.</em></p><h3>Closing points</h3><p>As I mentioned before, the process I outlined is not linear in real life and also I have simplified it on purpose. The aim of this article was to bring non-engineering roles in the spotlight so that you can see there are a lot of other things you could be doing if you want to work in tech, but you don’t want to be a developer.</p><p>The article is missing a lot of ceremonies and actions the product team takes and is also missing talking about amazing roles that are more engineering focused like tech support, DevOps or data science teams.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1021f698afbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jobs in tech]]></title>
            <link>https://medium.com/@cristina.trifonescu/jobs-in-tech-b1bed06c3e98?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1bed06c3e98</guid>
            <category><![CDATA[working-in-tech]]></category>
            <category><![CDATA[tech-jobs]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Fri, 10 Jul 2020 17:12:39 GMT</pubDate>
            <atom:updated>2020-07-10T17:12:39.115Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of people think that to work in technology means you have to be a software engineer. That is not true and I want to paint the full picture of what other roles you can pursue if you want a career in tech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldSscTdiJw1nAAGkAU0l3w.jpeg" /><figcaption>@ Secret Escapes: summer interns presentations about their experience in the tech team</figcaption></figure><p><em>Note: this article is part of a series called “</em><a href="https://medium.com/@cristina.trifonescu/i-hear-you-want-to-work-in-tech-256be2bc0783"><em>I hear you want to work in tech…</em></a><em>”, so check out the next articles and let me know if you want me to write about a specific topic.</em></p><h4>Technology team defined</h4><p>When I say “technology team”, I am referring to all people involved in the development and launch of a product (e.g. a site, a specific feature, a mobile app etc). So this does not include, what we call the “business side” e.g. marketing, sales, customer services, finance, operations etc.</p><h4>Teams breakdown</h4><p>Bear in mind that the breakdown varies from company to company, depending on their size and organisational structure. Not all companies can afford to hire project managers, business analysts or quality assurance folks.</p><ol><li>Engineering</li><li>Product Management (PM)</li><li>Analytics / Business Intelligence</li><li>User Experience (UX)</li><li>Quality Assurance (QA)</li><li>Development and operations (DevOps)</li><li>Project management</li><li>Business Analysts</li></ol><h4>Roles, Responsibilities &amp; Skills</h4><p>I’ve created this table with <strong>SUPER</strong> high level information to give you an idea of the kind of stuff you could do in each team and what skills you need. <a href="https://docs.google.com/spreadsheets/d/15e9UMj9AKM35KDWRx80F9pVJgkzUvph0pYXHPfs-cOs/edit?usp=sharing">There’s a link to this table too.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*I6vOcRb7aOZvS4Ae04Y0SQ.png" /><figcaption>Disclaimer: all based on my personal experience. Each company has its own structure, but broady the roles are similar.</figcaption></figure><h4>Where to find these jobs</h4><p>If you are a recent grad, student or just don’t have that much work experience, finding jobs is usually hard. But what you DO HAVE is your attitude and personality. My advice would be to make a list with the companies you like and see if they have any grad schemes or internships available, send ad hoc application with a cover letter explaining why you want to work for them. You might not land your dream job from the beginning, but is often easier to move internally once people get to know you.</p><h4>Usual websites I found to be really good:</h4><ul><li><a href="https://www.linkedin.com/">LinkedIn:</a> make sure you include recommendations, main achievements or any volunteering work you have under your belt.</li><li><a href="https://www.glassdoor.co.uk/">Glassdoor:</a> you can apply for jobs, but is also a great source to see average salaries or ranges for different roles and industries.</li><li><a href="https://www.adzuna.co.uk/">Adzuna:</a> pretty similar to Glassdoor.</li><li><a href="https://hired.co.uk/">Hired</a>: my favourite site for jobs in tech. Companies request interviews with you, not the other way around.</li><li><a href="https://angel.co/">AngelList</a>: for jobs in startups.</li></ul><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1bed06c3e98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I hear you want to work in tech…]]></title>
            <link>https://medium.com/@cristina.trifonescu/i-hear-you-want-to-work-in-tech-256be2bc0783?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/256be2bc0783</guid>
            <category><![CDATA[life-in-general]]></category>
            <category><![CDATA[technology-jobs]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[student-life]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Fri, 10 Jul 2020 16:35:35 GMT</pubDate>
            <atom:updated>2020-08-10T20:17:43.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zox7M93MTW44_PexcCl1Sg.jpeg" /><figcaption>One of my old teams during user testing sessions</figcaption></figure><h4>Introducing a new format:</h4><p>Hello, hello! Hope you’re all well, thanks for coming back or welcome if you’re new!!!</p><p>I received a lot of feedback from friends saying they like my articles so far, BUT they would love them if they were shorter and more concise. I am super grateful for constructive feedback and that is why I am trying a new concept. I will start a few series, even more focused on specific topics and (hopefully) with shorter articles.</p><h4>First series is dedicated to students, recent grads or just anyone who is interested in working in TECH</h4><p>Why am I writing about this?</p><ul><li>a few students reached out to me to ask “what kind of jobs are there in the real world”?</li><li>a few parents asked me to spend some time with their kids to tell them what “they could do to work in tech?”</li><li>for my younger myself: would have genuinely been nice to have these chats with someone before I started my master degree/ first jobs.</li></ul><h4>“I hear you want to work in tech…” series include the following articles:</h4><p><strong>Published:</strong></p><ol><li><a href="https://medium.com/@cristina.trifonescu/jobs-in-tech-b1bed06c3e98">Jobs in tech - overview of different roles</a></li><li><a href="https://medium.com/@cristina.trifonescu/i-am-not-a-developer-but-i-want-to-work-in-tech-what-can-i-do-1021f698afbe">I am not a developer, but I want to work in tech. What can I do?</a> — article about seeing different roles in action, what each would have do to launch a specific feature.</li><li><a href="https://medium.com/@cristina.trifonescu/things-they-dont-talk-about-in-school-603070dbea1">Things they don’t talk about in school</a>- soft skills you should have or things to think about</li></ol><p><strong>Coming soon:</strong></p><p>4. Salaries, taxes and pensions….</p><p>5. Career progression</p><p>Please leave feedback if there is something else you want me to write about that could help students or recent grads.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=256be2bc0783" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with difficult stakeholders and toxic managers]]></title>
            <link>https://medium.com/@cristina.trifonescu/working-with-difficult-stakeholders-and-toxic-managers-65b1fbd02a96?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/65b1fbd02a96</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[badmanager]]></category>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[difficult-conversations]]></category>
            <category><![CDATA[difficult-people]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Thu, 25 Jun 2020 19:33:07 GMT</pubDate>
            <atom:updated>2020-06-25T19:33:07.352Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, hello! Hope you’re all well, thanks for coming back or welcome if you’re new!!! In <a href="https://medium.com/@cristina.trifonescu/the-dark-side-of-product-management-8ccc8aeb3a64">last week’s article</a> I touched on the fact that you almost never pick or hire your own team and I’d like to expand on this a little bit because it goes beyond your team and doesn’t just apply to product managers.</p><p>How many of you had to work with what we generally call “difficult stakeholders”? I’ll take a guess and say that at some point <strong>all of you </strong>crossed paths with someone like this OR you were that person and you didn’t even realise. I want to talk to you about what their characteristics are, what drives them and if there’s anything you can do about it.</p><p>Usual disclaimer: this article solely based on my personal experiences.</p><h3><strong>Traits of a “difficult stakeholder”</strong></h3><p>I am only using this term because I hear it a lot in my tech/ product world and it’s broad enough to capture all humans you work with, who are either impacted by your work, have a say, or a stake in it (from any department, at any level).</p><p>But let’s talk about a few tangible examples when someone is being “difficult” and why it’s hard to work with them if they exhibit these traits.</p><ul><li><strong><em>“Their way or the highway”</em></strong><em>- they are very keen on their own ideas because they think they are the best and don’t want to hear any alternatives or input from anyone else. In this category I’d also add people who have a job title that allows them to tell you what to do “because they said so and because senior member X backs them up”.</em></li></ul><p>It’s not about the “what”, it’s about the “how”. Their ideas could genuinely be amazing, but who enjoys working in a space that is not collaborative, where people feel they can’t express their thoughts and ideas or even ask questions. In the past I heard things like “why are you questioning this decision, it’s not your job to do that?”. Well, 1) for product managers: it’s definitely in your job description to actually do that and 2) if anyone does it so what? Maybe they are curious or they lack some context that you might have and would be beneficial for everyone if that context is shared. I also had the extreme when people shouted in meetings for not getting what they wanted. Like seriously, if you do that to people, they will instantly lose any respect they have for you, so good luck next time you need something from them.</p><ul><li><strong><em>“They don’t walk the walk”</em></strong><em>- walking the walk means to </em><strong><em>do</em></strong><em> the things that one says one will </em><strong><em>do. </em></strong><em>These people could be telling you one thing, but their actions don’t reflect their verbal commitments. Sometimes their narrative and attitude changes when senior management is involved or their manager is around.</em></li></ul><p>Why is it difficult to work with people who do that? Simply because it’s very, very hard to trust them. A colleague you can’t rely on or someone that morphs their behavior when their boss is around is just super untrustworthy. If you do that, sooner or later people will realise and they will try to avoid you as much as they can. What I am about to say could be controversial, but good work relationships are almost always transactional- you help someone, they help you in return when the time comes. So if people don’t trust you, you’re basically punching yourself in your own corner. Alone.</p><ul><li><strong>“Negative Nancy”-</strong><em> this is an expression used to describe someone that “is considered excessively and disagreeably pessimistic”. Have you ever worked with people who constantly disagree with what everyone else is saying or literally think about all the worst case scenarios they can think of. It’s like their mind is a constant waterfall or pre-mortems.</em></li></ul><p>Don’t get me wrong, you absolutely need people to think about bad outcomes, edge cases, basically bring to the table things you might not consider otherwise. The problem comes when it’s all they do without offering alternatives, solutions or any constructive feedback. It’s difficult because it drains everyone else’s energy and they start resenting working with someone that focuses on the negative things all the time.</p><ul><li><strong>“The shadows”- </strong><em>at pretty much every place that I’ve worked in my life there was always that someone who, most of the time, used their boss as a shield for everything that they did, kind of like being their shadow (where my nickname comes from). Shadows could do things like: cc their boss in every email they send or receive, point fingers when things go wrong, generally their primary agenda is to critique what everyone else does or says, in front of their boss of course.</em></li></ul><p>The funny thing about this type of people is that most of the time they are actually driven professionals, overachievers, who have a clear goal and will do whatever it takes to get there. The problem is the way they decide to do that. Sometimes they are not even aware that their interpersonal skills are nonexistent and frankly I don’t think they even care about developing them. Do I even have to say why it’s difficult to work with people like this? It’s very hard to trust them and rely on them because they are often egocentric.</p><ul><li><strong>“Toxic managers”- </strong><em>in the majority of the cases people leave their managers, not their companies. There are plenty of “bad managers” out there and I definitely had my fair share. Here I am talking about people who take it to the next level and create a terrible environment and place to work.</em></li></ul><p>Some examples include:</p><ul><li>severe case of micromanagement (e.g. they ask to read all your emails before you send them to stakeholders above them)</li><li>use intimidation techniques</li><li>deny all feedback they receive and have an explanations for everything (e.g. even if their team churn rate is ridiculously high, they don’t think it has anything to do with them)</li><li>publicly shame or badmouth people in their team</li><li>point fingers at their team members when something goes wrong</li><li>treat people differently in front of their boss (e.g. I had a manager once who would only ask about my wellbeing in front of their manager)</li><li>refuse to teach or upskill their team members (e.g. you would ask them how they’ve done something and they would give you the end result without explanations)</li></ul><h3><strong>Why are they like that?</strong></h3><p>From what I’ve seen so far it boils down to three main reasons that are spread across all the different types of people I identified above.</p><ul><li><strong>They have a clear agenda </strong><em>— they have been asked or told to get something done and you might be in their way.</em></li></ul><p>A “<strong>my way or the highway</strong>” person might be pushing in fact the ideas of their manager, so you coming with alternatives or trying to improve things sits in their way of achieving what their boss told them to. People who “<strong>don’t walk the walk</strong>” might tell you something that they think you want to hear so that they can ultimately achieve what they have in mind. So that’s where the discrepancy between what they say and what they do could come from. A “<strong>toxic manager</strong>” agenda could be to ensure their team does what they say, so that they feel in control.</p><ul><li><strong>They need to prove something </strong><em>— these people need to prove themselves or prove they are capable of achieving a set of things to advance in their careers/go up the ladder.</em></li></ul><p>This reason can apply to all types. E.g.: <strong>negative Nancy</strong> maybe feels the need to prove they are right, <strong>the shadows </strong>are usually in a race to advance in their career, so they need to prove they’re capable of “X” things to get “Z” job.</p><ul><li><strong>They see you as a threat </strong><em>— either by sitting in their way of achieving their goals, taking their job or damaging their image.</em></li></ul><p>You can be perceived as a threat to someone without realising. E.g. if you question something they’re doing to get more context, it can be seen as questioning their work to pick holes. If you ask too many questions to improve your skills, some people think you’re stealing their knowledge. Sadly, only people who are not really confident see others as threats and the root cause is not something you can fix or help with.</p><h3><strong>What to do about them?</strong></h3><h4><strong>Don’t take things personally</strong></h4><p>Took me a few years to master this, I am still learning, but the first thing on the agenda is to ensure you’re not taking things personally &amp; try to remove any negative emotions. We sometimes forget that the way people act is not something we can control, but what we can control are our feelings and emotions in response to their behaviour. It’s totally in your control to decide how much you will let a bad 1:1 with your toxic manager or a meeting with a negative Nancy affect your day.</p><h4><strong>Build empathy</strong></h4><p>It’s harder than it sounds, especially if some negative feelings are already growing inside, but try to put yourself in their shoes and understand where they are coming from. Even better, where you can, maybe take them on a neutral ground (like a coffee shop, outside the office) and try to understand their motivations.</p><p>I once had a pretty bad case of micromanagement and I took my boss for a smoothie to learn a few things about why they were acting the way they were. By the end of the chat I learned how much pressure they had from their own managers, we consolidated our relationship and even though I eventually left the company after a few months, we remained friends to this day.</p><h4><strong>Build a support network</strong></h4><p>This one is close to heart because it’s one of the most important ones if you are dealing with a toxic manager. It took me a while to realise that my peers were in the same boat as me and we started sharing notes about our experiences over a pint or two- it definitely helped. But what it also helps is building a support network internally and opening up to people that can maybe help you in different ways.</p><p>If you tried to share your feedback with both your manager, maybe HR and nothing changed, another option could be to start building relationships to see if you could move internally. At some point in my life I was in a situation when I really didn’t like my manager (they weirdly liked me a lot), but I loved the company. What happened was that I found someone to take me under their wing in another team. I will be forever grateful to them.</p><h4>Write things down</h4><p>I am referring to prompt, follow-up notes after meetings. This has helped me in the past when dealing with people who don’t walk the walk and often change their narrative when it comes to what they agreed to. This doesn’t mean you become obsessed about it, it simply means that after important meetings, where decisions are made, you ping everyone with a follow-up email with key points and actions. You will never know when you need some proof to back you up or simply remind them of their commitments in a polite way.</p><h4><strong>Map out all agendas</strong></h4><p>In the <a href="https://medium.com/@cristina.trifonescu/the-dark-side-of-product-management-8ccc8aeb3a64">same article from last week</a>, I wrote that one of the reasons why I love the product role is because it enabled you to “learn how the entire business works, what each department does and what their goals are”. Often, people you work with have different, competing agendas and you could find yourself in a world where you’re getting mixed messages because of this, especially in product management.</p><p>My advice would be to firstly identify and map out stakeholders on a power-interest grid (see an example from a product leadership course I recently attended) and try to overlay their “agendas” or goals on top of that. Will not only help you navigate the space, but also guide you to understand what people need from you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ustPJWRF44ap1iPb0ccFA.png" /><figcaption>Product Leadership Skills course by Roman Pichler (2020)</figcaption></figure><p>In my closing points, I want to remind everyone that no one is perfect. We’ve all been at some point a bit of negative Nancy or expressed “our way or the highway” when we were desperate to get what we wanted. Sadly, some people have these traits installed permanently in their DNA and that’s when they become “people who are difficult to work with”. Also, most people are self centered and very few take the time to understand how their actions are affecting others.</p><p>I think kindness and empathy go a long way and everyone has their own path and story.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65b1fbd02a96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The dark side of product management]]></title>
            <link>https://medium.com/@cristina.trifonescu/the-dark-side-of-product-management-8ccc8aeb3a64?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ccc8aeb3a64</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-roles]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Fri, 19 Jun 2020 19:22:42 GMT</pubDate>
            <atom:updated>2020-06-19T19:22:42.725Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, hello! Hope you’re all well, thanks for coming back or welcome if you’re new!!! (oh, I sound like a YouTuber now). I haven’t written that much, but I noticed that the article that got most attention was <a href="https://medium.com/@cristina.trifonescu/how-do-you-become-a-product-manager-837009bb4e7b">the one about becoming a product manager</a>. Also, a few people have reached out to me to ask for advice and I started thinking about how much hype there is around the role. I started questioning if we accidentally created the false impression that we, product people, have the best job in the world. This article is dedicated to the dark side of product management. <strong>Before you jump in: if you’re a seasoned product manager, probably this article is pretty high level for you, so I won’t recommend it.</strong></p><p>Usual disclaimer: this article is all based on my personal experiences and insight from my friends or companies I have interviewed with so far.</p><h3><strong>Theory vs practice</strong></h3><p>I was talking to a friend recently about how she stopped attending product events and conferences because they have become this place where people come and brag about how amazing they or their companies are. Most of the people I meet at these events are looking to hire or to switch jobs, so I get where she’s coming from. Maybe everyone is selling something: themselves or their companies.</p><h4>So what do the textbooks say versus what we do?</h4><ul><li><em>“Product managers are responsible for guiding the success of a product and leading the cross-functional team”</em></li></ul><p>There are a lot of loaded words in that sentence. “Guiding the success” doesn’t always mean you are directly responsible for the success. Shocking, right? A lot of organisations structure their teams in such ways that product teams have, let’s call them “business owners”- basically the person responsible for the P&amp;L (profit and loss). So guiding means you are responsible for making sure you are focusing on the right metrics and goals, you have the right resources and headcount in your team to achieve your goals, you take the right steps in your discoveries activities and so on.</p><p>“Leading the cross-functional team”- this is always a funny one because your team does not report into you. Sorry, grandma, if you thought I had an army of people reporting into me- disappointing, I know. :))</p><p>Usually you have designers and engineers in your team and they all have bosses who are not you (e.g.: head of design and/or UX, engineering managers, CTO etc). The beauty of working in technology as a product manager is that you work in a flat structure and everyone brings at the table a certain expertise, skills and domain knowledge they have. So the magic happens when all these skills are working together, but what it also means is that you cannot “force” your team to work on something, you have to convince them that is the right thing to do.</p><ul><li><em>Martin Eriksson says “product managers sit at the intersection of business, technology, and user experience”</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*3-CTj4zGtYxmBFKgDeVOpA.png" /><figcaption>By Martin Eriksson</figcaption></figure><p>Probably if you googled “what do product managers do?” you came across this swanky Venn Euler diagram. What this really means in most organisations is that you need to make sure that when you build your product, you take into account the needs of all parties involved and manage the trade-offs. In other words, you need to understand and represent your users, align the stakeholders, analyze the commercial uplift or benefits, ensure what you want to build is feasible, prioritize based on realistic ROIs (I mean benefits / effort).</p><p>Imagine being like a conductor at the opera and your role there is to ensure everyone is playing their part, make the audience have a great time, feel they spent their money wisely coming to your concert. Except it’s not a concert, it’s users or business needs that you need to solve and ensure you’re spending the company money wisely (aka the precious time of your colleagues — no one wants to work on something that is not useful or doesn’t make money, including yourself).</p><ul><li><em>Ben Horowitz says you’re “the CEO of the product”</em></li></ul><p>There is so much drama on the internet and offline in regards to this quote. If you would be in the shoes of a real CEO for even half a day, you will disagree with this straight off the bat. That is why I am not 100% a fan of this because IN REALITY yes, you do have to make hard decisions, analyze the trade-offs, set goals, motivate your team, sell the vision to your team and various stakeholders, BUT you usually (in most organisations) work with either goals set by the exec team or strategic initiatives set by the business. If those big bets are not quite what your users need or want in order to achieve X commercial goal (just an example, not everything is tied to user needs or commercial uplift) then how are you the CEO of your product, mate?</p><p>Of course, there are a lot of companies out there who claim to have a “bottom up” culture and product managers are 100% empowered to work with their teams to do blahblahblah, A FEW really do, but most of them simply do not work like that.</p><h3><strong>Is the job as awesome as it sounds?</strong></h3><p>Short answer: it depends. It depends on what matters to you the most. From my perspective it is super awesome because:</p><ul><li>You never stop learning, even within the same organisation.</li><li>You’re usually surrounded by very smart people — for example, working with engineers is not easy, but is definitely exciting or working with senior management / exec team.</li><li>No day looks like the other. I do not remember when was the last time I did the same thing 2 days in a row.</li><li>Usually you get to learn how the entire business works and what each department does, what their goals are etc. There are very few roles out there that give you this kind of exposure. The benefits of this exposure might not always be super obvious in the short term, but trust me, they will make sense sooner or later.</li><li>You develop and improve tons of skills on the job e.g.: you have to be good at storytelling, selling, impeccable communication skills at all levels, understand different UX and engineering principles, conduct user interviews, write well crafted surveys, data analysis, learn how to read commercial data, I can literally go on for 10 more mins- you get the idea.</li></ul><h3><strong>Things other product managers might not tell you…</strong></h3><p>Ok, the moment you’ve been waiting for (or not if you just scrolled to this section). It is definitely not always rainbows and butterflies.</p><ul><li><strong>There is no such thing as 9–5 when you are a product manager.</strong> Again, a lot of saga on the topic since Marty Cagan said something along the lines too and I agree with him. Your calendar during the day is packed with meetings, time your team needs from you for specific things or ceremonies etc. The reason why 9–5 is hard to achieve is because you rarely have time for quality thinking during those hours (of course, I am generalising and there are superhumans who prioritize their calendars better than their backlogs). So what I am trying to say is that, you might physically stop work at 5 or 6, but your brain doesn’t usually stop then.</li><li><strong>You’re accountable for delivery, but you have little control over it. </strong>When shit hits the fan or stakeholders are wondering why things are “taking so long” they usually blame you. If you are a decent human being you will never point fingers at your team. The reality is that you can’t make people code faster or have 9 women make a baby in 1 month. If you think this analogy is crazy, read it again. The best thing you can do is manage expectations and be transparent.</li><li><strong>You don’t pick / hire your team. </strong>You can rarely have a dream team with incredible skilled people, who also get along and go for beers / tea after work. Usually you end up with a mix of seniority levels and personalities and you have zero control over that, which can make things very interesting, but also challenging.</li><li><strong>As per “the theory vs practice” section above — you don’t have as much power as you think you do</strong>. Your power is the sum of a lot of activities, a lot of thinking and homework. Influencing people (your team, your stakeholders) does not happen because your job title says “manager” or might say “senior”, it happens when you have a proven track record that you’ve delivered and achieved goals and you know your s***.</li><li><strong>Frameworks are just frameworks. </strong>The way of working with your team of engineers and designers is a bit like reading glossy magazines and thinking all women should have perfect bodies and skin. You might think “what the f*** does this have to do with Vogue?” I think we are exposed to a lot of literature about how things should work in terms of team structure, ceremonies, ways of working etc and it is often very hard to apply things in real life. So we are constantly chasing this ideal and sometimes forget to give ourselves some credit for doing the best we can. Some things are very hard or impossible to implement.</li><li><strong>Working with your team is not easy. </strong>I mentioned before how awesome it is to be surrounded by smart people and work in a flat structure. Do not forget that designers are artists at heart, so the way you talk to them and “critique” their work can have a massive impact on how you work together. Just because their work is so tangible, doesn’t mean you have to give pixel feedback. There’s so much more you need to focus on, don’t waste your time talking about font sizes and let them do their job. Same goes with engineers, at heart they are builders and they usually want their things to be built to perfection. Conversations about de-scoping or speeding things up can be a minefield if you don’t have the right approach and mindset.</li><li><strong>You will feel lonely.</strong> You have “a team”, your cross functional team, but sometimes it is difficult for them to really understand your problems because your role is so different from theirs. And then you have a product team that you “belong to”, with your peers who share the same stories and struggles, but you rarely see them (with the exception of a few weekly meetings you might cross paths) or work with them. You will constantly engage with a lot of humans: colleagues, peers, stakeholders, users etc. but it won’t be easy for you to create deep connections because of point 1: you simply won’t have the time.</li></ul><h3><strong>How do you know for sure it’s the right thing for you?</strong></h3><p>Short answer: you won’t. Best advice is to JUST DO IT. Try a few different companies and org structures and see if you like it. There’s no other way to know, except by doing it.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ccc8aeb3a64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things to do during product interviews]]></title>
            <link>https://medium.com/@cristina.trifonescu/things-to-do-during-product-interviews-83426cad06e?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/83426cad06e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 17:24:17 GMT</pubDate>
            <atom:updated>2020-06-09T17:24:17.428Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why am I talking about this now?</h3><p>Hello, lovely humans! Sorry I’ve been MIA, the COVID-19 lockdown has come with challenges on all fronts, but I am back!!! Hope you’re all safe and sound.</p><p>I was thinking about continuing the product series where I left it, but then I realised that this unprecedented period of time has made some of us question if we’re truly happy with our jobs, companies we work for and where we are heading in our careers. I am going to flag from the beginning that<strong> this post is NOT about cracking the PM interview</strong>, there are tons of materials on this topic out there, including this good book “<a href="https://www.amazon.co.uk/Cracking-PM-Interview-Product-Technology/dp/0984782818/ref=sr_1_1?crid=2J4PKEOTSVEFY&amp;dchild=1&amp;keywords=cracking+the+pm+interview&amp;qid=1591699632&amp;sprefix=cracking+the+%2Caps%2C149&amp;sr=8-1">Cracking the PM interview</a>”.</p><p>Whether you’re interested in transitioning into a product role or jump ship, regardless of seniority level, there are a few things you should pay careful attention to during your interview process that will help you assess if the company is right for you. This is what this article is all about.</p><p>Disclaimer: this article is all based on my personal experiences and insight from my friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*og265sJqWg8cby18D1ipWQ.jpeg" /></figure><h3><strong>Best time for switching jobs?</strong></h3><p>Switching jobs is a big deal. Let’s be honest here, you already know we spend more time at work than we do with our families, the interview process is long, expensive and stressful. The last thing you want to do is waste anybody’s time, especially yours.</p><p>My two main pieces of advice are:</p><h4><strong>1. Have a clear idea of what you want</strong></h4><p>You shouldn’t start applying to all jobs you find on LinkedIn. Spend some time thinking about what you want and need. This exercise could help you realise you might not even need to switch jobs to get that. Maybe you just need the balls to have some conversations with your manager to make that happen.</p><p>If changing jobs is still what you have to do, then think about the things you need from your next role and company. Before I joined Secret Escapes (where I work now) I remember I had a clear, prioritised, wishlist in mind that I stuck to. This will help you massively narrow down the list of companies and increase the chances to find something great.</p><p>My pre-Secret Escapes wishlist sounded something like this:</p><ul><li>Work in a commercially driven product team that was focused on data.</li><li>Learn about experimentation.</li><li>Not a corporation (I’ve always enjoyed working in a fast paced environment).</li><li>Ideally work on a global product with millions of users.</li><li>Ideally work on a product I love and use.</li></ul><h4><strong>2. Don’t be desperate &amp; don’t compromise</strong></h4><p>I see a lot of people making these mistakes for various reasons and I’ve done them too in the past. Sometimes they actually don’t have a choice and they need to switch jobs ASAP to pay their bills — that’s slightly different.</p><p>If you can, my advice is to take your time and start the process when you’re on a high, not a low. You might say: oh, of course, that is common sense Cristina! But common sense is not that common, and people are impulsive and impatient (they want it all, they want it now, that type of thing).</p><p>Give yourself the time to think hard about why you want to do this and what you need, be patient until you’ll find the right fit for you. This means you shouldn’t settle and compromise on the things that are A MUST on your wishlist.</p><p>I have a bonus confession. I am one of those people who keep a very detailed tracker (in excel) when they start interviewing. My tracker includes things like: date when I applied (or been contacted), company, role, notes, links and most importantly status. This helps me keep on top of the process, chase people if I have to, see how long things take and also see at a glance what competing offers I might have. This usually depends on how well timed are the processes between companies and when I applied. I also like to see my personal CVR (total applied/offers received) only because I am crazy like that.</p><h3><strong>Interviews are a two-way street</strong></h3><p>As I mentioned earlier, interviews are super time consuming and stressful. A lot of people spend enormous amounts of time preparing to be grilled, ensuring they will have the perfect answers, do market sizing exercises fast and concise, crafting the perfect presentations and so on. What they forget to do is prepare to interview their interviewers. It’s in your best interest to interview them as much as they do. Otherwise, how are you going to know if the company is the right fit for you?</p><p>What I advise you to do is to go back to your wishlist and ensure you ask enough questions to figure out if the company ticks all the boxes. It’s both big things and small things that could make the difference. From how the product organisation is run and represented on the exec board to how much you like the people you meet along the way, it really depends on what you want.</p><h4>Here’s a few examples of things you can ask:</h4><ul><li>How the product teams prioritise their roadmaps or decide what to work on. This should give you an idea of the company culture, how top-down it is or not.</li><li>If there are any social events at the company. This should give you an idea of how much time people spend together outside work, if they like each others’ company.</li><li>How do they work with stakeholders? Presumably at some point you will be interviewed by a product manager and this will help you suss out if they collaborate with stakeholders or “follow requirements”.</li><li>What is the churn rate in the product team? Don’t be afraid of this question, it will give you an indication of how long people stay in the team and company and it’s a good proxy for how happy they are.</li><li>If it hasn’t been covered in your intro sessions, ask about the product vision. Not the company vision, but the product vision: a clear answer will be an indication of a well established product team within the organisation.</li><li>If it’s not part of the process: ask to meet the team or a few people for an informal chat. Nothing wrong with trying to suss out the vibe and what kind of people they are.</li><li>What they are working on right now and why? Well articulated and structured answers are a good indicator, especially the “why” part.</li><li>What tech stack do they use and what challenges they have in the engineering team? A super old tech stack, with no plans for modernisation is usually a bad sign for retaining engineering talent and shipping things slow.</li><li>Ensure you meet some people in the design team and try to understand how they work with product managers. You should be looking for signs of a healthy, collaborative way of working, not a “us against them” culture.</li><li>Do they have a career framework in place? If going up the ladder within the product team is something you care deeply about, ask if they have a framework in place for that.</li><li>Ask your manager how they like to manage people. It’s your chance to assess if you’ll get along with your future manager or not. This is one question, but please think hard about a few more for them. One of the main reasons why people quit their jobs is because they don’t like their boss. Try to see if you like them before you start the job.</li><li>What are the things they don’t enjoy at the company or things they would improve?. Maybe you’ll come across a theme and it’s something you’re running away from at your current company.</li></ul><h3><strong>Things to pay attention to</strong></h3><ol><li><strong>Tasks or presentations</strong> you’re asked to prepare: usually say a lot about the company and reflect how they work or the type of problems you will be asked to solve. For example, when I was interviewing for my role at Secret Escapes the product task was focused on making decisions based on sample data they sent upfront. They are an extremely data driven company, so that step of the interview reflected that.</li><li><strong>Some situational questions</strong> can reflect the problems they are facing and you’re asked to help them with some ideas. Example: if during a head of product interview you’re asked if you had to improve the ways of working with the design team, that smells like the company as some issues there and there might be some friction between the two teams.</li><li><strong>Key words like “digital transformation”. </strong>You will be hearing a lot that companies want to move to a microservices architecture, move to React etc. All really cool things, but if you do hear that, ask a few more questions about their plans to get there and if they need your help with that. It might not be something you’re interested in at all.</li><li><strong>Working hours:</strong> here it depends a lot on what you’re after, but let’s say you’re keen to work in a place with flexible working hours. When you go for a f2f interview, pay attention to how many people are around at their desks and ask questions about working arrangements. I’ve seen some companies don’t really walk the walk when it comes to flexible working hours or remote working.</li><li><strong>Negotiating your salary/ package:</strong> this is still part of your interview process. Let’s say it’s all rainbows and butterflies and it comes down to numbers. Personally, I really don’t like when companies negotiate pennies. If your request is reasonable and it’s not something you want to compromise on, then don’t! The interview process is more expensive for a company than it is for you. Think about all the employees involved in the process, how much their time costs, how many candidates they see and how long it takes (sometimes months for good product people).</li></ol><p>Thanks for reading! Let me know what you think and if you have any other tips on the topic.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83426cad06e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I faked it and I made it, now what?]]></title>
            <link>https://medium.com/@cristina.trifonescu/i-faked-it-and-i-made-it-now-what-d19dc3675020?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/d19dc3675020</guid>
            <category><![CDATA[productmanagment]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Thu, 13 Feb 2020 20:30:33 GMT</pubDate>
            <atom:updated>2020-02-13T20:30:33.955Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Your first 3 months as a product manager</strong></p><p>Hello again! You’ve done all the hard work, your research, due diligence, all the round of interviews, jumped through circles of fire, crazy tasks and you landed your first product role. Massive congratulations!!!! You started thinking like a product manager, now you have to act like one and deliver value!!!</p><h3>But how? What I read in books is not real life</h3><p>I had this problem in my first product role. I was lucky or smart (or both) enough to start a <a href="https://generalassemb.ly/education/product-management/london">product management course</a> with General Assembly more or less at the same time with my first product role.</p><h4>The course:</h4><p>The course was cleverly designed to put you in the mindset of a good product person and emphasised a lot on the validation idea I was talking about in <a href="https://medium.com/@cristina.trifonescu/how-do-you-become-a-product-manager-837009bb4e7b">my first article</a>. It was all about making sure you follow the right steps and research methodologies to avoid building throw-away work. One of the worst things that you could do is to build something your users end up hating or not using. Sometimes even with all the homework/ research done, they can still hate it, but that is a story for another time (yes, it happened to me too).</p><p>On top of that, the teacher was this amazing woman, <a href="https://twitter.com/RozemaryKing">Rosemary King</a>, who has an incredible background and vast experience across different industries and organisations. She was sharing with us her stories, learnings and awesome case studies whilst we had to practically work on our own ideas (or could bring products and ideas from work).</p><p>During the course I realised that my idea I was telling you about in <a href="https://medium.com/@cristina.trifonescu/how-do-you-become-a-product-manager-837009bb4e7b">my previous article</a> was a made-up problem that very few humans had, so I was learning a lot about validation and MVPs.</p><h4>On the other hand, at work…</h4><p>My life from 9–6 was at the complete opposite pole. The company had a very top-down culture and everything that we were aiming to build or already building was fabricated in someone’s mind without any validation. Coming up with solution and ideas is not a bad thing, but not validating them is suboptimal.</p><p>I was raising my thoughts with my manager at the time, but also with my teacher. I had a period when I thought that my experience is something that I have to accept because the more I was talking about it, more people were sharing the same thoughts. Looking back, of course it sounds silly for me to think that way. So what I am trying to say is that you might end up in a company that is not what you expected and that is fine. My advice is to learn as much as you can, focus on the positive things and have your interests at heart, especially when you are the beginning of your carrier. Not all companies have a good product culture and it might take some time until you find the right fit for you. Don’t despair!! (like I did for a bit)</p><h3>Your first 3 months</h3><p>Regardless of the kind of culture or environment you are in, I believe it is your responsibility to make the best out of any situations and your first few weeks in any company are pretty crucial. What was I suppose to do, cry my ass off and refuse to go to work? As temping as it sounded, that was not an option.</p><h4><strong>1. Be a sponge</strong></h4><p>I don’t mean that in the literal way (yuck!) Surround yourself with people who can help you. If you have the right attitude and good energy, most of the time people will want to help without you even having to ask (asking is obviously fine and advised). Someone way more senior than me from another team gave me a hand at the beginning and invited me to shadow his team ceremonies so I started to observe and learn how to interact and communicate with developers. Told you before that product people are nice.</p><p><em>Absorb all the knowledge!!!</em></p><p>I also started working with two senior UX and UI designers and I was constantly talking to them about more generic topics, outside our work . My aim there was to learn the basics, but also to absorb their terminology and language. As a product manager you don’t have to design things, but in order to work well with your team you need to speak the same language. Since then I’ve worked with many designers and I will share a few tips on that in another article.</p><p>At the end of the day, even if you’re not in the best environment or a cool tech startup or whatever your dream workplace is, you will always find smart people that you can learn from. Find them, hunt them and absorb their knowledge, stories and learn from their experience!!!</p><h4><strong>2. Learn how the business works</strong></h4><p>In your first months, please spend time shadowing different areas of the business and meeting the department heads.</p><ul><li>You will have to understand the high level tech architecture. Usually boxes and arrows on a piece of paper is a good way to learn about different systems you have and how they communicate between them. Ask your dev lead to give you a hand with this or the CTO. Or in a bigger organisation, someone with an architecture hat will be able to help.</li><li>Learn as much as you can about all departments in the business. I am not even joking. The longer you stay in a company, the more you will realise there are very few departments you don’t have to interact with. Top ones: customer services, marketing, operations, finance.</li></ul><h4><strong>3. Be a shadow</strong></h4><p>Learning about each department and how it works is fascinating, but you know what’s better than that? Seeing them in action. Ask to shadow some key teams to learn more about end-to-end processes. E.g.: if you work for a food delivery company, probably you have a website, an app where customers can order their food from. But this is only a part of the story. You have to learn how the food gets displayed on that interface in the first place, who’s taking part in that process? Most probably, they will use other systems on the way. The people who deliver the food are usually different than the ones who make it. What steps do they take and what technology do they use to ensure the food gets delivered as fast as possible to the person who’s ordering it? No one wants to eat cold food (yuck!).</p><p>You get the idea: see your colleagues in action as much as you can, shadow them, ask questions and <strong>where possible, try to do their role</strong>!!! Imagine how much more empathy you will have when you will be working on the technology for riders (people who deliver the food) if you already have a taste of how it is to be in their shoes.</p><h4>4. Meet your users</h4><p>It was about time Cristina to talk about our users!!! Here, it depends a lot on the type of product you are working on. As I said, your users can be your colleagues from other departments, in which case you can just go and talk to them, learn about their processes, biggest pain-points and where your team can help them. Or let’s say in an e-commerce business you could spend time listening to customer services calls, review existing data sources where users have left feedback, participate in focus groups or user testing sessions. They don’t have to be your own, maybe another product colleague is running some. Go and see who the real humans who buy from you are!!! Also learn about what they do from your analytics tools. They might say they love a feature you have, but the numbers might tell you otherwise (intriguing, right?).</p><h4>5. Learn the internal processes</h4><p>Unless you’re the first product hire and first tech team in the company, probably your team has some existing processes in place. Learn from your own team what they are and how they like to work, but don’t be afraid to go and shadow other teams too. See how they run their <a href="https://www.atlassian.com/agile/scrum/ceremonies">stand-ups, team retros, refinements etc</a>. Also, if you’re new to this amazing tech/ product world don’t be afraid to ask a lot of questions, especially around slang “scrum, kanban, agile, lean UX, design thinking, workshops, discovery, Jira”, basically anything that you hear and have no idea what it is. Don’t pretend! It’s worse if you do that and then start using the words wrongly (imagine that!!).</p><h4>6. Learn how the business makes money</h4><p>We need money to keep the lights on regardless of the sector that you work in. Learn about how the business makes money from a finance perspective. If you have a finance director or a CFO I guarantee they will be super happy to hear you’re interested in their area.</p><p>WOW, your first 3 months sound intense and we haven’t even spoken about the fact you will have to actually produce some work, not just shadow colleagues and talk to your users.</p><p>In the next article I want to share with you the baptism of fire I got when I started working at <a href="https://octopuslabs.com/">Octopus Labs</a> (an organisation with a good product culture) and talk about what mistakes to avoid and how you can juggle it all.</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d19dc3675020" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with a complex medical case]]></title>
            <link>https://medium.com/@cristina.trifonescu/dealing-with-a-complex-medical-case-e8d5a46a5e42?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8d5a46a5e42</guid>
            <category><![CDATA[travel-insurance]]></category>
            <category><![CDATA[medical]]></category>
            <category><![CDATA[diagnosis]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Sun, 09 Feb 2020 21:42:57 GMT</pubDate>
            <atom:updated>2020-02-09T21:42:57.145Z</atom:updated>
            <content:encoded><![CDATA[<p>Story and advice from the caregiver perspective</p><p>Hello again! I won’t be writing only about my work, but also about all things I am passionate about and most importantly, things I’ve learned that could help others too.</p><p>I have been lucky enough throughout my life and haven’t really dealt with any complex medical situations in my extended family. This was until a few months ago when my partner and I (currently living in London, UK) had to call the ambulance because he had a bad reaction (whole body shaking kind of thing) from a prescribed medication. It was actually the first time I went on an ambulance with someone close to me. The whole experience was a bit weird because they didn’t actually help with anything and sent us home thinking it was just an intolerance to that medicine. We both went to work the next day as if nothing really happened.</p><h4>Shit hit the fan on a long haul holiday - things to know when travelling</h4><p>So we got on with life, we had holiday planned, which we were super excited about and went to, what was supposed to be, a dream trip to the Maldives. Only that it turned to be the trip from hell. It started with more reactions on the flight to Male, we eventually made it on the island and after calling the resort doctor four times that night we eventually took an emergency sea plane to go to the hospital the next day. Now here’s where the advice starts:</p><ul><li>make sure you have travel insurance (obvious one).</li><li>make sure that you have a local number and internet connection (buy a local sim card as soon as you land)</li><li>before you go to the hospital, call or email the insurance provider and check if they work with the hospital you’re planning to go. You will most probably be referred to a private hospital.</li><li>take photos of all the things you have to pay for when the medical situation starts (sea plane/ any transporation receipts, new accommodation if you need it, food receipts etc). You will need them later.</li><li>make sure you have enough money in your bank account. This is an interesting one because if you have something straight-forward like, let’s say a broken leg, the insurance will give you the green light for the cover pretty fast. If not (like us), they won’t say yes until you prove it was not an undeclared pre-existing condition. So you have two options here: you either pay and argue with them later or you come prepared with 2 years worth of medical history from your GP (that’s what they asked us for on a Sunday afternoon).</li><li>knowing what “enough money” means is hard because it depends on where you are and what you have. The hospital did not give me any prices for anything upfront and the only thing I could find online, on Twitter, was a medical bill from someone who had a brain surgery in the same hospital. So when you’re in the hospital, maybe start messaging a few friends and family to be 100% sure you are covered in case you need more money. For the record, a full day in <a href="http://www.adkhospital.mv/">ADK Hospital Maldives</a> with pretty standard checks, blood tests and medication was around $1000 (USD).</li><li>make sure you get enough sleep. As you can imagine, we were very tired and our decision making capabilities were a bit fucked, so looking back we did the right thing to find a hotel next to the hospital to rest a bit and ensure he was out of the woods after spending 10 hours in the hospital (spoiler: we weren’t, we had to go back the next day).</li><li>when in the hospital, question all substances that go in your body: it is very important for you to be aware of what’s happening to you and why they think that what they are giving you is good for you.</li><li>talk to the doctors with confidence. If they say something like “this test results is a bit elevated” don’t take that for an answer: ask what the value is, what is the normal interval and what are their hypotheses.</li><li>take photos of every single medical paper they give you: blood tests, scans, X-Rays, I seriously mean anything.</li></ul><p>After a lot of drama and help from an army of people (because we couldn’t change the return flights on our own as they were part of a package holiday), we safely arrived back home, only to end up in A&amp;E again the night we landed.</p><h4>When you think things can’t get any worse … trust me they can</h4><p>Now this is where things really started to go south. I thought that our ruined Maldives holiday was bad, but I had no idea what was coming up. To keep the story focused on key things that could help others I won’t go into too many details about his medical situation, but the summary of symptoms were: liver enzymes were 5x elevated, some medicine (completely unrelated to each-other) was giving him bad muscular spasms, some foods were making his throat swell (so he couldn’t breathe) and he also had some weird rashes on his chest and cold hands when he was eating certain foods (again, no connection between them) and after two months his sight started to get affected too (blurry vision).</p><p>No doctor could link the symptoms under one diagnosis, not even two or three. With the exception of the liver tests, every single test that he did was coming out clean. We saw over 40 doctors in 3 months from the following specialties: gastroenterology, allergy and immunology, infectious disease, internal medicine, rheumatology, neurology, endocrinology, ophthalmology, parasitology (I am pretty sure I am forgetting some).</p><h4>It was like living an episode from <a href="https://en.wikipedia.org/wiki/Gregory_House">Dr. House</a>, but Greg was on holiday</h4><p>Some of the advice from the traveling section will be carried here as well.</p><ul><li>make sure you take photos of everything: all test results, scans etc.</li><li>print them and start making your own file. This will come handy in case your file is big and complex like ours. Most doctors are pretty old school and like to read things on paper.</li><li>when you tell your story make sure you disclose all details, but keep things focused on your symptoms.</li><li>be careful in A&amp;E departments/ emergency rooms. Those are busy places, where they won’t have time to hear your full story in case it’s super long. So keep your story concise and don’t forget key details like allergies and intolerances. Write them in your phone, which you most probably you’ll always have with you.</li><li>create a support system. Personally I told all my family and friends what we were going through. It was my preferred approach that paid off. We got help (accommodation, food etc) and advice (doctors recommendations, intros to friends of friends) from strangers or acquaintances who became our friends after and to whom we will be forever grateful.</li><li>don’t let doctors treat you like children. Same advice about talking with confidence: ask for exact values of test results, what they mean and what other hypotheses they have.</li><li>sometimes you have to be the one to push the doctors really hard. None of their previous patients had your symptoms and that sucks, but doesn’t mean they have to give up on you.</li><li>create personal relationships with doctors you can trust and try to have one or two that can analyse you holistically. What I mean by this is to have someone you can trust that can review your whole file and medical history because the problem with modern medicine is that is very compartmented.</li><li>do not lose your grit. If the medical system in which you’re in is not giving you what you need, find another one. We eventually ended up going for all tests in another country (Romania) which was 10x cheaper and most importantly 10x faster.</li><li>do not take “you’re fine” for an answer, even from prestigious doctors. If they haven’t seen something like this before, don’t have an answer for you and prefer to say “you’re fine” just because you look OK on paper, just run away. <strong>Find the kind of doctors that say “I don’t know what’s going on with you, but I will find out or help you find out”.</strong></li><li>a hard one, but don’t be scared of things you never heard before. Medical jargon is crazy, but always do your own research. During these 3 months he got tested for the wildest things ever, including Lupus (if you watched Dr. House you will know it’s never Lupus- that was correct in our case too).</li><li>last, but not least, please seek professional psychological help as soon as you realise you need it. Going through medical issues is very hard, stressful, draining and as much as your friends and family love you, they most probably are not equipped with what you need in these situations.</li></ul><p>Thanks for reading! I wish that no one will ever need this kind of advice, but if you end up in this situation, hang in there, stay strong and trust your instincts, “this too shall pass”.</p><p>Special thanks to an army of people: our families, friends (special shout out to the Dancu family who hosted and fed us for weeks), <a href="https://www.reethifaru.com/">the Maldives resort</a> (dreamy place and employees who handled the situation in the smoothest possible way) &amp; <a href="https://www.secretescapes.com/">Secret Escapes</a> (company where we got the Maldives package from, but also my employer who understood the situation and allowed me to work remotely for a long time whilst we were in an out of hospitals).</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8d5a46a5e42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you become a product manager?]]></title>
            <link>https://medium.com/@cristina.trifonescu/how-do-you-become-a-product-manager-837009bb4e7b?source=rss-3aa96da2ad03------2</link>
            <guid isPermaLink="false">https://medium.com/p/837009bb4e7b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <dc:creator><![CDATA[Cristina Trifonescu]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 22:41:44 GMT</pubDate>
            <atom:updated>2020-02-06T22:42:47.921Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>You start thinking like one and the rest will follow.</strong></h4><h3>Finding out the job exists</h3><p>A few years ago I was pretty bored in my job doing repetitive processes and tasks. In my spare time I would scribble wireframes to solve problems, only that: 1) I had no idea they were called wireframes and 2) the problems I was solving were imaginary, I had no idea if real humans had them or not. Someone pointed out that if I enjoy doing the above, probably I would enjoy a role in product management. Problem number 3) no idea what that was either.</p><p>This was enough for me to start reading about product and getting super excited about the idea of solving problems, doing different things every day, talking to real humans about how technology can help them. I imagined this life where one day you would be working closely with developers, UI, UX designers, looking into data, collaborating with commercial peeps to achieve goals (my first product roles were not quite that, but we can talk about it another time).</p><h3>Ok, cool we already know what product management is, what next?</h3><p>Probably if you’re at that stage in your life you’ve already realised there is no formal education for product management. There are a lot of courses, but you’re not sure which one is right for you and probably you’ve already asked yourself “how did other people do it?”.</p><p>That is exactly what I started with: trying to find the answer to that question. I started reaching out to complete strangers and asked them for their time to walk me through their journeys. Some were in person over coffee, some on calls, some in the building where I worked at the time and some even invited me to shadow them in action. <em>Don’t be afraid to ask!!</em> You will be pleasantly surprised that most of them will agree even if they don’t know you. I have a hunch that this is because majority of good product people have a lot of empathy.</p><h4>Top tips for learning how others got into product:</h4><ol><li><strong>Are you sure you know what you want?</strong></li></ol><p>Before asking for their time, think a bit about what you are going to ask them. You don’t want to waste anyone’s time, including your own. So think about what you want to get out of that meeting/intro/chat. At the beginning I kept things high level and wanted to learn about different team structures, what kind of stuff they work on and learn about how they landed their first product role. That was my goal: find out how to land a job in product.</p><p><strong>2. Have you thought about the questions you’re going to ask?</strong></p><p>Draft the questions, but don’t stick to the script. If you’re not sure if product is the right fit, you may want to ask them about their own motivations. “WHY?” is one of the most powerful questions you will be using in you product career. Ask about their challenges, ways of working with their teams, how was it for them at the beginning, best advice they can give you. I mentioned before, product managers are usually nice, chatty people, so the conversation should flow, don’t stick to a script and don’t be shy.</p><p><strong>3. Sell yourself. Why should they meet you?</strong></p><p>Yes, sure, we are nice people and we want to help out, but time is limited for all. So make sure your story represents you, be concise when you introduce yourself, but also make it personal and explain your motivation and why you want to meet them too. How do you think they can help. This goes back to point 1. If you have an idea of what you want to get out of the chat, say that upfront so that they can assess if they can help or not. Sometimes they can even prompt you to another colleague of theirs and that’s totally cool. Imagine if they are in a more systems/ back-end role and you’re super passionate about user experiences, probably they won’t be the right fit anyway.</p><p><strong>4. Who do you want to meet?</strong></p><p>This is a good segway from point 3- deciding who you want to reach out to.</p><p><strong>No idea what’s out there?</strong> If you don’t know much about different areas of product or types of product, then I recommend reaching out to someone a bit more senior (in experience, not necessarily years), maybe someone that has experience across different industries. Probably they have seen a lot by now and depending on what you’re passionate about at the beginning they can guide you.</p><p><strong>You already love some products: </strong>If you have some favourite products in mind or amazing companies you dream to work for, go ahead and reach out to those peeps and see what their journey was and what it takes to work on your dream product or at your dream company.</p><p><strong>You really like them as humans: </strong>their CV sounds awesome and you saw them at a few conferences, talks, YouTube videos etc and you might see yourself being where they are (or higher) in some time. Again, reach out and tell them why you want to meet them and how you think they can help you.</p><p>I reached out to people from all 3 categories, you don’t have to stick to one.</p><p><strong>5. Where do I find these product people?</strong></p><p>EVERYWHERE, I promise! You just have to get out of your shell and reach out, go to events, conferences, volunteer for organisations like <a href="https://www.mindtheproduct.com/">Mind the Product</a>, stalk them on LinkedIn. I reached out to people from my own company, shadowed them, to friends of friends, but also complete strangers, even from other countries. Let’s say your favourite company is <a href="https://www.boringcompany.com/">The Boring Company</a>. What is stopping you from reaching out to people who work there, even if they are across the ocean from you?</p><p><strong>6. What if they say NO or ignore me?</strong></p><p>IT’S FINE. Be prepared for that. This is only the beginning and until you land your first product role you are going hear NO a lot or, radio silence. That is totally fine and totally normal. DO NOT GIVE UP!!! Just keep swimming!!! (<a href="https://www.youtube.com/watch?v=0Hkn-LSh7es">Finding Nemo reference</a>)</p><h3>I met a bunch of people, now what?</h3><p>The combination of articles &amp; books you read, videos you watched, people you’ve met should, by now <strong>give you an idea of how a product manager thinks </strong>and what the role entails. You can go back to your CV and see if there’s any experience you have that is close to the stories you heard or the skills these people have. If not, you can start working on that.</p><p>Going back to my story, once I did all the above, I was very transparent with my manager at the time and told her about my hopes and plans. She actually helped me a lot in giving me the opportunity to work on projects that would bring me closer to product people in my organisation. e.g.: apps and new services launches, basically a lot of cool things that they were building and needed marketing support for. After doing that for a while I WAS HOOKED, my CV looked better and knew that product management was 1) awesome in real life, not just on paper and 2) product management was definitely for me.</p><h3><strong>You’re super pumped by now and you want to start applying for jobs</strong></h3><p>Now this is where the hard part actually begins. Because without any experience in product you will hear a lot of NO and your energy and enthusiasm will start to plummet.</p><p>STAY POSITIVE, BUBBLY and CONFIDENT. Your attitude and a bit of experience is all you’ve got at this point. If you lose that too, you’re doomed. I read a lot of articles about “fake it till you make it in product” and that is so true. You have to think like a product manager even before you start being one and be a great storyteller. Your motivation, your story and your passion is what is going to help you land that first product role.</p><h4>Things to know if you want to start thinking like a product manager:</h4><ol><li><strong>Validate hypotheses &amp; Product Market Fit</strong>. Massive buzzwords, but what it really means is that you question the problem you’re trying to solve. Is it a real problem?? How many people would benefit if you were to solve this?</li></ol><p><em>Imagine how a new food delivery services was born. A lot of them probably already existed, so what are you bringing to the table that is special, what problem are you solving and how big is the opportunity if you solve this problem?</em></p><p><strong>2. Testing and validating, building your MVP (minimum viable product)</strong>. Buzzwords again, here is all about identifying what is the minimum thing you can build/fake (a solution for your problem) that you can validate, test if it could work or not. Does it solve the problem?</p><p><em>At some point an MVP for a food delivery service was a human running around with a shopping list on a piece of paper. And that turned into something like </em><a href="https://postmates.com/"><em>Postmates</em></a><em>.</em></p><p><strong>3. Wireframing &amp; Storyboarding. </strong>Stop with the buzzwords already…Don’t be afraid to take a sharpie, whiteboard and lots of sticky notes to draw the user journey end-to-end. This is not only about your product, but also about your users, their needs, how and where they will interact with what you will build.</p><p><em>You’re not only thinking about.. let’s say a food delivery app and how it could look and what features it will have. You have to take a step back and see the big picture, most of the time you have to think about end-to-end processes, not just cool tech and pretty designs (that matters too, of course).</em></p><p><strong>4. Your engineering team is one of the most expensive resources you have</strong></p><p><em>Cherish them and collaborate with them as much as you can, but please keep in mind that before the idea turns into the first line of code, you have to be damn sure that is the right thing to do. Prototype, prototype, test, test, test upfront (with real humans where possible) to make sure you utilise your limited resources wisely.</em></p><p><strong>5. Know your numbers</strong></p><p><em>In my view, any good product manager has to be good with numbers. Both confidence in crunching numbers and understanding the basics of how a business runs and how they make/ could make money.</em></p><h3>You landed your first role and you’re absolutely terrified</h3><p>You did all the hard work, you kept positive, said all the right things and through a miracle they hired you (“oh wow, they must really like me” says a voice in your head).</p><p>Now it’s your first week and realise they are expecting you to contribute from day one and you think “What the f*** have I done? I don’t know what I am supposed to do”. I promise another article on this… maybe I’ll call it “I faked it and I made it, now what?”</p><p>Thanks for reading! Let me know what you think.</p><p>Cristina</p><p>xx</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=837009bb4e7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>