<?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 Tim Wilkinson on Medium]]></title>
        <description><![CDATA[Stories by Tim Wilkinson on Medium]]></description>
        <link>https://medium.com/@productheads?source=rss-25a4d73287c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HMRqimUqKp03K2Kgan0ajg.jpeg</url>
            <title>Stories by Tim Wilkinson on Medium</title>
            <link>https://medium.com/@productheads?source=rss-25a4d73287c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:26:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productheads/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[The true cost of product team hiring is massive.]]></title>
            <link>https://productheads.medium.com/the-true-cost-of-product-team-hiring-is-massive-fd22b42a9573?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd22b42a9573</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 09:19:11 GMT</pubDate>
            <atom:updated>2022-10-27T09:19:11.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3-bkuVMovCH8HRhg" /><figcaption>Photo by <a href="https://unsplash.com/@jpvalery?utm_source=medium&amp;utm_medium=referral">Jp Valery</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When you load in the persons salary, your time, your teams time, fees, and the time it takes for someone to get onboarded and start being productive, the figure gets big very quickly (some estimate in the region of £200k).</p><p>BUT the average life span for a first hire PM in a startup is under 12 months 🤯</p><p>This is mainly due to a mismatch between what the business needs and the skills and experience of the candidate.</p><p>5 of my favourite hacks for improving hiring outcomes are:</p><ul><li>Write down what outcomes you need your new hire to drive after 12–24 months in the role</li><li>Socialise and test those outcomes with colleagues and peers</li><li>Use the document to define skills and behaviours to test for during interviews, and have a standardised scoring mechanism</li><li>Involve people the new hire will be working with in the hiring process</li><li>Always ask follow up questions, and check that candidates have anecdotes from their own experience to back up theory</li></ul><p>By clearly defining what you want the person to achieve before you start the hiring process, you stand a much better chance of making the right hire first time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd22b42a9573" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Growing your team too quickly is one of the worst mistakes you can make]]></title>
            <link>https://productheads.medium.com/growing-your-team-too-quickly-is-one-of-the-worst-mistakes-you-can-make-9d4e80c91b8?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d4e80c91b8</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Mon, 25 Oct 2021 12:16:56 GMT</pubDate>
            <atom:updated>2021-10-25T12:16:56.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZglZaFAa5Klz4e4A" /><figcaption>Photo by <a href="https://unsplash.com/@a_d_s_w?utm_source=medium&amp;utm_medium=referral">Adrian Swancar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I know this might seem like odd advice coming from someone who helps companies build out their product teams, but honestly, growing too quickly (especially in the wrong areas) will lead to a world of pain.</p><p>If you are early stage, pre-product / market fit you should try and stay as small as you possibly can. Here’s why…</p><p><strong>1. Development inefficiencies</strong><br>Too much stuff in the backlog? Loads of ideas piling up? Throw more people at it right? Wrong! One of the universal truths of software development is that your dev team will never be big enough…get comfortable with that. The key is to make sure you are working on the most valuable stuff at all times. Get used to making hard trade offs. <br>If you hire too many devs now you will waste a tonne of time trying to manage them all and have them work on useful stuff. An outcome of that scenario is that the product will bloat. User journeys get messy, getting users to value takes longer (or doesn’t happen at all), there’s an ever growing list of things to maintain and progress grinds to a halt.</p><p>You don’t need that.</p><p>I can’t tell you the number of times I’ve heard founders complain that progress with a dev team is so much slower than when it was just them hacking it out on their kitchen table.</p><p>If you are still make large course corrections in the product you want to stay at 2–3 devs max and force yourself to make everything as cheaply and quickly as possible until you’ve validated out your product.</p><p><strong>2. Other teams put pressure on product and engineering when they are not mature enough to cope with it. </strong><br>We just had our first board meeting and the investors want us to start thinking about hitting sales numbers ready for our next round. We need customers, and loads of them! Let’s build a sales and marketing team!</p><p>Really? Do you? If you are pre p/mf you can probably get enough customers to be validating with through some basic outreach and community work. Going too early on these teams will cause a number of problems;</p><ul><li>Sale and Marketing teams will be trying to sell a product that is not necessarily fit for purpose, where the value proposition isn’t clear, and that doesn’t have a well defined ideal customer profile. You’ll definitely learn a lot about those things (if you have a good enough team), but you also have a tonne of failure and frustration with your team AND customers. Those people likely won’t come back to buy from you</li><li>You’ll start getting lots of complaints and feature requests coming into product. “If only we had X feature I could sell to this whale of a company I’ve lined up.” These things will create a tonne of noise making it hard to identify and focus on the stuff that really matters.</li><li>Sales people like to sell and make commission. If they are not doing that they will leave. Marketing teams like to generate leads and have work to do. If they can’t do that they will get board and start causing distractions / also leave.</li></ul><p><strong>3. Keeping the ship motivated and heading in the right direction becomes <em>really hard</em></strong><br>People are smart. They know when things aren’t going well and they get worried about their job. Are they performing well enough? Perhaps if they used their initiative and started doing XYZ? Is the company ever going to be successful? Will they even have a job in 12 months?</p><p>All this leads to them (understandably) asserting themselves in a variety of ways that you will end up having to deal with.</p><p>Additionally, because you’ve not perhaps found p/mf yet, got your pricing strategy sorted, know who you’re selling to etc etc, you’re going to be changing tack. A lot. That causes additional uncertainty and stress and every time things change you have explain it to the whole company, get them onboard, explain why the thing they were doing is no longer useful and instead you want them to put their heart and sole into this new thing.</p><p>That’s actually quite easy when you have a small team who are close to the problems and can see why a change is needed.</p><p>It’s really tough when you have a larger team (even 15+ people) who are just trying to execute on the thing you asked them to do yesterday.</p><p>When you’re having to move quickly to build a product people actually want, the fewer nodes of communication required to do that, the better.</p><p><strong>Of course, if you’ve read all this and you are still looking to build out your product team, head on over to </strong><a href="http://www.productheads.io/"><strong>productheads.io</strong></a><strong> and get in touch!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d4e80c91b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Killing features to improve your product]]></title>
            <link>https://productheads.medium.com/killing-features-to-improve-your-product-ec3eb6269062?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec3eb6269062</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Tue, 15 Jun 2021 14:44:12 GMT</pubDate>
            <atom:updated>2021-06-15T14:44:12.000Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z5GF0duDlAoy_vZ6" /><figcaption>Photo by <a href="https://unsplash.com/@hirmin?utm_source=medium&amp;utm_medium=referral">Max Kleinen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If we accept that 50% of features deployed fail to have the intended impact, then just like technical debt we need to have a regular process and commitment to actively prune these failed experiments.</p><p>Not doing so leads to increasingly obfuscated critical user journeys and of course adds to technical complexity and maintenance costs whilst delivering little or no value.</p><p>So how do you solve this problem?</p><p>1. Regularly audit your features and plot the results on a matrix showing how often a feature is used on one axis against the number of people using them on the other. You’ll end up with a grid showing features that are used all the time by all users in the top right, and those hardly ever used by anyone in the bottom left*.</p><p>2. For low use features on the kill list, make sure you understand why they were implemented in the first place. Speak to customers who are using them and understand what value they are deriving from them. How would they feel if it was removed?</p><p>3. Communicate internally showing your data and reasons. Remember, unfortunately discussions on features can be very political. The feature you want to kill might have been someones baby (CEO, CTO, VP Sales). In a healthy product culture this shouldn’t be the case, but many of us don’t operate in a perfect world!</p><p>4. If necessary, experiment by turning off the feature for new customers or a section of your user base.</p><p>Without this regular spring cleaning your product will bloat causing serious UX issues and making it harder for you to pinpoint where the problems are.</p><p><em>* Obviously some features are intended to only to be used once in a while (user profile changes for example), don’t kill these!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec3eb6269062" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 4 Biggest Killers of SaaS Companies (Part 1: The Market)]]></title>
            <link>https://productheads.medium.com/the-4-biggest-killers-of-saas-companies-part-1-the-market-a196ca03ed01?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a196ca03ed01</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Fri, 28 May 2021 15:48:39 GMT</pubDate>
            <atom:updated>2021-05-28T15:48:39.035Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5BJjQ2Dn9JkIlJNt" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=medium&amp;utm_medium=referral">Tim Mossholder</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Clearly there are thousands of reasons why start-ups fail but what I’ve tried to do here is abstract away specifics in order to come up with what I believe are the route causes of failure.</p><p>I don’t really talk specifically about personnel in these articles. One could argue that the *only* thing that matters is the capability of the team, and that if the founding team are good enough they’ll recognise any issues and have the wherewithal to fix them.</p><p>This is one of the reasons why early stage investors focus so heavily on the founding team, because at that stage in the businesses life they are really the only quantifiable and likely constant aspect. Everything else from the product to the market and the vision may well shift in pursuit of creating a viable business.</p><p>Finally, these 4 killers are based on my knowledge of working in enterprise SaaS. However, I’m pretty confident they apply to other types of software businesses as well.</p><p>So, here they are. My take on the four big killers of SaaS companies.</p><p>1. Bad / non-existent market (product discovery)<br>2. Blind faith in an idea (product discovery)<br>3. Lack of focus in execution (product delivery)<br>4. Speed of execution (product delivery)</p><p>You’ll see the four areas fit neatly across the two main pillars of strong product management, namely product discovery and product delivery. In each of the articles I’ll give some tips on successfully countering these killers based on good product management practice.</p><p>So lets dive in with the most important of all: The Market.</p><h3>Killer #1 Bad / Non-Existent Market (product discovery)</h3><p>The discussion on whether the team, product or market is the most important factor for success has raged on for years, but the fact is that it doesn’t matter how great the team is or how delightfully put together the product is, if there aren’t enough people around who want to buy it at a price that will sustain the business, you’re done.</p><p>Conversely it *is* possible to have a pretty crappy product and a team that makes every mistake under the sun and still have (some) success if the market pull is strong enough (although granted in these circumstances the company will struggle to capitalising on the opportunity and scale).</p><p>To succeed you need a sizeable market. The bigger the better. And I don’t just mean the financial size of the market. In my view you need *lots* of prospects because you’re going to churn through a tonne at the start of your journey. Even once you’ve got to product market fit and have figured out and optimised your sales funnel you are still only going to convert a percentage of prospects. Plus there’s competition etc etc.</p><p>If the business is seeking funding and therefor an exit event at some point in the future there will be a minimum market size required for investors to get the kind of returns they expect. For bootstrapped / life-style businesses the economics aren’t anywhere near as aggressive and it’s possible to create a great business around quite a specific niche (and still have a life changing exit at some point down the line).</p><p>Either way though, far too often founders fail to go through the rigour of proper product discovery before embarking on their start-up journey. This is usually because they have blind belief that their idea is going to be successful, but more on this later on.</p><p>Optimistic founders routinely over estimate both the size of the market (quoting huge figures for a market when in reality they’re going to be targeting a much smaller segment of that market), and the percentage of the market they’ll be able to grab.</p><p>It is much more likely that a company will be able to grab a tiny share of a massive market (and then potentially push out into other parts of it), than it will be able to acquire a massive share of a tiny market, especially if they want to / need to do that over a relatively short space of time (10 years).</p><p>Running through the total addressable market / total serviceable market / target market exercise helps but there is still scope for bias.</p><p>To assess the market, it’s worth doing both a top down and bottom up market analysis. What is the total market size, and how much of that do competitors currently own. How much space is left? Where is the market going and is there an opportunity for you to beat incumbents to that space or disrupt with a new business model.</p><p>Then go bottom up. Think about your likely ACV and what a _conservative_ estimate for sales growth might be. What do the best case and worst case scenarios looks like? Do the economics realistically add up?</p><p>Remember, your total serviceable market is actually made up of companies for whom the problem you are solving is a genuine pain point and likely a priority purchase. To really understand that, you need to go out and speak to customers. Early adopters can confuse matters here. I believe if you look hard enough for long enough you will always be able to find a small number of people willing to take a punt on your product. The challenge though is to ‘cross the chasm’ as is covered in Geoffrey Moore’s seminal book on the subject.</p><p>Proper market analysis is required on the number and profile of competitors (age, size, funding etc), how much of the market has already been captured, is the market growing etc. It’s also worth applying an analysis such as PESTEL (Political, Economic, Socio-cultural, Technological, Environmental, Legal) here. Where is the market going and what aspects of PESTEL might you be able to leverage in order to win.</p><p>Whilst your pricing model is likely to change a lot in the early years at least, getting some idea of what you are going to be able to charge from your competitors will again help you to model what the economics of the business are going to look like.</p><p>A note on competitors: It’s frustratingly common to hear “oh, we don’t have any competitors.”</p><p>This is nonsense. There are always competitors even if your competitor is Excel or a human doing the work. Even if you have a ‘blue ocean’ strategy [<a href="https://www.blueoceanstrategy.com/what-is-blue-ocean-strategy/">https://www.blueoceanstrategy.com/what-is-blue-ocean-strategy/</a>] you’ll be competing against the status quo.</p><p>So to sum up, a start-up is doomed from the beginning if there isn’t a strong pull from a big enough market to sustain its growth at a speed all the stakeholders need from it.</p><p>Some of the most successful enterprise SaaS companies solved initially for a very specific niche within a massive market and then grew out from there. The business worked even for that niche, so when they were able to transition into the bigger pond they created a company with exceptional value.</p><p>Next up, I’ll talk about the second killer; Blind Belief.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a196ca03ed01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is the Product Manager role becoming extinct?]]></title>
            <link>https://productheads.medium.com/is-the-product-manager-role-becoming-extinct-f2d14a65ee0e?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2d14a65ee0e</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Mon, 19 Apr 2021 11:17:48 GMT</pubDate>
            <atom:updated>2021-04-20T12:35:37.935Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VlquTCXiNiTMdrxk" /><figcaption>Photo by <a href="https://unsplash.com/@mcgilllibrary?utm_source=medium&amp;utm_medium=referral">McGill Library</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A friend (and fellow PM) recently shared <a href="https://www.moneycontrol.com/news/trends/features-2/6-things-everyone-needs-to-learn-about-product-management-6783491.html">this article</a> by <a href="https://www.linkedin.com/in/nisha-ramchandani-6225b213/">Nisha Ramchandani</a> and <a href="https://www.linkedin.com/in/varunchoraria/">Varun Choraria</a> with me on the future of the Product Manager role.</p><p>It covers a lot of ground and in doing so touches on some of the long standing challenges in product management today, namely:</p><ol><li>Large variability in the job description depending on the size and sector of the company, which in part leads to…</li><li>Continued confusion about the responsibilities of a Product Manager (creating frustrations on all sides)</li><li>The challenges of stakeholder management and communication (particularly in a remote first environment)</li></ol><p>At the end one of the contributers to the article asserts that as companies are forced to become more customer centric in order to survive, all teams will automatically tightly align around that goal and be expected to be accountable for it.</p><p>Furthermore, as tooling and tech stacks continue to evolve everyone across the business will be capable of delving into areas the PM’s have traditionally been responsible for (e.g metrics).</p><p>I think these are strong points and it’s great to get the discussion going on them.</p><p>I don’t think these shifts signal the end of the product manager though for a number of reasons.</p><p>Firstly, I think it’s tremendously positive for other roles (e.g engineering or sales) in a software organisation to have ownership of the product and want to get into understanding and solving the customers pain. I’ve been lucky to work in organisations with Product Engineers who have overlapped hugely with the PM. Having engineering get close to the customer massively increases understanding, innovation and the speed at which real value is delivered.</p><p>I see this situation as a big positive.</p><p>The same goes for metrics. When an organisation is fully conversant in data driven decision making, that information should be available to the whole company for everyone to work with (sales, marketing etc).</p><p>So where does this leave the PM? What is the PM’s role when these ‘technical’ skills are now able to be carried out by various roles around the org?</p><p>Ultimately I think this is one of those “do you sell oil or do you sell energy” discussions.</p><p><strong>The most critical thing a PM does is provide and communicate direction and clarity, and protect and nurture the product towards success in the face of a multitude of competing forces.</strong></p><p>As Sales, Engineering, the CEO / Board pull the product in all sorts of different directions, the PM is the person who has to manage those tensions (and personalities) in order to steer the team and the product towards something valuable, feasible and useable.</p><p>It <em>is</em> hard. It <em>can be</em> lonely.</p><p>If as a PM you define your value to the organisation as how great your user stories are, or your ability to interpret data, then whilst these skills are valuable at the moment, you may well go extinct just as mechanical type setters did when desk top publishing came along.</p><p>If however what you bring to an organisation as a PM is the ability to identify customer value (through a range of evolving techniques), develop a strategy and align the entire team around it (including potentially those more senior than you), and deliver a commercially viable product that customers love, then you needn’t worry.</p><p>You’ll be in work for a long time to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2d14a65ee0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The perils of sales led software companies]]></title>
            <link>https://productheads.medium.com/the-perils-of-sales-led-software-companies-18f8db73bcc1?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/18f8db73bcc1</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 17:55:52 GMT</pubDate>
            <atom:updated>2021-03-26T17:55:52.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*W-K10kAi2dOxXtdVHjsSHw.gif" /></figure><p>I’ve spoken to a number of PM’s recently who are frustrated because their B2B orgs (usually early stage start-ups but not exclusively) are sales led.</p><h3>What do sales led organisations look like?</h3><p>• Customers agree to buy the product but on condition that X or Y feature is built for them<br>• Roadmaps are either entirely composed of client requests, or if non-client features exist in the roadmap they are continually getting pushed back (or never get shipped at all)<br>• Engineering teams are constantly under pressure and behind<br>• Tech and UI/UX debt builds up quickly<br>• PM’s are really just project managers pushing work through the team</p><p>The problem with being sales led is that software companies make money by selling the same thing many times over. They don’t make money on the first version (because the investment to build the feature is 10x the contract value).</p><p>So if you are constantly charging people to essentially build a feature specific to them, you are actually running a consultancy and selling your time. In this scenario revenue is constrained by the size of your team and the number of hours they work.</p><p>The second issue with being sales led is that it hides the fact that your product probably either doesn’t have product market fit yet, or that you’re selling it to the wrong people (positioning is wrong). If you had those things nailed you wouldn’t need to commit to custom requests in order to close sales.</p><h3>So how do you fix it?</h3><p>1. Stop signing contracts on condition of features getting built 🤯! This is a hard habit to kick especially for founders / C-Suite and the sales team who (understandably) are laser focussed on growing customers and revenue. Often people don’t realise things have got so bad. It’s easy to convince yourself that because customer A is asking for this new feature, other customers will likely want it as well. However, as stated above, the economics of selling software is such that contractually committing to features for a specific customer will kill your business.</p><p>2. Identify your happiest customers and why they love your product. How does your product remove cost / time or add value to their business. Do these customers have similar characteristics? Are there other potential customers in the market who share these characteristics?</p><p>3. Start doing proper product discovery. Shadow customers, run customer journey exercises and really dig into customer requests to understand what the real pain is behind those requests.</p><p>4. Identify value based metrics for your product and obsess about ‘moving the needle’ on those metrics</p><p>I’ve been in early stage startups trying to get to product market fit and show the board that sales are happening. I understand how hard it is when a big name shows up and promises to buy, so long as you build feature x for them. I also know that sometimes you have to say yes to these requests.</p><p>However, these situations absolutely must be the exception and not the rule.</p><p>Somebody much smarter than me said <em>“there’s only one circumstance you should build something because a client requested it. If they offer you a ton of cash, and if you had it on your short term roadmap anyway.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18f8db73bcc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My top 4 tactics for building influence as a Product Manager]]></title>
            <link>https://productheads.medium.com/my-top-4-tactics-for-building-influence-as-a-product-manager-b4811dda67db?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4811dda67db</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 16:55:02 GMT</pubDate>
            <atom:updated>2021-03-05T16:55:02.972Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cn_YvI34OPixkkvp" /><figcaption>Photo by <a href="https://unsplash.com/@brookelark?utm_source=medium&amp;utm_medium=referral">Brooke Lark</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Being able to influence as a PM is pretty crucial to your success in the role. We all know how much plate spinning is involved in product management and this gets 10x harder if you can’t call plays and influence situations to keep everyone focussed.</p><p>But influencing doesn’t just happen in the moment. It’s a culmination of how you conduct yourself over a period of time.</p><p>If you’ve just left an interaction frustrated because you were unable to Jedi-mind-trick everyone into your way of thinking then (apart from checking your expectations), it might be worth reflecting on how you could have managed that interaction better and built your influence in advance.</p><p>So these are my top 4 tactics for building influence.</p><h3><strong>1. Build Rapport</strong></h3><p>Make a list of the most important relationships across your organisation for you to be able to win in your role (you could use <a href="https://www.productplan.com/glossary/stakeholder-analysis/">stakeholder analysis</a> for this but a list will also work). In a startup this must include the founders and/or C-suite but there will be others who are critical to the success of the product. These include engineers you work closely with, designers, marketers and sales people. There may also be influential people outside of your immediate circle who have a tendency to assert themselves every now and then sending your plates crashing to the ground (believe it or not, they are usually trying to help).</p><p>Invest in those key relationships. Take time to check in with those people and learn about them. What motivates them? What pains and pressures are they feeling? Empathise! The VP of Sales isn’t needlessly bugging you…she’s trying to make sure her team hit their number for the quarter and sees you as a blocker or facilitator of that.</p><p>Make sure to publicly praise and promote others where justified. Apart from just being a nice thing to do, putting others before yourself shows you are secure in your role and respect and value others — major rapport points!</p><p>Be a diplomat. This is a big part of the PM role and probably deserves a write-up to itself, but helping to resolve issues and negotiate a way forward between multiple parties will build a ton of credibility and build your relationship with those people. After all, you’ll be solving a problem for them and helping them move forward with their own agendas.</p><h3>2. <strong>Show you are safe pair of hands by understanding first and acting second</strong></h3><p>Whether you’re delivering a new feature or fire fighting you need to be able to act cooly and calmley to get things done (you can do this whilst still acting with high agency).</p><p>Make sure you understand enough of the facts before diving in. Actively listen to engineers, customers or whoever you need to in order to get the full understanding of the problem you’re trying to solve. Why are / were things done that way? What was the context at the time?</p><p>For significant or controversial issues or decisions be sure to seek consensus. There’s no harm in running a decision or potential solution by stakeholders to make sure you have the necessary cover. In fact, they’ll likely value being kept informed and you’ll be showing them that you’ve got everying in hand. Of course, if you’ve previously built rapport with them it’ll be a lot easier to informally call them / slack them to get their input.</p><p>When you are ready to act, act with commitment, confidence and urgency. Own the problem and follow it up to conclusion. Don’t leave lose ends… they’ll almost always come back to bite you and undermine all the good work you’ve done so far (it’s worth checking out <a href="https://www.amazon.co.uk/dp/B0739PYQSS/ref=dp-kindle-redirect?_encoding=UTF8&amp;btkr=1)">Extreme Ownership</a> for more on this).</p><h3><strong>3. Know your shit!</strong></h3><p>As a PM you should be the expert on your product. This means having complete knowledge of the product functionality, user metrics, your customers and the market.</p><p>If you are new to a company take the time to learn this stuff by living in the product. Take the sales training, join the CS team for a day every week, and do the market research. Once you’re confident, identify opportunities to prove your knowledge. Make presentations, show the market data you’ve collected, present a new take on the user analytics etc.</p><p>If you’re presenting a case for something make sure you have the evidence to hand. Get the data, or at least references to known experts who recommend the course of action you want to take. If you’re selling an idea, everyone will expect you to have done the legwork so you’ll quickly lose credability of someone else is able to torpedo the idea having only thought about it for the last few minutes.</p><h3>4. Deliver!</h3><p>When it comes to credability and influence there is no substitute for having a reputation for just consistanly and relentlessly delivering. This is a highly valued superpower that breads respect amongst your peers and superiors.</p><p>The other really valuable biproduct of constantly deliverying is that by doing it you will learn and grow your skills and capabilities no end.</p><p>If you do everything else on this list but fail to follow through and actually get shit done you’ll quickly find yourself sidelined and left out of the big decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/190/1*y2tYJmoUpk8O8cEOqwr9Lw.png" /></figure><p>If you liked this article be sure to follow me on twitter <a href="http://twitter.com/Tim_S_Wilkinson">@Tim_S_Wilkinson</a> and LinkedIn <a href="https://www.linkedin.com/in/tim-s-wilkinson/">tim-s-wilkinson/</a></p><p><strong>Productheads</strong> is a product focussed training, recruitment and consultancy company helping early stage software startups build great product and great product teams. <a href="http://www.productheads.io/">www.productheads.io</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4811dda67db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Big Feature Gamble]]></title>
            <link>https://productheads.medium.com/the-big-feature-gamble-dad5ec0e64f0?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad5ec0e64f0</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 16:24:36 GMT</pubDate>
            <atom:updated>2020-07-09T16:24:36.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ba7gFyxivGKL0TT0" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A lot of product and development teams have a gambling problem.</p><p>They make bets all the time on delivering a feature and when that bet doesn’t pay off, either because they fail to ship in a reasonable time or the customers didn’t like / couldn’t use it, they continue to sink money in by committing more time to try to complete the feature, or by allowing the feature to hang around in the product creating UX and support debt.</p><p>Smart gamblers know how much they can afford lose. They place their bet and if it doesn’t come off in the way they’d hoped they cut their losses and walk away.</p><p>Every time you commit to building something you are betting (investing) time and resource into building that thing. That’s time and resource that could have gone into something else if what you built turns out to be a dud. Failed features also bloat the product and get in they. They can cost the business down stream as well by causing problems for sales or support.</p><p>As a rule of thumb up to 50% of the features a team releases won’t have the impact they intended. So the aim is to test if an idea will deliver value as cheaply and quickly as possible so you don’t waste valuable time and resource.</p><p>Next time you go to place a product bet, make sure you limit your risk by:</p><ol><li>Clearly understanding the problem you are trying to solve for</li><li>Understanding how you will measure progress and what constitutes a ‘win’</li><li>Constantly check the value:effort ratio to make sure you’re not heading into a time sink</li><li>Understanding what is the smallest bet you can make to test your hypothesis (can you do this without committing development time?)</li><li>Know what your walk away point is (for example; “if we can’t ship this feature within 2 weeks, we’ll stop and re-assess, and potentially walk away completely”)</li></ol><p>Successful product teams win by innovating quickly and regularly pushing value to their customers. This is a whole team mindset that requires practice and commitment from everybody.</p><p>By stepping though the five points above when embarking on a new feature implementation you can limit your risk, protect your product and deliver a better outcome for your customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad5ec0e64f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take control in your next Product Manager interview]]></title>
            <link>https://productheads.medium.com/take-control-in-your-next-product-manager-interview-ffbbdf95d9a3?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffbbdf95d9a3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[job-interview]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Fri, 03 Jul 2020 15:44:08 GMT</pubDate>
            <atom:updated>2020-07-03T15:44:08.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EO4FhNk-ClmI0Vlz" /><figcaption>Photo by <a href="https://unsplash.com/@clarktibbs?utm_source=medium&amp;utm_medium=referral">Clark Tibbs</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You’ve seen an advert for a great product manager job, you’ve researched the company a little and it looks awesome, so you’ve fired off the latest and greatest version of your CV (and hopefully followed it up with a call to the recruiter).</p><p>A day or two passes and you get the call to come to interview.</p><p>Great work! You’ve got through the salmon run that is the CV sift and you’ve now got a chance to start actively influencing the process and chasing down the job offer.</p><p>But wait…</p><p>This is a big move that can have a huge impact on your career. Startups are messy and the next year could see you blossom in your role on the fast track to hero status, or burn up (and out) in a ball of flames, frustration and dented confidence.</p><p>When going for an interview it’s natural to slip into a submissive role and put your efforts into prepping yourself for the barrage of questions and judgement that’s about to come.</p><p>It’s vital though that you get yourself onto the front-foot.</p><p>Rather than thinking <em>“am I good enough” </em>start thinking<em> “are they good enough.”</em></p><p>This simple shift in mindset will force you to to stop thinking defensively and get you thinking offensively.</p><p>To answer the <em>“are they good enough”</em> question, you will need to:</p><ul><li>Research the company properly and understand the journey they’ve been on to date (e.g how much have they raised and when, how many customers do they have, have they pivoted since they started and why, what is the team make-up, are they exhibiting behaviors you know to be best practice, what’s the business model and does it make sense, who are the competition, and so on).</li><li>Research the founders and senior team. Have any of them done this before and if so, where?</li><li>Ask LOADS of questions in the interview. I don’t mean have a list of questions to ask at the end, I mean ask questions throughout the interview (to do this properly you will need to have researched the company as outlined above).</li><li>Always ask about strategy and focus. As you progress through the various stages, keep asking about strategy and focus right up to when you get to meet the CEO / Founder at the final stage (most pre-series B startups will have a chat with the CEO / Founder as the final stage in the process), it’s important that they answer the strategy / focus question the same way as everyone else you’ve met. Fuzzyness here is a red flag.</li><li>Always ask why they need the role you are interviewing for as early as possible. What problems are they looking to solve, and what will success for this position look like for them? This is your first chance to start understanding their view of the PM role (again, <em>ar</em>e<em> they good enough; </em>do they understand the role and will they give you the space to succeed), and for you to identify markers for your success once you’ve got the job. You can also talk to these pain points. Have you solved these problems before in previous roles for example?</li></ul><p>Doing this work not only benefits you enormously by giving you the information you need to decide whether this is the right move or not, but it will also ensure you impress in the interview.</p><p>Asking lots of questions will show engagement, it will show the interviewer that you know what you’re talking about, the level at which you are operating, and that you care about the company and role.</p><p>By the time you get to meet the CEO /Founder you will have gathered a lot of knowledge about the company and the role which you can use to impress (but don’t forget to keep looking for validation that these folks know what they’re doing and it’s going to be a great place to work).</p><p>It will also create a great back and forth conversation and connection with your various interviewers that are critical for a good (and memorable) experience on both sides.</p><p>Now go get ‘em!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffbbdf95d9a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sales, Customer Success & Product Fire Triangle]]></title>
            <link>https://productheads.medium.com/the-sales-customer-success-product-fire-triangle-1a936bd93049?source=rss-25a4d73287c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a936bd93049</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Tim Wilkinson]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 12:54:46 GMT</pubDate>
            <atom:updated>2019-10-07T12:54:46.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8nEgkzfk7eksV0gx-WalQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@benjamin_deyoung?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Benjamin DeYoung</a> on <a href="https://unsplash.com/s/photos/fire?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When I was at school I can remember learning about the Fire Triangle in Chemistry.</p><p>Basically it’s a model for understanding the necessary ingredients for fire to happen — heat, fuel and an oxidising agent of some kind. Take one of these three ingredients away or get the mix wrong and the fire will struggle to get going (or not get going at all).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*o3Y1tIH-q6K75_UvLriW3w.png" /><figcaption>The Fire Triangle</figcaption></figure><p>However, if you have all the ingredients present with an optimal mix you’ll get a powerful, sustained blaze.</p><p>The fire triangle is analogous to the relationship between Sales, Customer Success and Product Teams in a SaaS.</p><p>The relationship between those three teams is critical for success, and any disharmony can cause serious issues accross the business.</p><p>If Sales for example are selling too far ahead of the product CS will (rightly) come under pressure from customers who are struggling to get the value they were promised. NPS scores will be low and customers will start to churn.</p><p>Similarly Product will come under pressure from both Sales and CS when customers learn they can’t do all the things they were promised, and design and engineering teams start playing catch-up and spend less time on their core objectives or roadmap.</p><p>These situations lead to teams living in the top left hand corner of the <a href="https://en.wikipedia.org/wiki/Time_management">Eisenhower Box,</a> constantly dealing with urgent things, but crutially never getting time to work on far more valuable, but less urgent strategic imperitives.</p><p>However, when these teams are well aligned great things happen.</p><p>In an ideal scenario all three teams work together to properly understand customer pain points and how the product relieves those pains and drives improved customer outcomes.</p><p>Sales can then confidently sell to those points, CS can manage to them, and Product can set metrics and optimise against them.</p><p>If you’re a PM, make sure you are spending time with CS and Sales to not only understand what they’re hearing from customers and the market, but also align product value and strategies across your teams.</p><p>This will stop powerplays and politics, build trust and buy your product team time and space to get on with delivering strategic pieces that everyone will appreciate, making sure your team fire burns bright and long!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a936bd93049" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>