Book Review: The Lean Startup

I have read a number of books over the years particularly in the innovation and entrepreneurship space many of them, turning out to be a disappointment, or nothing more than some apparently successful entrepreneur providing a break down of how they struggled in the beginning then by some stroke of luck mixed in with some considered thinking they were able to unravel what they believe to be a recipe of success.

However, every now and then there comes a book that really opens up your thoughts, provides real value and actually starts to play a vital role in how you start to think about business and innovation. The Lean Startup is one of those books!

Why I read this book

This book was originally recommended to me by a colleague back in 2012, who really spoke highly of its virtues and couldn’t stop praising it. I have to admit, that after the initial purchase I had only halfheartedly read it, dipping in and out of it over a period months. At the time I wasn’t really working on any new business ventures and really had no new ideas to start any.

It was only again in 2016, that I really started to feel my entrepreneurial fires starting to burn again. After spending a few years, helping other startup businesses develop technological solutions to business problems.

Currently, I am hard at work in developing my very own startup! So I have recently re-read this book and if I am honest I re-reading it again and this time making copious notes and constantly referring back to it

What I learned from this book

Eric Ries provides an unusual mix of business practitioner and theorist who writes more convincingly than most academics and less simplistically than most business people. It helps that the book evolved out of his experiences as a technology entrepreneur, which led to numerous invitations to advise all kinds of companies, from start-ups to Fortune 100 enterprises, all struggling with the same problems of starting and building something new.

Ries argues for round after round of small experiments. Entrepreneurs should create a Minimal Viable Product (MVP) as soon as they can and start testing it with consumers. It will be worth a thousand hours of strategising and internal analysis.

Startups should keep testing every aspect of their business models. He is a great fan of repeated split testing , whereby you test slightly different versions of the same product with different groups of customers to see which works best.

This has proved exactly what we need to do to keep our product moving forward. We have chosen to release our product as early as possible. Primarily, due to the fact that the new platform we’re building isgoing to rely on the interaction and engagement of a community. We’re convinced that our concept will succeed but

What I like about this book

Ries is a software developer by trade and his greatest business success has been a company called IMVU, an instant messaging service that allows people to communicate using avatars. He uses his experiences as the basis for the main lessons in The Lean Startup, as well as a rich array of fresh entrepreneurial stories, mostly drawn from the technology industry.

This background very closely resembles mine, and I am able to relate to it. Most of the other books I have read over the years have always seemed to be ghost-writing tales of entrepreneurs in wildly different business sectors and it’s not always been easy to relate.

Ries defines a start-up as a “human institution designed to create a new product or service under conditions of extreme uncertainty ”. A successful start-up does not just rely on a brilliant idea, but also requires managing people through all the challenges of innovation and growth, and through times when the idea will fail

Why I recommend this book

Ries writes clinically and intelligently, without being patronising and blowing his own trumpet. He wishes businesses could innovate with less waste. It is a noble wish and one his book should help fulfil.

Gary Woodfine

Freelance Full Stack Developer at

Helps businesses by improving their technical proficiencies and eliminating waste from the software development pipelines.