Tough technology and business challenges face you at every stage of a project. The one-page ingredients in 101 Design Ingredients show you how to solve problems using practical examples you can apply right away. Case studies explain how leading companies combined these ingredients into their own unique recipes to catapult their businesses, and how you can too.
It seems that a lot of the time organisations have become complacent when it comes to solving big tech problems. Often we are seen firefighting, readily opting for a quick solution to pacify our customers.
Companies are in competition with each other, and the pressure means that they fail to invest in researching the right technology and capitalising on great opportunities.
In this book, the author Eewei Chen presents the readers with an insight on how to approach a problem in order to resolve it. He takes the reader back to the basics and some of what he discusses is obvious to those familiar with problem solving. However, his delivery of his ideas will get the readers thinking again of the various ingredients out there to be used for problem solving.
These ingredients are not limited and therefore inspire the readers to be brave to adopt or adapt them to improve and attain success of the business, project or team relationships.
The book is divided into five parts, with the first four corresponding to the stages of a project. The final part is dedicated to real case studies, including one on Google, which has innovated and managed to stay ahead, adapting to changing demands.
This is a factual and easy-to-read book that will give the reader inspiration to tackle problems. The book is well written with useful links, quotes and interesting illustrations.
The book scores 9/10 in terms of content and value for money as it reinforces the need to solve an issue by getting to the root cause and not just firefighting.
Reviewed by Uma Kanagaratnam MBCS, Senior Product Support Specialist
The book is a light read of what the author calls ingredients for success he has learned from all his years of experience, as well as ones you can grasp by following successful companies. Each recipe has illustrative art, a quote, the problem, and bullet point solutions. Each recipe is only few pages. It is meant to be quick frequent read and a reference.
But I feel it has been oversimplified that it ended up being nothing more than general lessons, most of which you may already know, and with little material behind to support it, I didn't feel it was adding a lot to my knowledge. I won't say there are no good lessons to grab from the book, but it's not a book I would say is too valuable to miss. It is mostly useful to those who are just starting and didn't have too much experience yet.
Probably useful to go through or use in brainstorming when you have a very very high-level problem to solve: choose a direction of the company, make big product decisions, get an idea where do you stand culturally.
I couldn't relate to most of the “solutions”, but I enjoyed the problems and their definitions.
I've got mixed feelings out of this book. On the one hand, the book contains a lot of very obvious information (at least to me, but I've been "in the tech business for over 20 years), on the other hand, there are quite a few small hidden gems of usefull knowledge in there. There was enough useful information to keep me reading, although it did take me a while to finish the book.
I can imagine that this book is really interesting especially for those that have not yet been in the tech business for as long as I have.
The author makes it really hard for the reader to read: a lot of external references (more than 300) and many are central to understanding, but other thank a link there is no hint to what they mean.
I think this book is for those that already know its contents, but there is no depth to appeal to them either.