IT Bookworm Blog

Nov 22 2010   9:22PM GMT

Review of “The Jazz Process: Collaboration, Innovation, and Agility” by Adrian Cho



Posted by: Guest Author
Tags:
Adrian Cho
The Jazz Process


Member Jennifer Griffiths agreed to review Adrian Cho’s book, The Jazz Process: Collaboration, Innovation, and Agility. If you’d like to review a book for the Bookworm Blog, send me an e-mail at Melanie at ITKnowledgeExchange.com to express your interest.

Adrian Cho is a professional musician, and also works for IBM, managing the development of software such as the Jazz team collaboration platform.

This book provides the reader with a “process” for making teams successful. Like most people in the working world, I work as part of several teams and collaborate with others on a daily basis.

From this perspective, I found the book useful because it made me more aware of how to be a good team member. For people who want to improve the performance of a team, this book may be particularly helpful.  The premise is that great jazz groups consist of musicians who are fantastic at collaborating, because through years of experience they have learned and honed techniques that succeed in creating great jazz performances.

The book outlines the jazz process so that the reader can apply it to their own situation. Cho makes no apologies for the fact that the book is “inherently abstract” rather than including detailed case studies to illustrate principles. Most of the time when reading the book I found myself thinking about how the principles applied to my experience, which was useful. On the whole, it is not too abstract – there are plenty of mostly short and interesting examples provided from arenas as diverse as sport, the military and business, not just music.

Cho explains that a jazz performance is a good analogy for business because among other things the performance happens in real time, with a very low margin for error. For example, if 99.999% of notes the musicians play sound good, in a performance of 100,000 notes there will be enough bum notes to make the audience boo the performers offstage. Likewise, if 99.999% of mail is delivered on time, in a postal system that moves a million items, hundreds of thousands of items will be lost daily which is unacceptable.

Cho emphasizes that the Jazz Process is misunderstood if viewed as a linear set of steps to be followed one after the other.  With this in mind, the book is nevertheless split into four sections – Working, Collaborating, Executing, and Innovating containing chapters that build upon each other.

The principles in the Working section are: Use Just Enough Rules, Employ top Talent, Put the Team First, Build Trust and Respect, Commit With Passion. I couldn’t find any fault with the principles. For example, Miles Davis’ album Kind of Blue was a successful jazz performance because, among other things, Davis employed top talent.

In the Collaborating section, Cho spends a lot of time outlining Essentials of Execution, including explaining positive and negative feedback loops. For example, a positive feedback loop is when a system has the tendency to move out of balance. This can be good, such as if cost cutting increases profitability, which leads to lower costs and further profitability. This happened to Ford in its years of boom. Or it can be bad, for example if global warming causes ice caps to melt, increasing temperature, causing more ice to melt, increasing temperature more. A negative feedback loop by contrast is when a system tends towards balance. This can be good: I may oversteer my car, and then correct this by steering the opposite way. Or it can be bad, such as if I over-correct the steering wheel to the left, and then over-correct it to the right, back and forth, causing the car to veer from side to side out of control and even crash.  Adrian calls a bad negative feedback loop “hunting.”

I found this section a little on the academic side in both style and content. I was left with a good understanding of the theory, but it wasn’t particularly easy to comprehend, possibly because I struggled to relate my personal experience to the theory.

The rest of the section Collaborating develops on the principles Listen for Change, Lead on Demand, Act Transparently, and Make Contributions Count. These are all principles which, when followed, can help ensure that executing avoids the bad types of positive or negative feedback loops.

The third section, Executing, includes the principles Reduce Friction, Maintain Momentum, and Stay Healthy. As with the first section I did find myself relating the principles to both my personal life and my experience. The final section is all about Innovation. The chapters here are Exchange Ideas and Take Measured Risks.

I found the chapter on exchanging ideas fascinating because I was new to the knowledge Cho presents regarding the relative importance of diversity in technical environments, versus diversity in extended social networks, in relation to both successfully rejecting bad ideas and creating good ideas. Also, Cho’s explanation of the difference between convergent and divergent thinking, including having a team with a diversity of technical experience if you want to make the most of convergent type thinking, and the importance of extended social networks for divergent idea creation was very interesting.

The last principle, Take Measured Risks, is refreshing in that it outlines the risks of implementing each of the Jazz Process Principles. I did find my mind wandering as he went through each principle expounding on its risks, however it is refreshing for a book of this type to be humble enough to not argue that following its principles is the answer to everything. Plus go to the extent of finding issues with the principles.

There is a lot to take in in this book, which is a credit to Cho’s experience and dedication to the Jazz Process which he has elaborated. Furthermore, as someone who works in both music and IT, it does make sense and fit in with my experience, unlike some business books I have read in the past. Overall it is very good. Personally I would like to see a far shorter, more concise and user-friendly version, because in places I found it tough going in and possibly more suited to those of an academic bent.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: