<?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 Julia M. Godinho on Medium]]></title>
        <description><![CDATA[Stories by Julia M. Godinho on Medium]]></description>
        <link>https://medium.com/@juliamgodinho?source=rss-8cf4f23db592------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-XLKp4DizaHKmnTV7fl4eQ.jpeg</url>
            <title>Stories by Julia M. Godinho on Medium</title>
            <link>https://medium.com/@juliamgodinho?source=rss-8cf4f23db592------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:24:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliamgodinho/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 I wish I knew when I started working as a Product Manager]]></title>
            <link>https://medium.com/swlh/things-i-wish-i-knew-when-i-started-working-as-a-product-manager-66ce339bbcb8?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/66ce339bbcb8</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 16:38:40 GMT</pubDate>
            <atom:updated>2022-02-15T16:38:40.466Z</atom:updated>
            <content:encoded><![CDATA[<p>I often get asked what I wish I knew when I first started on my journey as a Product Manager.</p><p>Every Product Manager has a different story as to how they got into the role as there isn’t one defined way to do so. When I first got a job as Product Manager I hadn’t worked in tech before, let alone heard of the role before! I was very lucky to have got the job, but I felt like I had been thrown into the deep end. I had to get up to speed very quickly — not just because I was working in a start-up where everyone did a bit of everything, but also as I was expected to hit the ground running.</p><p>Despite having started from scratch, looking back, I don’t think there are things that I necessarily wish someone had warned me about. Which isn’t very helpful for the purposes of this post, I know! Let me explain… To me, Product Management is an empirical job — you learn by doing. Perhaps that is why there are so many different flavours of Product Management, but it’s also what excites me as the possibilities are endless!</p><p>For people wanting to get into Product Management, here are six lessons I’ve learnt along the way that have defined how I work:</p><h4><strong>1. Learn some frameworks, but don’t be prescriptive</strong></h4><p>It’s a running joke that Product Managers love a framework. Which is true! However, they aren’t the be-all and end-all. Frameworks provide us with ways of looking at things differently and organising our thoughts, but they should be the start of a conversation. They are especially important when you are starting out in your career as you consolidate what you see in practice, but the important thing is that you aren’t prescriptive with your use of frameworks. Learn what framework, tools, or key theories can help progress you forward at any stage of the product development lifecycle (e.g Cynefin, Lean canvas, Opportunity Solution Tree, HEART — <a href="https://www.product-frameworks.com/">CHECK SOME MORE OUT HERE</a>), but then break the rules and create your own!</p><h4><strong>2. Lead with context, not control</strong></h4><p>The very well-known mantra of Netflix, “lead with context, not control”, couldn’t be more representative of the role of a Product Manager. We are not CEOs or project managers, although you hear this a lot. It is the job of the Product Manager to provide context, join the dots — especially as we sit in the intersection of different parts of a business. You have to do this through inspiring and empowering your team, not by trying to control it. This is something that you need to actively exercise, as I believe that trying to control a situation is easier than leading with context as you need to put much more effort into it. However, in the end, your team and product will be much more successful as a result of your context.</p><h4><strong>3. Make just-in-time decisions</strong></h4><p>You may have heard of the Just-In-Time in the context of the Toyota Production System, a manufacturing philosophy that aims to eliminate waste and create the most efficient ecosystem possible. This way of thinking can also be applied to how we work in product, and often manifests itself in discussions debating “Agile vs Waterfall” ways of working. For me, it means deferring decision-making until the last responsible moment, as it’ll be at that moment that you will be in the best place to make the most informed decision as your knowledge about a given thing will be higher than ever. Let’s say your team is going to kick-off a new project. In a complex environment such as product development where there could be multiple ways to answer the same question, you can’t answer everything upfront. As your project progresses, so will your understanding of the context; you’ll be better equipped to make decisions as the time progresses. For this reason, don’t feel like you need to have all the answers upfront. Instead, make a note of them and answer them just-in-time. This can be unnerving, but Product Managers must learn how to be comfortable with ambiguity, and making swift (but informed) decisions.</p><h4><strong>4. Don’t create extra work for yourself, focus on the biggest impact</strong></h4><p>As Product Managers, our minds are always buzzing with ideas and things to do. This can quickly make things overwhelming. Limit your work in progress and focus on what will bring the biggest impact for you, your team, or your product. Focus on the one thing that matters, and forget all the thankless tasks, or the extra work you think you need to do but no one has asked for — I can thank my therapist for this lesson! Once you’ve determined what will create the most impact, another thing that helped me overcome the feeling of being overwhelmed was thinking about the distinction between “good”, “good enough” and “best”. Strive for “good enough” as it’ll be easier to get started and make progress. If you aim for the best and only stop when you think you’ve achieved perfection, the end will seem unattainable. The <a href="https://www.onepageonehour.com/">ONE PAGE/ ONE HOUR PLEDGE</a> has helped me with this: “I will spend no more than one page and one hour working on any deliverable before sharing it with my colleagues”. Get feedback early and often, and you’re “good enough” will naturally become the “best”.</p><h4><strong>5. Keep it simple</strong></h4><p>My personal mantra is “Keep it Simple”. This has not only served me well in my personal life, but mostly in my day-to-day as a Product Manager. There’s not much to say here other than resist the temptation to overcomplicate things. Don’t be afraid to always question yourself and others around you whether you are keeping things simple, even if you’re halfway through something. This isn’t a simple habit to develop (pardon the pun), but it’ll pay off in the long-term.</p><h4><strong>6. Be positive!</strong></h4><p>This was perhaps the hardest thing for me to learn, as I didn’t want to come off as insincere: sometimes you don’t feel positive, and that’s ok! However, leadership and evangelism are key skills of a Product Manager. It is important that we embrace things with a positive mindset so that we can motivate and inspire our team; we must lead by example. There are different ways you can bring positivity in what you do: storytelling (take people on a journey, starting with an inspiring vision — use this when crafting your product strategy for example); team socials (to energise and bring your team together); and fail parties (a little celebration of a recent failure with your peers so you can learn to see the positive even in adverse conditions). Remember why you’re here in the first place and let your passion for Product shine through in what you do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGMhzNxzQeGvXJfrM2R7ZQ.jpeg" /></figure><p>These reflections are a result of hindsight, and for that reason I don’t think I would’ve done anything differently when I first started my journey as a Product Manager. You’ve just got to trust your instincts!</p><p>Lately, I’ve spent a lot of time thinking whether awesome Product Managers share characteristics in common, regardless of how they got into the role — maybe this could help aspiring Product Managers better prepare for what’s to come. This is something to address in another post, so for now I’d say that it’s important for aspiring Product Managers to always be curious, think creatively, and be determined. And of course, enjoy the journey and have fun!</p><p><em>Originally written for the </em><a href="https://www.blackvalley.co.uk/post/things-i-wish-i-knew-when-i-started-working-as-a-product-manager"><em>Black Valley mentoring programme</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66ce339bbcb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/things-i-wish-i-knew-when-i-started-working-as-a-product-manager-66ce339bbcb8">Things I wish I knew when I started working as a Product Manager</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking your career growth: three steps to getting where you want to be]]></title>
            <link>https://juliamgodinho.medium.com/hacking-your-career-growth-three-steps-to-getting-where-you-want-to-be-dfb0c24db63?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfb0c24db63</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[goals]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Fri, 11 Jun 2021 15:45:52 GMT</pubDate>
            <atom:updated>2021-06-15T00:56:34.334Z</atom:updated>
            <content:encoded><![CDATA[<p>As someone whose career path has been anything but linear, career progression and self-development are things that I’ve given special attention to. I am passionate about this topic because it’s relevant to us all, regardless of our present or future aspirations.</p><p>This post will focus on frameworks, tools and techniques, rather than topics such negotiating pay rises or even looking into specific role frameworks (which are all really important) — I want to focus on more practical steps that can help regardless of your role, position, or where you want to get to.</p><p>Before I delve into the above, I wanted to do a quick poll:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.pollsights.com%2Fc%2FZevGzd&amp;dntp=1&amp;display_name=Pollsights&amp;url=https%3A%2F%2Fwww.pollsights.com%2Fc%2FZevGzd&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=pollsights" width="800" height="950" frameborder="0" scrolling="no"><a href="https://medium.com/media/74f8913f8b3beb83b417f820f19842f0/href">https://medium.com/media/74f8913f8b3beb83b417f820f19842f0/href</a></iframe><p>Having come from a non-tech background before working as a Product Manager, I’ve felt a mixture of all of these. So the desire to learn, grow and progress once I got into tech is something that has been very present since the beginning. This particular subject resonates with me because many times in my career I haven’t felt supported as I thought I should’ve been, so that made me take a DIY (do-it-yourself) approach to career development.</p><p>With the steps that I’ll go through today I have been able to change careers, beat impostor syndrome, progress in my role, take on more challenges and responsibilities, and even negotiate pay along the way. I feel that if I hadn’t taken the time to do this, I wouldn’t have progressed as much as I did, or even be as proud of what I have achieved than I am.</p><p><strong>What I want to convey here is that personal development isn’t synonymous with performance reviews, and it’s up to you if or how you develop and progress in your career.</strong></p><h3>What I’ll cover</h3><p>I’ll be dividing this post into three steps:</p><ul><li>Where do I want to be?</li><li>Where am I now?</li><li>How do I get there?</li></ul><p>I’ve found at times thinking about career development or progression can be overwhelming, especially when you already have lots going on at work. So, as a rule of thumb, I like to keep things simple and attainable. And that’s what I sought to do with my approach to hacking my career growth.</p><p>I’ll be exploring evaluating where we want to get to, where we currently find ourselves, and how we can get to where we want to be. This may sound cliché or very simplistic — and that may be true — , but these steps are effective; take from it what you will, and I hope that there are some nuggets of inspiration along the way.</p><h3>Where do I want to be?</h3><blockquote><strong>What did you want to be when you were growing up?</strong></blockquote><p>I want to start with this question, because it’s likely that your aspirations have changed (unfortunately, I haven’t turned out to be the archaeologist-fashion-designer that I dreamt of). But this is OK, because things change.</p><p>So, when thinking about setting a career goal, the best place to start is where you currently are in terms of wants and needs — whether the goal is to get a promotion by the end of the year, or be on a 10-year plan to become the next CEO at your favourite company.</p><p>The first step to hacking your career growth is asking yourself: <strong>where do I want to be?</strong> Two things are important to answer here are “why?”… and “why?” again. Taking time to articulate the why behind your goal is important to help you focus and stay motivated. I cannot stress this enough because if you, like me, can at times feel demotivated, having a goal at the back of you mind will keep you going even in the hardest of times.</p><p>So, where to start? You may already have a clear direction or goal in your head. If so, great! But if you don’t, look for some inspiration.</p><p>This is where frameworks come in (as a Product Manager I couldn’t <strong>not</strong> bring them up!). Frameworks will help you articulate your goal — which can be role-specific or personal. If you want to choose a career progression-oriented goal, you may want to go with a competency or role-based framework to help you step up to the next level. Or, for example, if you are looking to work on your leadership skills, you may want to find a more in-depth skills framework that breaks down the different facets of leadership.</p><p>The frameworks and tools below will help you articulate your goal:</p><h3>Ikigai</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*xJ1XTs-41jtv9AJy0YFWCQ.png" /><figcaption>Source: Forbes.com</figcaption></figure><p>The Japanese concept of Ikigai translates into “reason for being”, and postulates that the balance is achieved at the intersection where your talents and passions meet with the things that the world needs and is willing to pay for. This is an ideal framework to use if you’re not sure where to begin, or want to go back to the basics. Just take this framework and fill it out with as many answers as possible, you’ll start seeing some patterns, combinations or alternatives which will spark some interesting thoughts or revelations along the way.</p><h3>LinkedIn</h3><p>Yes, LinkedIn. This one if for the curious professional stalkers. You may lack frames of reference as to what is possible in your career, or you just may not have seen what people in the same position as you have the potential to do. So, that’s why I love looking at people’s profiles on LinkedIn; you can see where they started and under what conditions, and where they got to, with all the juicy journey in between. What I also like looking at is how they communicate what they did and the value they created. This is a really helpful skill when articulating your goals.</p><p>Have a look on LinkedIn. Look for people with similar roles, but different journeys: how did they get to where they are, how do they talk about their achievements? Look for people at the top of their game, what makes them stand out? What inspires you?</p><h3>Moving Motivators</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*-n6FDw04C9rWN5Bmn_b6lA.png" /><figcaption>Source: Management 3.0</figcaption></figure><p>Moving Motivators is a Management 3.0 tool. It is used to reflect on your motivations. I personally use this one a lot because it affords me the opportunity to dig a bit deeper beyond my day-to-day role.</p><p>There are 10 pillars, each of which has a definition, as listed below, which encourages you to reflect on how you are currently feeling towards each one.</p><ol><li><strong>Curiosity:</strong> I have plenty of things to investigate and to think about</li><li><strong>Honour:</strong> I feel proud that my personal values are reflected in how I work</li><li><strong>Acceptance:</strong> The people around me approve of what I do and who I am</li><li><strong>Mastery:</strong> My work challenges my competence but it is still within my abilities</li><li><strong>Power:</strong> There’s enough room for me to influence what happens around me</li><li><strong>Freedom:</strong> I am independent of others with my work and my responsibilities</li><li><strong>Relatedness:</strong> I have good social contacts with the people in my work</li><li><strong>Order:</strong> There are enough rules and policies for a stable environment</li><li><strong>Goal:</strong> My purpose in life is reflected in the work that I do</li><li><strong>Status:</strong> My position is good, and recognised by the people who work with me</li></ol><h3>Skills frameworks</h3><p>There are frameworks that focus on skills and competencies rather than roles or responsibilities. The <a href="https://www.mindtheproduct.com/wp-content/uploads/2021/02/Mind-the-Product-Skills-Assessment-PDF.pdf?utm_source=Mind+the+Product+Newsletter&amp;utm_campaign=172df7fbbc-EMAIL_CAMPAIGN_2021_01_26_07_27&amp;utm_medium=email&amp;utm_term=0_babd9cfe61-172df7fbbc-110340231">Mind the Product’s Product Skills Assessment</a> is an example of this; it lays out general skills that should be developed if you work in product regardless of your role, and it’s broken down into “human” and “technical” skills.</p><h3>Career framework</h3><p>Different to the skills framework, a career framework focuses more on specific roles and responsibilities, describing the different levels of a profession in more detail. For example, if you are a Product Manager, you might see the different expectations of the different levels, such as Associate PM, Mid-Weight PM, Senior PM, Group PM, and Chief Product Officer.</p><p>Many companies will have their own career frameworks which make it easier to guide yourself with, and really understand what you need to do to get to the next level. However, some companies don’t have this, but you can still get some inspiration from other companies and use them to think about your own personal development; have a look at <a href="http://progression.fyi/">Progression.fyi</a>, a comprehensive repository of open-source career frameworks from tech companies that you can take a look at.</p><p>Those were some frameworks that you can use to think about where you want to go. It is also helpful to <strong>set a timeframe</strong> for yourself too, so that you have something to strive towards. This will depend if it’s a short, medium, long-term, or even a lifetime goal! Think about what you want to accomplish in the next 6 months, 1 year, 5 years… write it down on a piece of paper and then come back to it after you’ve gone through the three steps in this post; think whether anything has changed or surprised you.</p><p>And one tip: your goals are great to keep you focused and moving in a direction, but don’t worry if things change, just repeat the process based on your current situation. It’s an initial goal, so don’t put yourself down if things change. As I have to constantly remind myself… be kind to yourself!</p><p><strong>In a nutshell, thinking about where you want to be is the first step to hacking your career growth, and using a framework helps you draw up points of reference that will help you get there. Which takes me to the next step…</strong></p><h3>Where am I now?</h3><p>The next step is to ask yourself: “Where am I now?”.</p><p>Once you have a framework, you’ll have your frame of reference. So, the next step is to figure out where you currently are compared to where you want to be. Again, this is really simple, but the key is to be candid with yourself. You are doing this to highlight where you’ll focus your attention next, and not to put yourself down.</p><p>The following techniques will help you benchmark yourself in relation to your goal:</p><h3>Sliding scale</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*de1mwh-XH9mNwriSrtTsqw.png" /></figure><p>On the sliding scale, you determine the two sides of the spectrum; it can be 0 to 5, or “needs a lot of improvement” to “awesome”. You can get creative here. The objective is to set diametrically opposed markers, and then place yourself within that continuum.</p><h3>Spider diagram</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*_-EYRMo_etwYcjvKTbjtPQ.png" /></figure><p>A <strong>spider diagram</strong> is another great way to visualise your current situation, and provides a more holistic view of your capabilities. Decide what skills/competencies/criteria you’ll use (the example above uses the Mind the Product framework), and then plot them on each axis. The middle where the lines all meet is 0, and the top of each line is 5/10/100. Again, think about where you sit in relation to each of these lines. Then join up the dots; it will form a shape (radar chart) you can use to better measure your progress with the passing of time — the example above demonstrates how you can overlay your first assessment with the second to see how you’ve developed.</p><h3>Career journal</h3><p>Lastly, I wanted to bring one that I use myself. I’ve called it <strong>Career Journal</strong>, and it uses the Moving Motivator framework. I’ve created a <a href="https://www.notion.so/Career-journal-template-91055918da9942e88ed579801e5a3291">template on Notion</a> that you can duplicate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IQ-QV5Yf2cpH8_2AnLSvaQ.png" /></figure><p>I’ve listed out each motivator, so I can then assess myself on a scale from 0 to 3, and also describe why I’ve given myself that score. Next, I can add a description of what success would look like for that motivator in 6 months’ time. This has been instrumental for me as I have to properly articulate the “why” of my score, which is also interesting to revisit later on as I then see how far I’ve come.</p><p><strong>The critical point here is, regardless of the technique you decide to go with, you should take time out to have that open, honest conversation with yourself. The point of this exercise is to identify your areas for improvement, and even spending 30 minutes doing this will give you a boost and a sense of direction.</strong></p><h3>How do I get there?</h3><p>Now, it’s time to ask yourself: “How do I get there?”.</p><p>Take a look at the benchmarking you’ve just done. What jumps out at you? Are there any obvious areas for improvement? or ideas you have to get better at each of them? List them out on a piece of paper.</p><p>Next up, for each area for improvement, take some time to think about <strong>what’s holding you back</strong>. This could be one thing, or a list of things, but it’s important to take some time to take stock of the things that can get in your way so you can mitigate them down the line.</p><p>It’s nowtime to prioritise these, so I wanted to bring some of my favourite techniques:</p><h3>Dot voting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*F-J9H_bkkITsMQai7aTTTg.png" /></figure><p><a href="https://gamestorming.com/dot-voting/">Dot voting </a>really forces you to prioritise. Give yourself a limited number of dots (let’s say 3), and vote on the ones that you consider to be top priority.</p><h3>Impact vs. Effort matrix</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*cXKfHTohMugbDewQj5vgCg.png" /></figure><p>This is a variation of the Eisenhower Matrix. Write each blockers, ideas, or tasks on a piece of paper, and place them on the matrix along each axis. First, think about the impact that this will have on your life if you solve it (or finish it), and then think about the effort required to do this. You’ll then have each piece of paper on a quadrant on the matrix. Start with the quick wins, and then go on to the big bets which will require more planning or breaking down. Don’t focus too much energy on the ones below, as they don’t bring as much value to your life.</p><h3>Circles and soup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*xrdS2Z1rRp2cn7_2z10YQg.png" /></figure><p>The <a href="https://www.innovationgames.com/circles-and-soup/">Circle and Soup</a> activity helps you focus on the areas you can change or impact, and forget the ones that you can’t. Similarly to the matrix above, you’ll plot each blocker, idea or task on the circles. The inner circle is dedicated to the things that you can directly change. The middle circle are the things that you can influence and take persuasive actions to move ahead. The outer circle, called the soup, are elements of the environment that cannot be currently changed, and that you must adapt to. Ideas that stem from the inner and middle circles will help you to identify ways to respond or mitigate issues in the soup.</p><h3>Mini brief</h3><p>The activities above will help you prioritise what to focus on first. Once you’ve picked the ones you’d like to tackle (whether that’s one thing, or your top 3), create a mini brief for yourself. It doesn’t have to be long; put just enough information so that you remember what the goal is when you come back to it later. Take some time to think about why you are doing it, what steps indicate progress, and how you will think and feel once you’ve accomplished it. You can even add how you’ll celebrate when you achieve a milestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*iPdTm6eiBPgXOZmoK6UiNg.png" /></figure><p>The important bit here is to break this task down even more. This is where many plans fail, because they are too big, or not actionable enough, so make sure you break the steps down. This could be something like writing one blog post a month rather than writing 4 posts every month, or scheduling a 1:1 with someone rather than trying to tackle a breakdown in communication with a whole department.</p><h3>Review and check-in</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*Oe3JJGJmkf5S_X8kkqKirw.png" /></figure><p>The last step is to review your goals and actions and to decide when you’ll do a check-in with yourself. A good technique to instil a sense of accountability towards your action plan is called <strong>10–24–7</strong>. When introducing a new practice or behaviour it is helpful to review it regularly, so there’s a teaching theory that suggests that to better remember something you should review it in 10 mins, 24 hours and 7 days. Review your goals and actions at the end of your session, ask yourself how you will remember them and how will you make sure you are following up on them. Then, check in the next day and also the week after to see if there are any edits or changes you’d would like to make to your plan once you’ve had some time to mull things over. If you want to go even further, tell someone about your plan, and you’ll have an accountability buddy!</p><p><strong>So, the important thing to remember here is to start somewhere, anywhere, and start small. This is just a guide or direction, so celebrate your wins if you achieve a milestone or your goal, and if not, reflect on what didn’t go as expected, and just start over from where you find yourself at that time.</strong></p><h3>Recap</h3><p>These steps seem very obvious and simple, and they are! The steps above are not time-consuming, but they do require us to carve a small amount of time out to properly articulate where we want to get to. But once we’ve done that, we’ll be left with some actions that will help us progress towards our goals.</p><p>So, to recap…</p><ol><li>First of all, personal development isn’t just something you do at work for performance reviews. Do it for yourself.</li><li>The first step is to think about where you want to be, or even who you want to be. Thinking about this is the first step to hacking your career growth, and using a framework helps you draw up points of reference that will help you get there.</li><li>Second, ask yourself: “Where am I now?”. Regardless of how you go about it, you should take time out to reflect on where you are right now compared to where you want to be. The point of this step is to identify your next areas for improvement.</li><li>And lastly, think about how you’ll get there. Break the plan down into steps, and make sure that first step towards your goal is attainable. You’ll be more likely to follow up with the plan if you see yourself making progress early on. Plus it’ll give you that warm sense of achievement 🎉</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfb0c24db63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing your career as a Product Manager]]></title>
            <link>https://juliamgodinho.medium.com/developing-your-career-as-a-product-manager-28641da9e535?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/28641da9e535</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 00:15:53 GMT</pubDate>
            <atom:updated>2021-03-01T01:57:59.641Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TJxYt1noF5bvvYpwE_fwQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dsmacinnes?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Danielle MacInnes</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As a Product Manager I’ve always been fascinated by reading job descriptions. For the same role, I’ve seen so many responsibilities and key skills — some, at times, contradictory. After all, <a href="https://melissaperri.com/blog/2017/06/29/product-manager-vs-product-owner">are Product Manager and Product Owner interchangeable?</a> Is a <a href="https://svpg.com/product-manager-vs-business-analyst/">Business Analyst</a> the first step in becoming a Product Owner? Are they all the same thing? A quick search for Product Managers on LinkedIn will show you that there are so many different flavours of Product Managers, and a myriad of ways to get into product management.</p><p>Having come from an arts background prior to working in Tech, job descriptions have given me somewhat of a framework; an outline of the skills and knowledge I should learn to become a good Product Manager. However, as these job descriptions vary so much, you can quickly become overwhelmed with the amount of information, or confused by where to focus your attention.</p><p>Recently, Marty Cagan and Chris Jones published the book “<a href="https://svpg.com/empowered-ordinary-people-extraordinary-products/">Empowered: ordinary people, extraordinary products</a>”, one of the few books out there about product leadership. Cagan and Jones argue that top tech product companies aren’t successful because they hire extraordinary talent that can innovate like no one else. Instead, they believe these companies stand out from the rest because they create an environment where extraordinary talent can emerge.</p><p>In this book, Cagan and Jones introduce a tool to assess the skill level of a Product Manager — a Product Skills Taxonomy. It is based on three pillars: <strong>Product, Process and People</strong>, and highlights different dimensions under each pillar to better set out the expectations regarding the knowledge, skills, techniques and responsibilities a Product Manager should have. The authors propose that a Product Manager should assess their current capabilities against the taxonomy to identify where they currently stand, and which areas can be further developed.</p><p>Let’s take a look at each of these pillars:</p><h3><strong>Product knowledge</strong></h3><p><strong>User and customer knowledge</strong>: you are an expert on your target user/customer and understand their needs and motivations. The main way of doing this is by talking to them first-hand, but you can also take advantage of the knowledge other colleagues have (for example, a customer service representative).</p><p><strong>Data knowledge</strong>: not only are you skilled with data tools and know how to answer questions with them, you also understand what the data is telling you (this could be user or sales analytics, for example).</p><p><strong>Industry and domain knowledge</strong>: it is fundamental that you understand the competitive landscape and relevant industry trends. This knowledge should be applied to your local context in a way that you can proficiently converse with the subject matter experts around you.</p><p><strong>Business and company knowledge</strong>: you understand all domains of the business, how they operate, and their opportunities and constraints as you often have to engage with many different areas at once (such as Marketing, Finance and Legal).</p><p><strong>Product operational knowledge</strong>: you know how the product works — inside out. You can effectively demo it’s functionality for stakeholders, train a new customer on how to use it, or deal with customer inquiries.</p><h3><strong>Process skills and techniques</strong></h3><p><strong>Product discovery techniques</strong>: you understand the <a href="https://svpg.com/four-big-risks/">different types of product risks</a> (value, usability, feasibility and viability) and how to mitigate them. You do this through qualitative and quantitative techniques in collaboration with other roles.</p><p><strong>Product optimisation techniques</strong>: you are proficient in optimisation techniques (such as A/B testing) to rapidly iterate on your product once it is live and in production.</p><p><strong>Product delivery techniques</strong>: you know your responsibilities towards the engineers and other team members, and can effectively support the delivery of work with an Agile mindset.</p><p><strong>Product development process</strong>: you have a deep understanding of the overall product development lifecycle, from discovery to delivery and fully understand the Product Manager’s role throughout the process.</p><h3><strong>People skills and responsibilities</strong></h3><p><strong>Team collaboration skills</strong>: you build trust between disciplines, and work collaboratively with product designers and engineers, involving them early and often.</p><p><strong>Stakeholder collaboration skills</strong>: you put the time and effort into collaborating with your stakeholders and understanding their concerns and constraints.</p><p><strong>Evangelism skills</strong>: you share your product’s vision and strategy widely in an inspiring and motivating manner. You are proficient at communicating what you need to do and how you’ll get there.</p><p><strong>Leadership skills</strong>: a skill that takes life-long learning, leadership is something you earn. You influence and inspire, and your are looked upon and trusted by your peers.</p><h3><strong>Gap Analysis Assessment</strong></h3><p>Once you’ve identified what is expected from a Product Manager, now you are able to assess yourself against this framework. Conduct regular check-ins with yourself — or your manager. I’ve created a simple spreadsheet that can help you document your progress. <a href="https://docs.google.com/spreadsheets/d/1rgQRPI6f7vncq2IFxH8QCcfMWiVq2vzfgoQogsrpkt8/edit?usp=sharing"><strong>Access it here</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bqqvq9pozxhxsV_poZbqHA.png" /></figure><p>Whether you’re starting out, or a seasoned pro, using frameworks such as this one helps put things into perspective and pin-point the areas we can further explore and develop. Revisit it as many times as necessary; we’ll always have room for improvement. There are many other helpful resources too: from Facebook groups, <a href="https://www.progression.fyi/">career progression frameworks</a>, online courses, certifications, meet-ups, and well-known books (such as “Cracking the PM Interview”, by Gayle Laakmann McDowell). Although each one offers a perspective on the role (and adjacent roles), the best source of learning is putting yourself out there and gaining practical experience; nothing quite beats seeing something play out in real life, both the good and not-so-good experiences!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28641da9e535" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A week in the life of a product manager]]></title>
            <link>https://juliamgodinho.medium.com/a-week-in-the-life-of-a-product-manager-329df6875a15?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/329df6875a15</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Wed, 23 Sep 2020 20:53:09 GMT</pubDate>
            <atom:updated>2021-01-14T13:48:35.596Z</atom:updated>
            <content:encoded><![CDATA[<p>No one day of a product manager is the same. This is what I usually tell people who ask me what I do. This of course can be true for many professions, but working in this role has taken the meaning of this sentence to a whole new level.</p><p>This means that when I am mentoring aspiring product managers, or coaching people on product ways of working, it’s difficult to tell them exactly what it is a product manager does, step-by-step. This doesn’t mean that the responsibilities of the role are ill-defined, it just means that they are very comprehensive — we do a little bit of everything to ensure that we are creating a product that meets both user and business needs. Product management is the intersection between business, technology and user experience, and in <a href="https://svpg.com/">Marty Cagan</a>’s words, the the job of the product manager is to discover a product that is valuable, usable and feasible, yet works for the business.</p><p>This can take on many shapes and forms depending on the industry you work in, the role of product in your organisation and the maturity of your product. This is what makes this role so interesting for me — not only can one day look different to another, but product manager careers can also vary greatly. For me, this diversity of experiences and perspectives is what makes great products.</p><p>For some context, I work in a private member’s club for creative people. Although we are in the hospitality industry, I’d say that our audience and members are very different from what you’d typically think. Furthermore, I am currently working on a product tasked with understanding what it would mean to create meaningful digital connections between our members — a conversation that wouldn’t normally permeate hospitality discussions. Nevertheless, this is what a (4-day) week in September looked like for me and my remote team (due to lockdown) of developers, designers and data engineers working on a mobile app.</p><h3>Monday</h3><p>I start the day looking at our analytics on Firebase and Redash. Last week we released a new feature so I’m keen to observe the uptake and how people are using it. Throughout the week I’ll take a look at our data, but each Monday I do a more in-depth analysis of our product metrics. In my team, we pay special attention to engagement markers: for the Noticeboard (a place on the app members can post and reply to all members), we’re taking a deeper look into the first time vs repeat posters and visitors as we’re interested in ways we can encourage the habit of coming back to the app to engage with fellow members. We’re slowly starting to see some trends, which is exciting because we’ll be able to dig deeper into how we can improve members’ experience of our product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYQvvFb634hW0V-KMmpkSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*peBUvzmuKG4eHC-gaYPuzw.png" /></figure><p>After I caught up on Slack messages and emails, I checked in with the team. At 10 am we’ll be kick-starting the week with a hack day. The purpose of this session is to give the team the opportunity to explore different ideas — blue sky thinking, some research about our users, an itch that is begging to be scratched… anything. We like to keep it broad and place only one boundary: the idea must align with the purpose of our product. The day starts with a pitching session to present ideas and decide what everyone wants to work on, and at the end of the day we come together to demo our work. There is a lot of preparation that goes into this day, but I’ll keep it for another post!</p><p>I decided to do some desk research this time. I wanted to explore what the future of communities could look like and what tools people will be using to connect amongst themselves. Community is at the heart of what we do so it is important that we can anticipate trends and interactions, as well as (and more importantly) thinking about the impact of our technology on people and society.</p><p>After the demo where I got to see all the amazing work the team got up to, I ended the day in a meeting with other mobile app product managers. We are exploring how we can create a forum for product managers to talk about our mobile app and the ideas we want to explore, our work in progress and the things that will be released. As we all work on different membership types, we want to ensure we’re creating a consistent experience and that we’re not duplicating effort… we’re slowly getting there!</p><h3>Tuesday</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*edaqG36BJ0iXdbwpa0A4JA.gif" /></figure><p>After doing the usual catching up on my messages, I had two separate sessions to discuss some work that is being built. I first caught up with the iOS developers to talk about the transition effect when a member swipes up to view a profile and its trade off with the hierarchy of the information we display on the profile drawer. In the second session, I discussed ways to make it easier for members to access the noticeboard.</p><p>After the team’s stand-up we walked through the user journey of a new prototype we’re building. The UX and UI designer used the outcomes from our team’s workshops to create some prototypes. With rough wireframes we were able to discuss feasibility, but we’ll have to spike some of the implementation work and choose a 3rd party provider for a portion of the user journey.</p><p>After mulling over the our desired outcomes, wireframes and the logistics that would be required to make the idea a reality, I started to rethink some parts of the journey and realised it was time to pivot.</p><p>As the main reason we want to build this prototype is to get as much learning as possible with the least amount of effort, I was sure there were simpler ways of doing this. I then caught up with the team to discuss how we can stay true to our core purpose whilst providing our users with a valuable experience. After some discussion as to how we could validate our hypotheses through a simpler journey, I got started on user story mapping that we’d finish as a team the following day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*Bng4xfIvhT4SFeNXSN5jBA.gif" /></figure><p>All this pivot chat left me with very little time to continue with the research I was working on, but I managed to squeeze some more reading and writing at the end of the day.</p><h3>Wednesday</h3><p>The day started preparing for a walkthrough of the new proposed user journey with the team. Once we got together to go through it after stand-up, we discussed any questions, risks and unknowns. We used virtual post-its to plot down any tasks we’d need to do and the next steps for each one of us. We decided to delve deeper into two parts of the journey, so I put in a separate session with the team for that over the next week.</p><p>After lunch I caught up with the CTO. We discussed a range of things, from mental health, the effect of lockdown on teams and future-thinking about the product. As the product I am working on is embarking on bigger and better things, I got some great advice about bringing people on the journey and the value of seeking diverse viewpoints in the process of setting the product’s foundations.</p><p>Later, I helped with testing some of our work. I tested the profile drawer work that we had looked into yesterday as well as testing our “conversation starters”, which is a feature on our video calls to help people break the ice, especially if they find it difficult to initiate conversations with strangers. Although Sam is no stranger, I found out that Brad Pitt would play him in the film of his life!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMDjLZSwbDNBgu4lwWVg-A.png" /></figure><p>After spending the afternoon preparing for some team workshops, I ended the day with a couple of emails. We’re getting ready to send a worldwide survey to non-members to test appetite for our overall proposition. This research will be really important to understand how our journey will progress, so I’m really excited to get this out!</p><h3>Thursday</h3><p>The day started off with a cross-team meeting about some proposed changes to the mobile app home screen. This was followed by some quick “slack sessions” (as some of us are still working from home) with different colleagues to refine our solution.</p><p>Following our team stand-up, we had a workshop on how to approach the build of direct messaging into the app. This was an initial session to think about the must/should/nice-to-haves from both a user and technical point of view. We’ll then use the requirements to initiate conversations around how we’ll go about building it.</p><p>I then had a session with the UX and UI designers to discuss how we use filtering for certain features and how we intend to revisit this in light of the new work we’re doing. After lots of juicy discussions, we came to an initial proposed solution we’ll mock up to test with our members. Phew!</p><p>I met with the Head of Product as we’re conducting interviews with several key business stakeholders for the new mobile app strategy we’re working on. Today we talked to the Group IT Director who took us through her team’s vision, goals for next year and how the product team can help achieve them. I’ve created a table on Miro to easily summarise the outputs from the interviews to help us when outlining the strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F2ENTa1fPsFWqjgeQKwjHA.png" /></figure><p>Before our fortnightly product demo, I reviewed an interview script for a focus group we’ll be doing with members. This is intended to supplement the survey we’re sending out to non-members and will help us to identify the similarities and differences between the different audiences. The goal of this research is to understand what members are trying to achieve as a result of connecting with each other — this will help guide our proposition in the upcoming months.</p><p>From improving how members invite guests to the Houses, revamping our bedroom booking journey and some A/B testing experiments, the demo was full of interesting work; it’s always great to see what other team are up to. My team showcased our explorations during our hack day, the pivot we had earlier in the week, and the Noticeboard web interface we created for staff so that they could easily reply to posts while at work.</p><p>Before the last meeting of the day, I wrote the release notes for the app store as we prepared to submit a new iOS version of our app. If approved, members will see our new work on Monday — exciting!</p><p>At the end of the day, I had a the first meeting of the newly appointed Diversity and Inclusion steering committee which I am a part of. The company has recently signed a diversity pledge, and from next week we will be participating in C-suite meetings to give feedback, consult and hold leadership accountable proposed changes.</p><p>After work, I jumped on a call with my mentee through <a href="https://blackvalley.co.uk/">Black Valley</a>, an initiative that aim is to improve social mobility and the accessibility of working in the tech industry for the black community. In this session we explored different product and design roles in Tech, and setting small tasks to learn what each does through practice.</p><h3>Friday</h3><p>Although I don’t work on Fridays, the hustle doesn’t stop! I finally managed to finish the desk research I started on Monday 😅</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z89MLJgnLq-c2CAR1Rp0rg.png" /></figure><p>I also participated in a Google user research session and caught up with Sam (Tech Lead at Soho House) to talk all things digital, communities and some ideas we want to explore 👀🔮</p><p>As mentioned, no day looks the same — as you’ll have figured from this account. I hope this gives you some insight into the role, and the only guarantee I can give is that the following week will look really different!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=329df6875a15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learnt from failed job searching during a pandemic]]></title>
            <link>https://juliamgodinho.medium.com/lessons-learnt-from-failed-job-searching-during-a-pandemic-60b56206861e?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/60b56206861e</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[covid-diaries]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 22:24:55 GMT</pubDate>
            <atom:updated>2020-09-14T22:24:55.590Z</atom:updated>
            <content:encoded><![CDATA[<p>Firstly, I must admit the title is a bit click-batey. Secondly, that the act of writing this post is inherently narcissistic. This post <strong>is</strong> about the lessons I learnt applying to jobs during the pandemic (aka COVID-19; aka a year I’ll never forget). However, it’s specifically about the lessons I learnt about myself.</p><p>As agile practitioners, we’re constantly talking about the need to inspect and adapt our ways of working; looking back and identifying what went well and what can be improved. From those reflections, we take some actions forward in the hope of doing it better next time. I wonder, however, how many of these people actually take on their own advice and apply it to their own work. I, for one, know that I don’t do it enough.</p><p>Today, taken by a cathartic/dramatic “I-have-nothing-else-to-lose” feeling, I wanted to share some things I learnt from one of my most recent failures. Talking about failures for some may seem a like a pity story, a little too personal or gauche. I, however, think it is important to destigmatisedestigmatize failure and celebrate it for what it is: life. Sometimes you get what you want, sometimes you don’t.</p><p>I need not divulge too much about the context, as I feel we’re unfortunately still in the midst of it all. But… in 2020 COVID-19 happened. The unprecedented effect of the pandemic on our personal and professional lives (not to mention society as a whole) will be felt for years to come. I am a dot in the ocean and count myself as privileged to have kept my job, albeit with some adjustments. However, this didn’t prevent me from being sent into a spiral of self-doubt, racking my brain to think of Plan B, questioning the purpose of life and so on.</p><figure><img alt="If 2020 could be rated: 1 star rating out of five. Text underneath the stars read: very bad, would not recommend." src="https://cdn-images-1.medium.com/max/700/1*DOvnbfgcOrxfjI7byzS-9w.jpeg" /><figcaption>Source: <a href="https://www.boredpanda.com/funny-jokes-2020/?utm_source=google&amp;utm_medium=organic&amp;utm_campaign=organic">Bored Panda</a></figcaption></figure><p>I’ll cut the story short and get to the juicy bit: after a handful of frustrating interactions with recruiters, hours of crafting my CV and applications, one arduous four-month recruitment process, and turning down other job opportunities along the way, I didn’t get the job I wanted. I realise a four-month recruitment process isn’t common place, however, it gave me a LONG time to think about everything and process my feelings — which brings me to my first lesson:</p><h3>You’ll feel ALL the emotions</h3><p>I went on an emotional rollercoaster ride where I felt everything I thought I could feel: elated, excited, anxious, passionate, nervous, sick to my stomach (literally! More on that later), proud, determined, ashamed, angry, upset, relieved.</p><p>It’s OK to feel all the emotions, it is part of everyday life. Give yourself time to feel all the feels. What I found helpful was talking about these emotions with friends and family. I was able to acknowledge and let them go (most of the time).</p><p>I have come out of this experience more aware of how self-critical I am, and how I hold myself to standards that are at times unsustainable. Cliché as it may seem, I must be kinder to myself and believe that I have the right skills and experience for the job — otherwise I wouldn’t have been shortlisted in the first place. Let the others do the judging.</p><h3>Don’t run away from bad situations</h3><p>Take this with a pinch of salt. You shouldn’t have to live with situations that are detrimental to your mental health, or put up with an abusive colleague or a toxic workplace.</p><p>This is about understanding your motivations to seek a job in the first place. Are you dissatisfied with a project? a process? a manager? Before considering a move, is there anything in your sphere of influence that can be changed? Is there anything that you can make your job more enjoyable or worthwhile? Maybe a holiday?</p><p>Look for another job because you want new opportunities that will bring your growth, that will challenge you or steer you closer to where you want to be.</p><h3>Give yourself a fighting chance</h3><p>Come prepared to your interviews. Do your research, review your CV, think about questions you may be asked. Give yourself enough time to prepare, but don’t overdo it. There’s no need to script it — all that knowledge is in your head; it’s your experience and skills, you know it off by heart!</p><p>By researching the role, doing a mock interview, and having a good structure to answer your questions (think <a href="https://www.thebalancecareers.com/what-is-the-star-interview-response-technique-2061629">STARS framework</a>) you’ll avoid draining all your energy and thinking about “what ifs” after the interview.</p><h3>Ask your aunt to pray for you</h3><p>My aunt lives on the other side of the world but I felt her support every time she said she’d pray for me during these past months. Whatever your religion (or lack thereof) surround yourself with people that care for you. Don’t drown in the emotional labour alone; friends, family, colleagues (and sometimes even strangers) can double up as your support group or sounding board.</p><p>The most important part of this journey was being able to share it with my friends and family. This is something new to me as I wouldn’t normally do this as I feared failure: what would they think of me if I said I hadn’t got the job? Well, I didn’t get the job, but I had amazing people besides me to cheer me on.</p><h3>No job is worth going to the hospital for</h3><p>I landed in hospital after a string of psychosomatic events. I let myself be too consumed by the anxiety and stress of the process that I wound up in a lot of pain. Don’t follow my lead on this one, it’s not worth it. Look after yourself in the process, make sure you haven’t let everything else fall by the wayside. Hold on to the things you like doing: watch your favourite series, go out with your friends, read a book, go for a walk — anything that is familiar and can keep you grounded.</p><h3>Celebrate the journey</h3><p>Applying for a job is one event in a long journey — your career. You either get it or you don’t — which is easier said than…accepted. But once you come to terms with the 50/50 outcome, you can focus on the process.</p><p>I’ve always been that weird person that gets a kick out of doing interviews. This is because, if anything, it teaches me a lot about myself. I become better at articulating my experience, connecting the dots, expressing my value and impact. In this process you will question yourself a lot. Why am I actually doing this? Is this what I really want? Why do I want to join this company? It gives me an opportunity to put things into perspective: what do I value in an organisation? how does this help me grow? how do I measure success in my role? does this fit into my long-term goals? Enjoy the process for the journey it takes you on.</p><h3>Talk about your failures openly</h3><p>Not getting the job you wanted sucks. I personally felt shame and frustration. What happens if I keep these feelings to myself? They’ll build up.</p><p>Or, what would happen if I were to talk about my failures openly? By talking openly, we are able to destigmatise failure, share our learnings, and help others. Take stock of what you did well, and what you could’ve done differently. Reflect on any feedback you may have gotten too. This will come in handy down the line. Now, how will you show resilience?</p><p>Throw a fail party to celebrate your facepalm moments, or write a blog post about it. Alternatively, listen to Elizabeth Day’s podcast “<a href="https://podcasts.apple.com/gb/podcast/how-to-fail-with-elizabeth-day/id1407451189">How to Fail</a>” for some candid, insightful anecdotes on how other people failed miserably but succeeded better next time around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*xr97soGwY1O0V3J0d9xN1Q.gif" /><figcaption>Source: Giphy</figcaption></figure><p>I finalise this little failure of mine with another thing worth celebrating: this post. Over the past months I struggled with deferral and not doing things that could’ve uplifted me — such as writing. Better late then never! I write in the hope that my lessons learnt resonate with other people on the search for their next opportunity and acts as a reminder to be kind to yourself. After all, this is a small blip in a long — and hopefully fulfilling — journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60b56206861e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Agile training at Cancer Research UK — part 2]]></title>
            <link>https://juliamgodinho.medium.com/improving-agile-training-at-cancer-research-uk-part-2-7efae821410e?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/7efae821410e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[training]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Sun, 12 May 2019 22:44:06 GMT</pubDate>
            <atom:updated>2019-05-12T22:44:06.397Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving Agile training at Cancer Research UK — part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GRYXM1F4z2phQEHGgQbD-Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5aiRb5f464A?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jo Szczepanska</a> on <a href="https://unsplash.com/search/photos/workshop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.</figcaption></figure><p>In my <a href="https://medium.com/@juliamgodinho/improving-agile-training-at-cancer-research-uk-part-1-6d0cb8bdfee1">previous post</a>, I talked about the first steps the Agile Team at Cancer Research UK took to improve its basic Agile training. The initial discovery involved context-setting, defining and fleshing out the problem, and exploring potential routes to test and validate the initial hypothesis. This post will explore the training module’s learning objectives and interviewing participants to deepen our knowledge on their needs and expectations.</p><h3>Drafting the learning objectives</h3><p>The overarching goal of this project is to identify why, if and how Agile training at Cancer Research UK can be improved. As an initial result, we wanted to develop a prototype for one training module that could be tested in the organisation to determine whether we can better meet participants’ expectations.</p><p>In the first stage of this lean research, we identified that people who participate in the basic Agile training sessions are not as confident as they could be in applying what they learn in the sessions to their role because they feel as if they leave without any tools or techniques to do so.</p><p>As an initial hypothesis, we believed that if we could better manage expectations through clear learning objectives (and refine the training content to better reflect them) and demonstrate how agile values, principles and practices can be applied to participants’ context of work, participants will feel more confident in applying their learnings to their role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gXvqso5aH7PhCuwW66VSig.png" /><figcaption>Previous learning objectives for Agile training at Cancer Research UK.</figcaption></figure><p>The initial training learning objectives were not really objectives but more of a list describing the content that would be covered during the session. Learning objectives describe what the participants should know or be able to do at the end of the training session; and that’s what we wanted to create and prototype based on the research we conducted.</p><p>With the overall aim of the training module being the ability to describe the distinction between “being” and “doing” Agile, we drafted a first iteration of the learning objectives:</p><h4>Learning Objectives: Agile Fundamentals</h4><p>You will come out of the session being able to:</p><ul><li>Explain Agile values and principles and how it can relate to your work</li><li>Describe what Agile means for Cancer Research UK</li><li>Apply basic tools and techniques to encourage an Agile mindset</li><li>Identify where to find more information about Agile</li></ul><p>One objective in particular still remained nebulous: “Apply basic tools and techniques to encourage an agile mindset”. In our previous post, we mentioned that we wanted to further explore this topic by trying to understand how many tools and techniques are enough to enable participants to work in a more Agile manner. This is motivated by the need to understand the level of specificity we need to provide, and determine what is realistic for the time and amount of training. However, after bouncing these ideas with some of our colleagues, we decided that this question needed to be turned around: <strong>what we need to understand is why participants say that they need to learn tools and techniques to use in their day-to-day role and what they are trying to achieve with these</strong>. With this knowledge, we are then able to find something practical (tool, technique, activity, etc.) that will help them solve their problem. To answer this, we decided to validate the learning objectives (with special focus on the question above) by conducting interviews.</p><h3>Validating the learning objectives</h3><p>Alongside my colleague Maria Bonorchis, we conducted interviews to look deeper into the motivations behind the training participants’ expectations and understand why they say that they need to learn tools and techniques to use in their day-to-day role and what they are trying to achieve with these. For this, we conducted interviews with different audiences: people who have undergone the training and people who have expressed interest in attending.</p><p>With the help of UX Designer Katie Foster, we created an interview script that was divided into different sections: context of use, motivation, expectations, prototype and improvements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrZZCnZ6rr7fcTy1F02b-Q.png" /><figcaption>Interview script</figcaption></figure><p>In total, we interviewed ten people from different parts of the organisation. The highlights from the interview included:</p><ul><li>6/10 people heard about the training session through a colleague</li><li>8/10 people weren’t aware of the Agile Coaches prior to the training</li><li>Participants identified that Agile was a priority for Cancer Research UK and teams are more frequently adopting Agile ways of working</li><li>People wanted to understand how Agile could improve their current projects on an individual and team level</li><li>Participants expect to leave the training being able to articulate what a Agile means and how it applies to their work</li><li>7/7 people had a very positive reaction to the learning objectives: “it would be two hours very well spent!” (participant 4)</li></ul><h3>Practical feedback</h3><p>Following the interviews, we decided to take one step further by testing the learning objectives in a training session. Alongside my colleague Taruna Robinson, we modified parts of the existing training content to include content that covered the new learning objectives. We delivered the session to 16 participants from different departments across the organisation.</p><p>After the session, we conducted a <a href="http://www.liberatingstructures.com/9-what-so-what-now-what-w/">“What, So What, Now What”</a> Retrospective. This format allowed us to understand what we had objectively done differently, what the changes meant and what recommendations we wanted to make for the rest of the team.</p><p>We also sent out the post-training questionnaire to the participants. With the collected data we were able to measure that particular session against the average of the other sessions delivered to date. Although we had only conducted one session using the new learning objectives, it gave us a good indication of better fulfilling the participants’ expectations. To get a better data set, we suggested to the team that we deliver the next training sessions with the newly modified content to get a better and more consistent picture of the feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNdOCJQ0qQSE77KC_ok8Qg.png" /><figcaption>The new training session scored higher on all questions compared to the average of the previous training sessions.</figcaption></figure><h3>Getting agreement from the team</h3><p>Maria and I then ran a debrief workshop with the Agile team to relay our findings from the interviews. We conducted an activity to build consensus around each learning objective. At the end of the session, the team emerged with a set of learning objectives that we will now use for our Agile Fundamentals training:</p><h4>Learning Objectives: Agile Fundamentals</h4><p>You will come out of the session being able to:</p><ul><li>Explain Agile values and principles and how it can relate to your work</li><li>Describe what Agile looks like for Cancer Research UK</li><li>Articulate how basic agile practices support an Agile mindset</li><li>Identify where to find more information about Agile</li></ul><p>We also ran another activity to understand what the training facilitators need from the participants in order to make it the best session possible:</p><h4>What we need from you:</h4><ul><li>Be fully present in the room! We encourage the use of devices for note-taking — please disable all notifications and close applications</li><li>Question and challenge us! We encourage healthy debate</li><li>Be mindful of the time, we want to make sure everyone has the opportunity to ask questions. If needed, we’ll park questions and answer them after</li><li>Read the learning objectives beforehand and think about what you would like to get out of the session</li></ul><p>To close the session, we asked the team to brainstorm what content we would need in order to cover the learning objectives. We then mapped it out against the current training content and decided what we would keep, lose or improve.</p><h3>Next steps</h3><p>Next up, we will run through the new and improved training deck with the rest of the Agile team so that we are familiar with the content and can deliver the session consistently.</p><p>Maria and I are now planning to conduct follow up interviews to understand if and how people have applied what they’ve learnt from the session. This will allow to identify whether there are still areas that can be improved; so watch out for the final post in the series!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7efae821410e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five steps to effectively set up a new team]]></title>
            <link>https://medium.com/swlh/five-steps-to-effectively-set-up-a-new-team-ce067abd69ec?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce067abd69ec</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Sun, 12 May 2019 10:34:43 GMT</pubDate>
            <atom:updated>2019-05-20T07:24:02.112Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4lNtRoCqOClLp2WVL_pQw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/lbLgFFlADrY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Perry Grone</a> on <a href="https://unsplash.com/search/photos/team-building?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Starting up a new team is a fundamental step towards fostering teams that work well together. Sounds obvious, right? However, it is an often overlooked or forgotten step, meaning that teams go head-first in the work to be done rather than thinking about how they would like to work together as a team.</p><p>This post will address one way of starting up a new team (aka team lift-off or kick-off). This applies to teams who will work on a dedicated project or product, or even teams that have already worked together. I have separated the kick-off into five different building blocks:</p><ol><li>What’s our purpose?</li><li>Meet the people</li><li>Know your process</li><li>The rules of the game</li><li>Inspect and adapt</li></ol><p>This format has been tried, tested and iterated. However, it is important that you tailor your kick-off based on the team’s needs. In order to gauge what level to pitch your kick-off, observe the team’s dynamics and their interactions with the wider organisation and ask individual team members beforehand whether they have any expectations, hopes or concerns for the session and build your activities around them.</p><p>Investing a short time at the beginning of an initiative to agree on things such as the values and behaviours we want to see in our team has a huge pay off. For example, agreeing upfront about how we want to be together in conflict as opposed to letting tension build up or explode allows us to navigate everyday communication in a more open and respectful manner.</p><p>Fear of conflict is one root cause of dysfunction within a team. In their book “<a href="https://www.tablegroup.com/books/dysfunctions">The Five Dysfunctions of a Team</a>”, Patrick Lencioni describes common pitfalls faced by teams as they seek to grow together. Absence of trust, lack of commitment, avoidance of accountability and inattention to results are the other four root causes classified by Lencioni. Albeit a simplistic model, these dysfunctions highlight problems that can be better navigated if a team takes time to intently think about how they work together.</p><h3>How to get started</h3><p>As mentioned, gather as much insight from team members to create a kick-off that is relevant for the team and will set them on the right track. Investing time for this is important as it sends out a message to the team and the rest of the organisation that you are serious about helping this team succeed.</p><p>Depending on the team’s needs, the session can be run in a couple of hours, one day or spread over a couple of days. The important thing is that you give the team enough time to have fruitful conversations that lead them to think about how they want to work as a team and the first steps they can take towards this. Give the session enough time and space — don’t cram too much in but make sure you keep the session energetic so people’s attention and engagement stay in the room.</p><p>Be clear not only about the outcomes for the session, but set the team up for success by painting a picture of what a great team could look like. You might want to mention <a href="https://martinfowler.com/bliki/ShuHaRi.html">ShuHaRi</a>, <a href="https://www.mindtools.com/pages/article/newLDR_86.htm">Tuckman’s stages of group development</a> (forming, storming, norming, performing and adjourning) or insights from studies on what makes successful teams, such as <a href="https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/">the one carried out by Google</a>, to illustrate the path they’re embarking on.</p><p>Once you have put a plan together for the session, share it with the team. Ask for feedback on whether they think it meets their expectations. Get them involved in their team formation from the very beginning.</p><h3>1. What’s our purpose?</h3><p>This session is an opportunity to think about the team’s development and what they want to become together. For this, Lyssa Adkins, in the book “Coaching Agile Teams”, suggests asking: “What’s in it for us as a team?”. This is different to setting the product or project vision or looking at the work you’ll be doing together (this can be achieved in a separate session).</p><p>After summarising the team’s intent, probe into individual motivations by asking team members what they want out of being in this team; this can be an accomplishment, a skill, or anything else they can think of.</p><p>These two questions are a great opportunity to set the scene, and you can refer back to them in the following building blocks.</p><h3>2. Meet the people</h3><p>This section goes further into building relationships between the team and starts to form a collective identity, hopefully with a bit of fun!</p><p>Through team building activities, you can get to know your colleagues on a more personal level. This doesn’t mean that trust will be established from the onset, but it is a good way of laying a foundation for trust and respect.</p><p>There are many activities you can draw from, here are some of my favourites:</p><ul><li><a href="https://medium.com/@cassierobinson/a-user-manual-for-me-d3a851fbc694">User Manual for Me</a></li><li><a href="https://medium.com/practicalscrum/market-of-skills-634a6ebf3363">Market of Skills</a></li><li><a href="http://tomek.kaczanowscy.pl/2016/02/journey-lines/">Journey Lines</a></li><li><a href="https://jasontreu.com/2018/06/02/mad-libs-team-building-performance/">Shared Stories</a></li><li><a href="https://blog.crisp.se/2012/11/06/anderslaestadius/team-liftoff-with-market-of-skills-and-competence-matrix">Competence matrix</a></li></ul><p>If you want to conduct a similar activity like the ones mentioned above but don’t have as much time, I’ve created the prompt below. It gets the team thinking not only about their roles and responsibilities, but also what they bring to and need from their team.</p><p><em>“My name is ____. I am a ____. One interesting/random fact about me is ____. On this team, I am responsible for ____. Two skills I offer to the team are ____ and ____. In order to do my best work, I need from my team ____. and ____. The way I like to receive feedback is ____.”</em></p><p>You can keep the interesting fact for later and anonymise them so the team members need to guess who the statement belongs to!</p><p>Use your creativity to tweak existing activities or try using <a href="https://www.lego.com/en-us/seriousplay/the-method">Lego Serious Play</a> to create your own. Choose activities that bring forward skills and interesting facts… I’ve even included a <a href="https://www.bbc.co.uk/programmes/b006qnmr">Desert Island Discs</a> section to my User Manual for Me so that the team has a playlist once they’re finished with the session!</p><h3>3. Know your process</h3><p>If, like me, you work with Agile teams, this is the moment in which you can revisit the Agile values and principles. If your team is already familiar with this way of working, just give them a speedy tour through the main concepts so that the team shares a common language. If the team is new to Agile, consider conducting a separate workshop to take them through it in more details, perhaps using Agile simulation games.</p><p>This part of the session aims to get agreement on ways of working and general logistics. This could include the frequency and time of each meeting to when, where and how to document our work.</p><p>Review the meetings, forums and tools you share as a team to understand their “what” and “why” alongside establishing what the team expect from each team member in each meeting. Also look into the team members’ working patterns, as it important to understand this from the start. This is a great opportunity for the facilitator to provide just enough guidance and take a step back to let the team lead this activity as this needs to work for them, not you.</p><p>Make sure to document the outputs and keep them somewhere visible so the team can revisit them frequently.</p><h3>4. The rules of the game</h3><p>Establishing the rules of the game for the team involve thinking about the behaviours they want to see and embody together. A working agreement defines what the team should hold each other accountable for.</p><p>There are many variations of how you can create a team charter. I usually start off by referring to the answers the team came up with when I asked “What’s in it for us as a team?”, or simply asking “what is a team?” — this is helpful to establish an aim to work towards together.</p><p>I then ask the team to list characteristics of unsuccessful teams. This helps the team to pinpoint potential downfalls or blockers to successful teamwork. I have found that teams are very good at coming up with lots of answers for this!</p><p>Only after asking the above questions is when I then ask: “What can make our team successful?”. I find at this point that our brain juices are flowing and are better at thinking outside the box. I prompt the team by asking them to think about:</p><ul><li>situations in which we interact and collaborate​</li><li>positive behaviours we want to see​</li><li>things that are working well and we want to keep up​</li><li>things that we can improve​</li><li>how we want to be perceived by stakeholders and other teams​</li><li>how we will call out conflict in the moment</li><li>how we use our tools​</li></ul><p>Once the team has brainstormed as many ideas as possible, we briefly discuss the ideas and group them by theme. I then invite the team to walk around the wall and have a look at what the team has come up with. I ask each team member to pick one post-it or theme and give them some time to formulate their proposal. Jimmy Janlén, when writing about bootstrapping working agreements for teams, suggests that you ask three simple yet powerful questions when the team members present their proposals back to the group:</p><blockquote><em>1. If we vote for this and honour it, can you give me examples of what that would look like? What would I be able to see with my eyes?</em></blockquote><blockquote><em>2. If we fail to honour this, what would that look like?</em></blockquote><blockquote><em>3. If we evaluate our ability to honour this working agreement two months from now, would we be able to evaluate whether we are respecting this bullet? How would we do that?</em></blockquote><blockquote>(<a href="https://blog.crisp.se/2018/12/05/jimmyjanlen/bootstrapping-a-working-agreement-for-the-agile-team">Jimmy Janlén</a>)</blockquote><p>The team then vote on whether it is a proposal they would like to include in their charter. If the team wants to present more than one proposal, go through another round but be mindful not to over-populate the charter, or the team won’t remember all of it! You can save the remaining proposals and revisit them at another time.</p><p>If you have time and want to take it a step further, get creative and ask the team to wrap up all the activities of the session by creating a team poster to present themselves to other teams and the wider organisation. You can use magazines, memes, Lego sculptures — anything that will help the team creatively articulate who they are as a team. Keep it somewhere visible once you’re finished. And why not create a team name to go with that?!</p><p>Before you finish this session, rehash the agreements the team have made together. Gauge the team’s confidence in holding each other accountable; this can be done through a quick exit retro using smileys, voting with numbers, or even using a <a href="https://luis-goncalves.com/agile-retrospective-set-the-stage/">constellation format</a>.</p><h3>5. Inspect and adapt</h3><p>The team charter and ways of working agreements are living documents and as such should be revisited by the team regularly.</p><p>A couple of weeks (or sprints) after the session, hold a retrospective for the team to inspect their team charter — the same can be done with the ways of working agreements the team have made. Use a <a href="https://medium.com/the-liberators/retrospective-do-the-team-radar-1794057653e9">team radar</a> activity to visualise where the team believe they are doing well and in what aspects they can improve.</p><p>In the subsequent months, revisit all or specific parts of the team’s agreements and vision so that it is at the forefront of their minds and they are frequently adapting their ways of working as they grow through the stages of team development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce067abd69ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/five-steps-to-effectively-set-up-a-new-team-ce067abd69ec">Five steps to effectively set up a new team</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to manage your workload and focus on the right things]]></title>
            <link>https://juliamgodinho.medium.com/how-to-manage-your-workload-and-focus-on-the-right-things-f8f5038feba?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8f5038feba</guid>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[task-management]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Sun, 14 Apr 2019 19:05:03 GMT</pubDate>
            <atom:updated>2020-05-09T00:21:00.519Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes, my mind feels like this…​</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*jkdb2HQoJf-EAJbAQ-MpOg.jpeg" /><figcaption>Source: abc News</figcaption></figure><p>Mainly it is because I feel like I’ve lost sight of all the tasks I need to complete. Sometimes, it’s because I have a lot of complex, moving parts, it’s difficult to know where to start.​</p><p>At times, this even manifests itself in the physical world… I find myself in the middle of a messy house and messy mind, and tidying up really helps me think clearly!</p><p>What I’d really want to see…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*n-o8cLwcD5kBOk0dePLlQg.jpeg" /><figcaption>Source: Thailand Tatler.</figcaption></figure><p>To avoid getting into a rut, I have inspected and adapted the ways I mange my workload over the years. I’m still on a journey to find better ways of working, but I’ve picked up some useful tips and tricks along the way.​</p><p>Why? To some it may seem obvious why you’d want to employ a systematic approach to managing your work, but to others it may not be.</p><p>There’s the old adage <em>time is money</em> that we’ve grown tired of hearing. But it’s true! We’re not very accustomed to thinking about the cost of our efforts on a more granular level (e.g how much it costs me and my team to be in this hour-long meeting), but we should be more aware of it. Time is money and we should be spending our time on the activities that will bring more value or have the most impact.</p><h3>Managing your workload</h3><p>There are three concepts that frequently come into play when I think about managing my workload: time management, prioritisation and productivity.</p><p>Time management refers to how you plan and organise your activities around a certain timeframe. Good time management can help you work more efficiently and effectively, getting more done in less time.</p><p>Prioritisation is a relative activity which involves determining which activity takes precedence over others based on criteria such as importance, urgency and impact.</p><p>Lastly, <a href="https://dictionary.cambridge.org/dictionary/english/productivity">the Cambridge Dictionary defines productivity</a> as “the ability to do as much work as possible in a particular period”. Although measuring outputs can be helpful (i.e measuring the amount of things done), a more useful way of measuring productivity is the amount of useful and/or valuable things done in a consistent and sustainable pace.</p><p>Understanding how you approach each of these concepts can help you determine the strengths and weaknesses of your current ways of working. With this self-awareness, you can focus on small improvements that set you on a track to work more efficiently and effectively.</p><h3>Impact vs. Effort Matrix</h3><p>There are many principles, tools and techniques that I have tried out or recommend to the teams I work with. You may of heard of some:</p><ul><li>Visualising your work</li><li>Limiting work in progress</li><li>Pomodoro technique</li><li>Eisenhower matrix</li><li>Trello</li></ul><figure><img alt="Impact vs Effort matrix" src="https://cdn-images-1.medium.com/max/1024/1*NchrycoXULc4EwIQgeDNrw.png" /></figure><p>For now, I am going to take you step-by-step through the Impact vs Effort Matrix I use to manage my workload.</p><p>The Impact vs. Effort Matrix is a useful tool for decision-making that can be used individually and in groups. It takes into consideration the amount of effort required to carry out something compared to its potential impact.</p><h3>1. Write down all your tasks</h3><p>Write each task on a post-it.</p><p>You may have different types of tasks such as one-off tasks, routine activities (like business-as-usual), projects, and problems-to-solve: make sure you write everything down, even the smallest of tasks.</p><h3>2. Identify 2-minute tasks</h3><p>If a task won’t take longer than two minutes to complete, set them aside in a separate pile.</p><h3>3. Identify tasks with an immovable deadline</h3><p>If a task has a completion date, add the date to the post-it.</p><h3>4. Refine each task</h3><p>This will help you with comparing and prioritising your work.</p><p>Gather as much information you have on each task. Make sure you are clear on the “why”, “what” and “who”. If you have any idea of the “how”, include that too — even if it’s just the first step.</p><p>You may want to use a <a href="https://www.mountaingoatsoftware.com/agile/user-stories">user story</a> format to shape the task description: “As a &lt;person/user/audience&gt;, I want &lt;a goal&gt;, so that &lt;some reason&gt;”. Or, if you want to break the task down into smaller components, use the <a href="https://agileforall.com/new-to-agile-invest-in-good-user-stories/">INVEST</a> acronym.</p><h3>5. Prioritise your work based on impact and effort</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xr3XaDEUpg59_misPmfwyg.png" /></figure><p>Before you begin, make sure you are clear about what impact and effort means to you so that you can objectively compare pieces of work. For example, when thinking about effort, you might consider different factors such as time, complexity and uncertainty.</p><p>On a clear table, draw one vertical line for “impact” and one horizontal line for “effort”.</p><p>Start off with a task that you are clear about what it involves. Place the post-it on the impact vs. effort matrix. Then, pick up another post-it and place it on the matrix; think about how it compares to the task you put down first. Then, repeat until you’ve gone through all tasks.</p><p>Tip: if your post-its end up in one quadrant, move the axes so that they are better distributed across the matrix.</p><h3>6. Start with the quick wins</h3><p>Start with the quick wins: tasks that are in the lop left quadrant. These should be done first as they have a high impact but take less effort.</p><p>The tasks in the top right quadrant are your larger projects — they will need more planning and possibly breaking down into smaller tasks. Ask yourself if there are any opportunities to reach the same impact with less effort. Maybe you can use a test and learn approach to determine the best way forward?</p><p>The tasks in the bottom left quadrant are your “fill in” tasks. Determine whether you can delegate this, or if there’s anything you can do to improve its impact.</p><p>The tasks in the bottom right quadrant are “thankless tasks”. Ask yourself if these really need to be done — avoid them as they aren’t impactful and require too much effort. Or, <a href="https://jamesclear.com/buffett-focus">eliminate ruthlessly</a>!</p><h3>7. Visualise your work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rj8KtKAG3hdsTvLYs4oWgg.png" /></figure><p>Create a prioritised list of your tasks based on the above step.</p><p>Use a simple and use a simple “to do”, “doing” and “done” board to move through your tasks.</p><p>Avoid multi-tasking — focusing on one task will help you move things to “done”.</p><h3>8. Time-box your small tasks</h3><p>With fresh eyes, take another look at your 2-minute tasks pile. If there is anything that you think isn’t worthwhile, don’t do it.</p><p>Then, book 10-minute slots in your calendar for the rest. Repeat until you have got through all the small tasks.</p><h3>9. Time-boxing the quick wins</h3><p>Go back to your prioritised list and put some time in your calendar to work on the quick wins.</p><p>Give yourself some slack — if you think you’ll need more time to plan a task or follow up on it, make sure you’ve put in time for that too!</p><p>Once you’ve got through the quick wins, you can then go in to more detailed planning for your “major projects” quadrant. Revisit your list regularly to make sure your are focusing on what matters.</p><h3>10. Repeat!</h3><p>Repeat this process regularly and adapt this technique to better suit your ways of working. You may find it helpful to incorporate other methods like the Pomodoro Technique to help progressing your tasks. A quick Google search on productivity hacks will get you inspired.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8f5038feba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving agile training at Cancer Research UK — part 1]]></title>
            <link>https://juliamgodinho.medium.com/improving-agile-training-at-cancer-research-uk-part-1-6d0cb8bdfee1?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d0cb8bdfee1</guid>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 10:25:18 GMT</pubDate>
            <atom:updated>2020-05-09T00:23:16.176Z</atom:updated>
            <content:encoded><![CDATA[<h3>Improving Agile training at Cancer Research UK — part 1</h3><p>When I arrived at Cancer Research UK, the Agile team were preparing to use <a href="https://medium.com/@juliamgodinho/using-objectives-and-key-results-with-your-team-a0ce5a935b58">Objectives and Key Results</a> (OKR) for the first time.</p><p>One objective the team was keen to work on was improving their agile training offering. I spent some time with the Agile Coaches to gauge the motives behind this and to understand what they needed out of training. I also had the opportunity to shadow my colleagues delivering one training session — Agile Fundamentals.</p><p>Two weeks in, as a team, we decided that we would try out the goal-setting methodology with two OKRs. I asked to take ownership over the second one: <strong>Improve basic Agile training modules</strong>. Taking ownership of this OKR meant that I would be responsible for reporting the progress that the team were making towards the objective.</p><p>At that point, I was the person with the most bandwidth to take on some work. I decided to dedicate a week to work on some initial discovery and involve my colleagues at key points in time.</p><p>Each of the three Key Results was broken down into a first iteration of initiatives (individual steps that describe what you will do to achieve your objective), which later evolved as I gained more context and knowledge on the subject.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qI0JEBGfEJmEbVGCgf4pg.jpeg" /><figcaption>First iteration of breaking down the objective and its key results.</figcaption></figure><h3>Providing context</h3><p>The first activities that I conducted were around<strong> unpacking existing knowledge</strong> of the agile training offering. This included identifying the main <strong>business drivers</strong> behind agile training at Cancer Research UK. I identified business goals by consulting different strategies in the <a href="https://medium.com/cancer-research-uk-tech-team-blog/the-cancer-research-uk-design-principles-5aa37a95cc76">Technology directorate</a>, which included embracing new ways of working, enabling collaboration, and embedding continuous improvement and a test and learn approach.</p><p>During this context-setting phase, I also sought to <strong>map out how people seek and receive agile training</strong> at Cancer Research UK. This resulted in a journey map which identified other areas for improvement (we’ll keep this for later!). I also <strong>identified the type of people who sought or could seek training</strong> in order to interrogate whether the training is or can be designed for them.</p><p>I then reviewed the training material of two different modules — Agile Fundamentals and Agile Methodologies in order to understand the work that had already been done to review the training modules and their learning objectives. Once reviewed, I <strong>identified the current and past training learning objectives</strong>. As part of this review, I conducted a <strong>SWOT analysis</strong> of the training modules with the Agile Coaches in order to identify the strengths, weaknesses, opportunities and threats from the perspective of those who deliver the training. This was carried out with the intention of picking up what might not come out of the participant’s responses to the pre and post training questionnaires.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gXvqso5aH7PhCuwW66VSig.png" /><figcaption>Current learning objectives for agile training at Cancer Research UK.</figcaption></figure><p>At this point, some questions started to arise. Are these the right learning objectives? Is this what people want or expect to learn? Does the training content meet the learning objectives? Is training even the right format to help the business achieve its goals? Motivated by these questions, I moved on to defining the problem and drafting an initial hypothesis.</p><h3>Defining and fleshing out the problem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bGTv_W8mN2Oxi28DlJmH9Q.png" /><figcaption>Training participants’ expectations grouped into themes.</figcaption></figure><p>Seeking to understand what people want or expect to learn, I looked into the pre-training questionnaire that is sent to all participants before the session. The questionnaire consists of questions that gauge the participant’s knowledge on agile and their expectations of the training — the latter providing qualitative data that I was then able to analyse and group participants’ expectations and needs into themes:</p><ul><li>Improving ways of working</li><li>Broaden agile knowledge</li><li>Relevance to Cancer Research UK</li><li>Personal development</li></ul><p>I then asked the Agile Coaches to <a href="https://gamestorming.com/dot-voting/">dot vote</a> the five participants’ expectations they believed would bring the most value if we were able to determine whether we could meet them through our training offer. The expectations below will inform the development of a set of training learning objectives that will be tested with participants and will shape the content audit at a later stage:</p><ul><li>Learn practical tips to improve ways of working</li><li>Know and be able to explain what agile is</li><li>Know how to encourage an agile mindset in a team</li><li>Understand what agile means for CRUK</li><li>Understand how agile is applied in a non-tech environment</li></ul><p>The post-training questionnaire also offered insightful data on whether the training met the participants’ expectations and what could have been done better. One of the five quantitative questions particularly stood out: “How confident do you now feel to use the learning from this session in your role?”. In both training modules, this was the question that scored lowest. We believe that this deserves more attention as it defines the core foundation of the problem space: <strong>people who participate in the basic agile training sessions are not as confident as they could be in applying what they learn in the agile training sessions to their role because they feel as if they leave without any tools or techniques to do so.</strong></p><p>As an assumption, we believe that if we could solve this problem, it would impact the participants positively by providing them with just enough knowledge to start applying what they have learnt to their day-to-day role. This would also satisfy the business’ appetite as it would promote a way of working that is more collaborative and focused on continuous improvement.</p><p>At this point, I started to think about ways that this could be validated and evaluated — which I will address later on in this post. As an initial hypothesis, we believe that if we can better manage expectations through clear learning objectives (and refine the training content to better reflect them) and demonstrate how agile values, principles and practices can be applied to participants’ context of work, participants will feel more confident in applying their learnings to their role.</p><p>All the while, throughout these two phases of discovery we were continuously acknowledging, challenging, testing and sometimes validating our assumptions which proved to be a useful tool when it came down to defining a hypothesis as we were able to pick a focal point for experimentation and maximise learning based on the five participant’s expectations we decided to focus on for our first iteration.</p><h3>Exploration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLBelg7K1nzQh1QtEnThdA.jpeg" /></figure><p>Having defined the problem space, this exploration phase sought to look further into the themes and patterns that have come up throughout the previous discovery phase. We also wanted to understand what “good” training looked like by exploring external training offered by agile trainers and certification and accreditation bodies such as <a href="https://icagile.com/">ICAgile</a>.</p><p>We then dove deeper into the post-training questionnaire to understand what participants most found useful and what they thought had room for improvement. By analysing the participant’s responses, we identified that they found the training to be useful and engaging — especially when using activities to explain concepts. However, many participants felt that there was no attempt of contextualising agile to the work that takes place at Cancer Research UK, and that they left the training without understanding how they could put their learning into practice, as noted by a participant’s feedback:</p><blockquote><em>“I think the training could be excellent but as it was all new methodology and there were no relevant examples of how we could apply it to our type of work it felt difficult to see the obvious application.” </em>(anon., post-training questionnaire)</blockquote><p>This suggests that the training, in part, doesn’t meet the participant’s initial expectations as laid out in the pre-training questionnaire.</p><p>From this analysis, with the prioritised list of participants’ expectations, both the positive and negative statements were transformed into opportunities by framing them as <a href="https://designsprintkit.withgoogle.com/methodology/phase1-understand/how-might-we">How Might We</a> (HMW) questions:</p><ul><li>HMW concisely explain the agile principles in a way that is relateable and relevant to all types of participants?</li><li>HMW create a balance between communicating agile as a mindset and providing some practical tools and techniques to put agile into practice?</li><li>HMW include examples of agility in Cancer Research UK in a way that non-tech people can relate to?</li><li>HMW improve group activities in a way that participants understand how the underlying message links back to agile?</li><li>HMW encourage participants to leave with an action to apply/explore what they have learnt?</li></ul><p>These are the prioritised, overarching How Might We questions that can be used for an initial round of testing. Once learning objectives have been drafted, and the time comes to suggest a first iteration of improvements to the training content, the full list of HMWs will be revisited to see if any others are worth exploring again.</p><h3>Next Steps</h3><p>The next steps will involve iterating on the training modules’ learning objectives to reflect the participants’ expectations and what the trainers can realistically offer in a two-hour session. To test whether these expectations can be met, we will need to audit the training content and suggest and implement improvements if there is a mismatch between the content and the learning objectives.</p><p>During the exploratory phase, I attended a Lean Workshop session held by Cancer Research’s Service Design team. I bought my work forward, and a small group worked alongside me to think about ways I could get this research out to the organisation to validate and test the assumptions we had made.</p><p>We focused on the participant’s ability to apply their learnings to their role. This involves different factors that will need further unpacking. The first involves understanding what level of practical takeaways is useful for participants and realistic for the trainers. The other involves understanding how to evaluate the confidence levels of those applying what they’ve learnt during training — whether it be understanding the different levels of engagement or defining what characteristics participants may display if they feel confident in applying learnings. More to come on this!</p><p>As an initial test, we would like to better understand the first factor: <strong>how many tools and techniques are enough to enable participants to work in a more agile manner?</strong> A possible technique to test this is a <strong>concierge test</strong>. The idea behind the technique is that you do the user’s job for them so that you can develop a better understanding of them and their interactions. This form of testing shouldn’t be used to validate a solution hypothesis (<a href="https://grasshopperherder.com/concierge-vs-wizard-of-oz-test/">as it isn’t good for testing out solutions</a>), instead, it can be used to generate new ideas. In this case, this would involve following up with participants to understand if and how they are applying what they learnt, and then providing agile coaching to get them to a point where they feel comfortable in doing so. The gaps in knowledge and/or opportunities identified can then be used to improve the training. This idea will be explored in further posts — watch this space!</p><p><em>Read Part 2 </em><a href="https://medium.com/@juliamgodinho/improving-agile-training-at-cancer-research-uk-part-2-7efae821410e"><em>here</em></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d0cb8bdfee1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day in the life of an Agile Coach at Cancer Research UK]]></title>
            <link>https://juliamgodinho.medium.com/a-day-in-the-life-of-an-agile-coach-at-cancer-research-uk-597b004b57b6?source=rss-8cf4f23db592------2</link>
            <guid isPermaLink="false">https://medium.com/p/597b004b57b6</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Julia M. Godinho]]></dc:creator>
            <pubDate>Sat, 09 Mar 2019 10:52:49 GMT</pubDate>
            <atom:updated>2019-03-09T10:52:49.220Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Julia Godinho and Taruna Robinson, Agile Coaches at </em><a href="https://medium.com/cancer-research-uk-tech-team-blog"><em>Cancer Research UK</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*HTCrISCpdY9teIPdK_QLaA.jpeg" /></figure><h3>Describe your role in three words?</h3><p><strong>Collaborative.</strong> We work with individuals and teams across the whole organisation, enabling them to work better together.</p><p><strong>Experimental.</strong> Cancer Research UK is a learning organisation. We are open for experimentation and want to foster an environment where it’s safe to fail — we’re interested in resilience and our ability to bounce back. We learn from both our successes and failures.</p><p><strong>Diverse.</strong> No one day is the same!</p><h3>What does a typical day look like for you?</h3><p>Agile Coaches at Cancer Research UK work across different products and initiatives in the Technology department and beyond. And, as mentioned, no one day is the same!</p><p>We typically start the day with team stand-ups, an opportunity for team members to update each other on our progress and agree on what we will work on next. If there are any blockers, we will help the team to remove them so they can get on with their work.</p><p>Twice a week, the Technology department come together for a stand-up. Individuals and teams present what they have been working on. Topics are varied and have included results from trialling remote demos to finding out about emerging technology experiments with artificial intelligence.</p><p>The rest of the day is varied and can include coaching individual team members about ways of working or development opportunities, and preparing for and facilitating workshops for our product teams or other non-tech teams — we especially enjoy running team vision and values sessions! We also facilitate the regular Agile events for our teams, such as planning, refinement and retrospectives.</p><p>The Agile team also have different meetings throughout the week focused on the team’s development. Every two weeks we hold a remote Community of Practice session for people across the organisation who are interested in Agile. We either facilitate them in a Lean Coffee style, or people present projects they have been working on. Topics have ranged from non-violent communication to exploring tools for distributed teams. Either way, it is a great opportunity to find out more about Agile ways of working across the organisation, especially in non-tech environments.</p><p>Regularly, the team provide training for anyone in the organisation who wants to learn more about Agile. We have two core training modules, but also offer ad hoc training such as user story writing and estimation and planning.</p><h3>What is the best thing about working in your role?</h3><p>The thing we most enjoy about our role is that we get to work with such a diverse group of people. It is gratifying to see them develop, achieve their goals and do such meaningful work for a great charity. We take pride in being part of this, supporting and motivating these people and their teams to work well together to create things that help the organisation reach its mission of beating cancer sooner.</p><h3>How did you begin your career at CRUK?</h3><p>Before working at Cancer Research UK, we both were already working as Agile Coaches in other organisations. The rest of the Agile team have held roles, such as a Scrum Master, Agile Delivery Manager or Product Managers. There isn’t one single pathway to become an Agile Coach, but key skills such as empathic listening, facilitation and problem solving come in handy!</p><h3>What is your greatest achievement since joining CRUK?</h3><p>When teams are willing to try out something new and embrace an experimentation mindset. When it pays off for them (even if it means learning from a failed experiment), it is always gratifying to hear “thanks — that’s really working for us!”.</p><h3>What Advice would you give to someone who is looking to join the team?</h3><p><strong>Embrace the sense of community!</strong> As a team, we are always open and willing to help each other. From co-designing sessions, coaching the coach, and filling in when needed, be prepared to help.</p><p><strong>Be bold!</strong> Be open to trying out new things even if it means stepping out of your comfort zone.</p><p><strong>Honesty is the best policy.</strong> As Agile Coaches, we want to mirror the behaviours we want to see in our teams. To encourage safe and trusting environments, we believe it is crucial to have open and honest conversations. Don’t be afraid to voice your opinions — we all are working towards the same goals!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=597b004b57b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>