<?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 Joe Dempsey on Medium]]></title>
        <description><![CDATA[Stories by Joe Dempsey on Medium]]></description>
        <link>https://medium.com/@joedempsey?source=rss-47cdfe763a03------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HQwljHwYuz3OTufG2g1DBQ.jpeg</url>
            <title>Stories by Joe Dempsey on Medium</title>
            <link>https://medium.com/@joedempsey?source=rss-47cdfe763a03------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:22:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joedempsey/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[When paying for Software Development, don’t ask for a fixed scope]]></title>
            <link>https://medium.com/@joedempsey/when-paying-for-software-development-dont-ask-for-a-fixed-scope-95fe469a83a9?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/95fe469a83a9</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 16:40:49 GMT</pubDate>
            <atom:updated>2018-09-04T16:40:49.535Z</atom:updated>
            <content:encoded><![CDATA[<p>In everyday life, buying products and services is often a clear cut process. You know what is being offered, you know how much it will cost and the exchange can be made relatively simply.</p><p>Software development should be treated differently, but it’s still perceived in the same way as buying a fridge or cable TV subscription. I’ve helped build a lot of tech products, and here are some common questions I’ve had:</p><p>a) How long will it take to build the product?<br>b) How much will all these features cost?<br>c) What features will be built in the next 6 months?<br>d) Can we agree a 12 month roadmap?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BML6dpky8Xt6ULhcepYxuQ.png" /><figcaption>Having a fixed scope is riskier than paying for development time.</figcaption></figure><p>I try to educate founders about a better way to build software. All the questions above revolve around the common misunderstanding that having a fixed scope is less risky than paying for development time.</p><p>Here are some reasons why you shouldn’t ask for a fixed scope and always find a tech partner that offers a full time Agile development team rather than fixed feature delivery.</p><h3>1. Startups need to stay agile</h3><p>You need to be able to change your mind about how something works, or what your product does. You will talk to potential users and your team, you will learn from other products, you will have ideas. If you are signed up to an agreed scope then you will not be able to change what is being delivered without bureaucratic change request processes and re-estimations. If you are paying for a team, then their priorities can be changed almost instantly if that’s the right thing to do.</p><h3>2. You are more likely to get the product you expect</h3><p>If you are agreeing a fixed scope, then you need to decide, design and finalise every aspect of your product up front before any development starts. This is very difficult to do as there are too many unknowns at the start of any project. With a fixed scope you will have to wait and hope the final product gets delivered working and looking as you imagined months earlier. With agile development, you can check in regularly and course correct often so expectations on both sides are continuously aligned.</p><h3>3. You can get essential feedback earlier</h3><p>With Agile development, your team will constantly be working to deliver value in small incremental chunks. This means that within a few days or weeks you can have real, working software that lets you complete some flows within your product. It might not be the final version, but even the simplest flow can be put into the hands of potential user to test if the value you expected is being offered and if your product is usable, desirable etc. Any feedback you get can be put back into the team immediately so they can adapt and change things while working on the next version. The alternative is waiting for months before getting the whole product delivered and hoping that users respond well to it when they see it. If you need to make changes after the whole product is built then everything becomes harder, slower and more expensive.</p><h3>4. It’s more efficient</h3><p>Software estimates are infamous for being inaccurate. This is perceived as developers covering their backs or agencies trying to win contracts or squeeze more money out of clients. However, as building tech products usually involves creating something new, it is very difficult to accurately estimate and predict what might happen in the future once work starts. The only way to accurately estimate how long software will take to create is to basically write out the logic and code…..this is very time consuming. Your team’s time would be better spent building a product and dealing with any unknowns that come up, instead of spending days trying to provide detailed estimates that will more than likely changed once more information is available.</p><h3>5. It encourages you to prioritise what is important to your business</h3><p>As mentioned in point 3, a good agile team will break down a product scope into layers of value and work on delivering working, valuable user flows in increments. This means that you can decide what is most important to your users and business and work on this first. Doing this means it can be delivered sooner and tested. If you have agreed to a fixed scope and delivery, then the team can decide to work on whatever part of the product is best for them first and fill in the rest later. Agile development forces the whole team to work on what is best for the users first. The great result of this is that you can keep re-prioritising the things that are best for your business and users, and it doesn’t matter if the low priority things never get done because your product is always working and always delivering more value.</p><p>Those are just a few reasons why I believe you should work with a team rather than a fixed scope. The only stumbling block is that for time based development to work, you need to fully trust the team is always working towards the correct goals and are pushing to deliver the maximum value to your product. As a Product Manager, I’ve found the best way to guarantee trust is by being 100% transparent with what the team are doing and why. This means exposing development boards to founders, sharing work every day, never hiding any code and showing the people behind the team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95fe469a83a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Lessons from a Startup Studio]]></title>
            <link>https://medium.com/@joedempsey/6-lessons-from-a-startup-studio-c693afb76475?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/c693afb76475</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 14:21:32 GMT</pubDate>
            <atom:updated>2018-02-27T14:21:32.027Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GC5N45M_JYF6LpDH8aYirQ.jpeg" /></figure><p>At ucreate, we help non-technical founders build and launch tech businesses. As a Product Manager, I’ve worked directly with many startups, and indirectly with many more. Here are the top 6 lessons I think Founders can benefit from when launching a tech startup.</p><h4>Building tech is an expensive way to validate your idea</h4><p>There are reasons that you should test drive a car before buying it, or taste your cake before cooking it. In the examples above, the first saves us from wasting a lot of money and time on the wrong thing, and the second gives us a chance to adjust the mixture to make sure the result is what it should be.</p><p>Both examples are no-brainers, yet lots of founders spend hundreds of thousands over several months building a tech product without really trying to find out if it stands a chance in the real world. With some help, most businesses can be boiled down to a very simple value proposition. From experience, there is always a way to start testing if this is actually valuable by spending less than £100 over one weekend. It might not be a crystal clear answer, but you will definitely learn something.</p><h4>Perfect design won’t define your startup</h4><p>I’m not suggesting that you release a sloppy product or don’t use a quality UX/UI designer, but you should stop focusing on design until you get users. Early users don’t care about pixels, they don’t care about font weights and they don’t really care about consistency. All they need to use your product is for it to be easy to find, easy to use and to solve a problem for them.</p><blockquote>Unconsidered design can lose a potential user, but very good design will never make your business. OK design is fine for product launches.</blockquote><p>Focus on the basics: clear screens with simple call to actions, UX that helps the user complete a task, the right amount of text, familiarity and intuitive flows (following a framework like Material Design is a great start). Regardless, your brand, logo, domain and name will probably change several times if you get to be as successful as you want, so don’t waste too much time on them at the first attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bCpFhbZNBbNiT6cLaxCXOw.png" /><figcaption>Material Design prioritises user actions to make core functionality immediately apparent</figcaption></figure><h4><strong>The hard work starts after you launch</strong></h4><p>‘Build it and they will come’ might be true for certain things, but it does not apply to early stage tech startups (there are some exceptions to this but if you believe your product will also be one then you are likely to be disappointed). A product doesn’t make a business, users don’t even make a business, you need many loyal users or users who will pay for your product.</p><p>Coming up with a solution to a problem can be hard, but it is a lot easier than convincing other people that your solution is the right one. Make sure you save some energy during your MVP build so that you can take what you’ve created and put it in front of the people who need it. I’ve seen many founders get so involved in building the product that they just relax when it is launched. This is equivalent to devotedly training for a marathon then turning up to the start line with a bottle of champagne and a Twitter status littered with 🚀 emojis. Remember that building a product is preparation for the race, you don’t automatically win by releasing your product.</p><h4>A good product won’t market itself</h4><p>I see lots of founders working full time to create the perfect product without spending any time working on how they are going to communicate the value of their product.</p><blockquote>If your strategy for growth is virality or word of mouth then, a) that is risky and b) you need to start somewhere.</blockquote><p>A better strategy is to start by setting some clear communication around how your product helps its users. Don’t focus on what it does, focus on why that is valuable. Put your tagline, video, diagram (or whatever communicates the value best) on a landing page before you start building, hustle or pay for some traffic from your target market and see how many sign ups you get. Similarly, while you are building you should be changing your messaging and fighting for traffic to test it on. By the time you launch, you should be able to explain the value of your product to anyone in your target market in around 10 seconds and not need another go at doing it after.</p><p>If your product does lend itself to being shared then you will still need a pocket of loyal early users who are willing to pass on the value of your product for you. Work hard to find these users and give them the tools and motivation they need to be your missionaries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*K6cP9bPeW7RGST-zaBLlZw.png" /><figcaption>Shout about the benefits of your product, not the features</figcaption></figure><h4>Paying for your first users is ok</h4><p>I‘ve noticed that Founders think (or are taught) that if you can’t acquire your first users based upon your value proposition alone then you don’t have a viable business. This can set up a lot of new businesses to fail.</p><p>If your value proposition is already well known, then simply positioning yourself in the market alongside the competition will give users the opportunity to find you. However, if you are launching a new or different product then people will be less comfortable to be the first to try. Consider paying to help users take the plunge, this needn’t be expensive as the following are all useful tactics: PPC marketing, Discounts &amp; Vouchers, Cash referral rewards.</p><p>You need users in order to learn and refine your product and business. An early sample size to learn from is worth spending money on as it will give you the opportunity to organically test your refined value proposition later. Not many companies have the luxury of large VC or Angel investment and can’t go on paying for users indefinitely, but doing so for a few in the beginning could be the key to building early momentum for your business.</p><h4>Grow your business, not your product.</h4><p>As I have mentioned, I don’t think design will kill a business and launching a product isn’t the finish line, but users are the be all and end all. Founders need to ruthlessly prioritise where they spend their time and I don’t think the product should be high on the list.</p><p>Setting a product vision is important but that doesn’t get the right product built. To achieve that you need engineering, design and someone to represent the user. There are a lot of hidden overheads that come with building a product and Founders should be shielded from this so they are free to market and sell to users. A good Product Manager smooths out the product development process, it’s a Product Manager’s job to absorb the overheads so that the team can do what they are good at. This includes the founder, if the product is looked after properly then setting a vision is enough for the founder to worry about.</p><h3>Takeaway</h3><p>As a Founder, focus on what will impact your business most. This is probably gaining loyal users and offering them value. If you have a team around you, then lean on them as much as you can. Set the vision for them and let them work towards it while you grow your business.</p><p>Building a product is hard, marketing a product is hard, selling a product is hard, hiring is hard, running a business is hard. Don’t try to do it all.</p><p><em>If you’re interested in learning more about all things Product Development then make sure to hold down on the clap button and follow me and the publication.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c693afb76475" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Product Management takeaways from Intercom (Part 2)]]></title>
            <link>https://medium.com/@joedempsey/10-product-management-takeaways-from-intercom-part-2-61667b274328?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/61667b274328</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 14:54:11 GMT</pubDate>
            <atom:updated>2017-11-07T15:01:26.475Z</atom:updated>
            <content:encoded><![CDATA[<p>The 10 key actionable insights from <a href="https://www.intercom.com/books/product-management">Intercom on Product Management</a> that will help you build better products and be a better Product Manager:</p><p><a href="https://medium.com/@joedempsey/10-product-management-takeaways-from-intercom-part-1-28ad577634fc"><em>(See Part 1 for takeaways 1–5)</em></a></p><h4>There are 3 ways to improve a feature</h4><ul><li><strong>Deliberate Improvements</strong>: Your aim is to make a feature better</li></ul><p>These improvements make a feature better for the people who are already using it e.g. easier to use, faster. Deliberate improvements on core value features (see lesson #1) are high risk/high reward because you can delight your entire user base or break your core workflow.</p><ul><li><strong>Frequency Improvements</strong>:<strong> </strong>Your aim is to make a feature be used more often</li></ul><p>Adding more options or more hooks into a feature e.g. notifications, might get existing users to use the feature more. <a href="https://www.amazon.co.uk/Hooked-How-Build-Habit-Forming-Products/dp/0241184835/">The Hooked Model</a> by Nir Eyal is an excellent guide to help with Frequency Improvements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eA6GKfaQYc01vPoELvYIKQ.png" /><figcaption>The Hooked Model can help to increase how often a feature is used</figcaption></figure><ul><li><strong>Adoption Improvements</strong>:<strong> </strong>Your aim is to make more people use a feature</li></ul><p>These improvements target people who aren’t using a feature. Examples include: better onboarding, in-product help and viral gamification. <a href="https://en.wikipedia.org/wiki/5_Whys">The 5 Why’s</a> technique is a great way to get to the root cause of why someone might not be using one of your features.</p><h4>Have an acid test to approve new features</h4><p>We’ve discussed that you should not continue to add features to your product without seriously considering the value they add. As a Product Manager it can be hard to keep multiple stakeholders happy with a finite development team at your disposal. Having a list of criteria that any feature request must pass before it is eligible for prioritisation can help make your decision making transparent and unequivocal.</p><p>Intercom list 10 questions that a feature must score straight yes’s on. You can check their list in the <a href="https://www.intercom.com/books/product-management">book</a> but here are my favourites and some of my own:</p><ol><li><strong>Does it fit in with the product vision?</strong> (Gospel! Always move towards your vision)</li><li><strong>Does it grow the business?</strong> (A yes here can conflict with #1 so be careful as growth should always be front and centre)</li><li><strong>Does it contribute to a predefined, measurable goal?</strong> (e.g. adoption. This will stop you accepting ad-hoc requests that don’t support #1 or #2)</li><li><strong>Will the the benefit out-way the support and maintenance costs?</strong> (think ahead, technical debt piles up)</li><li><strong>Do we have the competencies to build it well? </strong>(releasing early is not an excuse for a botched job)</li></ol><h4>Prioritise using ROI</h4><p>Takeaway #4, there are no small features! (see part 1). With that in mind, focus your roadmap around features that offer value for money, because everything costs money. Plot your backlog items on a quadrant with User Value and Effort as the axis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2wK0QkxMyPvRUBPxxKEQqg.png" /><figcaption>Intercom suggest plotting the ROI of features like this</figcaption></figure><p>Users only care about items on the right hand side of the quadrant so make sure your roadmap doesn’t have long period with none of these items. Of course it’s necessary to to do work from the left hand side e.g. Architecture improvements, but spread these out so users can see constant improvement in your product.</p><p>Items in the bottom right are the Low Hanging Fruit, this is usually the rarest category as the benefit disproportionally outweighs the investment. Use these to balance out periods where you need to add changes from the left hand side.</p><p>Here is another way of prioritising features based upon ROI (taken from <a href="https://medium.com/product-problems/product-management-is-like-roulette-except-the-house-doesnt-always-win-2a083ff96301">Product Management is like roulette, except the house doesn’t always win</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*6Y9Bq5AeXMbNotgHylizqg@2x.png" /><figcaption>A matrix to find quick wins that benefit users</figcaption></figure><h4>Roll out strategy matters</h4><p>This one depends on the stage of your product/company, the size of your user base and the nature of your workflow. Early stage companies with few users and non-essential workflows can consider immediately launching features to all users once they are test complete. However, if you are are an established company with lots of users who rely on your product for mission critical tasks (think B2B) then a phased rollout is safer.</p><p>Intercom using the following approach:<strong> Team testing ➡️ Company testing ➡️ Beta testing ➡️ Full roll out</strong></p><h4>Communicate about new features properly</h4><p>Designing, building and testing features is engaging so it’s easy to get addicted to doing this and never look up from the trenches. Once code is shipped it’s easy to forget about it and move on.</p><blockquote>A feature without engagement is not a feature, it’s technical debt.</blockquote><p>Companies and Product Managers do not win by having an ‘all encompassing’ product with lots of features . <strong>Engagement = winning!</strong></p><p>Here are some ways to properly communicate a new feature so users become engaged:</p><ol><li><strong>Show how it benefits them — </strong>Gospel! Nobody cares how smart your product is, they care how it can help them.</li><li><strong>Show how they can use it — </strong>Don’t patronise…but never assume that they know it as well as you, because you built it.</li><li><strong>Announce it in the right place — </strong>Communicating inside your product is better than outside via email. If you want a user to try your new filter feature then they are far more likely to do that if they are already filtering information when you alert them.</li><li><strong>Announce it at the right time </strong>— If a user has just joined your product, the first onboarding popup should not be about data export as the user hasn’t got any data yet. Map out your user journey and introduce features gradually at the relevant point as your users advance.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNDCVSiGu8BzZoqQ23Kwkw.png" /><figcaption>An Intercom example of good communication along a user journey</figcaption></figure><h4>Summary</h4><p>There are plenty of great lessons for Product Managers in <a href="https://www.intercom.com/books/product-management">Intercom on Product Management</a> and here are my top 10:</p><ol><li>Audit your feature usage</li><li>Be careful with customer priorities</li><li>Say No to features more (there are no small changes!)</li><li>People only use your product to solve a problem</li><li>The 3 ways to make products people want</li><li>There are 3 ways to improve a feature</li><li>Have an acid test to approve new features</li><li>Prioritise using Return on Investment</li><li>Roll out strategy matters</li><li>Communicate about new features properly</li></ol><blockquote>If you’re interested in learning more about all things Product Development then make sure to hold down on the clap button and follow me and the publication.</blockquote><figure><a href="http://eepurl.com/c9D9iT"><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ADkMmv3LFcydB0vCVTkuQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61667b274328" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Product Management takeaways from Intercom (Part 1)]]></title>
            <link>https://medium.com/@joedempsey/10-product-management-takeaways-from-intercom-part-1-28ad577634fc?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/28ad577634fc</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 14:51:43 GMT</pubDate>
            <atom:updated>2017-11-07T15:01:22.917Z</atom:updated>
            <content:encoded><![CDATA[<p>The 10 key actionable insights from <a href="https://www.intercom.com/books/product-management">Intercom on Product Management</a> that will help you build better products and be a better Product Manager:</p><h4><strong>Audit your feature usage</strong></h4><p>If you don’t know how many people are using your features, and how often, then you don’t know where to improve your product.</p><p>Use an analytics tool (Mixpanel, Intercom, Google Analytics etc), SQL or whatever works for you, to plot all your features (excluding administrative features like password resets) on two axes: <strong>how many people use a feature, and how often.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2xVTEMItpOz2wD8bhpZRg.png" /><figcaption>A typical feature audit example from Intercom</figcaption></figure><blockquote>“The core value of your product is in the top right area, because that’s what people are actually using your product for.”</blockquote><p>If most of your users are using one feature a lot and the others are not being used, then you have a bloated product and a competitor focusing on that one feature could quickly overtake you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKFhubr6xuzj4apTzCCUEg.png" /><figcaption>An Intercom example of ideal feature usage</figcaption></figure><h4>Be careful with customer priorities</h4><p>If you ask customers if they would like you to add feature X, they will probably say yes! This is a no-loss question for them. Within a company Product Managers are used to trade-offs because resources are finite. However, customers do not care about internal struggles and nor should they.</p><p>To get a better idea of what customers really want try making them choose between features e.g. Would you rather we added more search options or added this integration for you?</p><blockquote>I’m not a big fan of asking customers to prioritise a list of features because; a) that’s work for them to do to help you, and b) they will probably all come back as ‘Must haves’ which gives you no insight.</blockquote><h4>Say No to features more</h4><p>There are no small changes in Software Development. Seemingly innocuous or superficial features like character limits can impact existing features or disrupt loyal users. Even copy adjustments can change the perception of your product. Also, <strong>everything adds technical debt and complexity.</strong></p><blockquote>“Scope grows in minutes, not months.”</blockquote><p>It’s easy to keep developers busy with a backlog of feature additions that are easy and ‘no-brainers’ to add. But your product will get bloated one careless decision at a time. If all you do is add new features then your product will be miles wide and inches deep — the dreaded Jack-of-all-trades.</p><h4>People only use your product to solve a problem</h4><p>Persona’s are great as they help you understand your users and markets. However, products are not prescribed to people based upon their demographics, frustrations, good days, emotions, [insert relevant persona metric here]. Take it back to basics — people use your product to solve a problem that they have. Even when purchases are seemingly based completely on brand loyalty, the user is still solving a problem e.g. I want to wear Nike to look cooler in front of my friends.</p><p>The <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">Jobs To Be Done Framework </a>is good reading for Product Managers who want to understand why people use a product (and that should be all of you…)</p><h4>The 3 ways to make products people want</h4><p>Plenty of software gets created that is not useful to anyone. If you think you’ve identified an opportunity for a product or feature that can solve a customer painpoint then it should do one of these three things:</p><ol><li><strong>Remove steps/make it easier</strong>: Deliveroo reduced the number of steps needed to get a meal.</li><li><strong>Make it possible for more people</strong>: Thanks to Snapchat, Instagram, Youtube etc vlogging is now available to everyone, not just people with production companies.</li><li><strong>Make it possible in more situations</strong>: Mobile Banking apps let people manage their finances on the move without needing to visit a bank during working hours.</li></ol><blockquote>“It’s easier to build things people want than it is to make people want things”</blockquote><h4><a href="https://medium.com/@joedempsey/10-product-management-takeaways-from-intercom-part-2-61667b274328"><em>(See Part 2 for takeaways 6–10)</em></a></h4><blockquote>If you’re interested in learning more about all things Product Development then make sure to hold down on the clap button and follow me and the publication.</blockquote><figure><a href="http://eepurl.com/c9D9iT"><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ADkMmv3LFcydB0vCVTkuQw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28ad577634fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A simple formula to help Product Managers (or anyone)]]></title>
            <link>https://medium.com/@joedempsey/a-simple-formula-to-help-product-managers-or-anyone-2bafffa34541?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bafffa34541</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritisation]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Thu, 19 Oct 2017 14:34:14 GMT</pubDate>
            <atom:updated>2017-10-19T14:34:14.087Z</atom:updated>
            <content:encoded><![CDATA[<p>I almost called this a simple formula for success but there is no such thing 🙊. However, approaching your work in this way should help:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RF-jPM8XCH94wjM2B-yyAg.png" /></figure><p><strong><em>tldr; </em></strong><em>do the most important thing each day, focus on it and communicate what you’re doing</em></p><h4>Prioritisation x Execution</h4><p>Product Managers usually wear many hats and often have long to-do lists. This formula revolves around picking the task that will have the most impact and fully focusing on it so it’s value can be realised.</p><p>Assuming the importance of a task, and how well it is executed, are both rated on a scale of 0-10 then Prioritisation x Execution has a potential score of 0-100. <strong>Always aim for 100.</strong></p><blockquote>Scoring 100 means you are working on the most valuable thing you can, and you are delivering everything that is needed for all the value to be realised.</blockquote><p>If you have 10 tasks in your to-do list and you work on the fourth most important task, even if you do a great job on this task then your max score is limited to 40. Likewise, if you pick the most important task and only complete half of what is needed then you are only scoring 50.</p><p>Generally, when we apply ourselves to something we have the capability to do it well. So the Execution score in the above formula is usually high. <strong>The easiest way to improve your result is to increase the Prioritisation score by working on the task that will move the needle the most.</strong></p><p>In the book ‘First Things First’,<strong> </strong>Stephen Covey says that if you focus on moving the big rocks first then even if you only move that one rock each day, you will be productive; he is right ✅ .</p><h4><strong>Transparency</strong></h4><p>Transparency is included in the formula because I have found that it is very hard to over-communicate what you are doing as a Product Manager.</p><p>Being transparent about what you are doing and why has the following <strong>benefits</strong>:</p><ul><li>People can help you if they have more/different information</li><li>Expectations are clearly set for everyone</li><li>Communication is a fundamental skill that should be practised</li><li>Course corrections can be made early and often</li><li>Showing your work shows your value to others</li><li>Results can easily be measured back to clearly communicated goals/metrics</li><li>The Lean Startup approach — release your work early and often for maximum impact</li><li>You will get more feedback ➡️ you will learn and improve faster</li><li>A lack of communication leads to more spin/PR being needed later to align stakeholders. Spin/PR is difficult and risky.</li><li>You will never be chased for updates if you over-communicate</li></ul><h4>Summary</h4><p>Do the most important thing each day, focus on it and communicate what you’re doing.</p><p>For more on this topic check out this <a href="https://seekingwisdom.io/44-how-to-prioritize-6ad2a6fbd65f">podcast by Drift</a>, <a href="https://www.amazon.co.uk/First-Things-Stephen-R-Covey/dp/0684802031/">‘First Things First’</a> by Stephen Covey and <a href="https://www.amazon.co.uk/One-Thing-Surprisingly-Extraordinary-Results/dp/1848549253">‘The One Thing’</a> by Gary Keller. You can also 👏 for this article and follow me for more content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bafffa34541" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Management Hierarchy of Needs]]></title>
            <link>https://medium.com/swlh/the-product-management-hierarchy-of-needs-1003b6c439d2?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/1003b6c439d2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 15:28:40 GMT</pubDate>
            <atom:updated>2019-02-07T19:45:35.987Z</atom:updated>
            <content:encoded><![CDATA[<p>Maslow’s Hierarchy of Needs is usually portrayed as a pyramid with the largest, most fundamental needs at the bottom. The lower level needs must be satisfied before the higher level needs can be met.</p><p>I think a similar theory can be applied to Product Management and I’ve captured it in this diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*y6kZA5PdvGfUTFddgwxcGg.png" /><figcaption>The Product Management Hierarchy of Needs</figcaption></figure><p>So, starting from the bottom…</p><h3>The why</h3><p>The most basic need for a Product Manager is to have a problem to solve. The best products and companies stem from a real, well defined problem. Google made finding web pages easier, Amazon provided a greater choice of books and Paypal simplified online payments.</p><p>Impatient ‘entrepreneurs’ will often focus on a problem that doesn’t exist and try to convince others to go along for the ride while they fulfil a dream of being ‘CEO &amp; Founder’. Likewise, Product Managers can often get into a <a href="https://medium.com/product-problems/dont-be-a-feature-addict-ca5f426a734a">rut of delivering features</a> that aren’t really needed and offer no value.</p><p>Your idea must be <strong>viable</strong> — understand and validate the problem to make sure it exists and is painful enough to justify any work that goes into solving it. <em>(It’s ok to go after smaller problems if your outlay is minimal).</em></p><p>Successful products can come from seemingly nonexistent problems e.g. over 75 million Tamagotchis have been sold ‘just for fun’, but remember, it’s harder to sell a vitamin than a painkiller.</p><blockquote><em>Tip:</em> <em>Use the </em><strong><em>5 Why’s</em></strong><em> approach to get the underlying problem and understand the real pain points.</em></blockquote><h3><strong>The who</strong></h3><p>If you’ve validated that there is a problem and the risks/unknowns have been reduced enough to justify moving forward, then you can address the next basic need — users.</p><p>For an idea to be <strong>viable</strong>, there must be people who are willing to use your product (and pay if you’re selling it). This links very closely to the the why because if there is no market for your idea then it’s usually because you are not solving a real problem.</p><p>There can be times when a seemingly good idea is not viable because of user perception or circumstances e.g.</p><ul><li>People don’t want to be seen using your product</li><li>People can’t access your product</li><li>The people who need it, can’t pay for it</li></ul><p>To satisfy this need; know your users; talk to them, put things in front of them, watch them. Make sure you can answer questions about who they are, how many they are, where they are, what they do, their motivations/pains.</p><blockquote><em>Tip: Identify the </em><strong><em>persona(s) </em></strong><em>that will use/buy your product. Before building anything meet with at least 3 of each persona and buy them coffee/cake until you’re confident you can answer all the above questions and more.</em></blockquote><h3><strong>The what</strong></h3><p>You’ve now satisfied two needs: there is a problem to solve and there are users who want it. To be <strong>valuable</strong>, your product must benefit your users by delivering a solution that solves their problem.</p><p>Any solution you identify must also be feasible, i.e. can you create it within any constraints e.g. resource, expertise, the laws of physics….</p><p>Example — Building a human teleportation device definitely solves a transport problem, and definitely would have users, but is it an appropriate solution when compared to e.g. better public transport.</p><p>Make sure any solution you create is linked back to the problem you’re solving and the users you are solving it for. Favouring Lean Methodologies and putting your solution in front of users early and often offers guardrails that stop your product going too far astray.</p><blockquote>Tip: Sketch out the current user journey and mark everywhere your solution impacts this flow. Check that your product will have the desired effect or change at each point you have identified.</blockquote><h3>The How</h3><p>If you have identified a problem, and your target market can use your solution to solve this problem then you probably have something close to the fabled Minimum Viable Product or MVP. (<em>In this article I have emphasised offering value to your users so I think Minimum Valuable Product is a better term to use here.)</em></p><p>Once you have satisfied the most basic three needs and have an MVP Product Managers will naturally look to improve, refine and optimise their product. Maslow’s description of ‘Self-actualisation’ transfers well to this stage;</p><blockquote>“the desire to accomplish everything that one can, to become the most that one can be”</blockquote><p>Translation — you want your product to be the best that it can be.</p><p>This is ‘the how’, and can generally be held under the umbrella of User Experience (UX). User Experience is more than just the order that screens are shown in, or the location of tooltips and buttons. It includes the whole user journey from the moment the user finds your product, downloads/opens it, registers on it, shares it, reports issues with it, upgrades it, pays for it etc. If your app is great but nobody can find it or download it, then is it offering any value and is it really a great app?</p><p>UX is the final need in the Product Management Hierarchy and therefore offers the greatest level of freedom to be creative and individual. Learn what your users like and don’t like, experiment with A/B tests, put thought into design and optimise at every stage. Remember, simple is not easy and it’s often better to improve a product by taking things away rather than defaulting to adding things in.</p><blockquote>Tip: Use the <a href="https://medium.com/product-problems/product-management-is-like-roulette-except-the-house-doesnt-always-win-2a083ff96301">Kano Model</a> to categorise work items and implement delighters alongside your core product. Delighters are great ways to influence the UX and make your product sticky and loveable.</blockquote><h4>Summary</h4><p>If you think in terms of needs, and the order in which they are satisfied, then the process for solving problems becomes clearer:</p><ol><li>Start with why and understand the problem</li><li>Know your users inside out</li><li>Your solution must offer value</li><li>Optimise the whole User Experience to make your product loveable</li></ol><p>I believe there is a lot more to add around this theory but I like to eat my own dogfood so I’m publishing my thoughts early to get feedback. Let me know if you thought this was an interesting read, do you have an alternative view or something to add?</p><blockquote>If you’re interested in learning more about all things Product Development then make sure to hold down on the clap button and follow me and the publication.</blockquote><blockquote>You can also find out more about ucreate and the products we provide at <a href="https://www.ucreate.it/">ucreate.it</a></blockquote><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by +421,678 people.</h4><h4>Subscribe to receive <a href="https://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1003b6c439d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-product-management-hierarchy-of-needs-1003b6c439d2">The Product Management Hierarchy of Needs</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management is like roulette, except the house doesn’t always win.]]></title>
            <link>https://medium.com/@joedempsey/product-management-is-like-roulette-except-the-house-doesnt-always-win-2a083ff96301?source=rss-47cdfe763a03------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a083ff96301</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[prioritisation]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Joe Dempsey]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 09:43:50 GMT</pubDate>
            <atom:updated>2017-08-04T23:39:49.745Z</atom:updated>
            <content:encoded><![CDATA[<p>To play roulette you place bets on where you think the ball will land, simple. The different bets available to you carry different probabilities of winning and the rewards vary accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*nXW6bbdbc5FUXAsgPPQQYQ@2x.png" /><figcaption>The betting options available to roulette players</figcaption></figure><h3>Choices</h3><p>As a roulette player, there are a number of choices that can be made:</p><ul><li><strong>The size of each bet</strong></li><li><strong>Where the chips are placed</strong></li><li><strong>Your strategy</strong> e.g. Do you spread your chips around or focus a specific area? Do you change your bet on the next spin?</li></ul><p>Product Managers have to make similar choices when building products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rMbaDocCdEmN3_8fccB8xw.png" /><figcaption>Roulette vs Product Management</figcaption></figure><h3>Outcomes</h3><p>The results of Product Management and Development can also be compared to the roulette table.</p><p>Imagine each spin of the roulette wheel is a cycle (sprint, release etc) of product development. The work that gets done in the next cycle is chosen based on a number of factors:</p><ul><li>Priority</li><li>Cost &amp; Opportunity cost</li><li>Customer demand</li><li>Technical debt</li><li>Long term vision</li><li>And more….</li></ul><p>In most cases, roulette players will have a limited amount of funds they can bet with, their aim is to increase their funds by winning bets.<br>Similarly, Product teams have limited resource and therefore should constantly be looking to work on the areas that move the needle towards your goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*punRpx3TWfwWg-aT-YHtRg.png" /><figcaption>Backlogs can be huge, and resources are precious</figcaption></figure><p>How your table (backlog) looks before each cycle should be directly linked to a goal you have defined. Every bet you place should be traceable back to a hypothesis that you expect to impact your goal.</p><p>The goal can be different for every team/product, but it doesn’t matter if your goal is revenue, engagement, user growth, loading speed….you should place your chips on the area that will impact your goal. This is tough as <a href="https://medium.com/product-problems/dont-be-a-feature-addict-ca5f426a734a">releasing new features can be addictive</a>, but sometimes UX improvements, experimentation and performance can be better for your goal than a shiny new feature.</p><p>Without a goal to aim towards you are trusting the success of your product to luck. As with roulette, if you keep betting on the wrong things you will run out of time and money.</p><h3>Risk &amp; Reward</h3><p>Just like the odds in roulette, working on different areas of a product brings different risks and varied rewards. Something like a complex security improvement might require significant resources to build but all you get in return is a tick on a checklist that allows you access to an IT department. Conversely, a small tweak to your onboarding might only require a few hours of development but could remove a huge pain point for all your potential new users.</p><p>Here are a couple of simple models you can use to help find the best value bets and deliver value to customers quickly:</p><h4>Low hanging fruit</h4><p>Categorise your backlog items according to the resource they require and the value you think they will add to users (based on your research). Place your bets on the top right quadrant followed by the top left. Ignore anything in the bottom half.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*6Y9Bq5AeXMbNotgHylizqg@2x.png" /><figcaption>A matrix to find quick wins that benefit users</figcaption></figure><h4>The Kano Model</h4><p>Categorise your backlog items according to their type (Delighter, Core feature, Basic need) and then assess their presence/absence against customer satisfaction. Make sure your customers basic needs are covered then use the Low Hanging Fruit model to implement delighters alongside your core product development to make your product sticky and loveable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*iYj219kzHGykSWl1Hr6yEQ@2x.png" /><figcaption>The Kano Model can help Product Managers understand how users will perceive features</figcaption></figure><h3>Summary</h3><ul><li>Just like roulette, Product Managers must assess what bets to place and the outcomes they hope to achieve with each one.</li><li>Don’t trust to luck. Every bet comes with a cost (resource) so the potential reward should justify the outlay.</li><li>Prioritise ruthlessly. Product Managers should only focus on bets that move the needle towards a predefined goal.</li><li>Learn after every spin (development cycle). Double down on areas that are bringing the desired results and don’t be afraid to scrap features that aren’t adding value to users.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a083ff96301" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>