Why? Why things that worked with companies such as Toyota would work with BlendZ. The answer wasn't that sophisticated. The context in which BlendZ works around is completely different. By now, the sole fact that it is completely based in a school environment makes a lot of principles irrelevant already. As I read, I noticed I annotated to many ideas. After several chapters, I limited myself to a certain number of annotations, choosing only the ones that were related and we could think about in the context of our startup.
Few times--or maybe none--, one is able to learn something that is directly and fully related to what you want to learn from something as a book that is directed to public in general. No matter what source we get the info from (book, video, etc), we won't find one that teaches us everything we need to know and avoid irrelevant ideas for BlendZ. The only way to do so, is by experience. So in order to prepare for the experience, getting this information is important, obviously having a decent level of analysis that enables you what to focus on deeply because of it's relevancy with your project.
Because of this, through Lean Startup we were able to prepare for some situations and get ideas on possible projects or way of solving problems for BlendZ, but because of our context we actually didn't learn it fully until we had an occasion to test what we learned. Now, not only in BlendZ, I will be aware about the context I am working on and I'll prepare by getting information and analyzing it's relevancy, knowing that I'll always face unpredicted results because of the surroundings of the project I could be working on. Because of this--summing up to a great way of explaining a culture of work and why it is efficient--I am greatly proud of having read this book.