Commentary

Chris Murphy
Editor, InformationWeek  

Too Many Collaboration Platforms

Chatting in the lounge of our Global CIO virtual event this week, one CIO raised his concern about having too many collaboration platforms. A wiki here, e-mail alerts there, a SharePoint group there, and pretty soon the discussion's fragmented, and IT has a bunch more platforms to support.

Chatting in the lounge of our Global CIO virtual event this week, one CIO raised his concern about having too many collaboration platforms. A wiki here, e-mail alerts there, a SharePoint group there, and pretty soon the discussion's fragmented, and IT has a bunch more platforms to support.It's a worry I share, and my world's much less complicated than the environment managed by this CIO, who's at a major manufacturing company. (If you missed the Global CIO virtual event, you can see the presentations here. Sorry, lounge chats not recorded!) Here at InformationWeek, we have team members spread across the country, and we use e-mail, IM, and wikis extensively to collaborate. But we haven't exactly cracked the code for what's ideal for each platform. The wiki's wildly effective for managing a shared document-like the lineup of articles we have in the pipeline-but a lot of that information also still gets pushed out by e-mail, so we end up feeding both platforms, and missing a chance for efficiency.

We've indirectly recently written about this issue in two recent articles: one on how ad hoc collaboration fits with formal processes such as product development, and another on how to make enterprise social networking pay off.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

A couple consulting firms we know well in this area, Doculabs and Corridor Consulting, are trying to build a Web community around these issues, at sharepointgovernance.org. So I talked with Russ Edelman, whose Corridor Consulting specializes in Microsoft SharePoint projects, about how to know if you're adding too many collaboration platforms.

His advice is to first be clear on what type of "collaboration" we're talking about, since it might cover anything from video conferencing to wikis to more formal content management systems. Next is to define the goals, and that's where many a project goes awry. Says Edelman:

We lean very heavily on a blended perspective of business objectives and 'wif-m' --- what's in it for me - objectives. How do you make employees lives easier? … If it's not drop dead easy, often you might have a technical success of standing up a collaboration platform, but have a business failure. … If you're not answering the question of how you're going to make their lives easier, in addition to making the business more productive, people are absolutely going to choke on it. They'll say 'I'm too busy for this.'"

Collaboration platforms with that kind of lukewarm adoption are deadly. They suck up IT time and support, and they splinter collaboration into those on the system and off it, erasing the productivity and openness they're supposed to foster. The CIO in the chat in our virtual event had it right: Be wary of too many platforms.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links