<?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 Richard Stowey on Medium]]></title>
        <description><![CDATA[Stories by Richard Stowey on Medium]]></description>
        <link>https://medium.com/@richardstowey?source=rss-ce7fd885763a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*sabP7_pO8fluuFQGcBHTMw.jpeg</url>
            <title>Stories by Richard Stowey on Medium</title>
            <link>https://medium.com/@richardstowey?source=rss-ce7fd885763a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:45:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@richardstowey/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[8 Pieces of Advice to My Future Self — The Transition from Scrum Master to Product Manager]]></title>
            <link>https://medium.com/@richardstowey/8-pieces-of-advice-to-my-future-self-the-transition-from-scrum-master-to-product-manager-e2e1573fe467?source=rss-ce7fd885763a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2e1573fe467</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[inspect-and-adapt]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Richard Stowey]]></dc:creator>
            <pubDate>Wed, 15 Jan 2020 21:49:53 GMT</pubDate>
            <atom:updated>2020-01-15T21:49:53.174Z</atom:updated>
            <content:encoded><![CDATA[<h3>8 Pieces of Advice to My Future Self — The Transition from Scrum Master to Product Manager</h3><p>As I make the transition from Scrum Master to Product Manager I have taken the opportunity to put together a few words of advice for myself, from myself. I hope that it serves as a reference from which to look forward and back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x30gJ3L5arUuM6lRiHnDyQ.jpeg" /></figure><h4>Practice What I Would Preach</h4><p>I have been using Scrum for over two years and, in my most recent position, I’ve spent just over a year as a dedicated Scrum Master across three teams who build mobile and web apps. I am about to make a transition to the role of Product Manager for one of the web app teams, as well as coaching the teams on better ways of working, facilitation techniques and organisational design.</p><p>I have spent a lot of my time improving our understanding of Scrum, building structures within the team to handle cross-functionality and preaching about myriad of ways which things can be done better, all based on repeated inspection and adaptation with the teams.</p><p>I am fortunate enough to work with a group of talented people who have been honest about impediments and the need to change to make things better. Whilst much of my focus prior was on suggesting solutions which could be put in place, I now have more of an opportunity to put into practice some of the methods I’ve been recommending.</p><p>The following 8 pieces of advice are for the future me to look back on, with the goal of achieving the best for myself and those who I work with.</p><h4>1) Paint an Optimistic Future (and Share It!)</h4><p>When receiving regular pressure to make progress, from outside of the team, it’s all too easy to forget about the mid- and long-term future for the team. Secondary to that, it’s all too easy to verbalise something which fills a gap, but inevitably changes over time, and is more subject to unintended deviation.</p><p>Firstly, put some meaningful and considered thought into what the future holds, as a collaborative effort. Create something which represents a Product Vision, and define a Strategy for how to meet that vision.</p><p>Secondly, share the vision, share it again, and again. Then share some more.</p><h4>2) Be Collaborative</h4><p>Locally, within the team, it’s super important that everyone is on the same page, moving in the same direction, and has the best possible understanding of what is happening, and are contributing to the momentum.</p><p>There’s also a wealth of knowledge and experience both within the team and across the business when it comes to product performance, ideas and issues.</p><p>Join forces, with just the right amount of why, when and how, to both fully understand problems and define solutions.</p><h4>3) Transparency</h4><p>It’s not just about making sure the short-term work and long term vision is visible to everyone. There’s plenty more to it than that.</p><p>Be transparent with decision making, team performance, objectives, user research and testing, mission. Experiment with new ideas like the North Star Metrics — focusing on generating a set of transparent leading metrics to live by.</p><h4>4) Set a Good Pace</h4><p>Taking a systems thinking approach to work: minimising work in progress, shortening feedback loops and maximising the delivery of value to the end customer is of paramount importance.</p><p>Remember to focus on delivering value each iteration, whilst educating myself and others about the approach. When talking about a good pace, I mean the continuous delivery of value which is sustainable and repeatable.</p><p>Focus heavily on adding value to the team during the current and next iteration.</p><h4>5) Get Closer To The Customer</h4><p>I’ve probably repeated this statement every Sprint, across three or four teams, for the past year. It’s the single most important thing to do when it comes to validating the value that may have been or may be delivered.</p><p>And yet it’s the easiest to get out of the habit of doing.</p><p>Set a target for research and testing, and make it a habit. Start with a general set of assumptions to test and questions to answer. Build on it from there, adding specific tasks / questions / tests when the cycle of the product demands it.</p><h4>6) Remain Objective</h4><p>As a Scrum Master, when you remove yourself from the “what” and focus mostly on the “how,” it’s so much easier to be in a state of mind which allows you to be objective about ideas, situations, people, processes, communication and tools.</p><p>When you are in a position where you come up with more of the answers, and make more decisions, it’s naturally more difficult to keep track of what communication has been made about each one.</p><p>Objectivity shouldn’t necessarily be reserved for one person on a team, but be a state of mind which anyone can tap into at any moment, to reflect without prejudice.</p><p>One especially important part of this is to be a very regular part of the retrospective. Don’t skip it. Prioritise it. Use it to evaluate progress and continue to refine our approach, together.</p><h4>7) Focus</h4><p>The Scrum Master role requires a level of regular adaptation and multi-tasking to adapt with the needs of the team in relation to removing impediments.</p><p>As a Product Manager, I believe there’s more of a need to set a clear vision and relentlessly aspire towards that. With a product focused approach to delivering better outcomes, and focusing on the metrics which make that happen.</p><h4>8) Balance</h4><p>There’s always a balance.</p><p>Looking into the future and all the new shiny toys that it could bring. Focusing on the present to ensure maximum output and minimal friction. Maintaining a healthy view of past outputs to ensure good performance. Staying in touch with the rest of the business. Ensuring we understand our users well enough.</p><p>This is probably the hardest of all my advice to myself, and yet needs to remain the most fluid. Each iteration will need to adapt to focus on the right amount of each. Just remember not to forget either one, reset regularly and adapt frequently.</p><p>What I’ve captured above is a snapshot of the main things which are front of mind at the moment. Each one isn’t difficult in itself. However, when combined into an approach, which works in a well balanced harmony, evolves into a healthy challenge.</p><p>Let the new adventure begin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2e1573fe467" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>