<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.5 (http://www.squarespace.com/) on Fri, 30 Jul 2010 14:28:50 GMT--><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rss="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:cc="http://web.resource.org/cc/"><rss:channel rdf:about="http://allcollaboration.com/home/"><rss:title>All Collaboration</rss:title><rss:link>http://allcollaboration.com/home/</rss:link><rss:description></rss:description><dc:language>en-US</dc:language><dc:date>2010-07-30T14:28:50Z</dc:date><admin:generatorAgent rdf:resource="http://www.squarespace.com/">Squarespace Site Server v5.11.5 (http://www.squarespace.com/)</admin:generatorAgent><rss:items><rdf:Seq><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/23/effective-collaboration-is-supposed-to-look-messy.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/10/you-couldnt-do-this-by-telepresence.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/7/hows-your-collaboration-effort-going.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/7/empowerment-owning-problems-and-not-merely-tasks.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/4/what-empowerment-enterprise-20-meets-taylorism.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/3/microsoft-sharepoint-2010-pretty-pictures-or-good-results.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/6/1/the-people-affected-by-collaboration.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/5/27/bp-oil-spill-unmitigated-disaster-in-collaboration.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/5/26/sources-of-complexity-in-collaboration.html"/><rdf:li rdf:resource="http://allcollaboration.com/home/2010/5/25/leveraging-a-change-model-for-collaboration.html"/></rdf:Seq></rss:items></rss:channel><rss:item rdf:about="http://allcollaboration.com/home/2010/6/23/effective-collaboration-is-supposed-to-look-messy.html"><rss:title>Effective Collaboration is Supposed to Look "Messy"!</rss:title><rss:link>http://allcollaboration.com/home/2010/6/23/effective-collaboration-is-supposed-to-look-messy.html</rss:link><dc:creator>Lamont</dc:creator><dc:date>2010-06-23T17:32:24Z</dc:date><dc:subject>People Tools Wikis</dc:subject><content:encoded><![CDATA[As I lament how poorly most people use today's collaboration tools, I also put some of the "blame" on the collaboration tool makers for making people think the work effort is supposed to be pretty. &nbsp;I am a great fan of wikis, but many of the examples they show look more like clean web layouts than successful collaboration.]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/10/you-couldnt-do-this-by-telepresence.html"><rss:title>You Couldn't Do This By TelePresence</rss:title><rss:link>http://allcollaboration.com/home/2010/6/10/you-couldnt-do-this-by-telepresence.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-06-10T15:11:46Z</dc:date><dc:subject>Michael Sampson People Place Process Purpose TelePresence Virtual Teams</dc:subject><content:encoded><![CDATA[<p><strong>Sometimes you just have to be there ...</strong></p>
<p><object width="500" height="301"><param name="movie" value="http://www.youtube.com/v/ZosBRSOwhIQ&hl=en_US&fs=1&rel=0"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/ZosBRSOwhIQ&hl=en_US&fs=1&rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="500" height="301"></embed></object></p>
<p>&nbsp;This is <a href="http://currents.michaelsampson.net/">Michael Sampson</a>'s idea! Thanks Michael!</p>
<p>What lessons can we draw from this about virtual vs. face-to-face?</p>]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/7/hows-your-collaboration-effort-going.html"><rss:title>How’s your collaboration effort going?</rss:title><rss:link>http://allcollaboration.com/home/2010/6/7/hows-your-collaboration-effort-going.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-06-07T21:12:43Z</dc:date><dc:subject>4 Ps Diagnostic Tool People Place Process Purpose Strategy</dc:subject><content:encoded><![CDATA[<p>Congratulations, if your collaboration is going fabulously. Otherwise, something is missing. We can use the 4 Ps Diagnostic Tool, based on the <a href="http://allcollaboration.com/home/2009/12/15/the-four-ps-of-effective-collaboration.html">4 Ps Framework for Effective Collaboration</a>, to understand what might be less than adequate in your collaboration effort.</p>
<p>﻿<span class="thumbnail-image-block ssNonEditable"><span><a href="javascript:showFullImage('/display/ShowImage?imageUrl=%2Fstorage%2F4%2520Ps%2520Diagnostic.gif%3F__SQUARESPACE_CACHEVERSION%3D1275945962110',249,515);"><img src="http://allcollaboration.com/storage/thumbnails/4782749-7242249-thumbnail.jpg?__SQUARESPACE_CACHEVERSION=1275945979270" alt="" /></a></span></span></p>
<p>Missing &ldquo;&radic;&rdquo; represents one of the 4 Ps that needs extra effort.</p>]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/7/empowerment-owning-problems-and-not-merely-tasks.html"><rss:title>Empowerment: Owning problems, and NOT merely tasks!</rss:title><rss:link>http://allcollaboration.com/home/2010/6/7/empowerment-owning-problems-and-not-merely-tasks.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-06-07T19:22:07Z</dc:date><dc:subject>Empowerment Enterprise 2.0 People Problem Solving Process Purpose SMArt Strategic Mind Art Strategy</dc:subject><content:encoded><![CDATA[What if we could …

    * Break-down the business problem/challenge into sub-problems, to whatever level appropriate
    * Maintain and highlight inherent dependencies (precedence) of sub-problems; that is, the order in which they should be solved
    * Highlight the expertise needed to solve sub-problems and thus identify any skills/capabilities gaps
    * Translate collection of sub-problems into a “Solution Plan” (similar to a Project Plan)
    * Develop contingency plans for inherently visible dependencies
    * Have collaborators own sub-problems, for which they easily and clearly understand the impact and contribution of their efforts in the context of the larger business challenge
    * Effectively communicate the progress in terms of solution progress, instead of task status
    * Create an organization of problem-solvers, not task-performers]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/4/what-empowerment-enterprise-20-meets-taylorism.html"><rss:title>What Empowerment? Enterprise 2.0 Meets Taylorism!</rss:title><rss:link>http://allcollaboration.com/home/2010/6/4/what-empowerment-enterprise-20-meets-taylorism.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-06-04T17:35:16Z</dc:date><dc:subject>Empowerment Enterprise 2.0 Leadership People Process Strategy Taylorism</dc:subject><content:encoded><![CDATA[One buzzword of Enterprise 2.0 is EMPOWERMENT. The reasoning goes that empowerment leads to ownership, motivation, creativity, learning & growth, and superior performance, and so on (insert other organization development buzzwords here!). Proponents of the Enterprise 2.0 movement tell us what we should do and why, vis-à-vis empowerment. But, when it comes to the “how” in the real-world, the guidance is a bit sketchy. Here is what we face. We still use methods to manage collaborative efforts that go back to the command & control mindset of Taylorism, with task orientation and assignments. Sometimes, these tasks can be down to hourly or daily levels. Sophisticated tools exist and are in use today that allow for near real-time update and monitoring of progress.]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/3/microsoft-sharepoint-2010-pretty-pictures-or-good-results.html"><rss:title>Microsoft Sharepoint 2010 - Pretty Pictures or Good Results?</rss:title><rss:link>http://allcollaboration.com/home/2010/6/3/microsoft-sharepoint-2010-pretty-pictures-or-good-results.html</rss:link><dc:creator>Lamont</dc:creator><dc:date>2010-06-03T16:35:59Z</dc:date><dc:subject>Sharepoint Strategy Tools</dc:subject><content:encoded><![CDATA[<p>I have been reading much of the hype about Sharepoint 2010 and have yet to use it myself. &nbsp;But I found the <a href="http://www.informationweek.com/galleries/windows/reviews/showArticle.jhtml?articleID=224701355&amp;pgno=1&amp;isPrev=">image gallery at Information Week</a> enlightening -- and disappointing. &nbsp;To me, it looks like a combination of all the pretty editing functions of Powerpoint, Excel, Visio, Project, and so on, all bundled into a so-called collaboration tool.</p>
<p>It strikes me the emphasis is on making the results look pretty, rather than getting to the best solutions. &nbsp;In other words <strong>form over substance</strong>. &nbsp;I have <a href="http://lamonaco.com/blogs/2007/3/30/death-by-powerpoint.html">ranted</a> many times about the abuse of Powerpoint, where the presenter puts more effort into the graphics and animation, at the expense of a compelling story line. &nbsp;My fear is that Microsoft is turning Sharepoint into a tool to do the same thing for collaboration.</p>]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/6/1/the-people-affected-by-collaboration.html"><rss:title>The PEOPLE Affected by Collaboration</rss:title><rss:link>http://allcollaboration.com/home/2010/6/1/the-people-affected-by-collaboration.html</rss:link><dc:creator>Guest Poster</dc:creator><dc:date>2010-06-01T22:30:30Z</dc:date><dc:subject>4 Ps Model CEOs Cleints Contractors Customers People</dc:subject><content:encoded><![CDATA[As a reader of this blog, you are well aware of what I am about to say - effective collaboration can only be achieved through a holistic approach consisting of the 4 P’s: Purpose, People, Process and Place. And while I am in agreement with this approach, I firmly believe that PEOPLE is the most important of the 4 P’s. Without people, there would be no collaboration. You need other PEOPLE around you to work with you in your PLACE to identify a PURPOSE and collaborate within your business PROCESSES. So who are the people that are most important in collaboration?]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/5/27/bp-oil-spill-unmitigated-disaster-in-collaboration.html"><rss:title>BP Oil Spill - Unmitigated Disaster in Collaboration</rss:title><rss:link>http://allcollaboration.com/home/2010/5/27/bp-oil-spill-unmitigated-disaster-in-collaboration.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-05-27T19:58:37Z</dc:date><dc:subject>4 Ps Model BP Oil Spill People Process Purpose Trust</dc:subject><content:encoded><![CDATA[I must begin by saying that this is not a political post; this is not about bashing BP or the US administration. Second, although I do confess to being a news-junkie, I have the same limited knowledge of the situation that is available to all of you. I am no more plugged into the administration or BP than I am plugged into the hole one mile underwater in the ocean. More than one month after the start of this disaster, here is how I see it from a collaboration standpoint. I shall use our 4 Ps Model for Effective Collaboration: Purpose, People, Process and Place.]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/5/26/sources-of-complexity-in-collaboration.html"><rss:title>Sources of Complexity in Collaboration</rss:title><rss:link>http://allcollaboration.com/home/2010/5/26/sources-of-complexity-in-collaboration.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-05-26T19:04:37Z</dc:date><dc:subject>CCollaboration Gap Complexity People Surveys Virtual Teams</dc:subject><content:encoded><![CDATA[Despite its growing importance, we see a “collaboration gap” between the desired versus current state of collaboration in the enterprise. Managing complexity in collaboration to successful conclusions is a key to promoting a culture of collaboration in the enterprise. In this post, we identify the sources of complexity in collaboration using empirical evidence. The data used in this post comes from our primary research, Assessing the State of Collaboration: Return to Essentials.]]></content:encoded></rss:item><rss:item rdf:about="http://allcollaboration.com/home/2010/5/25/leveraging-a-change-model-for-collaboration.html"><rss:title>Leveraging A “Change Model” for Collaboration</rss:title><rss:link>http://allcollaboration.com/home/2010/5/25/leveraging-a-change-model-for-collaboration.html</rss:link><dc:creator>Lokesh Datta</dc:creator><dc:date>2010-05-25T17:20:01Z</dc:date><dc:subject>4 Ps Model Change Model People Place Process Purpose Strategy</dc:subject><content:encoded><![CDATA[I recognize that there are many “change models,” but this particular one caught my attention, for its simplicity and insights. I do not know who the author is. I feel that this change model applies to collaboration as well. Granted that change initiatives are at a grand scale, and we usually speak of collaboration "efforts," unless an organization is embarking on a change initiate to create a strong culture of collaboration. According to the change model, successful change has 5 key elements: i) Vision, ii) Skills, iii) Incentives, iv) Resources, and v) Action Plan. With these ingredients, the model lays out 5 possibilities:]]></content:encoded></rss:item></rdf:RDF>