<?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 Greg Le Sueur on Medium]]></title>
        <description><![CDATA[Stories by Greg Le Sueur on Medium]]></description>
        <link>https://medium.com/@greglesueur?source=rss-bd8bbc3397c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HZUEtlNrmkSC5n9lQhBEaA.jpeg</url>
            <title>Stories by Greg Le Sueur on Medium</title>
            <link>https://medium.com/@greglesueur?source=rss-bd8bbc3397c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:16:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@greglesueur/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[How to become more product-led?]]></title>
            <link>https://medium.com/@greglesueur/how-to-become-more-product-led-dc02ce18fb53?source=rss-bd8bbc3397c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc02ce18fb53</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[Greg Le Sueur]]></dc:creator>
            <pubDate>Mon, 24 Oct 2022 22:15:02 GMT</pubDate>
            <atom:updated>2022-10-24T22:15:02.784Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been asked this a few times by product people who feel they are focusing on the wrong problems, or perhaps solving them in the wrong way and don’t know how to get buy-in and autonomy to change. I’ve lived through this pain, as well as had plenty of conversations with others still living through it.</p><p>I’ve also softened my original positioning, which was evangelical about being product-led. I think books like “Inspired” by marty cagan really helped shine a light on how SaaS products could be built, but he also takes a very “fire and brimstone” approach — you’re either doing product, or you’re a feature factory — black and white. In reality there is a lot of grey, and you can carve out parts of the business to be more product-led then others. In this article I’m going to define what I mean by product led, then I’m going to talk through some common blockers and what I, or others, have found to help mitigate them.</p><h3><strong>Why do you want to be product led?</strong></h3><p>First, what do people mean when they say ”become more product-led?” — I asked 10 PMs and they either said:</p><ol><li><strong>Make Product the growth engine, </strong>or “Product led growth”, meaning acquisition, retention and monetisation strategies that are fueled by your product. Slack as an example:<br><strong>Acquisition</strong>: Invite coworkers to your slack, creates user generated growth.<br><strong>Retention</strong>: Usage of features (Slackbot, channels etc) builds habits for retention.<br><strong>Monetisation</strong>: A freemium product, along with usage based monetisation and transparent self serve plan pricing.</li><li><strong>Adopt Product principles</strong> into ways of working. There were a few, but the top 4 themes were:<br>* Focus on the end user first, deliver value, before extracting value.<br>* Use data to make decisions. Define what success looks like.<br>* Learn quicker, build in iterative cycles. Focus on outcomes.<br>* Give teams the skills required to meet an outcome (cross-functional teams)</li><li><strong>Both</strong> — They want product led principles, and think PLG is the best way to get it.</li></ol><h3><strong>But why is this important?</strong></h3><ol><li>They want more autonomy of the opportunities and solutions they work on.</li><li>They feel this is the way the industry is trending and want product-led skills in their career.</li><li>They want to work on a product that has “impact” and believe this is the best way to build and scale a product.</li></ol><p>If you’ve read “Drive” by Daniel Pink, you will see the common threads of Autonomy, Mastery and Purpose in the three sentiments above.</p><h3><strong>What are the blockers to becoming product led and how to overcome them</strong></h3><h4><strong>Product running as an agency</strong></h4><p>Product running as an agency, is sometimes referred to as a feature factory. This is when product teams get feature requests from potential customers. Often these are requirements to signing a deal, sometimes even with a timeline for when it’s delivered. Many companies start this way, and pre product market fit, it is a great model for understanding customer needs while generating money. But ultimately if the company doesn’t pivot from this model early it can lead to inflexible solutions. As you discover more about the problem and other customers with it, you will come up with better ways to solve this problem for a wider audience. Custom one-off solutions limit the flexibility of your product and create tech debt maintaining several similar but different systems. Ultimately this limits autonomy of your product team and slows the company down.</p><p><strong>When sales or customers ask for new features, try:</strong></p><ol><li>Turn sales calls into product discovery calls. Use them to understand what the underlying problem is? Who else has this problem? And how <strong>else</strong> could we solve it? For example can you solve this with integrations into 3rd party products?</li><li>Try pushing back, you would be surprised how many of the “must haves” are actually “nice to haves” and the customer may still sign.</li><li>Recognise that currently you’re not a good fit for the customer, but ask if they would be willing to stay in touch to test prototypes when they are ready. Then reach out when you have something and hopefully close them at a later date. Sales won’t like this so you need to be in a financial position to be able to justify this decision, and outline the cost to this extra work, not only the to build, but the cost to maintain and compared to opportunity cost of other work. Warning: If this happens too often it’s either a sales misalignment in the product positioning or you have gaps in your PMF — either way you need to solve this asap.</li><li>Last resort — If due to financial pressure you have to sign them now, try not to be specific about the solution — just the problem that needs to be solved. Try to be date agnostic, but if they require a delivery date, overestimate to get as long a time frame as possible. This will give you ultimate flexibility in how you allocate resources to solve the problem, while giving you more time to talk to others with similar issues so you create a more well rounded solution. .</li></ol><h4><strong>Target customer wants to be “sold.”</strong></h4><p>Some customers, for example Enterprise buyers, want to talk to someone before they purchase. Done well, this is a great method for getting high value customers. However it doesn’t mean you need to become “sales-led” everywhere, it just means you have a sale-led monetisation strategy for a target customer who expects that. <a href="https://www.linkedin.com/posts/elenaverna_growth-b2b-strategy-activity-6948653926757937153-hJiU/">Check out this matrix from Elana Verna</a> on examples of being product-led, sales-led and marketing-led for each step in the acquire, retain and monetise customer journey. The trick here is remembering you can adopt multiple strategies even when some of your customers want to be sold.</p><p><strong>When you’re currently running sales-led everywhere, try:</strong></p><ol><li>Adopting a “Product-Led Sales” approach, where the product helps with adoption and retention, but uses Sales for monetisation. This is sometimes also referred to as “bottom-up sales” — where the end users explore and validate the product. They then become internal champions that help sell it to the budget holder within the business. Again<a href="https://www.linkedin.com/posts/elenaverna_b2b-growth-activity-6921834807589011458-lIXr/"> Elana brings the goods with this post</a></li></ol><h4><strong>Technically hard to offer self-serve sign-up</strong></h4><p>Being product-led is easier when you have a large customer base, so you have a larger pool of insights to draw on. One of the lowest friction ways to get a large customer base is to let people try the product without having to talk to anyone. However, depending on how the product has been built, for many B2B companies, this is technically hard.</p><p><strong>When you can’t be product-led with acquisition, try:</strong></p><ol><li>Focusing on being product led for activation. There are always opportunities to work on building out the core habits of your product, particularly if you suffer from churn, which often comes from poor activation when they initially onboard. Activation is also something that is easy to measure in a leading way, which will help get you buy in for further investment (more on data, for buy in next)</li><li>Create a secondary product that can be product led, and use it for lead generation. <a href="https://clearbit.com/resources/tools">Clearbit does this very well with their “tools”</a> — Just make sure the value of the secondary product is aligned with your core product, to ensure leads are high quality.</li><li>If the total addressable market is large enough to support the opportunity cost, bite the bullet and prioritise building self serve acquisition into the product. Use growth modelling to justify the opportunity to external stakeholders, and make sure sales is onside by promoting the product-led sales approach mentioned above.</li></ol><h4><strong>Lack of data, so the HIPPO decides</strong></h4><p>If you don’t have customer data to make decisions then it’s hard to understand what’s working and what isn’t. In these situations, the HIPPO makes the calls, and without data can we blame them? Customer data is required to make better product decisions, measure outcomes and ultimately gain trust from leadership, which enables more autonomy.</p><p>Regardless of your set-up you likely have access to customer data already. But not all data is created equal. People put more stock in numbers over stories, so customer interviews and competitive analysis, while useful data points might not be enough. Also, hard numbers are only useful in making decisions if the metrics are leading indicators of success. For example if you only have revenue as a data point, it can be hard to see if the recent activation work you’ve just released is having an impact.</p><p><strong>When you don’t have the right data, try:</strong></p><ol><li>Testing the assumptions you’re making as cheaply as possible. Get multiple people interacting with customers each week. Customer interviews, prototypes, paid ads to landing pages, surveys, etc. There are a plethora of cheap and quick ways to get some qual data, and the more people involved the more they will buy into the findings (and the more you will reduce your own bias).</li><li>If you have a website, get familiar with Google Analytics — the new GA4 might need some dev work to help set up, but it’s not too hard and there’s plenty of data in there to help build a case.</li><li>FullStory is relatively easy to implement, if you don’t have the funds for that Microsoft Clarity is free (but much more manual to get insights out of)</li><li>Manually run SQL against the database, if you don’t have someone who knows SQL, you might have to learn it. <a href="https://www.datacamp.com/">DataCamp</a> has a good free course. Half the challenge here is not just learning SQL, but learning your database structure. Get a dev to walk you through it, often it’s a mess. Lastly, be smart about the questions you’re asking, as regardless of if you’re doing it, there is a real time cost to this process.</li><li>Invest in a tool like Amplitude — Self-serve usage analytics, coupled with split testing capabilities, gives you that next level of granular detail to both identify and validate opportunities, as well as measure success. It’s a game changer, and will help change opinions on the journey to being product-led<strong>.</strong></li></ol><h4><strong>Lack of trust in a product-led team.</strong></h4><p>Perhaps the biggest hurdle is the cultural change and getting stakeholders to champion being more product led. There will be people who are used to making decisions who will now be challenged, and potential customers lost in efforts to build more scalable solutions. Ultimately this comes down to risk mitigation, both the risk of getting it wrong, and the opportunity cost of what people could have done instead.</p><p><strong>When you don’t have trust in trying product-led, first:</strong></p><ol><li><strong>Share the benefits of PLG — </strong>Identify key stakeholders, make sure they understand the potential benefits of being product led. This is where I would focus more on PLG as opposed to product led principles, as it’s more likely to align with the vocabulary and metrics the leader cares about. <a href="https://openviewpartners.com/product-led-growth/">This article summarises PLG quite well</a> but in a nutshell PLG companies have:<br>* Faster acquisition = more scale<br>* Faster adoption = more retention<br>* Lower customer acquisition costs<br>* Attract and retain top talent.</li><li><strong>Make their goals your goals</strong> — Ideally company and department strategies are well communicated, but if they aren’t, you may need to start conversations and get alignment on what metrics your key decision makers care about. <a href="https://amplitude.com/north-star/getting-started-running-a-north-star-workshop">The North Star workshop</a> is a great tool to enable collaboration in these discussions. Regardless the end goal is:<br>* You’ve got some metric that you could measure in a leading way<br>* Key people agree, making this go up is very important right now.</li><li><strong>Make the ask small! </strong>Every company has limited resources, and the more you ask for, the more you put the project at risk of ending prematurely. Treat this like an MVP your using to get greater buy-in for a more holistic change. Use the above metric to pitch a project, time box it to 6 months and limit the team size to a product designer + 2 full stack engineers, with part time data analyst if you can’t self-serve.</li><li><strong>Pick the right time and people </strong>— people who have the experience in the parts of the product you will likely work on, and make sure they are passionate about making it work. Sell them on the opportunity space, the new way of working and the extra autonomy they will have in this project. Stealing top talent from other teams may impact those teams deliverables, this is why making sure your team is small and time boxed. If you’re struggling to get the players you want, another option is to pick a time of year where teams are less busy, for example that might be devs who are willing to work over december/january, while teams are disrupted by holidays regardless.</li><li><strong>Showcase success</strong> — When you do get the team, make sure you showcase success early and often, keep coming back to the predefined metrics and share learnings. The more you communicate the team’s wins during this trial period, the more likely you will get wider buy-in when the project is over.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xb0Qf6heqVwNtjKl" /><figcaption><a href="https://twitter.com/johncutlefish/status/1370298106319753219">Image by John Cutler</a></figcaption></figure><h3><strong>Summary</strong></h3><p>The main points I hope you’ve taken away are:</p><ol><li>You can be more product-led in some areas while staying sales-led in others, and that’s ok.</li><li>You recognise whatever blocker you’re facing right now, and have some ideas to try becoming more product led.</li><li>Product-Led growth is a great enabler of Product led principles. In particular self service acquisition, coupled with product data tracking is a great recipe for teams to deliver value quicker, that’s aligned with the end user, in a way where teams have more autonomy.</li><li>Recognising that change takes time, and potentially a small team on a time-boxed product-led project will be the catalyst for broader change in the organisation.</li></ol><p>I hope this helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc02ce18fb53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comparing down to the baseline VS up to the ideal.]]></title>
            <link>https://medium.com/@greglesueur/comparing-down-to-the-baseline-vs-up-to-the-ideal-5e74188d4287?source=rss-bd8bbc3397c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e74188d4287</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Greg Le Sueur]]></dc:creator>
            <pubDate>Thu, 26 Mar 2020 05:13:59 GMT</pubDate>
            <atom:updated>2020-03-27T01:51:51.463Z</atom:updated>
            <content:encoded><![CDATA[<p>9 months ago I transitioned from my Product Designer background into a ‘Head of Product’ role. I took the role because I believe that through some process changes we can get better outcomes for our customers and the business.</p><p>3 months ago I started seeing an executive coach, to help me become a better leader for my team of product managers and designers. I use the term ‘executive coach’ loosely because, in reality, these meetings are more like a therapy session.</p><p>One of the things we discussed today was my frustration that the company I work for wasn’t where I wanted it to be in terms of product maturity. By that, I mean that I read the articles of great product companies like <a href="https://www.intercom.com/resources/books">Intercom</a>, <a href="https://amplitude.com/north-star">Amplitude</a> and <a href="https://basecamp.com/shapeup">Basecamp</a> and I then compare what they are doing to what we are doing and get disappointed with the gap.</p><p>What my coach asked me was very interesting. He said what is the change that you’ve seen in the past 9 months, has it improved?</p><blockquote>The answer was yes, compared to 9 months ago our processes have gotten so much better.</blockquote><p>He then said I’m comparing my present situation to my ideal state — the promised land of where I want to be, the place these other companies have worked years to get to. Instead, I need to be comparing to the baseline, the old status quo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CR_B7PYSB_24bvU3YRlQ3w.jpeg" /><figcaption>example of how this works in product development. <a href="https://basecamp.com/shapeup/3.5-chapter-13#compare-to-baseline">Image from basecamps shape up book</a></figcaption></figure><p>Now what is funny is that earlier this week I ran a <a href="https://youtu.be/FRs_o-nySR4?t=1613">remote panel live on youtube</a> on how Product Managers at different companies had found adopting Basecamps “Shape up” principles. One of the slides in my deck had the image above. It’s the exact same concept my coach was talking about but instead applied to building product.</p><p>When you think about it, comparing up to your ideal state is natural for anyone who gets pride in their work. Naturally, we want our work to be the very best it can be, and we should keep striving for it. However too often we lose sight of how far we have come, and when you look back, hopefully you will find the new baseline is already a big improvement from the old one.</p><blockquote>This isn’t an excuse to settle — its a lens to feel encouraged.</blockquote><p>I can look at the past and know that eventually, we will get to that promised land state if we continue with the same rate of improvement. Through this lens, it shifts my perception from “this sucks, I wish were more like x” to “look how far we’ve come, let&#39;s just work on this next thing to move us closer to where we want to be”</p><p>This lens gives me more appreciation for what we have:</p><ol><li>A company with leadership that is investing in improving the product process. With a seat at the table to drive change.</li><li>A team that is behind this vision and is passionate about building great products, that has already made great strides to improving our processes.</li></ol><p>Through this lens when things don’t go the ideal way, I have more patience, because I know if we keep at it, eventually it will. All I have to do it look at how far we have come to see we are destined to get there eventually.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e74188d4287" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 8 tips for JTBD Interviews]]></title>
            <link>https://medium.com/the-job-to-be-done/top-8-tips-for-jtbd-interviews-6739c88f1cc9?source=rss-bd8bbc3397c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6739c88f1cc9</guid>
            <category><![CDATA[jtbd]]></category>
            <category><![CDATA[customer-research]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[Greg Le Sueur]]></dc:creator>
            <pubDate>Sun, 25 Feb 2018 04:58:38 GMT</pubDate>
            <atom:updated>2018-02-25T05:40:26.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p4sXEnXRjpm1X_p8T93Ikg.png" /></figure><p><em>I got some feedback on this article on </em><a href="https://medium.com/@greglesueur/what-to-do-with-all-your-jtbd-research-84b92774f42f"><em>what to do with your JTBD research</em></a><em>. I was told that I jumped into the deep end of JTBD and some people may not understand the reasoning for some of my recommendations. Instead of cramming it all into one article I’ve summarized my top 8 tips for JTBD Interviews that may help answer addition questions.</em></p><h3>1. Is JTBD even the right approach?</h3><p>As great as JTBD is, it’s not the holy grail of customer research. It’s just one of the many tools available in the Design Thinking framework. If you’re trying to innovate a new product or feature then JTBD is great. If your trying to work out how to improve an existing feature maybe you should try User Testing first. JTBD works best when you can find a switch event that has a lot of customer struggles in it.</p><h3>2. Focus on a switch event</h3><p>There is no point talking to someone who’s been buying “Product X” for years. If you ask them why they are purchasing that particular brand they will just give you a generic response. That’s because the struggle that made them switch to Product X happened years ago. Your better off talking to people who have recently bought Product X for the very first time. This will tell you all the struggles they went through when they switched from their old behaviour to their new behaviour. It’s in these struggles that you learn what is promoting and blocking the new behaviour.</p><p>So when your organising interviews try talk to people who have in the last 30 days switched to your product, or to a product similar to yours. This will help you understand why your customers are hiring you. You can also talk to people who switched away from your product to learn why they fired you.</p><h3>3. You might be competing against nothing</h3><p>Finding a switch event can be hard, especially when there’s nothing that is already trying to solve the job. If this is the case try and look for work arounds or hacks people are using to currently get the job done and focus on thouse switch events.</p><p>Audio books is a great example. I personally didn’t used to read a lot. I wanted to, but I never found the time and my learning style is more Aural then Verbal. I used to commute 90 minutes a day into work and in that time I listened to podcasts on my phone. Before Audible was launched someone from their team might have been able to interview me to work out what job I was hiring podcasts for and how Audible might improve it (which they did, I love it).</p><h3>4. Talk to 10 people (with the same switch event)</h3><p>This is a mistake I made when I first started, because we offer different products I focused on 4 different switch events. I also only talked to 3–4 people in each. The result was a bunch research notes that was hard to make sense of.</p><p>You need to focus on just 1 switch event at a time and talk to 10 people who have switched in the last 30 days. After 5 you should start to notice patterns in the events that lead them to switch. It will also help you prioritise the main motivations and pain points as you compare notes at the end.</p><h3>5. Do the interviews with a partner</h3><p>Another mistake I made. Having a partner helps the conversation flowing as you take notes and organise your thoughts. Ideally in an JTBD interview you will have someone leading and someone supporting.</p><p>The Leader will direct the conversation through each of the events in the timeline. They need a solid understanding of JTBD and know what questions to ask to uncover the struggle in a customers story.</p><p>The Supporter will help fill in the gaps by asking questions that dive deeper into whatever part of the timeline the Leader is talking about. This gives the leader time to take notes and work out what the next line of questioning should be. It also helps uncover other useful nuggets that might otherwise have been missed and keeps the conversation flowing naturally.</p><h3>6. Listen for the motivations and pain points that led to a switch</h3><p>While conducting the interview you need to be listening for 4 forces:</p><h4>Push of the situation</h4><p>What was it about their situation that led them to look for a new solution? <br><em>e.g. “I’ve bought so many books to read and I haven’t finished any of them”</em></p><h4>Pull of the new solution</h4><p>What was it about the new solution that led them to try it?<br><em>e.g. “Audible is cheaper and I can listen to it while I commute to work”</em></p><h4>Habits holding them back</h4><p>What habits did they have that held them back from trying a new solution? <em>e.g. “My podcasts are free and I still enjoy them”</em></p><h4>Anxieties of the new solution</h4><p>What Anxieties did they have about the new solution?<br><em>e.g. “What if I don’t like a book? Will I lose some books context without visual diagrams?”</em></p><h3>7. Start with the point of purchase and work your way back</h3><p>In timeine (customer journey) people will always want to talk about the point of purchase first, it’s what they remember easily and it’s why they think you’re talking to them so get it out of the way first. Work out what they got, where, how, with whom etc. Then work your way backwards asking them what they used to use to solve the job and when they first thought about solving the job differently. Then find out what was different about this particular situation that made them switch to Product X to solve the job. Finally go all the way past the purchase to work out if the product met their expectations.</p><h3>8. Learn why your customers are firing you</h3><p>If your trying to work out why customers are switching away from your product you need to do two interviews. First work out why they hired you, then you can learn why they fired you.</p><p>For people who have a subscription product this is easy, talk to people who recently canceled their subscription. For others you need to talk to customers who show a pattern of loyal behaviour that suddenly stops.</p><p>When conducting the interviews first work out what job they originally hired you for and then work out why they hired a different solution to solve that job (or why they went back to hiring nothing). It could be that your product didn’t deliver on their expectations or a competitor’s product solves the job better. Alternatively their situation might of changed and so the job is now different or no longer exists for them.</p><h3>I hope this helps, comment if you have any questions or suggestions.</h3><p><em>If you would like to learn more about JTBD Interviews I’d highly recommend </em><a href="https://learn.jobstobedone.org/courses/JTBDinterviews"><em>this course.</em></a></p><p>If you want to learn how to apply JTBD to your work, including what to do once you’ve got the research I’m working on a video course with <a href="https://medium.com/u/dcc57d338d26">David Herse</a> here j<a href="https://www.jobstobedone.pro/">obstobedone.pro</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6739c88f1cc9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-job-to-be-done/top-8-tips-for-jtbd-interviews-6739c88f1cc9">Top 8 tips for JTBD Interviews</a> was originally published in <a href="https://medium.com/the-job-to-be-done">Jobs to be Done</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to do with all your JTBD research]]></title>
            <link>https://medium.com/the-job-to-be-done/what-to-do-with-all-your-jtbd-research-84b92774f42f?source=rss-bd8bbc3397c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/84b92774f42f</guid>
            <category><![CDATA[jtbd]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[customer-research]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[Greg Le Sueur]]></dc:creator>
            <pubDate>Sun, 25 Feb 2018 04:58:07 GMT</pubDate>
            <atom:updated>2018-02-26T07:23:13.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43tVVP0UUPYm3tZppBBMtg.png" /></figure><p>There are lots of resources out there about what <a href="https://jtbd.info/2-what-is-jobs-to-be-done-jtbd-796b82081cca">Jobs</a> <a href="http://jobstobedone.org/">to</a> <a href="https://www.youtube.com/watch?v=RQjBawcU_qg">be</a> <a href="https://www.amazon.com/Competing-Against-Luck-Innovation-Customer/dp/0062435612">done</a> is.<br>There are also great resources for how to do <a href="http://learn.jobstobedone.org/courses/JTBDinterviews">JTBD interviews</a></p><p>However, once you&#39;ve conducted your JTBD research, what happens next?</p><p>How do you identify the patterns in your research? How do you present it so others can understand the job? How do you then use those insights to innovate your product to solve the job better?</p><blockquote>About a year ago I was asking these questions. I’d read Competing against luck and a dozen more articles. I’d completed Bob Moesta &amp; Chris Spiek’s JTBD Interview course. I’d done about 20 interviews and I was looking at my notes trying to make sense of it all.</blockquote><p>I managed to figure out an answer to my questions through conversations with others, as well as borrowing a few techniques from<a href="http://www.gv.com/sprint/"> The Design Sprint</a>.</p><p>I’m now sharing my method hoping that:<br>1. It will help others who have the same questions.<br>2. It opens up the dialogue for critique from people who have had more experience implementing JTBD than I have.</p><h3>Before we continue…</h3><p>I’m assuming you have at least 10 interviews around a switch event. For each interview, you should have notes on the <a href="http://jobstobedone.org/radio/unpacking-the-progress-making-forces-diagram/">forces</a> at play as well as a timeline of events. If you’re not sure about JTBD Interviews I’d highly recommend <a href="https://medium.com/@greglesueur/top-8-tips-for-jtbd-interviews-6739c88f1cc9">reading this first</a></p><h3>Part 1: Identify the patterns</h3><p>Draw out the timeline on a whiteboard. Then, going through your notes, start to add common events that happened at each step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_QsIbz9xjVWqX4UN4M4OFw.jpeg" /><figcaption>For this article I’m going to use the interviews I did for lotto syndicates as an example (a lotto syndicate is when a group of people pitch in for a lotto ticket, they share the cost and if it wins they share the prize)</figcaption></figure><p>Now below the timeline start to add in the Push, Pull, Anxiety and Habit forces. Use green &amp; red stickers to highlight struggles or motivations that come up more often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ms1E4HHi2zOCZ4Jixw9DVQ.jpeg" /></figure><p>By this stage, you should have a pretty clear picture of where the main struggles are in your customers journey. You might want to expand on some post-it notes in more detail, adding quotes or insights for when you present this.</p><h3>Part 2: Communicate &amp; Define the problem</h3><p>You’re now ready to have a “<strong>Problem Mapping Workshop</strong>”. Invite all the stakeholders you need to get buy-in, as well as any experts who will likely be working on the project. Tell them it should only take 2 hours. Then take them through the timeline and provide extra insights into the motivations and struggles. While you’re presenting they should be writing down ‘<a href="https://dschool.stanford.edu/resources/how-might-we-questions">How Might We</a>’ questions <em>(to save time I’m going to use the abbreviation HMW for How Might We)</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjUcT-wDykFeqX1A2fJ5AA.png" /><figcaption>Slide from my syndicate presentation, Highlighting one of the biggest struggles in the timeline for customers; collecting money from others. I also included some example How Might We questions for each insight to help the group get started.</figcaption></figure><p>Once you’ve finished presenting, tell your group to stick their HMW questions onto the timeline. While they are doing this, group similar questions together. Finally get the group to vote on the HMW questions. Remind them they should be voting based on what area they feel needs to be innovated to solve the job better for your customers.</p><p>You should have something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Li0bP9HDYUuy_oBqrIadTQ.png" /><figcaption>From the insights it was obvious that to do the job better we needed to be make it easier for syndicate organisers to collect money.</figcaption></figure><h3>Part 3: Ideate a solution</h3><p>You’re now ready to work on solutions. Invite everyone to your “<strong>Sketch Workshop</strong>” ideally it’s the same people from the problem mapping workshop. Again this workshop should only take 2 hours. Put your 5 most voted HMW questions into a slide deck. Then add any additional insights to each question to remind everyone what problem they are trying to solve.</p><p>Go through each question and give everyone 8 minutes to sketch a solution. We’re not after masterpieces, It just needs to convey their idea without them needing to present it. They can use words if they want to (but it shouldn&#39;t be a page full of text). After each HMW question briefly share sketch ideas. Timebox this sharing for 5 minutes, this isn’t about selling your idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wudUqiWWtnmTB3G7_Tf8Q.png" /><figcaption>Example sketch of a possible solution for organisers not having to worry about collecting money. The organiser creates a group, invites joiners via a unique link. The joiners can then pay when and how they want to via the link. Oz Lotteries can also send reminders to those who haven’t paid.</figcaption></figure><p>At the end give everyone 20–30 minutes to combine or refine their idea’s into a single solution sketch. Once done, tell them to give their solution a title and stick it to the wall. Again everyone then votes on the solutions and the most voted solutions get discussed.</p><p>To learn more about <a href="https://designsprintkit.withgoogle.com/methods/sketch/">Sketch Workshops go here</a></p><h3>You’re now ready to innovate to solve the job better.</h3><p>To recap you’ve:</p><ol><li>Interviewed 10 customers around a switch event</li><li>Identified patterns in the forces and timeline from those interviews.</li><li>Presented those insights to a group of stakeholders and experts.</li><li>Agreed on the most important problems to solve.</li><li>Ideated solutions for those problems &amp; agreed on the best ideas.</li></ol><p>You’re now ready to <a href="https://designsprintkit.withgoogle.com/methods/prototype/">Prototype</a> and <a href="https://designsprintkit.withgoogle.com/methods/validate/">Test</a> the solutions your group came up with to see if it does indeed solve the job better for your customers.</p><h4>Did this help? Do you have a different approach?</h4><p>Please comment on the parts you found most useful or disagree with. If you have another practical approach for implementing JTBD research please share it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84b92774f42f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-job-to-be-done/what-to-do-with-all-your-jtbd-research-84b92774f42f">What to do with all your JTBD research</a> was originally published in <a href="https://medium.com/the-job-to-be-done">Jobs to be Done</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best books I’ve read]]></title>
            <link>https://medium.com/@greglesueur/the-best-books-ive-read-a8b24e3aa860?source=rss-bd8bbc3397c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8b24e3aa860</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Greg Le Sueur]]></dc:creator>
            <pubDate>Thu, 23 Nov 2017 09:46:47 GMT</pubDate>
            <atom:updated>2017-11-23T09:54:18.852Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a culled list of books I’ve read and learnt alot from. They have all helped me grow as a Digital Product Designer.</p><p>I’d love to hear your recommendations if you feel something else should be on this list that isnt.</p><h3>Behavioural Psychology</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*im_UQcNo5HN8HgCLVRTvuQ.png" /></figure><h4>Thinking Fast &amp; Slow</h4><p>While this book is a little dry it highlights that we are not the logical beings we all like to think we are. Humans make fast emotional and sometime irrational decisions based on various cognitive biases that the book highlights. Once you can recognize those biases, you can design for them.<em> Note: I’d suggest reading the Undoing Project first (Mentioned below) it helps introduce these topics in an entertaining way.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*oUd9qC4UFqaO-y3XmgV75w.png" /></figure><h4>Drive: The surprising truth about what motivates us</h4><p>Recommended to me by Gamification expert <a href="http://www.gamificationgeek.com/">Zac Fitz-Walter</a>. This book highlights that once our basic needs are met we’re not highly motivated by extrinsic rewards. Instead we seek Autonomy, Mastery &amp; Purpose. This book helps you better understand whats important to you &amp; your users. It’s also great if you want to motivate your teammates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*05xgvYMQmZobRuduLrwZWg.png" /></figure><h4>Hooked: How to Build Habit-Forming Products</h4><p>Nir Eyal introduces the “Habit Loop” a 4 step model that encourages people to re-use a product. It starts off with the <strong>trigger</strong> asking for an <strong>action</strong> that when completed gives a <strong>variable reward </strong>and prompts <strong>investment</strong> back into the product so the next time round it’s easier. In particular what I found interesting was that rewards must be earned to be valued.</p><h3>Design &amp; Business</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*OiylvalcE2u1mxAlnKeC0w.png" /></figure><h4>Don’t make me think</h4><p>A practical guide for digital usability. It helped me understand alot when I first got started in UX Design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*Me-z4QqlWVNeZWFLdhtr7A.png" /></figure><h4>Sprint</h4><p>An amazing practical guide for using design thinking to validate new ideas quickly. Using real examples Jake and the Google Ventures crew walk you through step by step how to run a “Design Sprint” from identifying the problem to ideating a solution. Then finally validating that solution with prototyping and testing. All the while using techniques to bring others along the journey with you. One of the most practical books I’ve read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*EIc_9BVSrc8Zp98xDd6DeA.png" /></figure><h4>Competing against Luck</h4><p>The book that introduced me to <a href="http://jobstobedone.org/">Jobe to be done</a>. In a nut shell it explains that customers ‘hire’ different solutions into their lives because of a Job they have. It then goes into detail on why you should be innovating to better solve your customers jobs. It helped change the way I thought about designing features. Highly recommend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*IbgDdaJ6HI08rkeWTWb0EA.png" /></figure><h4><strong>The Personal MBA</strong></h4><p>Designing digital products is as much about UX as it is about business strategy and if you’re going to read one book on business it should be this one. It covers all business fundamentals in a simple and easy to understand way. Even if you have a sound knowledge on business I guarantee you will learn something. It also gives you a better vocabulary to explain business concepts to others.</p><h3>Great Stories</h3><p>Not as practical as the titles above, but I’ve still learn a lot from these stories.</p><h4>The Undoing Project</h4><p>Very entertaining story on how two israeli psychologists re-rote the book on how we make decisions. As mentioned above, a great pre-read for Thinking Fast and Slow.</p><h4>Sapiens &amp; Homo Deus</h4><p><strong>Sapiens</strong> dives into history of humans and helps shed light on why sapiens have been so dominant on earth. For me it also highlighted how silly some of our current traditions are, based on behaviours humans had centuries ago (In particular religion). <strong>Homo Deus </strong>kicks off where sapiens finishes and talks about the possible futures for humanity. In particular it provides some very interesting points of view on AI.</p><h4>Creativity Inc.</h4><p>Entertaining story about the creation of Pixar. Re Enforces the lessons learned in Dan Pink’s <strong>Drive </strong>about how people can create amazing things if you give them purpose and the autonomy to do it their way.</p><h4>Elon Musk, Steve Jobs, Losing my Virginity (Richard Branson)</h4><p>3 entertaining books about 3 very successful entrepreneurs. Each seemed to risk it all because they believed in their vision and each time it paid off.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8b24e3aa860" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>