Lean Startup Principles
•
9 recomendaciones•2,281 vistas
1) The document discusses the Lean Startup methodology for building startups. It emphasizes learning over execution and eliminating waste ("muda") through quick validation of assumptions with minimum viable products. 2) Key principles discussed include releasing early versions of products that customers may find embarrassing, developing customers as much as products, and treating learning rather than execution as the unit of progress. 3) Successful startups validate their ideas by showing customers will pay for the product or service, rather than investing large sums to build products nobody wants. Getting customer feedback is emphasized over internal planning.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (13)
Similar a Lean Startup Principles
Similar a Lean Startup Principles (20)
Más de Abby Fichtner
Más de Abby Fichtner (8)
Lean Startup Principles
- 1. Lean Startup Getting out there & Changing the World Abby Fichtner Hacker Chick / Startup Guardian Angel @HackerChick http://HackerChick.com
- 2. What makes entrepreneurs entrepreneurial? Saras D. Sarasvathy Boston Startup School - @HackerChick Paper: http://bit.ly/bss-wmee
- 3. Boston Startup School - @HackerChick
- 4. “Considering the incredible amount of human energy, passion, and creativity that we invest in creating new products & services… Boston Startup School - @HackerChick @EricRies
- 5. … it’s a terrible waste that so many of them fail.” Boston Startup School - @HackerChick @EricRies
- 6. Promise of the Lean Startup Instead of building our startups according to myths We can guide them with facts and knowledge Boston Startup School - @HackerChick @EricRies
- 7. Boston Startup School - @HackerChick
- 8. Boston Startup School - @HackerChick
- 9. Boston Startup School - @HackerChick
- 10. Boston Startup School - @HackerChick Andrew Mason, CEO of Groupon (NY Tech Meetup)
- 11. “You’re way too dumb to figure out whether your idea is good” Boston Startup School - @HackerChick Andrew Mason, CEO of Groupon (NY Tech Meetup)
- 12. Startups are NOT small versions of large organizations Boston Startup School - @HackerChick
- 13. Boston Startup School - @HackerChick
- 14. Startup Lesson #1 The unit of progress for entrepreneurs is learning, not execution Boston Startup School - @HackerChick @EricRies
- 16. What fun is spending months building something that nobody wants?
- 17. muda any activity that is wasteful and doesn’t add value or is unproductive wikipedia
- 18. Startup Lesson #2 Eliminate muda (building things nobody wants is the worst kind of muda) Boston Startup School - @HackerChick wikipedia
- 19. $5 BILLION ENGINEERING TRIUMPH MILLIONS of CUSTOMERS FAIL One of the Largest Bankruptcies in US History Boston Startup School - @HackerChick
- 20. “We’re a classic MBA case study in how NOT to introduce a product. First, we created a marvelous tech. achievement Then, we asked how to make money on it.” Boston Startup School - @HackerChick Iridium Interim CEO John A. Richardson
- 21. “Most technology start-ups fail not because the technology doesn’t work, but because they’re making something that there is not a real market for” Boston Startup School - @HackerChick @EricRies
- 22. What should startups do differently? Boston Startup School - @HackerChick
- 25. Boston Startup School - @HackerChick
- 26. Minimum Viable Product (MVP) strategy for fast & quantitative market testing of a product or feature Boston Startup School - @HackerChick wikipedia
- 27. “Papa built our last tree house in a day!” “Yeah, but that tree house was a couple pallets and a ladder” Boston Startup School - @HackerChick The Minimum Viable Tree House by Christian Wyglendowski
- 28. Boston Startup School - @HackerChick
- 29. Boston Startup School - @HackerChick
- 30. Startup Lesson #3 Don’t build mansions in the sky Start with a couple of pallets & a ladder Boston Startup School - @HackerChick wikipedia
- 31. Boston Startup School - @HackerChick
- 32. Startup Lesson #4 It’s just as important to develop your customers as it is to develop your product Boston Startup School - @HackerChick wikipedia
- 33. Customer Development Boston Startup School - @HackerChick @SGBlank
- 34. Lean Startup Boston Startup School - @HackerChick @SGBlank
- 35. Product/Market Fit When a product shows strong demand by passionate users representing a sizeable market The Entrepreneur’s Guide to Customer Development (@BrantCooper, @Vlaskovits) Boston Startup School - @HackerChick
- 36. Get outside the building!
- 37. Customer Discovery What is the problem? Who has the problem? @SGBlank
- 38. Customer Discovery How important is the problem’s solution to the customer? How valuable is the problem’s solution to the customer?@SGBlank
- 39. Boston Startup School - @HackerChick
- 40. Boston Startup School - @HackerChick
- 41. Customer Validation Boston Startup School - @HackerChick
- 42. Startup Lesson #5 To be successful, you need to make money. Until people are giving you money, your idea isn’t validated. Boston Startup School - @HackerChick wikipedia
- 43. Boston Startup School - @HackerChick
- 44. What Startup Behavior is the Single Biggest Predictor of Failure? Sticking to Initial Business Plan Boston Startup School - @HackerChick 300 startups surveyed (src: Don Sull, "The Upside of Turbulence”)
- 45. How do we measure progress? Learning Boston Startup School - @HackerChick
- 46. Fastest way to learn if our startup is working? Get out of the building! (customer validation) Boston Startup School - @HackerChick
- 47. Startup Lessons so far… 1. Unit of progress: learning 2. Eliminate muda (waste) 3. No mansions, a couple of pallets & a ladder 4. Develop your customers not just your product 5. Your idea isn’t validated until: show me the $$$! Boston Startup School - @HackerChick wikipedia
- 48. We had an idea for a new product. We went off & built it, put it on our website. Not a single person clicked thru to it What did we learn from that? Boston Startup School - @HackerChick
- 49. We had an idea for a new product. We went off & built it, put it on our website. Not a single person clicked thru to it Was there a faster way to get through that learning loop? Boston Startup School - @HackerChick
- 50. Boston Startup School - @HackerChick
- 51. Boston Startup School - @HackerChick
- 52. Boston Startup School - @HackerChick
- 53. Boston Startup School - @HackerChick
- 54. Boston Startup School - @HackerChick
- 55. Startup Lesson #6 If you’re not embarrassed by your 1st version, you waited to long to release Boston Startup School - @HackerChick
- 56. Boston Startup School - @HackerChick
- 57. Boston Startup School - @HackerChick
- 58. Boston Startup School - @HackerChick
- 59. Boston Startup School - @HackerChick
- 60. Product/Market Fit Assumptions Boston Startup School - @HackerChick
- 61. Your Turn 1. What is your Big Idea? 2. What are your Top 3 Assumptions ? • Customer • Problem • Solution 3. Pick 1 assumption: • How would you validate it (what data do you need)? • What the MVP to validate it? Boston Startup School - @HackerChick wikipedia
- 62. Learn More Eric Ries @EricRies http://startuplessonslearned.com/ Steve Blank @sgblank http://steveblank.com/ Ash Maurya @ashmaurya http://ashmaurya.com/ Abby Fichtner @HackerChick http://HackerChick.com Boston Startup School - @HackerChick
Notas del editor
- I want to talk about Lean StartupThis is how the startups you’re going to be joining will be operating at their coreAnd the thing to know is that they’re really not at all like big companies -- which of course is why we have Startup SchoolAnd they can feel pretty crazy & chaotic, but there’s actually a method to the madness & that’s what I’m going to talk about today.
- Let’s start off with – what do you think makes entrepreneurs entrepreneurial? Any thoughtsThese are awesome – so this was actually the topic of some research done bySaras “saraswathy” at the University of Virginia and what she found was thatNormal people employ what she calls Causal Reasoning. That is, they set an end goal & come up with a strategy for how best to reach that goalStraight forward –They have something they want so they come up with a plan to get itEntrepreneurs however, use Effectual Reasoning.In effectual reasoning we don’t even start with a specific goal in mind.Instead, we take a hard look at where we are TODAY – who we are, what we know, WHO we knowAnd we start to tinker – we start imagining & implementing possible things that can be created with all of thisAnd so we progress, allowing our goals to emerge over time.And so causal reasoning is all about the perfect plan & then following through on itBut effectual reasoning is more about exploring. And it’s all about executing. It’s all about trying stuff & then adjusting our path based on what we learned from it.
- Has anyone ever read Where Good Ideas Come From? By Steven JohnsonSUCH a good bookAnd in it he talks about these patterns of innovation that happen over and over again… but not innovation that happens in startupsHe’s talking about innovation in evolution & how our planet has evolved & how we’ve evolvedAnd he then ties this to innovations we think of – like the lightbulb or the combustion engineOne of patterns is called The Adjacent PossibleAnd the idea is that at any given point in time – there is a set amount of what’s possible.Things that can be done with the technology and the knowledge that we possess todaySo all innovation is going to happen at the adjacent possible – meaning what’s just beyond what’s possible todaySo if we can look at what’s possible today and take it just a little bit further, we’ve actually expanded that set of what’s possibleSo we’ve made the world a little bit better for everybody, because there’s more that can be doneAnd so I believe this idea of effectual reasoning where you look at what’s around you & see how you can build upon it to take things to the next levelI believe THAT is how we change the world.And what I love about lean startup is that it actually gives us a method for doing this.
- Eric Ries is the creator of the Lean Startup methodology
- 9 out of 10 new products fail
- A startup founder starts off with their Big Vision for how they’re going to change the worldAnd I know you’re saying no, no – Abby you just told us startup founders don’t do causal reasoning.But the truth is, you really can’t found a company without a vision of what you want to achieve, otherwise – what are you doing?It’s just that the trick is – to identify where your vision intersects with what reality can actually accommodateAnd that’s where the exploring comes in & the willingness to try different things out
- Great example of this is a Startup called the Point.The Point’s idea or BIG VISION was to harness the collective power of all the people on the internet<Read Tagline: Whether you’re raising money, organizing people, or trying to influence change: if you can’t do it alone, you can do it on The Point>Fantastic vision! But totally unfocused. It could be used for anything from political activism to boycotting multinational corporations to getting a group discount at your favorite pizzeria.It wasn’t gaining traction, they had to lay off the co-founder. About to become one of those 9 out of 10 statistics…But the CEO looked harder and said is there anything in this vision that IS working?And actually – that getting people together for a group discount at a pizzeria, THAT was working.And if that sounds familiar, it should…
- Because that CEO was Andrew Mason and he took that idea and turned it into Groupon, which became the fastest growing company EVER.Over 30MILLION Groupon subscribers in North America alone
- So I want to share with you some of the key learnings that Andrew Mason took away from The Point -> Groupon experience<play video>
- So normally when I show this example to new startup founders, I say if there’s ONE thing you take away, it’s this… <read>Build that very small thing & get it out there to the masses, and keep on trying different things. Eventually you'll get it right
- The takeaway here – and the reason you’re all at Boston Startup School is that… <read>Large organizations are already operating in a known market, solving a known problem. They’re focused on execution: better ways to solve that problem for their market & reaching more customers
- Startups are starting from nothing.They haven’t even validated that there’s a need for this fabulous idea of their’sThey’re about learning and discovery, not execution.
- So startup lesson #1 is….<read>And this is REALLY hard…
- Because building stuff is FUNAnd you’re at a startup. That’s really sexy. So your friends all want to know what you’re building.And you’re all – not much, but I’m learnin! Learnings sexy too right?Building stuff is fun.
- In lean we have a term for that – we call it muda.Muda is a japenese term because all of these lean concepts stem from Lean Manufacturing, which actually came from the Toyota Production SystemAnd we might translate it to waste, but it’s actually much broader than thatIt means anything that doesn’t add value or is unproductive.
- So Startup Lesson #2 is eliminate Muda<click><read>In fact… Eric Ries said the the #1 most important thing for a startup is learning to tell the difference between value & waste.
- So, to show a really big example of waste I had to go all the way back to the 90’s when we had really awesome phones.In the early 90’s, Motorola spun off a new company called Iridium to build satellite phonesAt the time, it was a HUGE engineering triumphThey spent $5 BILLION dollarsBuilt it to scale to MILLIONS of customersThey spent years and years on itAnd when they finally released, 11 years later, nobody wanted itAnd it became one of the largest bankruptcies in US history
- John Richardson, who stepped in as CEO after all of this happened said<read>
- The truth is… <read>And so we need a different model then that which big companies follow
- What do you think startups should do differently then big companies?<split into groups of 3-5 people, take 5 minutes to think about how you’d run a startup differently><Have volunteers share their best idea>
- The typical way we think about companies operating is… you’ve got a vision of what you want to do… <click> and you go build it.But when you’re creating something brand new & you haven’t yet validated that there’s a market for the product you’re buildingThat approach tends to lead to… WHAT?<click> 9 out 10 new products failingWhich is bad, right?
- The typical way we think about companies operating is… you’ve got a vision of what you want to do… <click> and you go build it.But when you’re creating something brand new & you haven’t yet validated that there’s a market for the product you’re buildingThat approach tends to lead to… WHAT?<click> 9 out 10 new products failingWhich is bad, right?
- So our goal instead is to do some exploring to figure out what piece of our vision reality can accommodateWhat is our group discounts for pizza?In Lean Startup, we do this with something called the Build-Measure-Learn loop. And this represents the process we’ll be iterating over to move us towards a successful business modelThe idea is – you start with some assumptionsAnd then you think about how you might be able to LEARN whether these assumptions are right or not(I am assuming that if I give people a platform for group action, they’ll use it for worthy causes – like political activism)So now you step back and say, okay, what can I BUILD that will let me capture the right DATA in order to learn if my idea is true or not?(maybe I can build the platform for group action & then capture some analytics to see how people use it)But – here’s the catch, and this is what Andrew Mason realized after he’d spent 10 months building The Point.We need something faster than taking 10 months to build the platform and see how people use it.We need to get that 1 little thing out there & see what people do with it.So the key to iterating through your ideas to a successful business plan is to <click>GET THROUGH THE WHOLE LOOP AS FAST AS POSSIBLEThink days or a week or two, NOT 10 monthsSo now we need to ask the question again. I’m assuming that if I give people a platform for group action, they’ll use it for worthy causes – like political activismHow can I learn if that is true or not in just a couple days or maybe a week?
- Our strategy for doing this is something called Minimum Viable ProductWhich says – what’s the SMALLEST thing I can build that will take us to the next step?And remember – we’re focusing on LEARNING over execution, so what’s the smallest thing I can build that will let me LEARN something?Preferably whether the assumptions I’m making are correct or not – so I can learn if I’m moving in the right direction or not
- So a story about this that I like is a blog post that Christian Wyglendowski wrote called The Minimum Viable Tree HouseAnd he’s talking about how he’s building a tree house for his kidsAnd it’s taking a while…And his oldest one says <read>This time, Christian had a WAY bigger vision…
- This kind of ROCKS, right? But here’s the thing – if we built this, is this really want our target market wants?If we’ve got kids – they’re probably looking for something high up, away from the adults, that feels like a secret stealthy kids only placeThis – ain’t stealthyFurthermore – if we actually BUILT something like this – you just KNOW we’d be inviting ALL our friends over & be all “look at what I built for my kids”Do you think kids really want to be hanging out in the place that mom & dad and all their friends are?Kind of defeats the purpose, right?
- And so kids might actually LOVE thisTHIS is our minimum viable feature set: It’s up high, away from the adults, and best of all, it’s available in a day so they can start playing NOWAs opposed to the other one where maybe it’ll be ready by the time they go off to college.You should NOT be building this (flip back)You should build THIS (slide)— something so crude that it embarrasses you to put it in front of your market.
- So Startup Lesson #3 is <read>
- In a startup it’s obviously essential that you’re able to BUILD a productBut it’s just as, if not MORE important to BUILD your customers.So Lean Startup combines agile development (for how to dev your product)With Customer Development (for how to develop your customers)
- So Startup Lesson #4… (just point & pause), OK.
- The way we develop our customers is with a process called Customer Development (created by Steve Blank)It has 4 steps, as Steve describes in his book: 4 Steps to the EpiphanyIn the 1st step: Customer Discover – we’re discovering who our customers are & what problems they haveIn the 2nd, we’re validating this knowledge. This is our test step and it’s important because… we’re dealing with people hereAnd people are notoriously complex & misunderstood & tend to say one thing (wow, that’s an awesome idea, I would totally buy that!) and do another.So you see there’s this arrow going back here. This is a very iterative process and you need to iterate on this until you get it right.And ONLY once you’ve been able to validate who your customer is do you get to start operating like a regular company: Scaling up your customer baseScaling up your company and your product
- So really it’s these 1st 2 phases that we’re talking about when we talk about Lean StartupAnd what we’re trying to achieve with these phases before we can go into normal company mode is…
- Something called Product/Market FitWho your market is (and what their problem is) and what product you’re going to build that’s going to solve that problem for them.Requires:Customer is willing to pay for the productCost of acquiring the customer is less then what they pay for the productThere’s sufficient evidence indicating the market is large enough to support the business(not mom & roomate)So how do we do this? How do we do Customer Development….?
- We get outside the buildingSteve Blank likes to say NO FACTS live inside the building, only guesseshttp://www.flickr.com/photos/jenniferyellow/2203389749/sizes/l/in/photostream/
- So let’s say our BIG VISION is that we want to make flying cars.So when we’re doing customer discovery, we get out of the building, we talk to customers & we try to learn…
- So let’s say our BIG VISION is that we want to make flying cars.So when we’re doing customer discovery, we get out of the building, we talk to customers & we try to learn…
- Once you’ve gathered this knowledge, you bring it back to your development teamWho creates not some 10 month long full blown product, but the Minimum Viable ProductWhat’s the MINIMUM thing we can build to take us to the next step?They give this Minimum Viable Product back to the Customer Development team who sets out to validate it.
- Once you’ve gathered this knowledge, you bring it back to your development teamWho creates not some 10 month long full blown product, but the Minimum Viable ProductWhat’s the MINIMUM thing we can build to take us to the next step?They give this Minimum Viable Product back to the Customer Development team who sets out to validate it.
- How do they validate it?They give it to a customer and see if they’re willing to pay.Because UNTIL you have customers that are actually willing to give you money, you don’t have a viable business.You just have guesses.
- So go back to the drawing board.Think about what assumptions you’re making, build a little something to validate if those assumptions are right, put it in front of the customers to learn from it, and keep iterating.
- So this is pretty scary, right?We’re used to knowing if we’re “on track” or not for how we’re tracking against the plan.But if always sticking to the plan means failure, how do we measure progress?
- So now that you guys know all about startups, let’s dive into some concrete examples of what startups are doing& then I’m going to turn it back to you guys to give it a try with some of the big ideas that you have been coming up with
- So let’s start with a really basic example
- So let’s start with a really basic example
- Oops – this feature isn’t available yetIf we had some analytics that could show us the count of 0 people that clicked through, that would have been just as effective.We would have learned just as much without having to actually build the product.And so a totally viable lean startup tactic is to build a landing page.
- A great example of this is Buffer. They do social media sharing.This is how they look today. But this is not how they started…
- 1st, they created what’s called a landing page to just see if anyone was interested.In other words, can 1st off can they get people to come to the page?And 2nd, will any of those actually click through to Plans & PricingIf they clicked plans & pricing…
- Ooops, you caught us before we’re ready.But if you’d like to be notified when we’re ready, give us your email address.They tweeted it out, a few people gave their email addresses. That was good enough – we don’t need a billion people, because we don’t want to wait months for this – we just need some initial validation.So now, let’s move to the next MVPIs the next MVP to build the product? <ask>We haven’t validated our business model unless… what? <ask>People are giving us money!
- So the next MVP added a page to check for just that.When people clicked Plans & Pricing they got 3 plans, 1 free, 2 pay.If anyone clicked any of the plans, they just got brought back to the Oops/give us your email address pagePeople continued to click the Plans & Pricing button, and now they clicked through on one of the plans, a small # even clicked a paid plan.Great, enough validation – they were ready to put something out there.They thought it was only going to be 1 week to build a really minimal version – I mean it’s just queuing up tweets to send out, right?As it turned out, it took 7 weeks and they had to leave out some pretty vital functionality (think: couple of pallets & a ladder)But they put it out there & very shortly thereafter had 500 users, and they were generating revenue through their monthly plans
- They’re validating their ideas. They’re starting to bring in revenue to help pay to build out their startupAnd they’re able to start getting feedback from real users so they’re evolving the system to what makes sense for the people using it. Not just what they THINK or guess might be right.
- Another example is something called Concierge ServiceOccasionally called Wizard of Oz approach for the man behind the curtainBecause instead of BUILDING something you say, hmm, what could we accomplish MANUALLY for our users?And this is really weird if you’re a tech startup where you feel like your whole reason for being is using technology to solve problems.
- A great example of this is AardvarkAardvark does social search. The idea is there are some things that you need to ask a real person, not a search engine.Like – what’s the most awesome Boston startup to go work for?Okay, how do you automate that? I don’t know – why don’t we see if anybody even WANTS it before we worry about how we’re going to build it.Which is exactly what Aardvark did.They put up a simple web form where people could ask questions.When a user asked, it would email someone at Aardvark -- probably one of the founders so they could understand what types of questions were being asked – and then a person at Aardvark would go track down an appropriate expert in the area, ask them via email, and then email the answer back to the initial user.Once they HIT the point where doing this manually wouldn’t scale any more.THAT’s when they realized, hey, it looks like we have a viable business now.Now we can go start building it.So Aardvark built it out. It took them a year. I imagine they did it very iteratively, probably prioritized to handle the most manually intensive parts of this first.And then they got acquired by Google for $50M. So it sounds totally ghetto. But it works.And they didn’t have to waste ANY time building things nobody wanted.
- So you all did a lean canvas for your idea, right?It can be a little overwhelming at first to think through all of this – but the goal isn’t to get it perfect.The goal is to get SOMETHING out there quickly – so you’d maybe spend a few hours, a day at MOST with your best guessesAnd then you start thinking about – okay, what assumptions am I making here?
- There was a startup at one of the Lean Startup Machines I was at – which is like a startup weekend totally focused on Lean StartupAnd they wanted to create a service that helped people find activities for weekend getawaysAnd they thought we’ll start with Boston students because that’s a market we can reach and even do a concierge service forWhere we work with them individually to help them find activities and then once we’ve learned from that we can automate it.So – they started to go out and talk to Boston students about what weekend getaways they were doing and where they needed help planningAnd, long story short – Boston students weren’t so much traveling over the weekends.And when they DID travel, it was because they had very specific activities in mind.So they didn’t actually need any help finding activities for weekend getaways.And so if you back that up a little, you’ll realize the startup was making the ASSUMPTION that Boston students had a problem where they needed help with thisAnd so really, ANY effort the team expended based on that assumption was just wasted. It was MUDA, right? Because it was an invalid assumption.
- So when you look at your lean canvas – at least in the very beginning, you’re primarily focusing on these 3 blocks for identifying what assumptions you’re making: Who’s your customer?What problem do they have?What product are you going to provide that will solve their problem for them?And before you spend ANY effort building any products, you need to first validate those assumptions.
- So I want you to give it a try.Stay in your teams of 4. And just have 1 person from each team volunteer to use their idea and canvas.