Commentary

Alexander Wolfe
 

Enterprise 2.0: Confronting Social Media's Dirty Little Secret

I'm encouraged that the dirty little secret of Web 2.0 and social media technologies is finally being openly addressed by early adopters and vendors alike. At the Enterprise 2.0 Conference in Boston, there's been frank discussion this week of the question average users have been whispering (so that their bosses don't hear them): Namely, what can this stuff do for me that's actually useful?

I'm encouraged that the dirty little secret of Web 2.0 and social media technologies is finally being openly addressed by early adopters and vendors alike. At the Enterprise 2.0 Conference in Boston, there's been frank discussion this week of the question average users have been whispering (so that their bosses don't hear them): Namely, what can this stuff do for me that's actually useful?In truth, though, the answers to that question are not yet completely apparent. Here's the deal. At last year's conference, most denizens of the Web 2.0/Enterprise 2.0 community were consumed with evangelism issues. There was a need to raise the profile of wikis, collaborative tools, social-messaging platforms - all the stuff that early adopters were already down with, but average corporate users, not so much.

This year, we've passed through the familiarity hurdle. We've all been wiki'ed up and Twitterized. The problem is, those who don't have an innate feel for the technology, or whose jobs don't make amorphous, asynchronous communications networks useful, have been left out of the cold.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Nevertheless, it's permeated the mass subconscious that these tools are the wave of the future. (The fact that twenty-somethings eat this stuff for breakfast has only added to the angst of older folks seeking Web 2.0 guidance.)

Which is why the "usefulness" discussion is so important. As I said above, there are no firm answers get. But the chat/debate is helping the 2.0 community grope its way towards answers.

The most hopeful remark I heard was from an Enterprise 2.0 panelist who sees wikis moving away from their current role as a repository of corporate knowledge and becoming a "palette for applications." This would enable them to deliver on the largely unfulfilled promise of groupware, which is now 20 years old.

The common thread among enterprises is that everyone is seeking ways (and tools) to connect people in more collaborative ways. Perhaps that's because many companies have been stripped-mined into flatness, where today's employees have to cut through layers to get stuff done, because those layers just don't exist anymore. Or maybe it's because of the geographically dispersed nature of modern workteams.

It's clear we'd get to real Web 2.0-ness a lot faster if we weren't in the midst of an economic climate where investment in new technology is a lot tougher to get approved than we'd all like to admit. (Tougher still is the fact that it's impossible to quantify the ROI on a lot of this stuff.)

OK, in true Web 2.0 fashion, I have to run to an Enterprise 2.0 session, even though I've just skimmed the surface. What are your thoughts? Leave a comment below or e-mail me directly at alex@alexwolfe.net.

Better yet, follow me on Twitter: (@awolfe58)


Like this blog? Subscribe to its RSS feed: (here)

 My videos on ( YouTube)  Facebook    LinkedIn Alex Wolfe is editor-in-chief of InformationWeek.com.


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