<?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[Product Lunch Club - Medium]]></title>
        <description><![CDATA[We’re a group of enthusiastic product people who meet for lunch in Bristol once a month - Medium]]></description>
        <link>https://medium.com/product-lunch-club?source=rss----8ab58010619d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Product Lunch Club - Medium</title>
            <link>https://medium.com/product-lunch-club?source=rss----8ab58010619d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:08:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/product-lunch-club" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Complexity Theory vs Strategic Delivery]]></title>
            <link>https://medium.com/product-lunch-club/complexity-theory-vs-strategic-delivery-512f039f0110?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/512f039f0110</guid>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Alexander Moore]]></dc:creator>
            <pubDate>Tue, 03 Aug 2021 12:17:49 GMT</pubDate>
            <atom:updated>2021-08-03T12:17:49.431Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unknown unknowns, how do we know?</h4><figure><img alt="A tree with wiggly roots criss crossing" src="https://cdn-images-1.medium.com/max/1024/0*6e_bw02TBZjQFQyO" /><figcaption>Life is …. complicated</figcaption></figure><p>Before I start this article two bits of housekeeping;</p><ol><li>If you read my first foray in to article writing and have comeback to read this then <strong>thank you</strong> :-) I appreciate all the kind words and feedback I have received so far. Although this topic wasn’t suggested as my next article I decided to write on this because….</li></ol><p>2. Complexity theory is something I find interesting, I <em>dig it</em>. However, I am no expert but I was inspired to put some words down on this because of this David Perell quote <em>“Read to collect the dots, write to connect them.”</em> So apologies in advance if this article involves a lot of dot connecting.</p><h3><strong>Complexity</strong></h3><figure><img alt="Toy dinsaur" src="https://cdn-images-1.medium.com/max/1024/0*tsDU1NbBWDhLip8R" /><figcaption>ROAR! scary dinosaur</figcaption></figure><p>So what do I know about complexity? My first real understanding of this came many years ago whilst reading Jurassic Park — random but bear with me - and as the characters do their best to not get eaten by the lovable reptiles, Ian Malcolm (Jeff Goldblum) states <em>“What you study, you change”</em>.</p><blockquote>This was one of those little nuggets of wisdom that was so simple, but I had never really thought of it before.</blockquote><p>“What you study, you change” was attributed by Ian Malcom to Heisenbergs Uncertainty Principle but is actually the <a href="https://en.wikipedia.org/wiki/Observer_effect_(physics)">Observer effect</a>!</p><p>As soon as you observe something you can impact that “something” in unforeseen ways, what you observe or build — say a dinosaur theme park or a strategy — may be perfectly practical when you model it, but as soon as you open your strategy to the world there are numerous factors that can impact this. There are always other forces perhaps ones you don’t know exist (Unknowns) or that do not even exist yet (Unknown Unknowns) that may impact behaviours.</p><blockquote>You obviously can only plan for what you know, but perhaps this reflects the importance of due diligence, do your homework and uncover as many variables as you can. The more factors you can build in to your modelling the more robust your strategy will be.</blockquote><h3><strong>Complexity and Strategy</strong></h3><p>Whilst thinking about the various ways uncertainty and complexity can impact strategic delivery I have split my thoughts in to two categories:</p><h4><strong>Internal factors</strong></h4><p>In my first draft I had originally written a long old list of internal factors that could impact a business, but scratch that! Actually what is more important is; is your strategy, the organisation, the “you” able to deal with internal pressures and change?</p><ul><li>Do you have staffing capacity in case you lose employees at short notice?</li></ul><figure><img alt="Cheesey picture of two colleagues high fiving" src="https://cdn-images-1.medium.com/max/1024/0*oVbpjdl-9UJ9InPx" /><figcaption>Hahahaha such fun</figcaption></figure><ul><li>Can your organisational structure handle any change needed to deliver new strategies?</li><li>Are managers able to communicate to their direct reports effectively? Does your messaging get lost as it is passed through the organisation?</li><li>Are employees incentivised and engaged to deal with new ways of working and embrace change?</li><li>Are you able to recognise change within your own organisation and able to react to it?</li></ul><p>Any of these internal factors (plus plenty more) can impact your chances of success, sometimes this can be like whack-a-mole, where as you cover one issue this may spark off a fresh and completely new issue to pop up.</p><blockquote>There are various tool to help you deal with this but perhaps some of the most helpful approaches you can take is ensure you have a shared understanding across the organisation of the vision and strategy and have effective feedback loops in place to track how successful your plans are tracking.</blockquote><h4><strong>External factors</strong></h4><p>I don’t <em>think</em> that understanding the danger of complexity theory means you can avoid the impacts of unforeseen events, but it does mean you can prepare and build a robust enough business model to survive them and a framework that lets you react to them.</p><p>Now I suspect everyone can think of an unforeseen external event that can impact a business!</p><p>As a more specific example, a sector that has done well out of our recent need to all stay at home is the food delivery service. In the UK the big players are Deliveroo and UberEats and in the US they have DoorDash, GrubHub and UberEats all of whom are well known and taking plenty of orders but were really struggling to make a profit out of food delivery. Who knows what would have happened if that world hadn’t changed but huge swathes of the population staying in and ordering out gave these companies an opportunity to survive until we started opening up again and profits dropped once more.</p><blockquote>That unexpected surge in profitability gave these companies a chance to invest and pivot into other directions, now they are expanding from trying to increase the delivery basket size “whilst we are delivering your KFC shall we pick up some toilet rolls and a dishwasher tablets for you”, to the more profitable alcohol delivery service and even delivering for big supermarkets, users can now pay for delivery from their local store to their home via UberEats.</blockquote><p>Where Amazon are the kings of <em>next day</em> delivery these companies are looking to own the <em>next hour</em> space. (for those interested in this specific example there is a great podcast on it by Business wars “Food Delivery Wars”)</p><figure><img alt="An UberEats driver gets ready to hop on his bike and delivery something tasty" src="https://cdn-images-1.medium.com/max/1024/0*5ordo2B2Fqv_VH7k" /><figcaption>Other delivery services are available</figcaption></figure><p>But of course the unknown may not give you that extra burst of cash revenue that can propel to you to success, changes in economies can affect in so many ways, impact may change and sometimes what was originally beneficially and feels like a great success may turn out to be negative even though your strategy was sound tides may turn and factors change. The internet helped Jeff Bezos expand from running a small online bookstore to going in to space But how many companies didn’t react to the same digital age and are now distant memories (remember Kodak, Blockbuster and Wimpy)?</p><h3><strong>How to Pull this all Together</strong></h3><p>Going back to my youth (ending like I began) in distant past when I studied Economics we talked about Ceteris paribus or “everything being equal” this term meant when doing modelling we could say, in the short term if X moves this way then Y will move that way e.g. Supply and Demand.</p><p>Everything being equal is often how strategies are created, “<em>based on where we are now and what we know at the moment we should do this</em>”, based on the current factor of X we should do Y. That isn’t necessarily a bad thing but perhaps we should just be aware that X can change or perhaps Z will turn up to confuse things for 6 months. Things change, people change, organisations change and economies change, just be aware that it happens build it in to your framework and ensure that you and your organisation is well equipped to handle instability and can adapt to the ever changing tapestry of life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xInOlxP__IzT4r3o" /><figcaption>The end is near</figcaption></figure><p>Hopefully you have found my attempts to “connect the dots” on complexity interesting, it is something I am still reading and learning about so please get in touch with any thoughts or resources that you have enjoyed.</p><p>Have a nice day</p><p>Alex</p><p><em>Here at Product Lunch Club </em>🥪<em> we’re a group of product people who meet regularly over lunch to help, encourage and support each other in our roles. </em><a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><em>Come and join us</em></a><em>! </em>🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=512f039f0110" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/complexity-theory-vs-strategic-delivery-512f039f0110">Complexity Theory vs Strategic Delivery</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Roadmaps Visual]]></title>
            <link>https://medium.com/product-lunch-club/making-roadmaps-visual-679a3937e1c6?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/679a3937e1c6</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[shared-understanding]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alexander Moore]]></dc:creator>
            <pubDate>Fri, 09 Jul 2021 13:21:56 GMT</pubDate>
            <atom:updated>2021-07-09T13:21:56.446Z</atom:updated>
            <content:encoded><![CDATA[<h4>Don’t hide your backlog in the shadows — bring it out into the light!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nYqOd7UmNJ95Xh3RhFmS_g.png" /></figure><p>Working in Product you will get many many (many!) requests for development, these requests should <em>always </em>be listened to and then prioritised in accordance to the strategic value of the item. i.e. how much does it help us on the path to achieving our vision. That prioritisation is your roadmap, the most important use of the roadmap is the ability to present stakeholders a clear illustration of the path to achieving our goals.</p><p>First things first, before you built your roadmap you should already have created your Vision and your Strategy, these are the first things you should have in place, the roadmap is there to bring the vision and strategy to life!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*6IcJ8A4kCqyFWRp2NnsXpg.png" /><figcaption>Bring the strategy to life</figcaption></figure><p>Things to consider when building your roadmap:</p><ul><li>Any item on your roadmap should add value to your strategy (and you should be able to demonstrate this if challenged)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/167/1*bC1tgRyNu5w4PCZ0XeeHMA.png" /><figcaption>A backlog shows all the individual tasks</figcaption></figure><ul><li>You need to show <em>what needs to be done, but not how</em> we do it (that will be your backlog)</li><li>It should help your team understand and prioritise in accordance with the strategy</li><li>You should be able to share this roadmap to your senior execs and they should be able to understand it</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*M7DgoSptwxw7dS4kidM_sg.png" /><figcaption>The roadmap is the strategic vision for what we want to build</figcaption></figure><ul><li>Remember the roadmap should be there to communicate to stakeholders it needs to be clear</li></ul><h4><strong>Ways of bringing clarity</strong></h4><p>Generally, the approach to Product Roadmaps seems to be inspired by Project Managers and their lovely Gantt Charts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*ANUNoaBEChIoHDkEE5U79Q.png" /><figcaption>Roadmaps often look a bit like this</figcaption></figure><p>Providing this level of detail is great as an aspirational tool, but in a truly agile environment can delivery be that well defined? Also, what do your stakeholders value, do they really care about which quarter each item will be delivered a date which may well change as roadmaps are reviewed and refined. Or perhaps the real value is in “what is coming next”, where in the queue is that item they are waiting for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/192/1*PagEMDjQguosm4RjVS28fw.png" /><figcaption>Keep working that roadmap</figcaption></figure><p>I emphasise this as the roadmap is something you will continue to refine, and as each development request is raised it is important that they are reviewed in line with the vision and strategy and items shuffled accordingly. No doubt many of you will have experienced seeing that lovely feature so close to being developed endlessly pushed back as new more strategic items drop into the roadmap.</p><h4><strong>So how about</strong>….</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*T1cpv_Tx-SPDtnd9fK-6IA.png" /></figure><p>One way of focusing on the priorities is looking in terms - short, medium, and long term (AKA Now, Next, Later). This removes some of the detail around timing of items and focuses on priority. In all things we do, we should look to hide the complexity, and this is certainly a simple way of showing the roadmap to your stakeholders.</p><p>I prefer to refer to short term rather than “now” as stakeholder expectations should always be considered / managed :-)</p><h4><strong>Or….</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*QQjUP74feJpMKQKeWBAxdQ.png" /></figure><p>This format reminds me of a Kanban board in design but I think it works well at providing clarity. Having a “To be prioritised” column isn’t essential but I think it is useful to stakeholders who have raised items as they will be invested in seeing them recognised. The table like format seems to resonate well with users and perhaps is a intuitive layout than the Now, Next, Later approach above.</p><blockquote>Note: The reason I have crossed out the “one day” box is that although I know it is used with this template for me it doesn’t add value. The final product is set by the vision and most likely will be an ever changing target as complexity and uncertainty make themselves know upon our vision and strategy.</blockquote><p>As always there are many ways and there are no wrong answers (well maybe a few!), for a real world example from a great Product led company check out the <a href="https://monzo.com/blog/2018/06/26/monzo-time">Monzo roadmap</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*RhaQFMILFuy5j1iBDvIY_Q.png" /><figcaption>Monzo are forward thinking with sharing the roadmap</figcaption></figure><p>Whatever approach you decide to take, just ask yourself:</p><ul><li>Could I show this to my team, technology, stakeholders or even my CEO and explain it in 5 minutes?</li><li>As new items come in and move through the prioritisation is their position on the roadmap clear?</li><li>Am I showing the right items? Remember the roadmap is your strategic vision, the detail will be on the backlog.</li></ul><p>Above all else, don’t be afraid to mix things up, if an approach doesn’t work make adjustments and move on. The important thing is that at any point there is clarity, clarity creates certainty and certainty leads to success!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/96/1*0YeNs5E0DQdfciu6kDmOhw.png" /><figcaption>Success = a person with a flag on some steps(!)</figcaption></figure><p>Do you use a different model to the above? Get in touch and let me know what works for you.</p><p>So dear reader what did you think? This was my first attempt at an article so get that feedback loop going. What was hot what was not, please be honest… Well honest-ish.</p><p><em>Here at Product Lunch Club </em>🥪<em> we’re a group of product people who meet regularly over lunch to help, encourage and support each other in our roles. </em><a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><em>Come and join us</em></a><em>! </em>🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=679a3937e1c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/making-roadmaps-visual-679a3937e1c6">Making Roadmaps Visual</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 Recommended Summer Reads for Product People and Beyond…]]></title>
            <link>https://medium.com/product-lunch-club/15-recommended-summer-reads-for-product-people-and-beyond-dd1518383c46?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd1518383c46</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[vacation]]></category>
            <category><![CDATA[book-recommendations]]></category>
            <category><![CDATA[summer-reading]]></category>
            <category><![CDATA[meetup]]></category>
            <dc:creator><![CDATA[Phil Osmond]]></dc:creator>
            <pubDate>Wed, 23 Jun 2021 18:59:59 GMT</pubDate>
            <atom:updated>2021-08-03T12:25:59.900Z</atom:updated>
            <content:encoded><![CDATA[<h4>Plus one bonus podcast!</h4><p>This month’s Lunch Club was dedicated to summer reading recommendations. What books have we been reading that we’d like to recommend and which titles will we be adding to our wish-lists?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZYztDDKXxx2R7jX-" /><figcaption>Photo by <a href="https://unsplash.com/@ohlennart?utm_source=medium&amp;utm_medium=referral">Lennart Heim</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>In no particular order…</h3><p><a href="https://www.goodreads.com/book/show/48710241-futureproof">Futureproof: 9 Rules for Humans in the Age of Automation</a> by Kevin Roose</p><p><a href="https://www.goodreads.com/book/show/50849430-capital-and-ideology?">Capital and Ideology</a> by Thomas Picketty</p><p><a href="https://www.goodreads.com/book/show/1632801.Strange_Stories_Amazing_Facts">Strange stories, Amazing facts</a> by Readers Digest</p><p><a href="https://www.goodreads.com/book/show/4371507-the-age-of-wonder">The Age of Wonder: How the Romantic Generation Discovered the Beauty and Terror of Science</a> by Richard Holmes</p><p><a href="https://www.goodreads.com/book/show/4099.The_Pragmatic_Programmer">The Pragmatic Programmer: From Journeyman to Master</a> by Andy Hunt, Dave Thomas</p><p><a href="https://www.goodreads.com/book/show/48716700-ask-your-developer">Ask Your Developer: How to Harness the Power of Software Developers and Win in the 21st Century</a> by Jeff Lawson</p><p><a href="https://www.goodreads.com/book/show/53518409-good-services">Good Services: How to Design Services that Work</a> by Lou Downe</p><p><a href="https://www.goodreads.com/book/show/25814544-sprint">Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days</a> by Jake Knapp</p><p><a href="https://www.goodreads.com/book/show/18050143-zero-to-one">Zero to One: Notes on Startups, or How to Build the Future</a> by Peter Thiel, Blake Masters</p><p><a href="https://www.goodreads.com/book/show/22616127-exponential-organizations">Exponential Organizations: Why New Organizations Are Ten Times Better, Faster, Cheaper Than Yours (and What To Do About It)</a> by Salim Ismail, Mike Malone, Yuri van Geest, Peter H. Diamandis (Foreword)</p><p><a href="https://www.goodreads.com/book/show/35485215-pig-wrestling">Pig Wrestling: Clean Your Thinking to Create the Change you Need</a> by Pete Lindsay, Mark Bawden</p><p><a href="https://www.goodreads.com/book/show/24611735-black-box-thinking">Black Box Thinking: Why Some People Never Learn from Their Mistakes — But Some Do</a> by Matthew Syed</p><p><a href="https://www.goodreads.com/book/show/49208734-what-ceos-need-to-know-about-design">What CEOs Need To Know About Design: A business leader’s guide to working with designers</a> by Audrey Crane</p><p><a href="https://www.goodreads.com/book/show/225111.The_Laws_of_Simplicity">The Laws of Simplicity: Design, Technology, Business, Life</a> by John Maeda</p><p><a href="https://www.goodreads.com/book/show/26156469-never-split-the-difference">Never Split the Difference: Negotiating As If Your Life Depended On It </a>by Chris Voss</p><p>And the bonus podcast: <a href="https://podtail.com/en/podcast/more-or-less-behind-the-stats/">More or Less: Behind the Stats</a> from BBC Radio 4</p><p>These are just recommendations of course, made by a selection of attendees Product Lunch Club —we’ve not all read all of them, but we hope you find some of them helpful.</p><blockquote>Whilst not all of these are directly focused on product management as a discipline, they can help broaden our horizons, inspire our being, feed our minds and help us think critically, looking below the surface.</blockquote><p>Let us know what you think! And have a great summer.</p><p><em>Product Lunch Club plans to be back in full force in the autumn.</em></p><p><em>Here at Product Lunch Club </em>🥪<em> we’re a group of product people who meet regularly over lunch to help, encourage and support each other in our roles. </em><a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><em>Come and join us</em></a><em>! </em>🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd1518383c46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/15-recommended-summer-reads-for-product-people-and-beyond-dd1518383c46">15 Recommended Summer Reads for Product People and Beyond…</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I landed my first Product Management job ‍]]></title>
            <link>https://medium.com/product-lunch-club/how-i-landed-my-first-product-management-job-d646050f57b7?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/d646050f57b7</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Alex Veale]]></dc:creator>
            <pubDate>Tue, 29 Dec 2020 08:02:46 GMT</pubDate>
            <atom:updated>2020-12-29T08:02:42.908Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, my name is <a href="https://www.linkedin.com/in/alexveale/">Alex</a> 👋, I currently live and work in Bristol, UK as a Product Manager for <a href="https://www.kaluza.com/">Kaluza</a>, an energy tech company part of the <a href="https://www.ovo.com/">OVO</a> group.</p><p>Reading this, you may or not know, Product Management is notoriously hard to land a job in without any prior experience. There is not a clearly defined pathway for landing a Product Management role, and people wind up here in different ways.</p><p>I applied to many Product Manager jobs without success. I realised it would be difficult to land a Product Management role without any direct experience in the role, but how would I ever get this illusive Product Management experience if I can’t get a job?</p><p>I wanted to share my experience, and some top tips as to how I landed my first Product Management role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRUqVaA6U6cHFfUogpw10A.png" /></figure><h3>1. Find the right company 💚</h3><p>I started by identifying companies that were a good cultural fit in terms of supporting career development and progression as well as having a strong and established product community. In my search, I came across OVO and I realised early on they were ticking the boxes in these criteria.</p><p>As I had experience working as a Business Analyst (BA) I found a BA role at OVO and was successful in my application and was placed in a position as a BA embedded in a product team. You could follow a similar approach and <strong>consider</strong> <strong>applying for roles where you have experience with the goal of transitioning into a Product Management role internally.</strong></p><p>Upon joining OVO and through the application process I was very open from the outset that my intent and my career development goal was to move into Product Management. I was lucky that I had managers who supported this and helped me shape my career development plan and find opportunities for me to develop my skills.</p><p><strong>If you have a career development goal, share this with your manager, hopefully they will support you.</strong></p><h3>2. Build up experiences &amp; transferable skills 💪</h3><p>My approach was to <strong>look at Product Manager job descriptions, the skills required for the roles</strong> <strong>and</strong> <strong>group them into themes.</strong> Once I had defined these themes, I did a self assessment to build up a picture of where I thought I was currently; strength areas I could demonstrate or skills I might be lacking as development/growth areas. I used <a href="https://trello.com/">Trello</a> to keep a track of this with a particular focus on the growth areas.</p><p>This helped inform my career development plan and the areas I wanted to increase my skills and experience in, for example, I got involved in user research with the UX team at OVO as I identified this as an area I wanted to gain some skills and experience in.</p><p>Using my Trello board I could <strong>capture experiences and work examples based on the themes/skills needed of a Product Manager to then draw on in an interview</strong> (p.s. <a href="https://pmstarterpack.onfielder.com/">PM Starter Pack</a> was a super useful resource for job interview prep).</p><h3>3. Never stop learning 🤓</h3><p>Besides building up your skills and experience on the job, there are loads of great resources to read to learn more about Product Management.</p><h3>Books 📚</h3><ul><li><a href="https://www.amazon.co.uk/dp/1119387507/ref=cm_sw_em_r_mt_dp_U_AjasEb2Z7YW4Q">Inspired</a> by Marty Cagan</li><li><a href="https://www.amazon.co.uk/Sprint-Solve-Problems-Test-Ideas/dp/0593076117/ref=pd_aw_sbs_14_6/261-9027345-9987633?_encoding=UTF8&amp;pd_rd_i=0593076117&amp;pd_rd_r=d8caefd3-a386-4a5d-9f1b-4e10e7697e72&amp;pd_rd_w=nUmZ5&amp;pd_rd_wg=LePqM&amp;pf_rd_p=15216146-4434-47f5-99d9-56240c85bf4d&amp;pf_rd_r=NF59N0QN7RS0PJGWVAH0&amp;psc=1&amp;refRID=NF59N0QN7RS0PJGWVAH0">Sprint</a> by Jake Knapp and co</li><li><a href="https://www.amazon.co.uk/Hooked-How-Build-Habit-Forming-Products/dp/0241184835/ref=pd_aw_sbs_14_5/261-9027345-9987633?_encoding=UTF8&amp;pd_rd_i=0241184835&amp;pd_rd_r=c62abcca-80f0-49fb-9523-6cfc94df697d&amp;pd_rd_w=1IGg7&amp;pd_rd_wg=8tm5p&amp;pf_rd_p=15216146-4434-47f5-99d9-56240c85bf4d&amp;pf_rd_r=2CZ177YYW14TQ3RC3B03&amp;psc=1&amp;refRID=2CZ177YYW14TQ3RC3B03">Hooked</a> by Nir Eyal</li><li><a href="https://www.amazon.co.uk/Lean-Startup-Innovation-Successful-Businesses/dp/0670921602/ref=pd_aw_sbs_14_2/261-9027345-9987633?_encoding=UTF8&amp;pd_rd_i=0670921602&amp;pd_rd_r=1da858a3-3b73-4d7e-a898-b152870d1010&amp;pd_rd_w=wcEx6&amp;pd_rd_wg=rUx0q&amp;pf_rd_p=15216146-4434-47f5-99d9-56240c85bf4d&amp;pf_rd_r=FD24GQ5FYBJGD49PNPNN&amp;psc=1&amp;refRID=FD24GQ5FYBJGD49PNPNN">The Lean Startup</a> by Eric Ries</li><li><a href="https://www.amazon.co.uk/Escaping-Build-Trap-Melissa-Perri/dp/149197379X">Escaping the Build Trap</a> by Melissa Perri</li></ul><h3>Podcasts 🎧</h3><ul><li><a href="https://www.mindtheproduct.com/category/the-product-experience/">The Product Experience</a> from Mind the Product which has some great interviews with many product celebrities</li><li><a href="https://podcasts.apple.com/gb/podcast/jake-and-jonathan/id1320916842">Jake &amp; Jonathan</a> — Jake Knapp and Jonathan Courtney having some light hearted product chat</li><li><a href="https://www.npr.org/podcasts/510313/how-i-built-this?t=1581783307842">How I Built This</a> from NPR, telling the stories of how some of the worlds biggest and best companies and products were built</li></ul><p>There are also many courses and talks available for free across the web. One example is a free Google <a href="https://www.udacity.com/course/product-design--ud509">Product Design</a> course on Udacity which I found really useful.</p><p>This is by no means an exhaustive list but besides these resources, Medium and Twitter and great places to go to follow some of the brightest minds in Product and get an insight into their thoughts, my go-to is <a href="https://twitter.com/johncutlefish?s=21">John Cutler</a>, who regularly tweets out some great stuff.</p><h3>4. Network, network, network 🗣</h3><p>It can be daunting at first to step out of your comfort zone, but just do it. The product community is super friendly and supportive and who better to learn more about product management from than the people who live and breathe it every day.</p><p>There are loads of great events/meetups running around the world, for me, notably those run by <a href="https://www.mindtheproduct.com/">Mind the Product</a>. In Bristol we are lucky to have ‘<a href="https://www.mindtheproduct.com/producttank/">Product Tank</a>’ which runs regularly (approximately every 6 weeks) and <a href="https://productcampsouthwestuk.co.uk/">ProductCamp</a>, an annual “un-conference” (and are both free!). Hopefully there are similar events near you.</p><p>A couple of chaps and I who met at the ProductTank events in Bristol even started the <a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><strong>Product Lunch Club</strong></a><strong> meetup where we meet regularly to discuss various product topics on a lunch time — please do join us!</strong></p><p>There are also lots of great Slack groups that you can join for free and engage with the product community such as:</p><ul><li><a href="https://www.mindtheproduct.com/product-management-slack-community/">Mind the Product</a></li><li><a href="https://productschool.com/slack-community/">Product School</a></li><li><a href="https://product-hive-slack.herokuapp.com/">Product Hive</a></li></ul><p>These are all great places to meet people, talk about Product to learn and grow (whatever stage of your journey you’re at), this was certainly hugely valuable for me when trying to break into Product.</p><h3>Recap! ⏮</h3><ul><li>Consider applying for roles where you have experience with the goal of transitioning into a Product Management role internally</li><li>If you have a career development goal, share this with your manager, hopefully they will support you.</li><li>look at Product Manager job descriptions, the skills required for the roles and group them into themes</li><li>Capture experiences and work examples based on the themes/skills needed of a Product Manager to then draw on in an interview</li><li>Never stop learning and building your network</li></ul><p>Thank you for getting this far and I hope this has been useful to you in some way, if you have any questions or feedback, please drop a comment or get in touch with me on <a href="https://uk.linkedin.com/in/alexveale">LinkedIn</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d646050f57b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/how-i-landed-my-first-product-management-job-d646050f57b7">How I landed my first Product Management job 🧑🏻‍💻</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Once we know the right thing to build, how can we help our teams build it right?]]></title>
            <link>https://medium.com/product-lunch-club/once-we-know-the-right-thing-to-build-how-can-we-help-our-teams-build-it-right-51a24e2a619c?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/51a24e2a619c</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[meetup]]></category>
            <dc:creator><![CDATA[Phil Osmond]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 10:43:01 GMT</pubDate>
            <atom:updated>2020-04-27T10:57:21.974Z</atom:updated>
            <content:encoded><![CDATA[<h4>Product Lunch Club 16th April 2020</h4><p>At this current time of lockdown, we’ve taken Product Lunch Club online in a new virtual format as we <a href="https://twitter.com/hashtag/stayhomesavelives"><em>Stay Home and Save Lives</em></a>.</p><p>This session’s topic was building the right thing in the right way — or in other words, <em>once we know the right thing to build, how can we help our teams build it right?</em></p><p>Essentially this is a story of two parts — effective discovery and efficient delivery.</p><blockquote>When we discover effectively we are more likely to delivery efficiently.</blockquote><p>And it’s a subject close to my heart — so many teams waste time, money and resources building the <em>wrong thing</em> and only find out when it’s too late (usually post-delivery). This is not something agile can help us with — but it’s where we, as product people need to step up, reduce the feedback loops and increase confidence in the solution we are delivering.</p><h3>It starts with ideas…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*drOu774fEujxJkIs" /><figcaption>Photo by <a href="https://unsplash.com/@jeremybishop?utm_source=medium&amp;utm_medium=referral">Jeremy Bishop</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>All pieces of work for a team start somewhere — often as defects to fix, or a problem to solve, but many start as ideas. These ideas come from research, competitors, or — as it seems — stakeholders, or otherwise highly paid opinionated people (the HiPPOs)</p><p>Therefore we discussed how to cut through the cruft and find the ideas worth pursuing — and how to do that when not all ideas <em>appear</em> to be created equal.</p><ul><li><strong>Handle all ideas in the same way</strong>. Put all common ideas, opportunities, problems and defects into a common prioritisation space and treat them the same regardless of where they originated — be that research, discovery, HiPPOs or whatever. You may find that some — such as critical bugs or defects come straight out again, or you already know how important they are (i.e. critical impact) but the key is consistency.</li></ul><blockquote>I’ve sought to use 3 ‘backlogs’ in the past — a ‘back’ backlog for ideas, opportunities and the like; a ‘front’ backlog for items we are taking forward as product backlog items; and a ‘bin’ (accessed via the <em>delete</em> function) for those which don’t make the cut, or aren’t worth doing now.</blockquote><ul><li><strong>Move from ‘waiter’ to ‘doctor’ stance</strong>. This consistency is crucial if we are move away from simply building whatever is asked of us, to partnering with our stakeholders in a constructive and collaborative manner — which may involve pushing back where appropriate! In fact, saying ‘no’ becomes easier the less we say an unmitigated ‘yes’.</li><li><strong>Ask ‘what does success look like’</strong>? This is a good way to start a consistent approach to evaluating the value of each idea. For many ideas there may be no idea of what success looks like — far less any understanding of how it could be measured. It’s helpful at this point to set early expectations that we don’t want to be pursuing such shaky objectives! And as product people responsible for efficient use of (what could easily be) the organisation’s most valuable resources this is a right and proper response.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUco7GA2felR9mx8QRX6wg.png" /><figcaption>Slide from <a href="https://www.mindtheproduct.com/the-gist-framework-by-itamar-gilad/">Itamar’s talk at MTP Engage MCR 2020</a></figcaption></figure><p>Itamar Gilad introduced his <a href="https://www.mindtheproduct.com/the-gist-framework-by-itamar-gilad/">GIST framework at MTP Engage MCR this year</a>. In a world of MANY ideas from many people there are many ideas which are not worth doing. At Bing and Google only 10–20% of experiments actually yielded positive results. At Microsoft only a third were worth doing — the rest neutral or negative. Itamar notes that around 30% is actually high — most of the time we’d do well with a 10% success rate…</p><p>Therefore challenge is finding and testing these 10% quickly and effectively!</p><blockquote>Of course there will be times when we just need to JFDI — often at the behest of someone with much influence — where possibly our job and reputation will depend on how we comply. In these cases we are usually well within our remit to explore the implications and impact of such a request. In many cases success may be staying afloat, responding to market conditions or simply adhering to regulations. It should be remembered that many HiPPOs may actually have a well-informed ‘gut instinct’ fashioned over many years. In these cases let us follow their leadership but respectfully seek to measure the impact so we can learn together — and tune our collective ‘gut’ in the process!</blockquote><h3>It involves the team…</h3><p>On the back of this we discussed the danger of becoming the bottleneck, or the only arbiter of truth. Instead we have a splendid opportunity to involve the team, and draw them into the process.</p><p>Not only is this a great way to prevent us from becoming the bottleneck, it means the team are also learning, and bringing their wisdom to the table. It can bring the team closer to experts in the business or amongst customers so they can experience problems first hand — or at least closer to first hand.</p><p>It is also a valuable opportunity to move away from requirement documents disguised as user stories — and move back towards <a href="https://medium.com/@sherifmansour/how-weve-destroyed-user-stories-8b36120645c6">‘telling a story’ through conversation</a>.</p><h4>When to involve the team</h4><p>They say the best time to plan an oak tree is twenty years ago but the second-best time is NOW. The best time to involve the team is at the beginning, but if that is not possible, then do it NOW.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nfC94_lpPlD0UZFu" /><figcaption>Photo by <a href="https://unsplash.com/@wolfgang_hasselmann?utm_source=medium&amp;utm_medium=referral">Wolfgang Hasselmann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We discussed how many product people already rightly practise high levels of transparency with their teams — sharing the vision, mission, roadmap and associated collateral with them at very opportunity. This means there are no surprises and the product benefits from the team’s collective wisdom.</p><p>We noted this doesn’t always need the entire team’s attention at once. Various methods can be employed to share information asynchronously and involve the team members to varying degrees. Some shared their experience with using a ‘three amigos’ style group to review and discuss high-level epic / initiatives, before doing more research, answering questions and further prioritisation before reviewing with the wider team if the initiative is deemed worth taking forward. This is a useful way to garner high-level technical feedback or estimates required for prioritisation or to assess return on investment (ROI).</p><blockquote>As well as GIST, other ideas such as <a href="https://uxdesign.cc/agile-lean-hcd-are-not-puzzle-pieces-which-can-be-put-together-d073e5144ec4">Dual Track</a> or Ryan Singer’s (Basecamp / 37 Signals) <a href="https://basecamp.com/shapeup%E2%80%A9">Shape Up</a> philosophy involve techniques we can try (<a href="https://medium.com/@johnpcutler/review-notes-shape-up-2c2bde31fc8a">John Cutler has written a helpful summary</a>) but at the end of the day — it is culture and mindset which truly matter, not processes we use. More on that shortly!</blockquote><h4>How to ensure their involvement is worthwhile</h4><p>In our role as stewards of the resources committed to us — as we try to avoid developing worthless solutions — it is also incumbent on us to ensure any team activity is worthwhile, and well planned.</p><p>We appreciate that how this happens can vary greatly depending on how well the organisation appreciates the importance of product discovery vs churning out features. However in all cases to prevent burnout, and provide designers and developers with enough time to focus and reach ‘peak flow’, we need to plan carefully how we involve them in discovery.</p><p>However we choose (be that dual-track agile or something else) we acknowledged that transparency and effectively demonstrating clear benefit and value for the development of the product are of utmost importance:</p><ul><li>Doing that pre-work to ensure the meeting is productive (<a href="https://cutlefish.substack.com/p/tbm-1653-the-boring-bits"><em>see John Cutler writing more about this</em></a>)</li><li>Being clear on any meeting / workshop agendas and outcomes</li><li>Rotating team members where possible to spread the experience around</li><li>Accounting for time to be spent at sprint planning to prevent friction or over-realised delivery expectations</li><li>Wherever possible taking opportunities to bring experts (or actual users if appropriate) into the refinement sessions to add colour and depth to the discussions</li></ul><p>Over time, we anticipate team members will see the benefits and advantage to being involved, and appreciate the value of that time which helps prevent them coding or designing <em>the wrong things</em> — even if there is initial (or even continued) push back on this, where developers claiming they are ‘paid to code’, not do research or write backlog items, and teams using ‘spikes’ as a delay or defence mechanism.</p><h4>So that together we win</h4><p>As rightly pointed out — this is a cultural issue. In a ‘<a href="https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory">feature factory</a>’, <a href="https://svpg.com/product-vs-feature-teams/">delivery team</a>, or agency environment where cost and resource are tightly controlled the focus will be on <em>simply getting features out</em>. However in a mature and healthy empowered product development environment the team will have a greater appreciation of <em>why</em> they exist — that is to <em>think, not just code</em>. As noted at a recent <a href="https://www.pita.social/past-events/pita-005">Product in the (A)ether session</a>:</p><blockquote>“Your JOB may be coding, but it’s customer value that PAYS your salary”</blockquote><p>On that basis all developers and designers probably should be IMMENSELY interested in whether they are working on the <em>right things</em>! (And to be fair many are — I’ve personally worked with some very astute developers who don’t want to waste a single byte.)</p><blockquote>We also briefly raised the concept of ‘bets’ (ala <a href="https://blog.crisp.se/2016/06/08/henrikkniberg/spotify-rhythm">Spotify DIBB </a>framework), which can be <a href="https://hackernoon.com/place-your-bets-4022b732ba4c">immensely helpful</a> here as a way to change the way team members and other stakeholders throughout the business approach product investment. On this basis <a href="https://jpattonassociates.com/">Jeff Patton</a> asks, how much we are willing to bet on the fact we’re building the right thing — the price of our lunch, or our holiday, or car / house / pension fund? As a general rule the bigger the bet the more confidence we require. Yet how often have we seen product development teams at a burn-rate of some many £k per sprint hammering away at something which eventually fails once delivered? Anyone spent the value of their house (a few £100K) on the <em>wrong thing</em>?</blockquote><p>This makes the concept of measuring success at all stages all the more important. How do we know if we are winning or losing, succeeding or failing?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XU1new8Xl7qr2ZAj" /><figcaption>Photo by <a href="https://unsplash.com/@themeinn?utm_source=medium&amp;utm_medium=referral">Theme Inn</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>It continues after delivery…</h3><p>If understanding success is important <em>before</em> we invest, measuring it <em>as</em> we invest is crucial. This means metrics are vitally important here. Not only do such metrics give us the information we need to assess and evaluate success, but they also give us concrete facts with which we can communicate with our teams, our users, and crucially for many — stakeholders and the wider business.</p><blockquote>We noted this is especially important for work of a more ‘technical’ nature — be that a re-platforming project or efforts to tackle technical debt — where immediate value may not be clear. If we have meaningful metrics we can use to transparently highlight savings or tie up to important business outcomes we stand a better chance of being able to repeat such work and establish its value.</blockquote><p>We concluded measurement — at least done well — is also a cultural issue. Regardless of what we say, the processes we may implement or even the steps we may take — mindset is crucial. As product people we are well placed to change our cultures by modelling and encouraging behaviours, explaining our choices and showing as we tell!</p><p><em>And it starts at the beginning — when we discover effectively we will increase our ability to delivery efficiently</em>.</p><p><em>Here at Product Lunch Club </em>🥪<em> we’re a group of product people who meet regularly over lunch to help, encourage and support each other in our roles. </em><a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><em>Come and join us</em></a><em>! </em>🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51a24e2a619c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/once-we-know-the-right-thing-to-build-how-can-we-help-our-teams-build-it-right-51a24e2a619c">Once we know the right thing to build, how can we help our teams build it right?</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key Takeaways from MTP Engage Manchester 2020]]></title>
            <link>https://medium.com/product-lunch-club/key-takeaways-from-mtp-engage-manchester-2020-ec8632509c58?source=rss----8ab58010619d---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec8632509c58</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cats-and-dogs]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[Phil Osmond]]></dc:creator>
            <pubDate>Wed, 12 Feb 2020 22:56:16 GMT</pubDate>
            <atom:updated>2020-02-13T16:37:15.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVUwwqP0n1CWELomMnNSnA.png" /></figure><p>I must confess I was late booking for Engage in Manchester this year. I wasn’t sure if I could make it, or even if it would be worth it… but I could make it, and boy I was wrong — it was SO worth it!</p><p>What a great community the <a href="https://www.mindtheproduct.com/">Mind The Product community</a> is — kudos and much gratitude to all involved putting together such a fantastic event.</p><p>Reflecting on what I take away let’s summarise it in three statements:</p><ul><li>Product is hard</li><li>Product is possible</li><li>Product is great!</li></ul><p>Time prevents me going into all the details of every talk I attended, or each conversation I had — but here are some of the highlights…</p><h3>Product is HARD</h3><p>Whilst product management (from now on just ‘Product’) is great (more on that shortly) it is not easy. We were reminded of that from many angles.</p><p><a href="https://twitter.com/simplybastow">Janna Bastow</a> kicked off the day talking about ‘<a href="https://www.prodpad.com/blog/decisions-debt-and-other-dilemmas/">Decisions, debt and other dilemmas</a>’ — 3 d’s with which all Product people dance. We thought about <em>tech</em>, <em>design</em>, <em>process</em>, <em>culture</em> and <em>admin</em> debt.</p><blockquote>Culture debt struck a chord with me — it feels like the most subtle and pernicious form of debt, where the culture of big business trumps effective product development. Predictability is king, deadlines prevail and vanity metrics are worshipped — everything modern product development eschews! This is where the feature factory becomes normal, product management is seen as a cost and, of course, the wrong things are (probably) being built.</blockquote><p>But all is not lost — as Product people we can play a key role here, building trust within the business, communicating consistently and seeking constructive collaboration. Outcomes over output. Focus on the strategic objectives and holistic measures. Safe communication. Not easy but oh so valuable!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3LvHeVx-UHhXTAPyVShLWA.jpeg" /><figcaption>John Cutler — Product <strong>is</strong> HARD</figcaption></figure><p>Later that session <a href="https://twitter.com/johncutlefish">John Cutler</a> picked up on The Beautiful Mess which is product development. I started reading John’s writing a few years back on HackerNoon and I was hooked. So much to think about and so much sense. This occasion was no different — and it was great to chat with John over lunch as well.</p><p>In his session John reminded us that Product is indeed hard, and nobody has it nailed. Indeed, making progress on one thing often leads to problems in other areas — and then there is SO MUCH PRESSURE TO GET IT RIGHT. All those “product blog gods” who <em>appear</em> to have it sorted.</p><blockquote>Well, John has spoken with those teams, and — as it happens — they don’t have it nailed. “Where are your spells?” “Oh we’re normal”. In fact sometimes what that team espoused as great they’ve since moved on from and are now doing something different. But even if a process does work for such-and-such a team, it may not work for a different team. Every team, every environment, every product is different. A recipe for ‘perfect product cookies’ does not exist.</blockquote><p>So what is John’s advice to us?</p><blockquote>“<em>Don’t become the North Star Framework person. Don’t become the OKR, design sprint, design thinking, mob-programming, or Agile person. Don’t stop learning, of course. Don’t stop trying to help using what you know. But don’t lead with The Way</em>”</blockquote><p>Introducing <a href="https://www.slideshare.net/cperrone/popcornflow-continuous-evolution-through-ultrarapid-experimentation">Popcorn Flow</a> to us John exhorts us to lead with that and start small, reasonable changes in a safe fashion with patience, humility and curiosity. Sage advice!</p><h3>Product is POSSIBLE</h3><p>Talking of humility, <a href="https://twitter.com/thormitchell">Thor Mitchell</a> (pronounced ‘<em>Tor</em>’) graciously exhorted us to be humble and encourage humility — where humility is properly defined as the ‘<em>quality of having a modest or low view of one’s importance</em>’.</p><p><a href="https://medium.com/@thor.mitchell/the-importance-of-humility-in-product-management-7878e6640b8b">The importance of humility in  product management</a></p><p>I’d read Thor’s <a href="https://medium.com/@thor.mitchell/the-importance-of-humility-in-product-management-7878e6640b8b">original article on this subject</a> and resonated with it immensely. As Product people we are ‘not all that’ —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGrEHjcIKyMsjYMWK2P-rA.jpeg" /><figcaption>Thor Mitchell on set</figcaption></figure><ul><li>We are <em>not</em> essential — but we are fortunate, and we are in a position to build trust and prove our worth</li><li>We’re <em>not</em> important — this is a tough one to stomach, but whilst we have no authority, we do have influence</li><li>No task is below us and we can learn from anyone — servant leadership is the way forward</li></ul><p>In fact, at the end of the day we are probably wrong and it will all (actually and ultimately) all be our fault!</p><p>But that is okay.</p><blockquote>Are we Product people to prove to the world how great we are? Or to work with real humans building great products? It is our responsibility to learn from our failures, pass on the credit and delight our users. This sort of humility cannot be taught, but can be encouraged — Thor encouraged us to practice humility, hire for humility and build humble cultures.</blockquote><p>Yes, yes and yes.</p><p>Believe it or not, stakeholders are real humans, and stakeholder management, or <em>people management</em> is key to great product management. <a href="https://twitter.com/thedailyem">Emily Tate</a> and <a href="https://twitter.com/_ShaunRussell">Shaun Russell</a> both reminded us that empathy (not playing politics) makes great product management possible. Stepping into the shoes of our stakeholders, creating alignment on goals and embracing conflict effectively are all essential aspects for us to develop and grow.</p><blockquote>Let’s say what we really mean, take positive action and keep going — even when it’s uncomfortable! Conflict, as <a href="https://www.slideshare.net/ShaunRussell1/conflict-is-where-the-magic-is-227235122">Shaun reminds us</a>, is ‘where the magic is’.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6HzoAil_9YhrASVgLanDQ.jpeg" /><figcaption>Shaun Russell sharing the magic</figcaption></figure><p>And of course, as Emily reminded us, mistakes will happen, humans will be human and not every day will be rosy. But let’s be transparent, communicate often and pick our battles wisely. Let’s seek to understand our stakeholders and dig into their point of view (by using 5 Whys for example).</p><p>Let’s own our product and use data to fight the HiPPOs! Dealing with angry people is part of our role and is possible to handle well — just watch out for jerks — we may not be able to handle everyone, and that’s okay — let’s just be sure to take care of ourselves.</p><h3>Product is GREAT!</h3><p>Jerks aside, Product is GREAT! We have such an opportunity to make a difference — in the lives of our teams, in the lives of our users and in our own lives too…</p><h4>In the lives of our teams</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SWFCkwl22YnhbbRn" /><figcaption>Tomatoes — Photo by <a href="https://unsplash.com/@seven11nash?utm_source=medium&amp;utm_medium=referral">Marc Mueller</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>According to Salma Alam-Naylor our teams are <em>not</em> bonsai trees. She’s absolutely spot on — they’re not! They’re not to be oppressed in shallow containers, clipped and sculpted into weird shapes for the enjoyment and praise of the ‘grower’…</p><p>No — they are to be nourished with light, warmth and scheduled care, enriched and protected, cultivated and given space to grow. Our teams are in fact TOMATO PLANTS. And in time the fruits of our joint labours will be ready to enjoy (although it may be here the analogy begins to break down!) — and whilst no team may be perfect, let’s embrace those imperfections and learn from them. It’s from those imperfections and dissonance that creative solutions arise.</p><h4>In the lives of our users</h4><p><a href="https://twitter.com/mrjoe">Joe Leech</a> reminded us to look forwards and not back — exhorting to focus on the needs of our users, not competitors and their features! <a href="https://mrjoe.uk/jtbd-talk/">The HOLE is not the GOAL</a> — let me say it again (as Joe did many times!):</p><blockquote>The HOLE is not the goal!</blockquote><p>Introducing the Jobs To Be Done framework, Joe explained how he didn’t want a HOLE in his wall — quarter-inch or otherwise — nor did he really want a drill. What he <em>actually</em> wanted was a nicer looking room — and he was hiring pictures hung on the wall to achieve that.</p><blockquote>Why use a drill when high quality adhesive picture hanging strips are available?</blockquote><p>The HOLE is <em>not</em> the GOAL. Do we know what our users actually want and why they are hiring, or could hire, our product?</p><p>JTBD FTW. And a nod to the late great <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">Clay Christensen and the Harvard Business Review article on Jobs to be Done</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhccQuVv97g5h6s2B9oU8A.jpeg" /><figcaption>Yes Joe — the HOLE is not the goal!</figcaption></figure><h4>In our lives too!</h4><p>Talking of Harvard, <a href="https://twitter.com/lissijean">Melissa Perri</a> — author of Escaping the Build Trap and teacher of Product Management at Harvard Business School (amongst other things!) took the stage to close the day explaining how Product people can grow their careers to CPO level and beyond.</p><blockquote>Are we suited to start-up, growth or enterprise organisations? Do we understand Product <em>and</em> how the c-suite works? Can we empathise with the c-suite as well as our users? Can we bring people together?</blockquote><p>There is a career path available for Product people and it is a good one.</p><p>She also reminded us that SAFe sucks, and in general splitting the product owner role from the product manager role is a bad idea because it prevents a PO from being strategic and hides the tactical everyday nuts and bolts of product development from PMs. Both are necessary for a long and rounded career in Product!</p><p>We also enjoyed many cats. Thanks Melissa! Talking of cats — last but not least, <a href="https://twitter.com/hashtag/DogsInProduct">#dogsinproduct</a> is a perfect example of why the Product community is <em>so</em> GREAT. Does any other discipline have such endearing dogs?!</p><p>That’s it! I could go further, but if you want to go deeper <a href="https://www.mindtheproduct.com/mtpengage/manchester/mtp-engage-manchester-2020">checkout the write-ups and subsequent videos appearing over at Mind the Product</a>.</p><p>Product is hard. But it IS possible, and it is GREAT. I’m looking forward to next year already — may even try to catch some early bird pricing!</p><p><em>Here at Product Lunch Club </em>🥪<em> we’re a group of product people who meet regularly over lunch to help, encourage and support each other in our roles. </em><a href="https://www.meetup.com/Product-Lunch-Club-Bristol/"><em>If you’re in Bristol come and join us</em></a><em>! </em>🍻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec8632509c58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-lunch-club/key-takeaways-from-mtp-engage-manchester-2020-ec8632509c58">Key Takeaways from MTP Engage Manchester 2020</a> was originally published in <a href="https://medium.com/product-lunch-club">Product Lunch Club</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>