<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Jazz Process</title>
	<atom:link href="http://www.jazzprocess.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jazzprocess.com</link>
	<description>Collaboration, innovation and agility</description>
	<lastBuildDate>Mon, 08 Mar 2010 03:46:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Making repeat collaboration work</title>
		<link>http://www.jazzprocess.com/2010/03/making-repeat-collaboration-work/</link>
		<comments>http://www.jazzprocess.com/2010/03/making-repeat-collaboration-work/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 17:29:31 +0000</pubDate>
		<dc:creator>Adrian Cho</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.jazzprocess.com/?p=226</guid>
		<description><![CDATA[<p>Harvard Business Review editor, Andrew O&#8217;Connell, asks &#8220;Does Repeat Collaboration Really Kill Creativity?&#8221; The short answer is that it can.  Yet as O&#8217;Connell points out, there are collaborations that can remain highly creative for a long time.
</p>
<p>Creativity can be pursued simply for its own sake.  This is often the case in art.  Creativity can also <a href="http://www.jazzprocess.com/2010/03/making-repeat-collaboration-work/">[Read more]</a>]]></description>
			<content:encoded><![CDATA[<p>Harvard Business Review editor, Andrew O&#8217;Connell, asks <em><a href="http://blogs.hbr.org/research/2010/03/if-repeat-collaboration-kills.html" target="_blank">&#8220;Does Repeat Collaboration Really Kill Creativity?&#8221;</a> <span style="font-style: normal;">The short answer is that it can.  Yet as O&#8217;Connell points out, there are collaborations that can remain highly creative for a long time.<span id="more-226"></span><br />
</span></em></p>
<p>Creativity can be pursued simply for its own sake.  This is often the case in art.  Creativity can also be the first step in solving a hard problem.  This application of creativity is innovation and it happens in two phases.  In the first phase the team must generate many possible solutions by leveraging <a href="http://en.wikipedia.org/wiki/Divergent_thinking" target="_blank">divergent thinking</a>.  In the second phase they must select the best of the possible solutions through the process of <a href="http://en.wikipedia.org/wiki/Convergent_thinking" target="_blank">convergent thinking</a>.  What makes creativity and innovation successful is diversity.  The kind of diversity I&#8217;m referring to is that which enables collaborators to contribute to their team&#8217;s pursuits of creativity and innovation.  For a software development team it&#8217;s a diversity of technical experience.  For a basketball team it&#8217;s a diversity of playing experience.  For a jazz ensemble it&#8217;s a diversity of musical ideas and musical elements such as instrumentation and styles of music.  In each case diversity increases the possibility of generating great ideas or solutions while also increasing the success of ruling out the weak possibilities and selecting the best one.</p>
<p>Changing collaborators can be an easy way to increase diversity.  This is why many  jazz musicians are not content to always play with the same people.  They will constantly search for new collaborators, inviting them to perform as guest artists with their existing ensembles or engaging with them in new ensembles.  The most creative jazz musicians will make it a point to work with musicians who have instruments, playing styles and musical approaches that differ from their own.  They will even collaborate with artists in other disciplines such as dance and the visual arts.  It&#8217;s also entirely possible to get the same diversity with a constant set of collaborators if those people are open to new ideas.  Good jazz musicians are constantly listening.  They do this not just on the bandstand but by listening to live performances and recordings.  They absorb it all and incorporate what they like into their playing.  Effective software developers are constantly learning about new technologies and techniques.  They benefit greatly from studying other solutions and prototyping their own.</p>
<p>Having great ideas is not the only ingredient for success.  You must be able to put them into practice.  A great basketball player not only knows lots of different plays but can execute them.  The downside of changing collaborators is that you can lose the synergy that a strong team has developed.  Every time you bring someone new into the mix you have to take several steps backwards, rebuilding the trust that is necessary to enable a team to take risks without compromising the health of their activity.  The ideal situation is one in which you can establish a strong team of people who are open to constantly learning through an exchange of ideas.  Such a team can continue innovating over the long term.  It&#8217;s good to spice things up from time to time by introducing new collaborators either temporarily or permanently but you don&#8217;t have to find a whole new team to work with if you&#8217;ve got the right people.  As always, people are more important than process.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jazzprocess.com/2010/03/making-repeat-collaboration-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Be humble.  Always seek to improve.</title>
		<link>http://www.jazzprocess.com/2010/02/be-humble-always-seek-to-improve/</link>
		<comments>http://www.jazzprocess.com/2010/02/be-humble-always-seek-to-improve/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 13:16:48 +0000</pubDate>
		<dc:creator>Adrian Cho</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.jazzprocess.com/?p=217</guid>
		<description><![CDATA[<p>I thoroughly enjoyed this short Harvard Business Review blog post detailing some of the lessons that can be learned from snowboarding sensation Shaun White.  While people are all different, there are many ties that bind us together.  More specifically, while we all work and play in a wide variety of domains there are principles that <a href="http://www.jazzprocess.com/2010/02/be-humble-always-seek-to-improve/">[Read more]</a>]]></description>
			<content:encoded><![CDATA[<p>I thoroughly enjoyed this short <a href="http://blogs.hbr.org/cs/2010/02/lessons_from_the_halfpipe.html" target="_blank">Harvard Business Review blog post</a> detailing some of the lessons that can be learned from snowboarding sensation <a href="http://www.shaunwhite.com/" target="_blank">Shaun White</a>.  While people are all different, there are many ties that bind us together.  More specifically, while we all work and play in a wide variety of domains there are principles that are universally applicable.  We all deal collectively with many of the same fundamental problems.  It’s just our contexts that differ.  While it’s natural to look towards fellow disciples when seeking solutions to the problems we encounter in our work, I’ve found that some of the best inspiration can come from people working in completely different disciplines.<span id="more-217"></span></p>
<p>The point in the article that really resonated for me was the importance of being humble.  Author Vijay Govindarajan wrote: <em>&#8220;The more humble you are, the more you know what you don&#8217;t know; you seek to learn.&#8221;</em> Great performers constantly improve their processes in the pursuit of higher levels of performance.  They do it not just because they are forced to respond to change but simply because they want to improve.  In reviewing their performance in retrospect, people only need ask themselves such simple questions as “What worked well?”, “What didn&#8217;t work well?” and “How can we do better or avoid those problems in the future?”  Software development teams can perform such retrospectives at the conclusion of an iteration or after reaching a particular milestone.  Jazz musicians are constantly trying to improve their level of performance and their process of playing and engaging with others.  They will ask themselves such questions as “How can I play more in tune?”, “How can I ‘lock in’ better with everyone else?” and “How can I make my solo more engaging or meaningful?”  This process of continuous improvement is so automatic that the musicians often don’t realize they are doing it.  The same is true of any performance athlete such as the pitcher on the mound who is thinking about what he or she can do differently to get that next ball past the batter and into the catcher’s mitt.  As Govindarajan points out, this process begins with having the humility to accept that you can do better.</p>
<p>When people dedicate themselves to giving their best and then constantly improving each performance, they are capable of not only delivering great results once but again and again, even in the face of changing conditions.  In sports, just as in the arts and in business, the truly successful people are not the “one hit wonders” that deliver a single great performance but those that deliver repeatedly with consistent results.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jazzprocess.com/2010/02/be-humble-always-seek-to-improve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Discussion of Jazz Process on NPR Jazz Blog</title>
		<link>http://www.jazzprocess.com/2010/02/discussion-of-jazz-process-on-npr-jazz-blog/</link>
		<comments>http://www.jazzprocess.com/2010/02/discussion-of-jazz-process-on-npr-jazz-blog/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 17:18:57 +0000</pubDate>
		<dc:creator>Adrian Cho</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.jazzprocess.com/?p=214</guid>
		<description><![CDATA[<p>There&#8217;s an interesting discussion of the Jazz Process on the NPR Jazz blog prompted by the recent Dr. Dobb&#8217;s article.</p>
]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s an <a href="http://www.npr.org/blogs/ablogsupreme/2010/02/how_jazz_can_improve_your_busi.html" target="_blank">interesting discussion of the </a><em><a href="http://www.npr.org/blogs/ablogsupreme/2010/02/how_jazz_can_improve_your_busi.html" target="_blank">Jazz Process</a> </em>on the NPR Jazz blog prompted by the recent <a href="http://www.drdobbs.com/architect/222900758" target="_blank">Dr. Dobb&#8217;s article</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jazzprocess.com/2010/02/discussion-of-jazz-process-on-npr-jazz-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What can software developers learn from jazz musicians?</title>
		<link>http://www.jazzprocess.com/2010/02/what-can-software-developers-learn-from-jazz-musicians/</link>
		<comments>http://www.jazzprocess.com/2010/02/what-can-software-developers-learn-from-jazz-musicians/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 17:58:07 +0000</pubDate>
		<dc:creator>Adrian Cho</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.jazzprocess.com/?p=196</guid>
		<description><![CDATA[<p>Here&#8217;s a link to an article that I wrote for Dr. Dobb&#8217;s, a software development magazine that is now an insert in InformationWeek:  What can software developers learn from jazz musicians? Trying to describe the Jazz Process in 1500 words was a challenge.  I couldn&#8217;t really get into much detail but I think the article <a href="http://www.jazzprocess.com/2010/02/what-can-software-developers-learn-from-jazz-musicians/">[Read more]</a>]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a link to an article that I wrote for Dr. Dobb&#8217;s, a software development magazine that is now an insert in InformationWeek:  <a href="http://www.drdobbs.com/architect/222900758" target="_blank">What can software developers learn from jazz musicians?</a> Trying to describe the <em>Jazz Process</em> in 1500 words was a challenge.  I couldn&#8217;t really get into much detail but I think the article hits the important points.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jazzprocess.com/2010/02/what-can-software-developers-learn-from-jazz-musicians/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Let&#8217;s jam</title>
		<link>http://www.jazzprocess.com/2009/12/lets-jam/</link>
		<comments>http://www.jazzprocess.com/2009/12/lets-jam/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 18:43:00 +0000</pubDate>
		<dc:creator>Adrian Cho</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.jazzprocess.com/blog/?p=53</guid>
		<description><![CDATA[<p style="text-align: justify;">This site is dedicated to an exploration and discussion of collaborative excellence.  Specifically, how do high-performance teams innovate and respond with agility to changing conditions and the unexpected?  My research and personal experiences in the arts as a leader, conductor and jazz bassist and in business as a software developer and manager have shown <a href="http://www.jazzprocess.com/2009/12/lets-jam/">[Read more]</a>]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify;">This site is dedicated to an exploration and discussion of collaborative excellence.  Specifically, how do high-performance teams innovate and respond with agility to changing conditions and the unexpected?  My research and personal experiences in the arts as a leader, conductor and jazz bassist and in business as a software developer and manager have shown me that the practices employed by successful teams are widely applicable.  Whether it&#8217;s performing jazz, playing basketball, developing software, or executing business, political or military strategies, there are specific actions that can make or break a team&#8217;s collective efforts to succeed.  The <em><a href="the-jazz-process/">Jazz Process</a></em> specifies fourteen best principles that I believe are worth focusing on.  Yet there is so much more that&#8217;s important and worth exploring.  I&#8217;ve been fascinated with the concepts of collaboration, innovation and agility for as long as I can remember and I&#8217;m always eager to learn more and to share my own experiences.  To that end I&#8217;ve taken a few steps toward facilitating and contributing to an ongoing discourse on these topics.  Firstly I have started this new blog - you&#8217;re reading the opening post now.  I am finalizing a <a href="the-book">book</a> that has taken over a year of my &#8220;spare&#8221; time and I am glad to say it should be published sometime in early 2010.  I am also hoping to post jazz performance videos that will support the book and the blog and forum discussions.  I hope you&#8217;ll be inclined to read, watch, listen, comment and/or discuss and I look forward to exchanging experiences, ideas and opinions with you.</p>
<p>Cheers</p>
<p>Adrian</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jazzprocess.com/2009/12/lets-jam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
