<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.9.2 (http://www.squarespace.com/) on Fri, 12 Mar 2010 11:28:56 GMT--><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><title>Business Collaboration Journal</title><subtitle>Business Collaboration Journal</subtitle><id>http://www.collaborativeye.com/collaboration_journal/</id><link rel="alternate" type="application/xhtml+xml" href="http://www.collaborativeye.com/collaboration_journal/"/><link rel="self" type="application/atom+xml" href="http://www.collaborativeye.com/collaboration_journal/atom.xml"/><updated>2009-09-16T20:44:08Z</updated><generator uri="http://www.squarespace.com/" version="Squarespace Site Server v5.9.2 (http://www.squarespace.com/)">Squarespace</generator><entry><title>Questions to ask (and answer) before your small business jumps onto Twitter or Facebook</title><category term="Social Media"/><category term="Twitter for Small Business"/><id>http://www.collaborativeye.com/collaboration_journal/questions-to-ask-and-answer-before-your-small-business-jumps.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/questions-to-ask-and-answer-before-your-small-business-jumps.html"/><author><name>Dave Kresta</name></author><published>2009-09-16T20:31:58Z</published><updated>2009-09-16T20:31:58Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Getting started with Social Media is so easy, you may be tempted to fire and then aim. This is a BAD IDEA. Here are some questions I've developed to help businesses think through their goals and target audience prior to jumping onto Twitter or Facebook.</p>
<p><strong>#1 </strong><strong>What would you like to achieve with your Social Media program? (choose top 5 and rank in order of importance):<br /></strong></p>
<ul>
<li>Building and promoting brand</li>
<li>Increasing customer engagement</li>
<li>Improving collaboration and communication</li>
<li>Promoting thought leadership</li>
<li>Networking</li>
<li>Marketing/Sales campaigns</li>
<li>Generate revenues</li>
<li>Customer service/support</li>
<li>Help with product development/market feedback</li>
<li>Recruit and retain talent</li>
<li>Generate ideas/innovation</li>
</ul>
<p><strong>#2 Community engagement: Choose the <span style="text-decoration: underline;">top 3</span> and rank importance for how you would like to engage with your community:</strong></p>
<ul>
<li>Corporate Voice ( speak to your market)</li>
<li>User-generated content (create excitement)</li>
<li>Enthusiasts (stimulate a passion around a topic, activity, or hobby)</li>
<li>Associates/subscribers (engage with members)</li>
<li>Loyalty (build and reward loyalty among most loyal customers)</li>
<li>Peer Support (help each other)</li>
<li>Events (build and sustain buzz around specific events)</li>
<li>Innovate (generate ideas)</li>
</ul>
<p><strong>#3 </strong><strong>List top 10 keywords/phrases that your audience would be interested in</strong></p>
<p><strong>#4 Who are the top 5 thought leaders and influencers your audience respects?</strong></p>
<p><strong>#5 </strong><strong>What web sites, magazines, and blogs does your audience interact with? </strong></p>
<p>Thinking about and answering these questions will give you a solid footing on which to build a social media strategy for your business.</p>]]></content></entry><entry><title>Twitter myths for small business: Part II</title><category term="Social Media"/><category term="Twitter"/><category term="Twitter for Small Business"/><id>http://www.collaborativeye.com/collaboration_journal/twitter-myths-for-small-business-part-ii.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/twitter-myths-for-small-business-part-ii.html"/><author><name>Dave Kresta</name></author><published>2009-09-11T17:17:49Z</published><updated>2009-09-11T17:17:49Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>In part 1 we exposed the myth that people just want to buy things from you. Let's continue exploring the Twitter myths prevalent in the USA Today <a href="http://www.usatoday.com/money/smallbusiness/columnist/strauss/2009-04-06-twitter-entrepreneurs_N.htm">article</a> by Steve Strauss that may be keeping some of you from trying Twitter for your small or medium sized business.</p>
<p><strong>Myth #2: Twitter offers too much information.</strong> This is a common argument against the use of Twitter: "Who wants to hear about what you are having for lunch or if you are having a bad hair day." True. But nobody that I follow (for long) offers this type of information, and neither should you. Much has been made of a recent <a href="http://www.pearanalytics.com/wp-content/uploads/2009/08/Twitter-Study-August-2009.pdf">study</a> that found 40% of Tweets are meaningless babble. I expect this will change over time as people learn how to better use Twitter, and as people find that nobody is listening to their meaningless babble.</p>
<p><strong>Myth #3: It takes too much time.</strong> OK, I sort of agree with this one, so maybe calling it a myth is not quite right. However, as with anything in business, you have to invest in order to get a return. The important thing with Twitter is to not enter aimlessly, and then be frustrated that you aren't seeing a return on your time investment. This means a strategic review and assessment should be done BEFORE you start using Twitter, to determine what your business's overall goals are and how Twitter can possibly meet those goals. Also, there are methods to automate some of the tasks involved in using Twitter (automated feeds from your blog or other interesting news sources, for example). Finally, some Twitter outsourcing services are popping up where you can pay somebody to manage your Twitter activity for you.</p>
<p><strong>Myth #4: 140 characters is not enough to be meaningful. </strong>This one is SO WRONG. The beauty of Twitter is that it forces you to be succinct. Also, the most valuable Tweets are actually summaries and pointers to additional information on a blog or other website. If you have more to say than can be captured in 140 characters, then write a blog entry and use Twitter to capture interest and exposure for your blog entry.</p>
<p><strong>Bottom line?</strong> Twitter is a tool, and like all tools, it can be used successfully, and unsuccessfully. Also, it is an emerging business tool, so we can expect some false starts (like the 40% babble) that will likely soon get corrected. Start with an assessment of your objectives, and then start using Twitter. Don't let myths like those I've exposed above get in your way.</p>]]></content></entry><entry><title>Twitter myths for small business</title><category term="Social Media"/><category term="Twitter"/><category term="Twitter for Small Business"/><category term="loyalty"/><id>http://www.collaborativeye.com/collaboration_journal/twitter-myths-for-small-business.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/twitter-myths-for-small-business.html"/><author><name>Dave Kresta</name></author><published>2009-09-10T04:31:35Z</published><updated>2009-09-10T04:31:35Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>USA Today had an <a href="http://www.usatoday.com/money/smallbusiness/columnist/strauss/2009-04-06-twitter-entrepreneurs_N.htm">article</a> earlier this year that showcased some Twitter myths that are confusing a lot of people. While Steve Strauss is undoubtedly an expert, and right for applying a healthy skepticism to "Twitter snake oil", he is dead wrong on a number of things.</p>
<p><strong>Twitter small business myth #1: "'People just want to buy things from you."</strong></p>
<p>OK sure, when I go to the local drug store for antacid, I want to buy it and leave. But I can buy that antacid anywhere -- I have no loyalty to one place or another. If you want to build loyalty, you need to provide people more than a transaction. Maybe it is a smile, or extra help getting stuff to your car, or your small business's involvement in the local community. These are the things that create loyalty. How can Twitter build loyal customers? There are many possibilities, and many are still emerging.&nbsp; For example, let's say you run a local bakery (which Steve would probably say is not a candidate for Twitter usage). Why not build a following of people who are interested in baking tips? Things you've learned through the school of hard knocks. Share ideas for recipes, special ingredients, or tricks. Maybe even give out some of your recipes (gasp!) People who love baked goods will look forward to your Tweets. And you can be sure they will be thinking of you when they crave a luscious cinnamon roll!</p>
<p>Another example is a local coffee shop (another business Steve says is not a candidate for Twitter). WRONG! People who go to coffee shops, wait for it, LOVE coffee. I can identify with this one. I like to learn about different types of coffee, tips on brewing, trivia on coffee, etc. I would love to follow a coffee shop that gives out tweets like these. You don't need to be a marketing whiz to figure out that if somebody is exposed to your business brand often, they are more likely to visit and purchase something from it.</p>
<p>Next: more small business twitter myths including Too much information, Too much time, and 140 chars is not enough.</p>
<p>&nbsp;</p>]]></content></entry><entry><title>Effective Communication</title><category term="Communication"/><id>http://www.collaborativeye.com/collaboration_journal/effective-communication.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/effective-communication.html"/><author><name>Dave Kresta</name></author><published>2008-08-22T03:53:59Z</published><updated>2008-08-22T03:53:59Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Here is a blog post constructed exclusively from 10 tweets on Twitter. If you are a Twitter user, follow <a href="http://www.twitter.com/davekresta">me</a>!&nbsp;</p>
<p>------------------------------------------------------</p>
<div class="desc hentry">
<p class="entry-title entry-content"><span class="entry-content">Luntz's <a href="http://www.amazon.com/Words-That-Work-What-People/dp/1401302599/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1219378042&amp;sr=1-1">Words That Work</a>. Ignore the partisanship: powerful stuff on effective communication. His 10 rules are gems (I break them often).</span></p>
<table id="timeline" class="doing" border="0" cellspacing="0">
<tbody>
<tr id="status_895096842" class="hentry">
<td class="content"><span class="entry-content"> Rule 1. Simplicity: Use Small Words. How about "wrong name" instead of "misnomer"<br /><br /></span><span class="meta entry-meta"> </span></td>
</tr>
</tbody>
</table>
<p class="entry-title entry-content"><span class="entry-content">Rule 2: Use Short Sentences. Instead of overly complex and wordy constructions, stick with simpler, easier to understand sentences, thereby</span></p>
<p class="entry-title entry-content"><span class="entry-content">Rule 3: Credibility is as Important as Philosophy. These tweets will change your life, and make you a superior communicator like I.</span></p>
<table id="timeline" class="doing" border="0" cellspacing="0">
<tbody>
<tr id="status_895118139" class="hentry">
<td class="content"><span class="entry-content"> Rule 4: Consistency Matters. Consistency Matters. Consistency Matters. Consistency Matters. Consistency Matters.</span><span class="meta entry-meta"><a class="entry-date" rel="bookmark" href="http://twitter.com/davekresta/statuses/895118139"><abbr class="published" title="2008-08-22T03:23:59+00:00"></abbr></a> </span></td>
</tr>
</tbody>
</table>
<table id="timeline" class="doing" style="width: 640px; height: 17px;" border="0" cellspacing="0">
<tbody>
<tr id="status_895120146" class="hentry">
<td class="content"><span class="entry-content"> <br />Rule 5: Novelty - Offer Something New. Tell me something I don't know. Like these 10 rules</span><span class="meta entry-meta"><a class="entry-date" rel="bookmark" href="http://twitter.com/davekresta/statuses/895120146"><abbr class="published" title="2008-08-22T03:26:40+00:00">.</abbr></a><br /><br /></span>
<table id="timeline" class="doing" border="0" cellspacing="0">
<tbody>
<tr id="status_895128018" class="hentry">
<td class="content"><span class="entry-content"> Rule 6: Sound and Texture Matter: How about "Nyuck, nycuk, nycuk", "Porky Pig", or "Ba Boom"!</span><span class="meta entry-meta"><a class="entry-date" rel="bookmark" href="http://twitter.com/davekresta/statuses/895128018"><abbr class="published" title="2008-08-22T03:37:14+00:00"></abbr></a> </span></td>
</tr>
</tbody>
</table>
<br />
<table id="timeline" class="doing" border="0" cellspacing="0">
<tbody>
<tr id="status_895133394" class="hentry">
<td class="content"><span class="entry-content"> Rule 7: Speak Aspirationally. You have great things to say, and now you can say them clearly and confidently.</span><span class="meta entry-meta"><a class="entry-date" rel="bookmark" href="http://twitter.com/davekresta/statuses/895133394"><abbr class="published" title="2008-08-22T03:44:25+00:00"></abbr></a> </span></td>
</tr>
</tbody>
</table>
<br /></td>
</tr>
</tbody>
</table>
<table id="timeline" class="doing" border="0" cellspacing="0">
<tbody>
<tr id="status_895135111" class="hentry">
<td class="content"><span class="entry-content"> Rule 8: Visualize. Imagine a crowd of 1500 giving a standing ovation to your next presentation.</span><span class="meta entry-meta"><a class="entry-date" rel="bookmark" href="http://twitter.com/davekresta/statuses/895135111"><abbr class="published" title="2008-08-22T03:46:37+00:00"></abbr></a> </span></td>
</tr>
</tbody>
</table>
<br />
<table id="timeline" class="doing" style="width: 575px; height: 23px;" border="0" cellspacing="0">
<tbody>
<tr id="status_895135886" class="hentry">
<td class="content"><span class="entry-content"> Rule 9: Ask a Question. What will you do to become a better communicato</span><span class="meta entry-meta"> </span></td>
</tr>
</tbody>
</table>
<br />
<p class="entry-title entry-content">Rule 10: Provide Context and Explain Relevance. We have all been misunderstood. Now let's take control of our communication!</p>
<div style="float: right; margin-top: -5px;">
<div id="status_actions_895144198" class="status_actions"><a onclick="new Ajax.Request('/favourings/create/895144198', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895144198').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></div>
</div>
</div>
<table id="timeline" class="doing" style="width: 575px; height: 126px;" border="0" cellspacing="0">
<tbody>
<tr id="status_895135886" class="hentry">
<td class="content"></td>
<td width="10" align="right">
<div id="status_actions_895135886" class="status_actions"><a onclick="new Ajax.Request('/favourings/create/895135886', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895135886').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></div>
</td>
</tr>
<tr id="status_895135111" class="hentry">
<td class="content"></td>
<td width="10" align="right">
<div id="status_actions_895135111" class="status_actions"><a onclick="new Ajax.Request('/favourings/create/895135111', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895135111').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></div>
</td>
</tr>
<tr id="status_895133394" class="hentry">
<td class="content"></td>
<td width="10" align="right">
<div id="status_actions_895133394" class="status_actions"><a onclick="new Ajax.Request('/favourings/create/895133394', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895133394').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></div>
</td>
</tr>
<tr id="status_895128018" class="hentry">
<td class="content"></td>
<td width="10" align="right">
<div id="status_actions_895128018" class="status_actions"><span class="full-image-inline"><span><a onclick="new Ajax.Request('/favourings/create/895128018', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895128018').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></span></span></div>
</td>
</tr>
<tr id="status_895120146" class="hentry">
<td class="content"></td>
<td width="10" align="right">
<div id="status_actions_895120146" class="status_actions"><a onclick="new Ajax.Request('/favourings/create/895120146', {asynchronous:true, evalScripts:true, onLoading:function(request){$('status_star_895120146').src='/images/icon_throbber.gif'}, parameters:'authenticity_token=' + encodeURIComponent('4114a4522b6bb4360b88e2f12b0737a87106f735')}); return false;" href="http://twitter.com/davekresta#"><br /></a></div>
</td>
</tr>
<tr id="status_895118139" class="hentry">
<td class="content"></td>
<td width="10" align="right"><br /></td>
</tr>
<tr id="status_895110065" class="hentry">
<td class="content"></td>
<td width="10" align="right"><br /></td>
</tr>
<tr id="status_895098497" class="hentry">
<td class="content"></td>
<td width="10" align="right"><br /></td>
</tr>
<tr id="status_895096842" class="hentry">
<td class="content"></td>
<td width="10" align="right"><br /></td>
</tr>
<tr id="status_895078095" class="hentry">
<td class="content"></td>
</tr>
</tbody>
</table>]]></content></entry><entry><title>Crossing the Chasm (again) with New Relevance</title><category term="Collaboration and Innovation"/><id>http://www.collaborativeye.com/collaboration_journal/crossing-the-chasm-again-with-new-relevance.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/crossing-the-chasm-again-with-new-relevance.html"/><author><name>Dave Kresta</name></author><published>2008-07-10T15:57:38Z</published><updated>2008-07-10T15:57:38Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>I am working my way through a book I haven't read in literally a decade - Geoffrey Moore's <a href="http://en.wikipedia.org/wiki/Crossing_the_Chasm" target="_blank" class="offsite-link-inline">Crossing the Chasm</a>. If you have never read this book, stop what you are doing, go to the nearest bookstore, buy it, and READ IT! I'm not going to give a book review, but if you promise to read it, I'll give you a two sentence summary: High tech products follow a Technology Adoption Curve with distinct customer segments comprised of Innovators, Early Adopters, Early Majority, Late Majority, and Laggards. There are gaps between these segments, but a large chasm from Early Adopters to the mainstream Early Majority segment. How to cross that chasm is the subject of the book.</p><p>Why rehash this today? Aside from the fact that the Technology Adoption Curve still holds, I believe the social media/social networking phenomenon has a huge roll to play in helping products cross the chasm. The book was written in 1991, when &quot;social&quot; was more closely associated with Karl Marx or ice cream than technology.&nbsp; A key to getting the Early Majority segment to adopt your product is to appeal to the pragmatic bent of these types of consumers. They don't care about the technology, but want to know how it can improve what they are doing, today, right now. They want to know other people's experiences, and would rather hear from them than a slick sales person or a flashy vendor demo. In the past, this meant putting together a case study or &quot;success story&quot; on whatever meager evidence was available and leaving it behind in the hopes that it would be enough to push the prospect to a &quot;yes&quot;. Fast forward to today... connect your prospects in an online community with existing customers. Let them ask questions, or read posts on real customer experiences. Scary? Yes, but oh so much more believable and relevant. </p><p>Many companies have&nbsp; implemented customer communities, but these are typically private and isolated. Who do you know that is breaking the mold and opening up these conversations to prospects and other &quot;outsiders?&quot; Let me know and I'll summarize.<br /></p><p>&nbsp;</p>]]></content></entry><entry><title>All's Well with Groundswell</title><category term="Collaboration Culture"/><category term="ROI of Collaboration"/><id>http://www.collaborativeye.com/collaboration_journal/alls-well-with-groundswell.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/alls-well-with-groundswell.html"/><author><name>Dave Kresta</name></author><published>2008-05-05T00:01:13Z</published><updated>2008-05-05T00:01:13Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Not another book on the power of social networking. Pleeeaaase. But I went ahead and bought a copy of <a class="offsite-link-inline" target="_blank" href="http://www.forrester.com/Groundswell/index.html">Groundswell</a> anyways. I would characterize this as an &quot;evidence and endorsement&quot; book for social and collaborative technologies, rather than a visionary or revolutionary book. But that can be a good thing. Li and Bernoff base the book on case studies, practical advice, and even ROI CALCULATIONS. These calculations alone (actually the methodology behind the calculations) make this a highly recommended book. Yes you can determine ROI numbers for social networking applications!</p><p>The POST (People, Objectives, Strategy, Technology) planning process described in the book is a very usable, and smart approach. Among the various insights that derive from this      , I believe two stand out:</p><p>1) <strong>Solve your customers' problem, not yours</strong>.&nbsp; How many times have you been in a planning session where the situation analysis focused on the challenges and strategic objectives of <u>the company</u>? Of course the customer needs are incorporated LATER into the process. Be honest -- you've probably led a few of these sessions yourself.&nbsp; Li and Bernoff challenge us to start with the customer -- what would they get out of a community, for example? How can a blog help your customers or prospects? This advice is wise, obvious, and usually ignored. Added benefit: it can also be applied to business decisions far beyond social technologies. <br /> </p><p>2) <strong>Start small, build successes one at a time.</strong> This is not about technology. It is about culture change. It is about re-visioning your relationships with customers. It is about getting buy-in from all levels of an organization. These things take time. Li and Bernoff describe several cases where companies built successful social-based strategies over a period of years, usually starting with something that was very focused, and didn't require corporate-wide endorsement. This advice may seem overly simplistic, but it is easy to fall into the &quot;got to hit a home run, NOW&quot; trap, especially if you feel pressure to catch up with everybody else. </p><p>Near the end of the book, Li and Bernoff touch on the issue of short-term, reactionary behavior verses long-term strategies. Some (not the authors) may view the hyper-responsive, close-in contact with individuals that social networking enables, as at odds with long term planning. Some believe, erroneously in my opinion, that with social technologies, products and services will just design themselves. Yes there is a place for customer involvement in the design and development process, and yes many companies have isolated this process from the customer. But there is still a need for product road maps, requirements gathering and synthesis, forecasting, and other long-term planning exercises. Truly connecting to the &quot;groundswell&quot; will enable you to react quickly, and to feel your customers' pain and understand their goals and desires -- things that have always been necessary to run a successful, long-term business.<br /></p><p>&nbsp;</p>]]></content></entry><entry><title>Learning to Ride a Bike with Enterprise 2.0</title><category term="Collaboration Culture"/><category term="Collaborative Leadership"/><category term="Collective Intelligence"/><id>http://www.collaborativeye.com/collaboration_journal/learning-to-ride-a-bike-with-enterprise-20.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/learning-to-ride-a-bike-with-enterprise-20.html"/><author><name>Dave Kresta</name></author><published>2008-04-27T22:56:40Z</published><updated>2008-04-27T22:56:40Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>Why aren't there any books on how to ride a bike? (OK -- I found one on Amazon, but work with me...) You can read and learn from books on molecular biology, cost accounting, and computer programming, so why not something as simple as learning to ride a bicycle? The truth is, you don't really KNOW how to ride a bike, until you've been on it, fallen off a few times, and become personally engaged with the bike. Philosopher <span class="f">Michael Polanyi called this "<a mce_real_href="http://books.google.com/books?id=wZ9SEf7NpO4C&amp;dq=personal+knowledge&amp;pg=PP1&amp;ots=kLaZzTdv1o&amp;sig=EnpYda_WEDONT-PRcSlxFOUYp7E&amp;hl=en&amp;prev=http://www.google.com/search?q=personal+knowledge&amp;ie=utf-8&amp;oe=utf-8&amp;rls=org.mozilla:en-US:official&amp;client=firefox-a&amp;sa=X&amp;oi=print&amp;ct=title&amp;cad=one-book-with-thumbnail#PPP1,M1" class="offsite-link-inline" target="_blank" href="http://books.google.com/books?id=wZ9SEf7NpO4C&amp;dq=personal+knowledge&amp;pg=PP1&amp;ots=kLaZzTdv1o&amp;sig=EnpYda_WEDONT-PRcSlxFOUYp7E&amp;hl=en&amp;prev=http://www.google.com/search?q=personal+knowledge&amp;ie=utf-8&amp;oe=utf-8&amp;rls=org.mozilla:en-US:official&amp;client=firefox-a&amp;sa=X&amp;oi=print&amp;ct=title&amp;cad=one-book-with-thumbnail#PPP1,M1">Personal Knowledge</a>" in his ground breaking book of the same title back in 1958. Fast forward 50 years to several <a mce_real_href="http://tools.cisco.com/dlls/tln/page/research/detail/rs/2005/interactions" href="http://tools.cisco.com/dlls/tln/page/research/detail/rs/2005/interactions" target="_blank" class="offsite-link-inline">McKinsey studies</a> in which three types of knowledge interactions as posited: transformational, transactional, and tacit. Transformational interactions change raw materials into finished goods; transactional interactions involve knowledge which can be codified and explained as a process or set of steps (e.g closing the books for the month, or entering sales data into a CRM system). Tacit interactions, on the other hand, are much more complex, ambiguous, and involve what Polanyi called personal knowledge. Tacit knowledge requires judgement, context, and interaction with others to determine the best solution. For example, how should you respond to an irate customer? What features should be included in the next release of product X? Which logo treatment is best? What investment fund is most appropriate for this customer?<br> </span></p><p>McKinsey research indicates that 70% of all jobs created since 1998 involve tacit knowledge interactions as their primary component. However, only 24% of software spending is aimed at improving tacit knowledge interactions! No wonder we feel that we are getting further behind even though we have more and more technology at our disposal!</p><p>The implications of tacit knowledge on business cannot be overstated. Organizations which successfully improve the productivity and effectiveness of their tacit knowledge workers will be able to build competitive advantage which will be difficult for others to copy. There will be no "play book" to copy -- rather the competitive advantage is built into the tacit interactions between employees, customers, partners and the ability to innovate and come to the right solution to a problem more quickly.&nbsp; How can business leaders improve their organization's tacit knowledge effectiveness?  </p><p>1) By providing the tools where interactions and collective knowledge are encouraged and preserved.&nbsp; Technology examples include collaboration platforms such as blogs, wikis, instant messaging, knowledge management platforms, etc. The goal is to make collaboration&nbsp; so simple and pain free that it increases meaningful, shared communication dramatically. And no, email is obviously not the answer. </p><p>2) Exploring communication platforms that can capture experience, context, and nuanced judgement more successfully than stand-alone text. For example, listening to a set of successful conversations between a customer service rep and an irate customer may be much more effective than reading a 10 page paper on customer service protocol. Or another example, providing tutorials on the use of a CRM system which show exactly how to perform an operation, complete with screen recordings, and audio narration discussing possible exceptions, alternate approaches, and considerations. &nbsp;&nbsp; </p><p>3) Clear the decks for more tacit knowledge interaction by reducing the burden of transactional interactions. Very little time should be spent learning how to fill out an expense form or learning how to run a monthly report in the ERP system. Companies must provide focused, on-demand learning that provides employees with transactional knowledge when and where they need it. </p>]]></content></entry><entry><title>Designing a Collaborative Company from the Ground Up</title><category term="Collaboration and Innovation"/><id>http://www.collaborativeye.com/collaboration_journal/designing-a-collaborative-company-from-the-ground-up.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/designing-a-collaborative-company-from-the-ground-up.html"/><author><name>Dave Kresta</name></author><published>2008-03-12T23:33:42Z</published><updated>2008-03-12T23:33:42Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>It is exciting to see concrete examples of radical collaboration in business ventures, particularly new ones that have a chance to make a big splash. <a class="offsite-link-inline" target="_blank" href="http://golifemobile.com/">GoLife Mobile </a>, a startup venture headquartered in Portland, OR, yesterday announced their collaborative framework for developers of mobile applications (or widgets). Rather than taking on the impossible task of producing all of the applications themselves, they are enlisting a potentially vast pool of developers who are interested in mobile platforms, and who don't mind making a buck or two for their efforts. Developers are encouraged to share widgets, and build upon the work of others. The nifty thing is that whenever your widget gets used (either as the primary application, or a component in an application), the author of the widget gets a piece of the advertising revenue that the GoLife Mobile platform will produce. </p><p>Not only will this collaborative development eco-system reduce the time to produce applications, it promises to spur innovation as well. Developers are incentivized to create compelling, reusable widgets in the hopes that other developers will incorporate them into their own applications. I particularly like the way that GoLife Mobile is combining collaboration with good old fashioned capitalism. James Whitley, the CEO of GoLife Mobile, shared with me at their developer briefing that he's a died-in-the-wool, Central Oregon capitalist, while his president of technology Mounir Shita is from &quot;socialist Norway&quot; -- obviously a great mixture that promises to produce some interesting results!</p><p>&nbsp;</p>]]></content></entry><entry><title>When NOT to Collaborate (or...When Collective Intelligence turns Stupid)</title><category term="Collaborative Leadership"/><category term="Collective Intelligence"/><id>http://www.collaborativeye.com/collaboration_journal/when-not-to-collaborate-orwhen-collective-intelligence-turns.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/when-not-to-collaborate-orwhen-collective-intelligence-turns.html"/><author><name>Dave Kresta</name></author><published>2008-03-01T03:16:45Z</published><updated>2008-03-01T03:16:45Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>We all know by now that social networking technology, collaboration, and &quot;wikinomics&quot;-thinking works. There are still some naysayers, but their arguments are wearing thin. However, there <u>are</u> limits to collective intelligence and the wisdom of crowds and understanding these limits is just as important as understanding the potential. So when does collective intelligence just plain not work? </p><p>Interestingly, as far as I know, all the books extolling the virtues of Enterprise 2.0, Collaboration 2.0, and your-favorite-term-here-2.0, were written by one or two authors rather than hundreds or thousands. These authors created a position, gathered support, did the research, created drafts, and pushed the writing project through. <a class="offsite-link-inline" target="_blank" href="http://www.amazon.com/We-Are-Smarter-Than-Me/dp/0132244799/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1204342199&sr=1-1">We are Smarter than Me</a> tried to break this pattern and use the concepts that the authors write about in the creation of the book. But they concede that part-way through the project &quot;...we found the actual text of the book, the flow of the topics, and the graphical design had to be produced in the conventional way, rather than relying on the crowd to perform these functions.&quot; (pg. xiv) I applaud Barry Liebert and Jon Spector for their candor. Why the breakdown?</p><p>Before we answer, the same book provides another example of &quot;collective intelligence gone wild&quot;. TheBusinessExperiment.com (TBE) was created to harness collective intelligence for the incubation and creation of businesses.  Interaction was good during the idea creation and refinement stage, but when an actual project was chosen to work on, the wheels fell off. Most people lost interest, and getting any real work done was difficult to impossible. A &quot;traditional&quot; leadership was created, with a CEO who quickly drove the project forward. Again, why the breakdown?</p><p>I think these examples provide important reminders that collaboration and collective intelligence still require leadership, albeit leadership of a different kind. The role of such leadership?</p><p>1) From Jim Collins of <a href="http://www.amazon.com/Good-Great-Companies-Leap-Others/dp/0066620996/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1204410835&sr=1-1" target="_blank" class="offsite-link-inline">Good to Great</a> fame:&nbsp; Get the right people on the bus (and correspondingly get the wrong people off the bus). TBE founder Rob May noted that inviting people to vote on ideas attracted people who liked to discuss ideas rather than people interested in the actual idea itself. In application, this means that leadership needs to chose a specific direction or plan (hopefully applying collaborative principles in the idea creation, vetting, and refinement process), and then amass the right team to make the initiative a reality. The actual implementation, once passionate people are on board, can again utilize collective intelligence. </p><p>2) &quot;2.0&quot; leadership still requires the hard work of translating an idea into a plan. Leadership must create a vision around the plan, sell that vision, and&nbsp; set goals. That plan must include some type of work-breakdown-structure to give concrete things for people who are &quot;on the bus&quot; to sink their teeth into. The size of tasks is important: too big and the task is too open-ended to realistically develop in a collaborative, distributed manner. On the other hand, the task cannot be too small or progress will grind to a halt. </p><p>My goal in this post is not to say that collaboration doesn't work. Far from it. As we evolve in collaboration maturity, we will see failed experiments from which we must learn. Understanding the limitations in a concept is crucial to appropriate and most effective application of that concept. Collaborative leadership understands these limitations and knows how to strike the right balance between top-down decision making and collaborative wisdom. Further, collaborative leadership must be willing to explore where that balance is. <br /></p><p> </p>]]></content></entry><entry><title>Not All Games: Putting Game Theory to Work - Part 2</title><category term="Collaboration Culture"/><category term="Collaborative Leadership"/><id>http://www.collaborativeye.com/collaboration_journal/not-all-games-putting-game-theory-to-work-part-2.html</id><link rel="alternate" type="text/html" href="http://www.collaborativeye.com/collaboration_journal/not-all-games-putting-game-theory-to-work-part-2.html"/><author><name>Dave Kresta</name></author><published>2008-01-09T03:44:41Z</published><updated>2008-01-09T03:44:41Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>In our <a href="http://www.collaborativeye.com/collaboration_journal/not-all-games-putting-game-theory-to-work-part-1.html">previous post</a>, we discussed game theory and highlighted 5 conclusions from Axelrod's work on the Evolution of Cooperation which help promote cooperative environments: </p><p>1) Enlarge the shadow of the future - make future interactions more frequent and likely and important<br /></p><p>2) Change the payoffs - give incentives to value cooperation more than non-cooperation.<br /></p><p>3) Teach people to care about each other</p><p>4) Teach reciprocity</p><p>5) Improve recognition abilities</p><p>We will focus on  several of these as ways to foster cooperative and collaborative environments.</p><p><strong>Enlarge the Shadow of the Future</strong></p><p>Collaboration thrives in environments where current behavior is heavily weighted by future prospects of interaction. Keeping units small (see the&quot;magic&quot; of the number 150 in a <a href="http://www.collaborativeye.com/collaboration_journal/pathway-to-collaboration-transactive-shared-memory.html">previous post</a>) is key to encouraging frequent and repeat interactions between individuals. Social networking software can also aid in bringing people together more frequently because the costs of interaction are reduced, and it is also easier t find the &quot;right people&quot; to maximize the benefit of the interaction. </p><p><strong> Change the Payoffs</strong></p><p> Can leaders make it more attractive to collaborate than to not? Certainly, and we are not talking about monetary awards for &quot;most wiki entries&quot; or &quot;most prolific blogger.&quot; Rather, ingrain collaboration in the culture by sharing stories of effective collaboration, giving public recognition, and promoting known collaborators into positions of leadership. Again, social networking software can aid in sharing the story of the power of collaboration and increase the implicit value of these types of interactions.</p><p><strong>Improve Recognition Capabilities</strong></p><p>In game theory, cooperation is predicated on the ability of the &quot;players&quot; to recognize each other between &quot;games&quot; (iterations), and see and understand their behavior so that they can react to it appropriately at the next iteration. Transparency and reputation management from social networking systems can aid tremendously in this vein by reducing uncertainty about the past behavior of individuals. And coming full circle, reputation management also serves to enlarge the shadow of the future by increasing the &quot;durability&quot; of interactions, i.e capturing the behaviors in a system that is open for others to see. </p><p>The bottom line is that collaborative environments can be created and nurtured through attention to factors such as those outlined above. And such factors as enlarging the shadow of the future, changing the payoffs, and improving recognition capabilities can be enhanced through the judicious application of social networking capabilities.  </p><p> </p>]]></content></entry></feed>