<?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[Love the Problem - Medium]]></title>
        <description><![CDATA[Thoughts on using Continuous Innovation to build products your customers cannot refuse. By the makers of LEANSTACK and Lean Canvas: https://leanstack.com - Medium]]></description>
        <link>https://medium.com/lean-stack?source=rss----8a472b45761d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Love the Problem - Medium</title>
            <link>https://medium.com/lean-stack?source=rss----8a472b45761d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:23:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/lean-stack" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Moved to Substack]]></title>
            <link>https://medium.com/lean-stack/moved-to-substack-bfe1f65def33?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/bfe1f65def33</guid>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Fri, 11 Nov 2022 16:24:12 GMT</pubDate>
            <atom:updated>2024-03-01T19:39:50.488Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moved to LEANFoundry.com</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUiRQr-Yp9uMdGeqONAVaw.png" /></figure><p>I’ve moved this blog to <a href="https://leanfoundry.com/articles">https://leanfoundry.com/articles</a>.</p><p>I’m still a huge fan of the writing experience at Medium. Not a fan of their business model.</p><p>If you’d like to follow my work, check out:<br><a href="https://leanfoundry.com">https://leanfoundry.com</a></p><p>Thanks for reading!</p><p>Ash</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe1f65def33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/moved-to-substack-bfe1f65def33">Moved to Substack</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Simple Shapes of Customer Stories]]></title>
            <link>https://medium.com/lean-stack/the-simple-shapes-of-customer-stories-4d133b920a7a?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/4d133b920a7a</guid>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[customer-development]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Wed, 17 Aug 2022 17:28:29 GMT</pubDate>
            <atom:updated>2022-08-20T15:57:32.573Z</atom:updated>
            <content:encoded><![CDATA[<p>Inspired by Kurt Vonnegut’s lecture on “the simple shapes of stories,” I’ve previously riffed on <a href="https://blog.leanstack.com/the-simple-shapes-of-startups/">The Simple Shapes of Startups</a>. More recently, however, I discovered that customer stories too have archetypical shapes.</p><p>These archetypical shapes take form when you plot customer happiness over time as customers hire and fire products in the course of getting the different jobs in their lives done.</p><p><em>If you are unfamiliar with the theory of jobs-to-be-done (jtbd) or the specific definition presented below, I’d recommend </em><a href="https://blog.leanstack.com/what-is-a-job-to-be-done-jtbd/"><em>reviewing this post</em></a><em> first.</em></p><blockquote><a href="https://map.leanstack.com/Job-To-Be-Done"><em>A job to be done</em></a><em> is the instantiation of an unmet need or want.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*xLRS3sFA6qKcqJT_.png" /></figure><p>Understanding the basic shapes of customer stories can help you better understand your own customers, uncover new opportunities for innovation (problems worth solving), and build products and features that deliver on these opportunities.</p><h3>1. The Status Quo Story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v2RH35VVJAJ6nkMV.png" /></figure><p>Our customer starts at some basal happiness level until they encounter a <a href="https://map.leanstack.com/JTBD+Trigger">jtbd trigger</a>, for example, hunger pangs. Since jtbd triggers open a gap between the customer’s current state (hungry) and desired state (satiated), they cause a slight dip in happiness level.</p><p>As customers are creatures of habit, they quickly recruit an existing solution (e.g. the refrigerator) and proceed to get the job done.</p><p>Notice that the customer ends at a higher level of happiness after the job is done as jobs are about making progress. But this higher level of happiness isn’t permanent. In short order, the customer returns back to their basal happiness level… until the next triggering event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oh1MsBCT3DPsueBO.png" /></figure><p>This story type is called the status quo story because this story plays out much the same way until the customer encounters the first plot twist.</p><h3>Meet the Switching Trigger (first plot twist)</h3><p>A <a href="https://map.leanstack.com/Switching+Trigger">switching trigger</a> is an additional event that occurs either before or after the jtbd-trigger causing the old way to “break”. This “break” could be literal (e.g. iPhone breaks) or just in the mind of the customer (e.g. Apple announces new iPhone). It could be aspirational (e.g. new technology will deliver better outcomes) or consequential (e.g. regulatory will change how things need to be done). But for a switching trigger to cause a customer to take further action, it must cause their happiness level to cross over from satisfaction to dissatisfaction.</p><p>This is a pivotal point in the story.</p><blockquote><em>Switching trigger = JTBD Trigger + Expectation Violation</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KkZfrDtFj4Y0cfCi.png" /></figure><p>Now that the customer is out of a working solution, they need to find a new way to get the job done. This begins their search for a new solution, which wavers from passive to active looking until they hire a new way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0fp5vZmrUW4dsiar.png" /></figure><p>Hiring a new way is an accomplishment of its own — one that is often accompanied with the hope of having acquired something better.</p><p>This causes a rise in happiness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JNAwkKntKv5rKDc4.png" /></figure><p>This happiness, too, is fleeting as the customer realizes that they’ve gone from being an expert in the old way to a beginner in a new way.</p><p>This is the <em>dip of onboarding</em>.</p><p>They’ll have to invest additional effort in learning how to use the new way. This is also the point where we encounter another fork in the road that shapes the story down two different paths.</p><h3>2. Switching Story A (New Way Wins)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dhg2orUaEGqDQHHh.png" /></figure><p>In order to keep the customer moving forward, the new way must overcome its own onboarding friction while keeping the customer moving towards job done. The best way to accomplish this is to break the journey into one or more intermediate aha moments (activation). These moments reaffirm faith in the new way and raise the customer’s happiness (and motivation).</p><p>Getting the customer to <strong>job done</strong> better than the old way did, creates off-scale happiness — past satisfaction and into delight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sG76F97P5rvf1zx9.png" /></figure><p>This is what all new products should strive to achieve, as getting here creates a switching moment. This is the second pivotal moment when the customer decides to make the switch from the old way to the new way permanent.</p><p>Unfortunately, delight also follows a natural decay curve. Every new car smell eventually wears off… and the customer subsequently moves back to their original basal happiness level. But the players have changed. The new way has taken the place of the old way shown here as the new status quo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8DlZA6sCR3rOUeVL.png" /></figure><p>From here on out, the status quo story plays out until a new switching trigger plot twist comes along.</p><h3>3. Switching Story B (Old Way Wins)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X3Tb33eGhxwLB1qI.png" /></figure><p>The story above could take a different turn after the customer hires the new way. It could take them from being already dissatisfied to off-scale unhappiness or frustration if the new way’s onboarding process proves too complex or difficult to implement.</p><p>At this point, the customer hits bottom and, this time decides to fire the new way and revert back to their old way. This reversion is usually quick since the old way is already familiar to them (status quo).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*adCJJtsxkjrXX10y.png" /></figure><p>Notice that this time the happiness level of getting the job done with the old way is lower than before because the customer is still worked up about all the extra run-around they just did.</p><p>But this lower level of happiness is also short-lived, as they gradually make their way back up to their original basal happiness level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lccQ2hgn2E9uAj_O.png" /></figure><p>The old status quo is reinstated.</p><h3>The 3 Archetypical Story Shapes</h3><p>I show all three archetypical story shapes below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m57Wak2X4wVylYc6.png" /></figure><p>Remember that these are archetypical shapes, and there are a few additional variations — like a customer failing to find a new way and seemingly giving up (non-consumption story). It is also possible for these stories to span multiple user roles (e.g., complex B2B sales) and/or multiple products (e.g., SaaS trials).</p><h3>What Do These Stories Tell Us?</h3><p>They help surface all kinds of insights such as:</p><ul><li>What causes customers to buy (triggers)</li><li>How to identify early adopters (one who acts on triggers)</li><li>What do they buy (the old way)</li><li>What’s broken with the old way (opportunities for innovation)</li><li>What trade-offs do they make (perfect solutions are a myth)</li><li>The best time to approach customers with a new way (first crossing point)</li><li>The worst time to approach customers with a new way (second crossing point)</li><li>What solution to build to cause a hiring moment (new way UVP)</li><li>How to cause a switch (aha-moments + desired outcomes)</li><li>Or, if you already have customers, what solution/features to build to prevent a switch away (old way UVP)</li><li>and more…</li></ul><h3>What is the Best Way to Uncover These Stories?</h3><p>The best way to uncover these customer stories is not through surveys, focus groups, problem validation interviews (customer, do you have this problem?), or problem ranking approaches (on a scale of 1 to 5, how bad is this problem?).</p><p>The best way to uncover these customer stories is through <strong>carefully unscripted</strong> (or meta-scripted) problem discovery interviews. All customer stories have drama and the job of the interviewer is to unpack this drama.</p><p>This is a skill that can be learned. There is a <a href="https://runlean.ly/3e">new book (Running Lean — updated edition)</a>, a <a href="https://leanstack.com/training/45-day-pd">workshop (45-Day Problem Discovery)</a>, and now a <a href="https://leanstack.com/customer-forces">new tool (Customer Forces)</a> that can help you automatically visualize your customer stories, prioritize problems worth solving, and design solutions for switch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0CRx_oDssZeR0exOuF3MSg.png" /><figcaption>Customer Forces — A Problem Discovery Tool</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d133b920a7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/the-simple-shapes-of-customer-stories-4d133b920a7a">The Simple Shapes of Customer Stories</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Lean — 10th Anniversary Edition]]></title>
            <link>https://medium.com/lean-stack/running-lean-10th-anniversary-edition-5ea33119120?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/5ea33119120</guid>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Thu, 03 Feb 2022 23:47:58 GMT</pubDate>
            <atom:updated>2022-02-03T23:47:25.352Z</atom:updated>
            <content:encoded><![CDATA[<h3>Running Lean — 10th Anniversary Edition</h3><p>Time flies. It’s been 10 years since the last edition of Running Lean. Since then, I’ve spent thousands of hours training and coaching hundreds of product teams, coaches, and stakeholders all over the world. My goal was to further test and refine the systematic step-by-step process first laid out in the book — moving beyond my own products and across a diverse set of products and industries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/0*TZn6oZJS4AnxeW2Y.png" /></figure><p>While the book answered some questions, I was faced with a barrage of challenging follow-on questions like:</p><ul><li>How can I get my investors (and stakeholders) to buy into my idea with just a Lean Canvas?</li><li>How do I run problem interviews around desire-driven products like video games or fashion?</li><li>How do I apply Running Lean to non-tech products and services?</li></ul><p>The new edition addresses all these questions and more.</p><p>Along the way, I developed additional business modeling tools, newer and better validation strategies, and more practical techniques synthesizing concepts from a wide range of methodologies and frameworks, including Lean Startup, Design Thinking, Business Model Design, jobs-to-be-done, Systems Thinking, Behavior Design, and many more.</p><p>I found that to achieve breakthrough innovation under conditions of extreme uncertainty, one shouldn’t be limiting themself to just one framework, but rather using the best from all of them. While these frameworks overlap, each has a specific superpower that makes it stand out above the others. I’ve curated these superpowers into a new framework of frameworks (the Continuous Innovation Framework) that is laid out in this book.</p><p>In addition to the Lean Canvas, the book also covers:</p><ul><li>the traction roadmap for better idea sizing,</li><li>the customer factory metrics model for better risk prioritization, and</li><li>the customer forces behavior model for better understanding your customers.</li></ul><p>In this 10-year anniversary edition of Running Lean, you’ll find:</p><ul><li>More effective stress testing techniques for shaping your early business model,</li><li>A completely revised problem discovery interview script for uncovering real customer problems worth solving,</li><li>A battle-tested process for building products you know customers want and don’t just hope they want.</li></ul><p>If you’ve read this far, you’re probably thinking that this edition isn’t just a minor lift of the last edition. And, you’re right. The third edition packs in 120 more pages and aside from a few paragraphs, this book is a complete rewrite.</p><p>Here’s what one of our long time practitioners and coach had to say after an early-access review:</p><blockquote><em>To me, this could easily be a new book, rather than a new edition. At the very least, it’s so different that just another edition doesn’t do it justice. I was planning on a quick run-through but it really needs a decent amount of examination.<br>- Ross McKay — Professional Mentor</em></blockquote><p>And Ross would know as he’s made everyone read the previous edition :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*CnmqjiPpGyicRb_P.jpeg" /></figure><h3>My Personal Why</h3><p>When people tell me they wish they had read Running Lean sooner, I reply: “Me too.” I’ve made every mistake in the book and I used the last edition to clarify my own thinking. This edition is about refining that thinking.</p><blockquote><em>I wrote the last edition of Running Lean for myself.<br>The third edition is for you — the entrepreneur.</em></blockquote><p>My mission with <em>Running Lean</em> (and my company: LEANSTACK) is democratizing how entrepreneurship is taught and practiced. In short, I’d like to help the next generation of entrepreneurs to, at least, avoid making the same mistakes.</p><p><strong>Life’s too short to build something nobody wants.</strong></p><p>This is where you come in…</p><h3>I Need Your Help</h3><p>If you find this book and mission worth supporting, please take a moment to <a href="https://runlean.ly/3e">preorder the book today</a>.</p><p><em>Running Lean 3e</em> is available for preorder from many retailers, including <a href="https://runlean.ly/3e">Amazon.com</a>. The book currently shows the list price ($39.99) but you won’t be charged until the book comes out on <strong>March 7th, 2022, </strong>by when Amazon’s discounting algorithm should drop the price to <strong>under $25</strong>. So think of the preorder more like a reservation.</p><h3>Why Preorder?</h3><p>The reason I’m asking is that preorders drive how much support retailers, influencers, and new readers give a book — especially a seemingly old book. This in turn helps drive the reach and impact of a book. Yes, it was a lot easier and tempting to wipe the slate clean and write a shiny new book, but I chose the harder (and still believe) right path of updating the book.</p><p>I strongly believe this book will be well worth the read for both new and old readers alike.</p><p>As an added bonus, I’m including replays of my <a href="https://leanstack.com/training/30-day-bmd">30-Day Business Model Design workshop</a> ($749–999 value) if you <strong>preorder the book before 11:59 PM CST on March 6, 2022</strong>.</p><h3>How to claim the 30-Day BMD workshop bonus</h3><ol><li>Preorder the book (<a href="https://runlean.ly/3e">Amazon</a>, <a href="https://www.indiebound.org/book/9781098108779">Indiebound</a>)</li><li>Forward your receipt to <a href="mailto:preorder@leanstack.com">preorder@leanstack.com</a></li><li>Check your inbox for a link to the workshop replays</li></ol><p>This book is the product of 10 years of rigorous testing, hundreds of product case studies, and thousands of iterations. I’m excited to share it with you. And hope you share it with others too:</p><h3><strong>http://runlean.ly/3e</strong></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ea33119120" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/running-lean-10th-anniversary-edition-5ea33119120">Running Lean — 10th Anniversary Edition</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Customer Factory Manifesto]]></title>
            <link>https://medium.com/lean-stack/the-customer-factory-manifesto-d9a374bae3fb?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/d9a374bae3fb</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 01:03:06 GMT</pubDate>
            <atom:updated>2020-12-08T19:05:53.539Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Successful businesses are more alike than unalike. They share a common universal goal and employ a systematic approach to building a repeatable and scalable business model.</em></p><p><em>This manifesto shows you how.</em></p><h3>1. All Businesses Share a Common Universal Goal</h3><p>All businesses, irrespective of business model type (b2b, b2c, digital, hardware, services, etc.), share a common universal goal:</p><p><strong>To make happy customers</strong>.</p><h3>2. Making Happy Customers vs. Making Customers Happy</h3><p>Making happy customers is NOT the same thing as making customers happy.</p><p>Making customers happy is easy. Just give them lots of stuff for free. But that doesn’t lead to a working business model.</p><p>Making happy customers, on the other hand, is not just about making customers feel good. It’s about making customers achieve results (desired outcomes).</p><p><strong>Happy customers get you paid.</strong></p><p>The work of making happy customers happens in a customer factory.</p><p>Every business has one.</p><h3>3. Throughput (aka Traction) is The Goal</h3><p>Throughput in a customer factory is the rate at which you create happy customers. This is synonymous with traction.</p><p><strong>Traction is the only thing that matters.</strong></p><h3>4. The Customer Factory Blueprint</h3><p>At a basic level, a customer factory takes in unaware visitors as input (raw material) and turns them into happy customers (finished product).</p><p>This process can be further broken down into 5 macro steps that can be found in all businesses: <strong>acquisition, activation, retention, referral, and revenue</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPvD5wkungW-9hrCVckaBA.png" /><figcaption>The Customer Factory Blueprint</figcaption></figure><p>The customer factory represents everything inside your business: Your marketing, sales, customer service, and product.</p><h3>5. The Activation Step is Where You Make Happy Customers</h3><p>The activation step is where happy customers are made. While all the steps are needed to make your business model work, the most important step is the activation step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xc4Zn-2IYdbPS74JC6kySA.png" /><figcaption>Activation is where you make happy customers</figcaption></figure><p>This is where value is created for your customers. When you create value for your customers, they reciprocate — allowing you to capture some of this value back in the form of monetizable value.</p><p>Notice how the activation step has the most number of lines leading out of it. This is what makes <strong>activation a causal step</strong>.</p><p>Making customers happy at this step causes customers to<br>- buy from you,<br>- keep coming back, and <br>- refer others.</p><p>The inverse is also true.</p><h3>6. The Customer Factory Isn’t Just A Cute Metaphor</h3><p>The manufacturing reference in the customer factory is intentional. Metaphors are quite powerful when they enable us to transplant and adapt ideas from one domain to another.</p><p>We have been running real factories for a long time and have learned how to model and optimize them as systems.</p><p><strong>Your business model is also a system.</strong></p><h3>7. Focus on Systems vs. Goals</h3><p>A lot of us are taught to set goals. While there’s a place for goals, simply setting a goal is never enough. It’s way more actionable to focus on building systems that move you towards a goal.</p><p><strong>Goals focus on outputs. <br>Systems focus on inputs.</strong></p><p>Example: Goal: Losing 10 lbs.<br>System: Learning to eat right.</p><p>The problem with goals is that they don’t tell you how to achieve it or what to do when you achieve it. In the example above, a number of people can brute-force losing 10 lbs once through sheer willpower. But once that wears off, the weight comes back on.</p><p>Systems on the other hand, like learning to eat right, help you focus on key activities or routines that move you towards the goal. Once these key activities turn into habits, you not only achieve your goal, but shoot past it.</p><p>The best way then is to use goals for ballparking your desired outcome, and systems for formulating key steps to achieving the goal.</p><p>You still need to size up your goal because the effort that goes into losing 10 lbs is quite different from losing 100 lbs. But once a ballpark goal is set, like losing 10 lbs, does it really matter if you lose 9 lbs or 11 lbs ?</p><p>Focus your energy instead on building systems for helping you achieve the goal.</p><p><strong>Systematizing the 5 macro steps in the customer factory blueprint is how you achieve your goals in a business model (aka growth).</strong></p><h3>8. Establishing Repeatability is a Prerequisite For Growth</h3><p>A key attribute of systems is that they are repeatable. When a factory manager wires up his machines on the factory floor, he first establishes a predictable throughput baseline (give or take a small expected tolerance for variability) before undertaking any optimization steps.</p><p>Your customer factory is no different.</p><p>You can’t scale a business model that isn’t first repeatable.</p><p>Getting to your first 10 customers, while an achievement, isn’t repeatable if you don’t know where your next 10 customers will come from.</p><p><strong>Random isn’t repeatable, which means it isn’t scalable.</strong></p><p>When is the right time to start prioritizing for repeatability? <br>Right after your first sale.</p><p>If you don’t focus on establishing repeatable sales quick enough, you start getting pulled in many different directions, can easily lose focus, and hit a brick wall.</p><h3>9. Grow Your Customer Factory Systematically in Stages</h3><p>A lot of entrepreneurs try to prematurely scale their business models by going fast on everything.</p><p>They often end up wasting needless time, money, and effort on the wrong things at the wrong time.</p><p><strong>Going fast on everything is a recipe for getting lost faster.</strong></p><p>The counter-intuitive mindset here isn’t speeding up to rush scalability, but rather slowing down to focus on building a repeatable customer factory in stages.</p><p>Every product goes through 3 stages:</p><ol><li>Problem/Solution fit,</li><li>Product/Market fit, and</li><li>Scale.</li></ol><p>Each stage is essentially a customer factory.</p><p>The difference across the stages is the amount of throughput (i.e. number of happy customers) that you repeatably generate.</p><p>In other words, each stage is essentially a smaller-scale version of the next stage.</p><p><strong>Optimizing your customer factory in stages helps you focus on the right actions at the right time.</strong></p><h3>10. Systematic Growth Comes From Focusing on Constraints</h3><p>The steps in the customer factory are like links in a chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A9RIHwObY-k2GujXfifINg.png" /><figcaption>Focus on your constraints.</figcaption></figure><p>At any given point in time, there is always a single weakest link or constraint. Growth comes from correctly identifying, prioritizing, and breaking this constraint.</p><p><strong>80% of your entire team’s effort should be focused on your weakest link and nothing else.</strong></p><p>Once a constraint is broken, search for the next constraint, and repeat the process.</p><p>How do you know when a constraint is broken? When your customer factory throughput goes up as a result of something you just did.</p><p>Yes, this is the <strong>Theory of Constraints</strong> applied to the Customer Factory.</p><h3>11. The Customer Factory is non-linear</h3><p>It’s important to always keep in mind that systems (like a customer factory) are made up of a series of interconnected steps where the whole is often not equal to the sum of its parts.</p><p>Sometimes 1 + 1 + 1 can equal 5. This is when every step in your customer factory is aligned for customer value creation (making happy customers) — creating a compounding effect.</p><p>Other times, 1 + 1 + 1 can equal -2. This is when you attempt to brute-force or game a step at the expense of making happy customers.</p><p>Examples:</p><ul><li>Using sleazy or aggressive sales tactics to close,</li><li>driving low quality leads into your customer factory.</li></ul><p><strong>These short term tactics may work to locally optimize a step, but at the expense of your overall throughput (and operating costs).</strong></p><h3>12. Focus on the bigger context</h3><p>Features, benefits, costs, and revenue live in the product (or solution) context.</p><p>Your customer’s desired outcomes live in the bigger context.</p><p><strong>Your customers don’t care about your solution but about achieving their desired outcomes.</strong></p><p>If you continuously focus your efforts on removing the obstacles standing in the way of your customer’s desired outcomes, you systematically build a repeatable and scalable customer factory.</p><p>You win.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9a374bae3fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/the-customer-factory-manifesto-d9a374bae3fb">The Customer Factory Manifesto</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The True Value of Your Time]]></title>
            <link>https://medium.com/lean-stack/the-true-value-of-your-time-194862bd725?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/194862bd725</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Tue, 11 Feb 2020 18:08:38 GMT</pubDate>
            <atom:updated>2020-02-12T16:23:50.526Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Time is our scarcest resource. Other resources like money and people can fluctuate up and down, but time only moves in one direction.</em></p><p>When I share this quote with others, they appear to get it — but then their actions prove otherwise. Most people still value money more than time and make decisions based on the present value of money vs. the future value of their money investment (ROI).</p><p>This is, not limited to, but quite prevalent with early-stage entrepreneurs who mistakenly equate bootstrapping to being cheap. And pride themselves in spending nothing, but sweat equity on everything. They forgo buying books, paying for training, or hiring experts.</p><p>The rationale: I’m pre-revenue and so cash poor and time rich. I’ll do it myself.</p><p>This is a huge fallacy.</p><p>First, bootstrapping has nothing to do with being cheap. Bootstrapping is about being efficient with your resources. A bootstrapper’s primary objective is getting to customer revenues as quickly as possible. Speed of learning, not frugality, is their true unfair advantage. In other words, if the ROI is baked in, trade money for speed.</p><p>Next, sweat equity is the most expensive type of equity and should be reserved for your unique contribution — something that cannot be easily replicated by others. This is your super-power or personal unique value proposition (UVP). Everything else can and should be delegated — provided the ROI is there.</p><p>So how do you determine ROI? Let’s walk through the steps.</p><h4>How to value your time</h4><p>First, you need to value your time correctly. Sweat equity isn’t $0. Far from it.</p><p>One way to value sweat equity is by using the opportunity cost of working on your startup at your going hourly rate. Let’s assume you could make $75/hour ($150K/yr) working a job. When you instead choose to spend that time on your startup project, you should value your time at that going hourly rate, right? That’s a start, but it’s still not the right way to value your time. The startup math needs to also adjust for risk and payback time.</p><p>The opportunity cost math assumes a high certainty of getting paid. When that isn’t the case, such as when working on a startup, you need to adjust for that. Using the commonly used 10% success rate of startups, your sweat equity value goes from $75/hr to $75/hr ÷ 0.10 = $750/hr.</p><p>Then, there’s the payback time. In a typical, job you get paid bi-weekly or monthly. In your startup, you might forgo a full salary for a year or two or longer…Adjusting for that raises your sweat equity closer to $1,000/hr and probably even higher.</p><p><strong>When working on a startup, your time is worth $1,000/hr.</strong></p><p>This means</p><ul><li>You are investor #1 in your business.</li><li>You can’t just look for a 1x or 2x salary return. You have to think 10x.</li><li>You can only sell so many hours in a day and hourly rates also have a ceiling. What can you sell while you sleep?</li></ul><h4>How to determine ROI</h4><p>Determining your ROI now becomes straightforward: If you can hire someone or something to get a job done for less than $1,000/hr, you should.</p><p>Well, not quite. You still have the real problem of cash availability. Unless you’ve got a personal war chest of gold stashed somewhere, you can’t simply pay your way for all the jobs you need done.</p><p>This is where the real essence of bootstrapping shines through: Right action, right time.</p><p><em>At any given point in time, there are only a few key actions that matter. You need to put all your energy towards those actions and ignore the rest.</em></p><p>Within these key actions, you’ll often find a mix of core jobs and non-core jobs.</p><p>Non-core jobs, like accounting, appointment scheduling can and should be delegated to less expensive services or tools. There is zero ROI in you doing these yourself.</p><p>Within core jobs, you’ll find jobs you’re good at, i.e. they fall within your personal UVP, and jobs you’re not yet good at. Trying to learn these skills on your own seems smart, but it isn’t. A better approach is hiring a learning accelerant, like a book, or a workshop, or an expert — often in that order.</p><p><em>Remember: Speed of learning is typically your only unfair advantage in the beginning.</em></p><p>Buying books is a no-brainer. For $20/book, if you get to apply even one new idea in your startup, the return could be 10–1000X. The problem, of course, is that millions of books get published every year. The real cost isn’t the cost of the book, but your time.</p><p>You need a deliberate strategy.</p><ol><li>Start with what you need to learn that aligns with your right action/right time goal.</li><li>If you’re new to a skill, prefer timeless classics vs. books that were just published. Books that have stood the test of time have been vetted by others and if they are still popular/recommended, it’s because they teach evergreen principles vs. short-term tactics. Start there. Tactics come later.</li><li>Don’t wait to finish a book to start applying it. When I buy a book, I first scan the table of contents and only commit to reading the Intro chapter. This is usually where the author lays out their thesis. If I don’t find anything new or actionable there, I flip through the rest of the book looking for something that grabs my attention. If still a no-go, I put the book down. My time’s too valuable to read a bad book.</li></ol><p>Hiring training or experts typically require a bigger investment, both in money and time, than a book. So it’s prudent to test the ROI of these learning accelerants through smaller sampling first. Before attending a workshop or hiring an expert, sample their work first. They may have books, articles, videos, etc. online. Again, if this is something you need to learn now, sample what’s available, and attempt to apply what you can before hiring them. This will make your face time with them ten times more productive.</p><p><em>Sidenote: I’m always amazed to see people who attend my workshops without first reading my books.</em></p><h4>Don’t forget to value “free time”</h4><p>The ROI calculation breaks down for certain intangibles that are way more valuable than money. We have solely been focusing on how to value time for work. But there are 3 more buckets that are just as critical to living a meaningful life:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*Y7zrDOuiw3H4_TQqB9_Gbg.png" /></figure><p><strong>Health<br></strong>If you work harder than is healthy, your health eventually suffers and you may not be able to reap your eventual rewards at your fullest.</p><p><strong>Relationships<br></strong>If you work at the expense of your relationships, you may not have anyone with whom to enjoy your eventual rewards.</p><p><strong>Wealth</strong><br>You are investor #1 in your idea and need to be even more ruthless with its viability than your investors. They invest money. You invest time. Time is more valuable than money.</p><p>But despite your best efforts, startups are inherently uncertain and you may still not have an eventual payoff. You need a plan B.</p><p>Consider this, putting aside just $300/month in the S&amp;P 500 index fund would grow to ~$1M in 40 years. The ROI of automating something like this in your twenties (or thirties or forties) is crazy.</p><p><strong>Work</strong><br>And finally, doing good/original work comes from creativity. And recent studies show that creativity happens in the empty spaces between stretches of hard, focused work. In other words, you need to bake in free time for “doing nothing” in order to create something meaningful.</p><p>===</p><p>The way I balance these quadrants is with a calendar. Like most entrepreneurs, I am naturally driven to allocate most of my time to work. So I first block off non-negotiable time on my calendar for the other 3 quadrants. Then prioritize my remaining time for work activities.</p><p>===<br>We are taught to value money over time. Hopefully, this article has at least made you question how you spend your time.</p><p><strong>What separates us is what we do with the 24 hours we are given every day. Don’t waste it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=194862bd725" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/the-true-value-of-your-time-194862bd725">The True Value of Your Time</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In Search of Unicorns]]></title>
            <link>https://medium.com/lean-stack/in-search-of-unicorns-623419208204?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/623419208204</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 18:42:04 GMT</pubDate>
            <atom:updated>2020-06-12T14:48:37.796Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The traditional startup funnel is broken.</em></p><p>According to the 2019 Global Entrepreneur Monitor (GEM) report, more than 100 million startups are launched every year all over the world. That equates to about 3 startups per second.</p><p>These entrepreneurs come from all walks of life and transcend age, gender, and geography. The stereotype of the entrepreneur is no longer two guys in a garage in Silicon Valley.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uTXtI7GJg8B4Fl1C.png" /></figure><p><strong>We are living through a global entrepreneurial renaissance and this represents an incredible opportunity.</strong></p><p>To meet this surge in demand, there has been a corresponding explosion in the number of accelerators, incubators, and university programs that started in just the last ten years. Ten years ago, there were <strong>less than 50 startup accelerators</strong>. Today, there are <strong>over 5,000</strong>.</p><p><strong>But there is a dark cloud in all of this.</strong></p><p>Even though we are creating more startups than ever before, the overall startup success rate has decreased — not increased.</p><p>This is because while the seed or early stage of a startup is the easiest to get going, it’s also the most uncertain and riskiest.</p><p><strong>The challenge for accelerators today isn’t just attracting investment-ready startups, but rather starting even earlier, and shaping founders into world-class startups.</strong></p><p>The massive explosion in startup activity <strong>breaks the traditional startup funnel </strong>and requires a rethinking of the traditional accelerator model.</p><h3>What’s wrong with the 12-week accelerator model?</h3><p>The typical accelerator runs a batch of 10 teams through a 3–4-month cohort leading up to the grand Demo Day where startups get to pitch to investors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7x0A81AMsUW2NJVi.png" /></figure><p>It has become increasingly difficult to get teams to investment-readiness in 12 weeks.</p><p>Here’s why:</p><h3>Problem 1: There are a lot more startups than before</h3><p>As the top of the startup funnel has widened, it’s easy to get lots of applications. What’s difficult is finding and selecting the right teams for the very limited spots.</p><p><em>A typical accelerator starts its application process three months prior to launching a new batch and processes over 600 applications during that time.</em></p><p>The lack of clear metrics-driven heuristics for ranking applications leads to a lot of time spent reviewing applications and injects subjectivity into the selection process. Because a follow-up with every team is not possible, lots of good teams with bad applications get missed in the process.</p><p><strong>The stakes for picking the wrong team are high as it takes a direct hit on the overall cohort performance.</strong></p><h3>Problem 2: Spending more time educating versus accelerating startups</h3><p>Once a cohort is underway, that’s when the hard work for getting startups pitch-ready begins. Investors today only care about one thing: Traction. The problem is that entrepreneurs care about something else: Product.</p><p>Unless you know how to screen for this, it’s not atypical to find your startups with a minimum viable product and maybe some paying customers… But they don’t know where their next 10 customers will come from and they struggle to effectively communicate their traction story.</p><p>So you spend time filling that gap with education. You line up a curriculum on business modeling, lean startup, metrics, and pitching skills. Add to that UX, sales, marketing, growth hacking… and whatever else you can cram in.</p><p>It’s easy to overwhelm startups as they simultaneously try to juggle their time between learning, pitching, and building their business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RBK5NqrbXA74nzR5.png" /></figure><p><strong>12 weeks is NOT enough time for education AND acceleration.</strong></p><h3>Problem 3: Nurturing latent entrepreneurs</h3><p>To overcome the challenges above, many early-stage accelerators simply try to only accept ideas with the most traction. This naturally leads to better results.</p><p><em>When you’re working with great ingredients, even a mediocre cook can achieve good results.</em></p><p>This, however, is more easily said than done — unless you’re a top 5 accelerator. Power laws always kick-in. Further, once a startup has sufficient traction, they usually don’t need an accelerator and can go directly to investors.</p><p>The art is <em>catching startups early enough in their lifecycle</em>.</p><p><strong>The ideal time to do this is pre-traction — before they even apply to a single accelerator.</strong></p><p>That’s exactly what Y-Combinator does with Startup School and Hacker News — and how they establish themselves as the most desirable alternative and make their competition irrelevant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TyiUxSBmkA1IAuKJ.png" /></figure><p>Because 12 weeks is too little time for taking startups from idea to investment, many accelerators have introduced a front-end pre-accelerator or incubator program.</p><p>But these pose challenges of their own…</p><h3>Traditional pre-accelerators and incubators aren’t the answer either.</h3><p>A traditional pre-accelerator delivers an education-based curriculum over a longer 6–9 month period with the goal of turning early stage startups (typically with just an idea) into venture back-able businesses ready for acceleration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sy1hdHI_oP7dMSZN.png" /></figure><p>While sound in principle, the challenges facing such programs are cost, effectiveness, and scalability.</p><p><strong>Simply put, traditional pre-accelerators/incubators break the business model.</strong></p><h3>Problem 1: Operational costs go up</h3><p>This one should be obvious. As you delay the window to investment, <strong>the costs of running a co-located pre-accelerator program go way up</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dswBnjtJdyYxpQy8.png" /></figure><h3>Problem 2: Dealing with the even messier ideation stage</h3><p>To keep costs in check, many of these programs offer a one-size-fits-all curriculum of foundational educational content sprinkled with volunteer-driven mentorship.</p><p>But the <strong>ideation stage is messy</strong>.</p><p>Ideation represents the honeymoon period of a startup when anything is possible. It’s also the stage riddled with the most uncertainty — we don’t know what we don’t know.</p><p>Speed-advising startups teams during this period through volunteer mentorship typically does more harm than good. It creates the <a href="https://blog.leanstack.com/adviser-whiplash-f415207e0932"><strong>adviser whiplash problem</strong></a>. Ask ten seasoned entrepreneurs for advice, and you’ll get ten different prescriptions. Which one does the startup follow?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LJc8KlpJh6hyicOy.png" /></figure><p><strong>High uncertainty + Conflicting/prescriptive advice = A recipe for driving startups around in circles.</strong></p><h3>Problem 3: Hard to scale</h3><p>In order to overcome the adviser whiplash problem, you need to invest in coaches that can deliver a personalized curriculum — not advisers and not a one-size-fits-all curriculum.</p><p>Advisers focus on providing the right prescriptive solutions. While coaches focus on asking the right questions. Coaches help transform founders into entrepreneurs versus simply trying to brute-force their ideas to success.</p><p><strong>The true product of a pre-accelerator isn’t pushing an idea forward but pushing a founder forward.</strong></p><p>This, however, is hard to scale without a consistent coaching system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I4ySJkFK2K1P_VUu.png" /></figure><p>As might be clear already, there is a funnel in play here. In order to create 10 accelerator-ready teams, you have to start with a much great pool of ideation teams.</p><p>To make this model work, you need to reimagine a new startup funnel that can address these three core challenges:</p><p><strong>1. Finding the best startups pre-traction in a noisy world.</strong></p><p><strong>2. Measuring investment readiness pre-traction.</strong></p><p><strong>3. Scaling coaches/mentors vs. advisors.</strong></p><p>Doing all this in 3–6 months vs. the traditional 9–12 months.</p><h3>Is this possible?</h3><p>The answer is yes. We, at LEANSTACK, have cut our teeth in the messy early stages over the last several years, working alongside entrepreneurs and accelerators, in search of a repeatable and scalable solution to the new startup funnel.</p><p>The answer we found is striking the right balance between just-in-time founder education, a high-leverage coaching system, and consistent progress-reporting metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-8lhd3Mnt26jcjDhY2i2dg.png" /></figure><p>If you’re running an accelerator (or university program) and want to learn more, check out our latest <a href="https://leanstack.com/accelerators">LEANSTACK for Accelerators</a> platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=623419208204" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/in-search-of-unicorns-623419208204">In Search of Unicorns</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Start With Mindset]]></title>
            <link>https://medium.com/lean-stack/start-with-mindset-d52ffd573f0c?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/d52ffd573f0c</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Thu, 12 Sep 2019 14:36:38 GMT</pubDate>
            <atom:updated>2020-06-12T14:51:02.314Z</atom:updated>
            <content:encoded><![CDATA[<p>Time flies. We’re already at the 10 year anniversary of the Lean Startup. Yes, it was a little over 10 years ago that Eric Ries started sharing a series of blog posts and giving talks on a new way of building products — ideas that went on to spark the global Lean Startup movement.</p><p>By now, “almost everybody building products” has at least heard the term and has been exposed to the big ideas. Yet, when we look around we don’t find the corresponding adoption across teams. And what we do find usually isn’t a rigorous enough implementation… but rather a cherry-picking of tactics and tools — often part of a mandated checklist imposed upon teams.</p><p>I’m always happy, for instance, to see Lean Canvas posters in conference rooms. That happiness, however, is short-lived when upon closer inspection, I find them blank, not up to date, or a list of problems invented to justify the solution the team is already committed to building.</p><p>It’s like going from WAgile to WatLean.</p><blockquote><strong><em>Using a Lean Canvas does not a Lean Startup make.<br></em></strong>(Feel free to replace Lean Canvas with your favorite tool or tactic — mvp, experiment, a/b test, etc.)</blockquote><h3>Has this all just been a huge waste of time?</h3><p>I have spent the last several years focused on this question.</p><p>I’ve watched teams come to my workshops and leave with a full understanding of the framework. Yet, when I follow up with them weeks later, it’s back to business as usual. There is always something else that needs to be built first — that mythical killer feature always lurking.</p><p>That’s when it dawned on me: <br><strong>The challenge to adoption isn’t about just the merit of the framework or motivation of the teams, but overcoming old habits and new anxieties.</strong></p><p>Adopting anything new takes effort.</p><p>It requires us to go from being experts in the old way (the familiar) to becoming beginners in the new way (the uncertain). This is uncomfortable — especially when we are met with negative versus positive reinforcement like a failed experiment (which is almost a certainty with initial experiments), or probing questions we can’t answer yet from our stakeholders and team members (all processes are easy until you add people).</p><p>What happens next is quite predictable — <strong>we revert back to the old way</strong>.</p><p>This is just the nature of <strong>behavior change</strong>.</p><p>The good news is that we now understand the science of behavior change a lot better thanks to the work of people like Daniel Kahneman, Amos Tversky, BJ Fogg, Dan Ariely, Charles Duhigg, Nir Eyal, James Clear and more.</p><p>We encounter behavior change challenges all the time.</p><p>We, for instance, know certain activities are good for us like eating healthy, exercising regularly, and saving money. Yet, we struggle to implement them into our regular routines.</p><p>Adopting a fundamentally new product development process is no different.</p><p>Once I viewed process adoption this way, it completely changed my approach. I shifted my attention from lecturing at teams to studying causes for their anxieties and habits and looked towards devising new ways of overcoming them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y-jVZIyBbDnTnS80rQW85Q.png" /><figcaption>The Customer Forces Canvas applied to Continous Innovation adoption</figcaption></figure><p>In the picture above, we don’t need more PUSH or PULL, but need to devise ways to reduce INERTIA and FRICTION.</p><h3>A bootcamp was born</h3><p>That’s when I had the idea of running an immersive 10-week bootcamp. I would recruit the most motivated early adopter practitioners and lead them through a high-touch coaching program. My logic was that if I couldn’t get them to apply this framework successfully, there’s no way it could work with more mainstream innovators.</p><p>I launched the first bootcamp in September 2012 with just a napkin sketch of a curriculum. Even though everyone didn’t make it to the desired outcome (problem/solution fit, in this case), the transformation created was obvious.</p><p>So I doubled down.</p><p>I have since then run dozens of bootcamps over the last seven years with hundreds of startup and corporate teams spanning the globe — all delivered virtually from Austin, TX where I live.</p><p>Each bootcamp built on the previous one and underwent many iterations with lots of experimentation. Along the way, I got to see what worked and what didn’t, patterns emerged, more tools got built, another book got written.</p><p>Immersing oneself in the world of customers and their problems is the best way I know for finding solutions to problems worth solving.</p><p>This is exactly how I wrote all my books and developed tools like the Lean Canvas. And exactly how this bootcamp evolved from a high-touch coaching program to a repeatable and practicable set of stage-based playbooks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24bxBZjQUS-wPJpMa3vUNg.png" /><figcaption>These Continuous Innovation playbooks (in Running Lean style) show you a step by step process for getting from point A to point B on the hockey-stick curve</figcaption></figure><h3>Start with mindset shift</h3><p>One of the a-ha moments when developing these playbooks was realizing that the <strong>early stage is all about investing in people and teams — not ideas</strong>.</p><p>We spend too much time building barriers during ideation with heavyweight processes like business planning, for instance. This is the #2 killer of ideas. Most good ideas never look that way at first because they often propose challenging the status quo which our tribal brain resists.</p><p>The answer <strong>isn’t doing more fictional analysis but gathering enough evidence of traction for the idea</strong>.</p><blockquote>Fast idea validation &gt;&gt; Elaborate idea generation<br>especially when speed to market is the new unfair advantage</blockquote><p>This requires a mindset shift both on the part of innovators and their stakeholders. Investing in people and teams is not about judging their idea submissions but leveling up their critical thinking and problem-solving skills.</p><p>This is the <strong>long game</strong> of innovation.</p><blockquote>Good teams will quickly recognize and kill off bad ideas and eventually find good ideas.</blockquote><blockquote>Bad teams can’t tell a good idea from a bad idea and they either stick with bad ideas too long or hopelessly fumble good ideas.</blockquote><p>Investing in people and teams specifically means first enabling key mindset shifts before investing in skills, tactics, or grand strategies.</p><p>All our playbooks follow this structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QnLSmQPnkwtalvHBsUlDrg.png" /><figcaption>Start with mindset</figcaption></figure><h3>What is a mindset shift?</h3><p>Mindset shifts are universal principles, like first principles in science, that serve as the building blocks for developing better critical thinking and problem-solving processes.</p><p>While we rightly place a lot of emphasis on doing, <strong>thinking precedes doing</strong>. And the quality of your output (results) is directly dependent on the quality of your inputs (ideas).</p><p>Over the years, I’ve collected many mindset shifts or principles as I’ve evolved my own thinking on product development:</p><ul><li>Release early, release often.</li><li>Less is more.</li><li>Right action, right time.</li><li>Get outside the building.</li><li>…</li></ul><p>I synthesized these first-principles into 10 key mindsets that define the operating system of the Continuous Innovation framework:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jo7QNYO9l_bo2bxEYRxS8w.png" /></figure><p>Before coaching any team, we first expose them to these 10 mindsets with lots of examples of each in action through our Foundations playbook.</p><p>We don’t expect an immediate transformation in behavior, but planting these mindsets early, allows us to then revisit them more contextually in later playbooks when the team is faced with making their own product decisions.</p><blockquote>Mindset shift is like a good tea — some steeping time is required and it can’t be rushed.</blockquote><p>If you’d like to take a deeper dive into these mindsets yourself, head on over to the <a href="https://leanstack.com/playbooks">Continuous Innovation Academy</a> and sign-up for the Foundations playbook — it’s free.</p><blockquote>Before building a skyscraper, you have to seemingly move in the opposite direction, digging a multi-story hole for the foundation.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d52ffd573f0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/start-with-mindset-d52ffd573f0c">Start With Mindset</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Level up your entrepreneurial game with our battle-tested playbooks]]></title>
            <link>https://medium.com/lean-stack/level-up-your-entrepreneurial-game-with-our-battle-tested-playbooks-f3736fb04adb?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f3736fb04adb</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Thu, 06 Jun 2019 11:56:40 GMT</pubDate>
            <atom:updated>2020-06-12T14:50:02.963Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re a long time reader of this blog, chances are high you’ve read my first book: <a href="https://leanstack.com/books">Running Lean</a>. But did you read my second book: <a href="https://leanstack.com/books">Scaling Lean</a>? My research says probably not. You’ve probably been waiting to pick up the second book for when you’re actually scaling your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*tSmH3stWlfiuvVA_d3Io2Q.png" /></figure><p>Being a deliberate reader myself, I’d probably have done the same. But what if I told you that, despite the title and book cover, Scaling Lean is actually sort of a <strong>prequel, not a sequel</strong>.</p><p>It’s not a book about dealing with the right side of the hockey-stick curve, but rather setting you up with a solid foundation, during the earliest stages of an idea, <strong>for systematically getting you to the right side of the hockey-stick curve</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgBhxtBH0SYKsFhHTw9Suw.png" /><figcaption>This might be a more appropriate book cover image for Scaling Lean</figcaption></figure><p>Scaling Lean shows you how to</p><ul><li>measure the 3 stages of the product lifecycle: problem/solution fit, product/market fit, scale with metrics — so you aren’t running blind,</li><li>identify your riskiest assumptions without guesswork — so you focus on right action, right time, and</li><li>run better experiments by learning how to source, rank, and test better ideas from your teams — so you avoid garbage in, garbage out.</li></ul><p>When asked to recommend a reading order of the books, I tell people to read</p><ul><li>the first 3 chapters of Running Lean,</li><li>then the first 3 chapters of Scaling Lean,</li><li>back to Running Lean, then Scaling Lean.</li></ul><p>Therein lies the challenge for books like these. While books are snapshots of the best thinking of the time, ideas and frameworks are constantly evolving. And something more dynamic is needed to better connect the dots.</p><h3>Meet the Continuous Innovation Academy</h3><p>We are <a href="https://leanstack.com/academy">launching a new initiative</a> for delivering <strong>stage based playbooks</strong> that teach you just the key mindsets, skills, and strategies you need to move your idea forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DchJgdHDQIZ8_Ot652BEQA.png" /><figcaption>You start with the foundations playbook and work your way up.</figcaption></figure><blockquote>Playbooks are curated how-to guides that help you define and achieve key milestones in your entrepreneurial journey by letting you focus on what matters and ignoring the rest.</blockquote><p>These playbooks were curated over thousands of hours of workshops and bootcamps and tested across a wide range of products and teams. They are delivered using a combination of self-guided content, integrated tools, and 1:1 coaching — so they always reflect the latest thinking and battle-tested tactics.</p><p>They build upon all the principles covered across both books and aren’t meant to replace them (that would just be an ebook), but complement them using curated and updated content, the latest tactics, and more examples.</p><h4><a href="https://leanstack.com/playbooks">Sign-up for the free 4-week Foundations playbook here</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3736fb04adb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/level-up-your-entrepreneurial-game-with-our-battle-tested-playbooks-f3736fb04adb">Level up your entrepreneurial game with our battle-tested playbooks</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Job-To-Be-Done (JTBD)]]></title>
            <link>https://medium.com/lean-stack/what-is-a-job-to-be-done-jtbd-21304ce7441b?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/21304ce7441b</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 21:54:37 GMT</pubDate>
            <atom:updated>2020-06-12T14:33:54.446Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve probably run into the jobs-to-be-done framework/theory. I did several years ago when I first stumbled into the <a href="https://www.youtube.com/watch?v=sfGtw2C95Ms">Milkshake Study</a> popularized by Clayton Christensen.</p><p>I was immediately intrigued and had more questions than answers.</p><p>I read up everything I could find and even worked alongside several JTBD thought leaders and practitioners including Bob Moesta, Chris Spiek, Tony Ulwick, Alan Klement, Des Traynor. A lot of their work influenced the development and still ongoing evolution of the <a href="http://innovatorsgift.com">Customer Forces Canvas and the Innovator’s Gift project</a>.</p><p>But even after all this research, two things continue to bother me.</p><p>First, the commonly found definitions of a jtbd are <strong>circular, polymorphic, or purposely vague</strong>. Second, a lot of the case studies felt like <strong>neat magic tricks </strong>— obvious in hindsight, but hard to recreate with your own product.</p><p>I want to attempt to tackle the definitions problem first. I believe starting with a clearer, more concise, simpler definition automatically moves us forward on the second issue.</p><h3>The Definitions Problem</h3><p>Here is a sampling of some of the definitions out there:</p><p><strong>Circular definition:<em> <br>People don’t buy products, they hire them to get a job done. <br></em></strong>A job then is something people are trying to get done. What is that?</p><p><strong>Polymorphic definition: <br><em>A task, goal or objective a person is trying to accomplish or a problem they are trying to resolve. <br></em></strong>Tasks, goals, and problems are separate and distinct things. How can a job be three different things?</p><p><strong>Purposely vague definition: <br><em>A job to be done describes the progress people are trying to make. <br></em></strong>How do we scope progress?</p><p>You’ll notice I left out the attributions on these definitions. This was intentional. Seasoned practitioners should have no problem identifying the sources and the curious should be able to easily look them up. I left them out because my goal isn’t casting judgment (or creating needless controversy). A lot of overlapping pieces are already laid out in these definitions. I am simply trying to piece them together through deconstruction.</p><p>The definition below helped me see and practice jtbd more clearly. I’d love to hear your thoughts in the comments below.</p><p>.</p><p>.</p><h3>What then is a Job-to-be-done?</h3><h4><strong>A simpler definition</strong></h4><p>A job to be done is the instantiation of an unmet need or want (in response to a trigger).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74LQCZxm-BqOTDlv7f_NWA.png" /><figcaption>A job to be done is the instantiation of an unmet need or want (in response to a trigger).</figcaption></figure><p><em>Notes: One could argue that you could simplify this further: A job is an unmet need or want. This isn’t as actionable a definition. What differentiates a </em><strong><em>job</em></strong><em> from a </em><strong><em>job to be done</em></strong><em> is the time-boxed sense of urgency that a trigger creates towards fulfilling an unmet need or want. In other words, jobs could be aspirational nice to haves. Jobs-to-be-done, on the other hand, signal action.</em></p><h4>All jobs start with a trigger</h4><p>We encounter triggering events throughout the day which means we encounter jobs to be done throughout the day too.</p><ul><li>It’s 12:36 pm and my stomach is grumbling. I need to eat.</li><li>It’s 7:36 pm and my stomach is grumbling and it’s my wife’s birthday. I want to take her to a fancy restaurant.</li></ul><p>Triggers are what define the context that shapes the job to be done.</p><p><em>Notes: Progress doesn’t have to game-changing or aspirational. It could simply be taking me from being hungry to being fed.</em></p><h4>Habits define what we do most of the times</h4><p>Having to find new solutions for every trigger we encounter would generate too much cognitive load so we rely on existing alternatives most of the times (like where to eat lunch).</p><p><em>Notes: Some jtbd practitioners focus jtbd solely around the hiring and firing of products which implies buying or switching. I decouple a jtbd from a switch or a purchase. In other words, hiring doesn’t require switching. One could simply be reusing a previously purchased product to get a job done.</em></p><h4>Until we encounter a switching trigger</h4><p>A switching trigger is a special trigger that comes with an <strong>expectation violation</strong>. That’s when we realize that our existing alternative(s) isn’t good enough to get the job done. That’s also when we seek new and different solutions.</p><p>In the lunch example above, what could cause us to seek out a new restaurant:</p><ul><li>a change in circumstance e.g. first day on a new job,</li><li>a bad experience e.g. food poisoning from the usual lunch spot,</li><li>an awareness event e.g. heard the new restaurant finally opened.</li></ul><p><em>Notes: Triggers instantiate jobs to be done which favor familiar solutions (existing alternatives). Switching triggers create expectation violations which open spaces for new solutions.</em></p><h4>Getting hired is only the first battle</h4><p>When prompted to switch, customers often evaluate and trial multiple products in search of the one that best gets their job done. Getting hired, while an important first step, is only the first step. Unless you can quickly deliver value (the aha-moment) and then establish yourself as the new status quo (the habit-moment), you could easily find yourself on the firing block.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDet0dtLC48qT-h9uVa9nQ.png" /></figure><p><em>Notes: Getting a job done isn’t just about acquisition. Activation and retention are where the rubber hits the road.</em></p><p>In case you are wondering how the customer forces canvas relates to the customer factory blueprint… here you go:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6I6YMnGmb9mM1T56WYapYg.png" /></figure><p>The customer factory is a systems view of how customers move through your product funnel transitioning through 5 states of unaware visitors to passionate, happy customers.</p><p>The customer forces describe the internal forces that make a customer go through between these state transitions.</p><h4>Needs versus Wants</h4><p>Needs are functional. Wants are emotional.<br>Needs have utility. Wants have energy. <br>Needs favor existing solutions. Wants favor new solutions.</p><p><strong>There is a place for both.</strong></p><p>We tend to focus on unmet needs in order to optimize existing solutions.<br>We tend to focus on unmet wants in order to search for new solutions. <br>Needs live in the solution context. Wants live in the bigger context.</p><p><em>Notes: The most effective marketing triggers on our wants, not our needs. When Apple announces a new product, people have already made an emotional purchase. They then read the features to rationalize the purchase.</em></p><h4>The bigger context is where you’ll find new spaces for innovation</h4><p>Every product exists in multiple contexts: the solution context and the bigger context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*mVUuosaj6eZKtq3dYsODuQ.png" /></figure><p>Examples:</p><ul><li>Cameras existing in the product context. Photography is the bigger context.</li><li>Lean Canvas exists in the product context. Innovation is the bigger context.</li></ul><p>Leveling up too many times on the bigger context can quickly get meta-physical quickly where you start questioning the meaning of life. But most innovators don’t level up at all.</p><p><strong>It’s better to level up and get out of scope and then narrowing down a level, than staying stuck in the weeds</strong></p><p>How do you find the bigger context? While the pursuit for better products should be outcome driven, not all outcomes are desirable. For example, you could build a stronger drill-bit that doesn’t break which delivers a better “hole in your wall”. But a “hole in your wall” is not the desirable outcome.</p><p><strong>Chasing desirable outcomes is how you move out of the solution space and into the bigger context.</strong></p><p><strong>Why do people drill a hole in their wall?<br></strong>- to get a quarter-inch hole (not desirable)<br>- to secure a hook (not desirable)<br>- to hang a painting (desirable)<br>- to decorate their home (desirable)<br>- to express their style (desirable)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSwgQle-29tPZTjNGV69cw.png" /><figcaption>Leveling up on outcomes from tasks/activities to the bigger context</figcaption></figure><p><strong>What do you do with this:<br></strong>- <strong>If you are a drill manufacturer</strong>, you might be inclined to focus on building better drill bits that don’t break.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*clVZendPJOLVgr04Ozp8ug.png" /><figcaption>A “stronger” titanium drill bit</figcaption></figure><p>- <strong>If you are 3M</strong>, you might build <a href="https://www.scotchbrand.com/3M/en_US/scotch-brand/products/catalog/~/?N=4335+3294268145+3294529207+3294857497&amp;rt=rud">strong mounting tape</a> that eliminates the need for drilling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eHjYDq7NYVS5-8KATQfhMg.png" /><figcaption>3M Extremely strong mounting tape: Hang paintings with no fuss, no mess.</figcaption></figure><p>- <strong>If you are Samsung</strong>, you might sell more <a href="https://www.samsung.com/us/explore/the-frame/design/">flatscreen displays</a> that replace artwork on walls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OL7ATDJdV3J7CauvaRArdg.png" /><figcaption>Samsung Frame TV: TV when it’s on, Art when it’s off.</figcaption></figure><p>If you are solution-agnostic, you could consider all three.</p><p>That’s why this stuff is so much fun…</p><p>This is sometimes equated to disruptive innovation — doing old jobs with new solutions.</p><p>When you’re moving really fast and constantly uncovering, prioritizing, and delivering on the unmet needs and wants of your customers, you’re not pursuing sustaining or disruptive innovation — <strong>it’s all continuous innovation</strong>.</p><p>Doing this not only positions your business model for causing switch. More importantly, it positions your business model against switch.</p><p><strong>Delivering on the bigger context is how you cause switch and preventing switch is how you continue to stay relevant to your customers.</strong></p><h3>How do you systematically uncover the right job-to-be-done?</h3><p>By using carefully scripted customer interviews and summarizing your key insights on a Customer Forces Canvas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zJshx6QAYONEPD6TV1V3Q.png" /><figcaption><a href="https://leanstack.com/customer-forces-canvas">Try it out on LEANSTACK.com</a></figcaption></figure><p>.</p><p>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21304ce7441b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/what-is-a-job-to-be-done-jtbd-21304ce7441b">What is a Job-To-Be-Done (JTBD)</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Root Cause for Innovation Theater and How to Avoid It]]></title>
            <link>https://medium.com/lean-stack/the-root-cause-for-innovation-theater-and-how-to-avoid-it-947d0ce5d5a5?source=rss----8a472b45761d---4</link>
            <guid isPermaLink="false">https://medium.com/p/947d0ce5d5a5</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Ash Maurya]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 16:04:52 GMT</pubDate>
            <atom:updated>2019-03-19T16:25:22.516Z</atom:updated>
            <content:encoded><![CDATA[<p>In a recent post, I shared a reference implementation of an innovation funnel built on the <a href="https://leanstack.com/library/categories/fundamentals/courses/what_is_continuous_innovation/lessons/fundamental_shift">Continuous Innovation Framework</a> and cautioned that while funnels are powerful visualization tools, <strong>they have their limitations</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L6dqN4xSvr7P5eG3c84yrg.png" /><figcaption>A reference innovation funnel built on the Continuous Innovation Framework</figcaption></figure><p>The biggest limitation is sub-funnel optimization which, in this case, is one of the leading causes for <strong>Innovation Theater.</strong></p><h3>The Problem With Funnels</h3><p>Real and meaningful funnels typically have long lifecycles which take time to study. Innovation funnels, for instance, need at least 2–3 years to go from idea to product/market fit.</p><p>To speed things up,</p><ul><li>we break these funnels into smaller sub-funnels,</li><li>define clear local KPIs (key performance indicators),</li><li>and assign different groups of people (departments or organizations) to optimize them.</li></ul><p>This is when the problem starts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4GYW_395KuqIBCUsDcEDPQ.png" /><figcaption>Divide and conquer leads to local optimization</figcaption></figure><p>This divide and conquer approach seems logical but it favors local optimization at the expense of longer-term system throughput i.e. real results. This problem is even further exacerbated when we attach incentives to these local KPIs.</p><p>Let me illustrate first with some examples from the product world:</p><ul><li>If you simply incentivize marketers to drive more leads, your ad budget gets spent and you get more leads — but longer-term conversion rates tend to go down.</li><li>If you simply incentivize salespeople to close accounts, magically accounts close usually towards the end of the month. If you study longer-term effects, you find that accounts closed during the last week of the month tend to churn more than others.</li><li>If you simply incentivize software developers to write more lines of code, more lines of code get written, but performance and quality suffer.</li></ul><p>Thankfully, we have done away with many of these policies. However, in some cases, we have still only replaced old local KPIs with a new local KPI — like build velocity over lines of code.</p><blockquote>Building something nobody wants on time and within budget is still not the right metric.</blockquote><p>In the world of innovation, if you incentivize innovation managers simply to run hackathons or launch accelerators, the money gets spent: t-shirts get printed, foosball tables get purchased, Lean Canvases get hung.</p><p>But these aren’t the right metrics either.</p><p>I once had a conversation with an accelerator that had low follow-on investment after their Demo Day. Their teams were really early stage and <strong>12-weeks just wasn’t enough time for</strong> <strong>acceleration and education</strong>. My suggestion was raising the bar on their application process and requiring their teams to level up on some basic business modeling concepts. They were afraid this could create too much signup friction and feared that the number of applications would drop which wouldn’t look good to their stakeholders. So they chose against it.</p><p>Even well-intentioned key activities, like running customer interviews, can be gamed when framed with the wrong incentives. The NSF I-Corps program, for instance, requires that scientists run 100 interviews as a pre-condition to securing a grant. Guess what? Exactly 100 interviews get run!</p><p>How about pairing startups with corporates? Startups need customers, corporates need innovation. The perfect pairing? Not so fast… I’ve seen some great short-term ideas come from this kind of pairing. The problem again is the longer-term. What do corporates then do with a promising startup idea? How do they (or should they) integrate them back into the mothership?</p><p>In each of these cases, people are attempting to optimize for the shorter-term sub-funnel but then getting stuck deeper down the funnel.</p><p><strong>You have to start with a holistic view of the funnel.</strong></p><h3>Think Systems, Not Funnels</h3><p>The antidote is thinking in terms of systems, not funnels. A key attribute of systems is the <strong>razor focus on a single macro metric</strong> (not a sub-funnel metric) that matters: <strong>Throughput</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tU34QeBmNn2k3IOQtTFsPw.png" /><figcaption>Throughput == Traction</figcaption></figure><p>Throughput in the innovation funnel can be measured in terms of the rate at which we generate successful ideas. But this is again subject to gaming. What does “success” mean? The good news is that we already have a well-defined single metric for measuring this: <strong>Traction</strong>.</p><blockquote>Traction is the rate at which a business model captures monetizable value from its customers.</blockquote><p>Traction can be further deconstructed into 7 key metrics which can be used to consistently measure any idea at any stage against a <a href="https://leanstack.com/traction-model">traction roadmap</a>.</p><p>Sure, some of the activities up above (like running customer interviews) are really key. I am also not against creating a different and fun work environment. I think that’s important too — especially given that you just asked your best teams to give up their familiar jobs and embrace a world of uncertainty.</p><p><strong>Innovation in the new world inevitably requires teams to unlearn old habits and learn new skills. This is uncomfortable and hard to sustain without positive reinforcement and small rewards along the way.</strong></p><h3>Think People, Not Funnels</h3><p>Yes, we all want more successful projects than failed projects. But good ideas are rare and hard to find. The best way to increase your longer-term success rate isn’t brute-forcing ideas to success, or worse, redefining what success means to meet your KPIs.</p><p>And this brings us to the bigger context…</p><p><strong>The long game goal of innovation managers, mentors, and coaches should be focused on creating better entrepreneurs and innovators</strong> — not by chasing unicorns but decreasing the cycle time between ideas.</p><p>This requires a deliberate and patient investment in leveling up your teams on new <strong>mindsets, skills, and playbooks </strong>for succeeding in the new world.</p><p>Ideas then are vessels for leveling up your teams. You can’t afford to just focus on activities, skills, or traction. You have to focus on all three.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5dn_5Wdij-pB9ugMkgFY4w.png" /><figcaption>Innovation Funnel Metrics</figcaption></figure><blockquote>Don’t build a better [x].<br>Build a better user of [x].<br>- Kathy Sierra</blockquote><p>Don’t build better [innovation processes and tools].<br>Build better innovators.</p><p>The rest will take care of itself.</p><p>.</p><p>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5d02a9%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F5d02a9%2F&amp;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F5d02a9%252F%253Fenpose&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb6830f6bb40962cdde72f1406d3d7d4/href">https://medium.com/media/fb6830f6bb40962cdde72f1406d3d7d4/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=947d0ce5d5a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lean-stack/the-root-cause-for-innovation-theater-and-how-to-avoid-it-947d0ce5d5a5">The Root Cause for Innovation Theater and How to Avoid It</a> was originally published in <a href="https://medium.com/lean-stack">Love the Problem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>