Learn more Shop now Learn more Shop now Shop now Shop now Learn More Shop now Shop now Learn more Shop Fire Shop Kindle Worried Blues Shop now Fitbit

Customer reviews

4.6 out of 5 stars
530
4.6 out of 5 stars
Format: Paperback|Change
Price:£9.74+ Free shipping with Amazon Prime


There was a problem filtering reviews right now. Please try again later.

TOP 500 REVIEWERon 3 February 2016
I'm a second time entrepreneur, but by Eric Ries' analysis I'm actually a third time entrepreneur, because he counts the time I set something up as a consultant for a large corporation. So he had me at hello, even if it was through flattery.

In fewer than 300 pages it gave me a good 15 flashbacks. Points where I was shouting out loud "exactly!"

Embarrassingly, it also gave me a whole bunch of moments where I said "why did nobody tell me that back then."

It's a MUST if you are starting a business.

It's not without its faults. It's an advertisement for his consultancy, it could do without the references to Toyota (of which there's tons), it really reads like one of those self-help guides obese people read on airplanes; it's far from perfect.

It is regardless AWESOME and it's a very quick read.

Look away now if you don't want me to spoil it for you, here come the main points:

1. Entrepreneurship can happen in funny places.

2. Value = providing benefit to the customer. “Success is not delivering a feature; success is learning how to solve a customer’s problem.”

3. Launch! You’re not going to increase the value of the product without real customer input

4. Launch! You could be perfecting a product of no value

5. Launch! You WILL throw a lot of work away; the earlier you launch the less you’ll throw away

6. For all the above reasons, keep going through short cycles of BUILD, MEASURE, LEARN

7. Plan to learn; don’t say “I learned” as an excuse after a failure if you did not have a lesson planned in there.

8. There is a problem with launching: Once you’ve launched you give up on the “audacity of zero.” In plain English, you start collecting micro amounts. Vis a vis the naysayers, you were better off collecting zero and talking billions. Nobody said it would be easy…

9. Every venture has a value hypothesis and a growth hypothesis

10. Value hypothesis: your guess about why people will want this product
a. Do consumers recognize they have a need you are trying to address?
b. Would they pay money for it?
c. Would they buy it from you?
d. Can you build it?

11. Growth hypothesis: your guess about how you will add customers / sales

12. Design proper experiments to test the two hypotheses. A/B experiments, whatever

13. The Lean Startup recipe is
a. Get a Minimum Viable Product out
b. Go through Build, Measure, Learn loops / experiments to test the two hypotheses and keep improving the product
c. Be happy to reject a few MVPs until you hit upon a good one

14. The MVP won’t be perfect, by definition, but
a. Early adopters won’t mind
b. Let customers decide it’s bad; they might love it (like IMVU’s jumping avatars)
c. You can be creative about showing how it works: e.g. do a video
d. You could do it mechanically, without the tech (concierge) for just a few users

15. Innovation Accounting consists of
a. Establish a baseline: test your riskiest assumption via an MVP or an experiment or even a poll of your customers
b. Tune the Engine: With the baseline secured, make the product better by picking good metrics that are relevant to your value hypothesis and your growth hypothesis and running Build, Measure, Learn loops to get the metrics to improve
c. Pivot or Persevere: Every once in a while, decide if you’re doing well or if you need to Pivot

16. Vanity Metrics won’t get you anywhere. Be careful what you measure. Don’t look at aggregates, look at cohorts or split tests, for example. Use metrics that are relevant to your model. So if the model is viral, measure how many customers every customer brings. Not how your overall number of customers is growing (just because you paid for advertising, for example)

17. The three A’s of Metrics are Actionable, Accessible and Auditable. That’s how you get everybody on board. Don’t bother measuring if others can’t verify your work, if it will be very onerous to measure and if you have not agreed upfront what to do with the numbers. Additionally, “metrics are people too.” If they’re not, make it that way. Make them relevant to the customer.

18. Your engineers need to work as a team. They must work toward testing and delivering product for the customer. Not toward completing projects that get stuck because there is a bottleneck in testing, for example.

19. A startup’s runway is the number of pivots it can make.
Money buys you the opportunity to make a fundamental change (or two) in your business strategy, but saving money without executing a pivot will just mean you die late.

20. Schedule a regular “pivot or persevere” meeting where both product development and business leadership teams attend. Maybe even outside advisors.

21. A catalog of pivots:
a. Zoom-in Pivot
b. Zoom-out Pivot
c. Customer Segment Pivot
d. Customer Need Pivot (e.g. bookings vs. cheap deals)
e. Platform Pivot (e.g. client vs. hosted)
f. Business Architecture Pivot (e.g. B2C to B2B, high-margin to high-volume)
g. Value Capture Pivot
h. Engine of Growth Pivot
i. Channel Pivot
j. Technology Pivot

22. Small Batches are individually more costly, but if you account for everything Large Batches can have very large costs too and you don’t find about them until it’s too late.

23. Small Batches allow the market to pull you in the right direction.

24. New Customers come from old customers in 4 ways
a. Word of mouth
b. As a side effect of product usage (can I Paypal you the money?)
c. Through funded advertising (take proceeds from custy X, buy ads to attract custy y)
d. Through repeat purchase or use (cable TV, not wedding planning)

25. There are three Engines of Growth. Find which one your business depends on and measure how it’s doing. And yes, more than one could be at work, but focus on the more important one.
a. The Sticky Engine of Growth: measure customer acquisition rate + measure churn rate; measure them separately, or you might not see anything!
b. The Viral Engine of Growth: measure if each customer brings > 1 customer through the door. Don’t despair if it’s 0.9, you’re close, experiment your way to pushing it above 1, but if it’s 0.3 you don’t have that growth model.
c. The Paid Engine of Growth: measure what each customer will spend and measure your acquisition costs.

26. A time comes when you run out of early adopters. Don’t wait until then to make the product that the public at large wants. Moving to a higher quality product will slow you down, but you have no choice. And it will in the long term actually speed you up. The earlier you can afford to go high-quality the better.

27. Use the Five Whys as a guide to improving your quality. Get to the bottom of every complaint / problem by behaving like a 4 year old and responding to the answer to your question “why” with another “why” four more times. You will find that in the end you always end up with a person! Not with a process, not with an inanimate object.

28. Have everybody in the meeting when you do the Five Whys. Otherwise those absent will be blamed.

29. When you find the culprit, take the blame yourself for having designed the wrong process. Save your wrath for when the mistake is repeated.

30. Don’t send your baggage through the Five Whys project. Only use them for problems that arose after you instituted the policy.

31. If you are innovating inside a corporation, it is your job to protect the corporation. Otherwise others will make it their job to thwart you.
0Comment| 41 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 1 July 2017
A must for anyone considering a startup or business venture especially technologists who seem to get obsessed with the awesomeness of an idea to business. Had to read twice whilst keeping notes. The author may come across as a pompous self obsessed douche butbth message conveyed is really important and it is delivered in a simple and clear manner.
0Comment|Was this review helpful to you?YesNoReport abuse
on 22 July 2017
It's quite good.

It's pretty obvious, nothing really radical - which is good in itself.

If you're a startup or considering going down that road, it's worth reading because almost everyone else has and you'll start to feel a bit excluded having not read it...
0Comment|Was this review helpful to you?YesNoReport abuse
on 20 June 2017
Had been recommended this book by a couple of CEO's from start-ups. It's great book when you thinking about starting up something yourself and would definitely recommend everyone to have a read at this before doing so.
0Comment|Was this review helpful to you?YesNoReport abuse
on 3 April 2017
Brilliant book with some great examples a must read for anyone interested in the subject or indeed setting up or running a business of any kind.
0Comment| 2 people found this helpful. Was this review helpful to you?YesNoReport abuse
on 1 October 2013
I'm working on my second company and everything this book says is helping me to drive my business. The methodology that Eric describes are hard to put in practice when you have employees that are used to the "conservative" way of building software. But, with small steps and making the results always on top of any meeting with stakeholders, everyone starts to get it and love it. I recommend to everyone that wants to manage a tech business or wants to build its tech business.
0Comment|Was this review helpful to you?YesNoReport abuse
on 8 March 2017
I like this book a lot as you can extract practical take outs from every subject, some very strong, some less but all well documented.
0Comment| One person found this helpful. Was this review helpful to you?YesNoReport abuse
on 2 April 2017
Excellent book that isn't just for start ups. There are lots of ways estavlished businesses can learn from this book.
0Comment| One person found this helpful. Was this review helpful to you?YesNoReport abuse
on 4 June 2017
A really good book, to understand the start ups enviroment and the agile metodology.
0Comment|Was this review helpful to you?YesNoReport abuse
on 25 January 2016
Probably the most formative business book I have read, cannot recommend it enough.
0Comment|Was this review helpful to you?YesNoReport abuse

Sponsored Links

  (What is this?)