<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.gilbane.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.gilbane.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
   <title>Collaboration Blog</title>
   <link rel="alternate" type="text/html" href="http://gilbane.com/collaboration/" />
   
   <id>tag:gilbane.com,2008:/collaboration//15</id>
   <updated>2007-11-19T21:18:05Z</updated>
   <subtitle>Collaboration technologies &amp; strategies, including enterprise wikis, blogs, and relevant 'social media' technology</subtitle>
   <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>


<link rel="self" href="http://feeds.gilbane.com/CollaborationBlog" type="application/atom+xml" /><entry>
   <title>Social Networks as a Feature in Email</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/187352375/social_networks_as_a_feature_i.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2316</id>
   
   <published>2007-11-19T19:40:41Z</published>
   <updated>2007-11-19T21:18:05Z</updated>
   
   <summary>Saul Hansell has a tantalizing tidbit in today's NYTimes, a report that Yahoo! and Google are thinking about making their email systems 'more social.' "Web-based email systems already contain much of what Facebook calls the social graph -- the connections...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Enterprise 2.0" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1064" label="email" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="864" label="enterprise 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1629" label="enterprise directory" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1625" label="Exchange" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1246" label="Lotus Connections" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1623" label="Lotus Notes" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1413" label="messagiing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="130" label="Microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1627" label="Outlook" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1313" label="social networks" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Saul Hansell has a tantalizing tidbit in today's NYTimes, a report that Yahoo! and Google are thinking about making their email systems 'more social.'&lt;a href="http://www.nytimes.com/2007/11/19/technology/19bits.html"&gt; "Web-based email systems already contain much of what Facebook calls the social graph -- the connections between people. That's why social networks offer to import the e-mail address books of new users to jump-start their list of  friends."&lt;/a&gt; Our personal email applications should keep track of who is most important to us, and let us know when those messages arrive.

Saul's report opens Pandora's box about the future of Enterprise 2.0. The dirty little secret is that our e-mail in-boxes track our social networks by default -- who we communicate with, when and in what order can be as interesting as what in fact we say (or do not say). Our personal address books are more than a random list of names -- they're the 'black books' that  contain the people with whom we've exchanged messages in the past, or want to communicate with in the future. 

We intuitively track our business networks through our use of email -- the names of folders we use when filing messages, the subjects we attach to messages, and the threads of a back-and-forth discussion are all grist for the social networking mill. Gmail, for example, collects message threads into a single record. This is a handy innovation, which helps to cut down on the message clutter that's so prevalent in Notes Mail &amp; Outlook. 

The real challenge is that messaging inside the enterprise is frozen in time -- captured by the two most widely deployed messaging applications, from Microsoft (Outlook/Exchange) and IBM (Lotus Notes). It's hard to believe that these are legacy platforms. 

We need to rethink what else we can do with email inside the enterprise -- &lt;a href="http://gilbane.com/collaboration/2007/07/lets_get_serious_about_social.html"&gt;Lotus Connections goes a long way towards staking out a few essential services.&lt;/a&gt; These include an "intelligent" enterprise directory &amp; a tag cloud that relates to communities within the enterprise. 

We need to do a lot more with features around privacy, security, organizational boundaries, and context. 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=EiNLEIB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=EiNLEIB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=gyBK4BB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=gyBK4BB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=XUZ2eYb"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=XUZ2eYb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=A6FG3rb"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=A6FG3rb" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=Cnho6uB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=Cnho6uB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=esdDjmB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=esdDjmB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=nceEOaB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=nceEOaB" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/187352375" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/11/social_networks_as_a_feature_i.html</feedburner:origLink></entry>

<entry>
   <title>Tools of Youthful Rebellion . . .</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/177741781/tools_of_youthful_rebellion.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2272</id>
   
   <published>2007-10-31T13:26:06Z</published>
   <updated>2007-10-31T13:52:16Z</updated>
   
   <summary>I'm not a regular commuter anymore and rarely catch "All Things Considered" during drive time. Yet yesterday afternoon I had the good fortune to listen to Andrei Codrescu (always a favorite commentator) expound on "From Poetry to Web: Tools of...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1582" label="Andrei Codrescu" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1261" label="Facebook" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1584" label="NPR" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="120" label="Web 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      I'm not a regular commuter anymore and rarely catch "All Things Considered" during drive time. Yet yesterday afternoon I had the good fortune to listen to Andrei Codrescu (always a favorite commentator) expound on &lt;a href="http://www.npr.org/templates/story/story.php?storyId=15785024"&gt;"From Poetry to Web: Tools of Youthful Rebellion."&lt;/a&gt; Listen &amp; enjoy! 

With all the hype around Facebook apps, Web 2.0, and social media, it helps to keep a poetic perspective. Yes the times they are a changin' -- the torch &lt;em&gt;is &lt;/em&gt;being passed to a new generation . . . but whether we are digital natives or immigrants, we still need to extract the business purposes from all the interactivity and information available at our fiingertips. What hasn't changed is the limit of the 24 hour day -- how we can work productively and play passionately within it. 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=VlgnpXA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=VlgnpXA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=OfsbIGA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=OfsbIGA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=BgD9x2a"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=BgD9x2a" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=vz6uhOa"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=vz6uhOa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=p29y1SA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=p29y1SA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=UhcRTwA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=UhcRTwA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=fvsmO4A"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=fvsmO4A" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/177741781" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/10/tools_of_youthful_rebellion.html</feedburner:origLink></entry>

<entry>
   <title>Wither Web 2.0? Come to Boston</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/174430412/perhaps_its_cyclical_like.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2254</id>
   
   <published>2007-10-24T17:49:35Z</published>
   <updated>2007-10-24T17:54:05Z</updated>
   
   <summary>Perhaps it's cyclical -- like the long Indian summer we've been having here in the Northeast. The Web/Enterprise/stuff "2.0" buzz has died down (for now) and we seem to be into the hard business of real application development. Perhaps this...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="728" label="Enterprise 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1261" label="Facebook" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="405" label="Google" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1547" label="industry survey" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1545" label="mash-up" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="120" label="Web 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Perhaps it's cyclical -- like the long Indian summer we've been having here in the Northeast. The Web/Enterprise/stuff "2.0" buzz has died down (for now) and we seem to be into the hard business of real application development. Perhaps this is a good thing -- running on hype does little to transform businesses or pay the bills. 

Certainly there's been a lot of excitement around Facebook as a collaborative platform for digital natives (and fellow travelers). Yet the long-lasting innovation, I think, is around the APIs and the notion of "open platforms." Of course Google was first to open the komono with its wildly popular Web services API into Google Maps. Now we're trying to make mashups of social networks. 

I'm curious but not convinced. &lt;a href="http://www.eweek.com/article2/0,1759,2189077,00.asp"&gt;Facebook is building out its community &lt;/a&gt;-- Google is not far behind, pursuing the notion of &lt;a href="http://blogs.zdnet.com/social/wp-mobile.php?p=314"&gt;social graphing. &lt;/a&gt;So far we can do all kinds of useful things in the consumer space. My favorite this week is &lt;a href="http://www.nytimes.com/2007/10/23/technology/23mobile.html?ref=technology"&gt;friend finding&lt;/a&gt; -- which also leverages GPS technology. But business applications? I haven't heard of anything really compelling, yet. I'm still looking. 

Which brings me to a preview of coming attractions. My colleagues Steve Paxhia, Nora Barnes, and I expect to cut through the Web 2.0 hype next month and shed some light on industry trends.  &lt;a href="http://gilbaneboston.com/session_descriptions.html#csc3"&gt;We'll be reporting the results of our industry survey at our Boston conference. &lt;/a&gt;We'll have a statistically significant profille of what collaboration and social computing tools are being using in American businesses -- beginning with email and Web sites and assessing many popular forms of social media. We'll snapshot how effective companies rate these tools and also report on what each tool is best suited for. And I expect that before we're done, we'll have a few indicators of next generation collaborative business applications. 

So join us, November 27th - November 29th in Boston.


      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=36tFg5A"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=36tFg5A" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=vqDuaAa"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=vqDuaAa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=VJY6N8a"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=VJY6N8a" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=xfUFDNa"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=xfUFDNa" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=jAK2YvA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=jAK2YvA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=LXRFBZA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=LXRFBZA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=FOrwiuA"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=FOrwiuA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/174430412" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/10/perhaps_its_cyclical_like.html</feedburner:origLink></entry>

<entry>
   <title>Notes as the New Mainframe</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/149295565/email_as_the_new_mainframe.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2149</id>
   
   <published>2007-08-28T15:05:48Z</published>
   <updated>2007-08-28T16:41:38Z</updated>
   
   <summary>IBM released Notes 8 and Domino 8 earlier this month -- two years in development and "the industry's first enterprise collaboration solution largely designed with input from its customers." IBM has devoted a lot of its efforts towards creating an...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1410" label="clutter" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1409" label="collaboration services" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1064" label="email" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="24" label="IBM" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1413" label="messagiing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="263" label="Notes" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1412" label="user experience" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      IBM released Notes 8 and Domino 8 earlier this month -- two years in development and &lt;a href="http://www-03.ibm.com/press/us/en/pressrelease/22169.wss"&gt;"the industry's first enterprise collaboration solution largely designed with input from its customers." &lt;/a&gt; IBM has devoted a lot of its efforts towards creating an integrated user experience -- messages, calendar entries, file folders, and queries to business applications can all appear within a single, tiled window. With customized sidebars and tool bars, application developers can add "peripheral vision" to the user experience, and integrate a variety of plug-ins. While this user interface style is hardly revolutionary, it does cut down on window-clutter and will go a long way towards improving the usability of complex application environments. 

IBM has also introduced "message conversations" into Notes email. Rather than messages being displayed as discrete items, they are concatinated into their discussion threads -- with the root message and all the replies captured in a single list. This reduces Inbox clutter -- 150 messages (the average daily total for a "typical" Notes user) can be reduced to eight or ten threads.

For organizations that made the Notes investment some years ago, there's no need to consider alternatives or doubt IBM's commitment to it's core collaboration platform. Like the mainframes of an earlier computing era, Notes remains a solid messaging platform with integrated calendaring and contacts. It continues to serve as a development environment for ad hoc (workgroup-level) applications. 

But I wonder about the growth opportunities for Notes. Many of us are quite comfortable with the "traditional" business activities engendered by this latest version  -- sending and receiviing messages, scheduling and attending meetings, contacting people. Yet when we have so much information readily accessable at our fingertips, we are continually looking for new metaphors for doing work -- bringing people together over the network, restructuring business processes, improving decision making. More is at stake than simply "reducing clutter." We need to focus as much on the "collaboration services" accessible within the network as on the quality of the user experience itself. 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=606viNIo"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=606viNIo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=QhFO98I5"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=QhFO98I5" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=V60bVjb1"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=V60bVjb1" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=IdZpHpLn"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=IdZpHpLn" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=c9OdH1dR"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=c9OdH1dR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=16p2X8A1"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=16p2X8A1" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=ZEIxOSZM"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=ZEIxOSZM" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/149295565" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/08/email_as_the_new_mainframe.html</feedburner:origLink></entry>

<entry>
   <title>Mashing-up the Wikipedia Code</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/145175347/mashing_up_the_wikipedia_code.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2135</id>
   
   <published>2007-08-16T12:33:28Z</published>
   <updated>2007-08-17T14:36:37Z</updated>
   
   <summary>Now here's an interesting tidbit from the BBC, courtesy of my daughter (who's a graduate student in London): Wikipedia 'shows CIA page edits.' It seems that staffers at the CIA, the Democratic National Campaign Committee, the Vatican, and many other...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="149" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1374" label="eBay" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="523" label="mashups" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1376" label="Pierre Omidyar" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1371" label="trust" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1372" label="verification" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Now here's an interesting tidbit from the BBC, courtesy of my daughter (who's a graduate student in London): &lt;a href="http://news.bbc.co.uk/2/hi/technology/6947532.stm"&gt;Wikipedia 'shows CIA page edits.'  &lt;/a&gt; It seems that staffers at the CIA, the Democratic National Campaign Committee, the Vatican, and many other well known institutions (who may be trying to remain nameless) have been 'caught' sprucing up various wikipedia articles. (Well of course this is a tarty British take on the matter!) 

And the secret sauce that pulls back the curtain? Revealed at the end of the article, a simple mashup that links the IP addresses of contributors to an article (obtained through the "history" page) with a directory of organizations owning IP addresses. Both are publicly available. The results are hardly surprising.

The point is that when information is so widely and freely available, we have to begin to worry about the sources of information and how it is presented. There's not a lot of anonymity on the public web -- and quite possibly this is a good thing. But building community also includes notions of trust, expertise, and terms of reference. For example, when starting eBay, &lt;a href="http://en.wikipedia.org/wiki/Pierre_Omidyar"&gt;Pierre Omidyar &lt;/a&gt;came up with the notion of "rate the buyer" and "rate the seller" as a way of organically building trust within the community of eBayers . . . and the rest is history. 

I hate to admit it but perhaps Ronald Regan said it the best. "Trust but verify." What's interesting is that mashing-up sources and IP addresses provides a whole new dimension to verification. I wonder what else is possible? Let's start a discussion -- comments? 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=nY68zU6j"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=nY68zU6j" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=jXcNSTCn"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=jXcNSTCn" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=i2Lrd7nU"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=i2Lrd7nU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=stKv7D61"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=stKv7D61" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=4MgAqMW5"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=4MgAqMW5" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=ne8mIkqe"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=ne8mIkqe" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=GlcBysZ6"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=GlcBysZ6" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/145175347" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/08/mashing_up_the_wikipedia_code.html</feedburner:origLink></entry>

<entry>
   <title>I've Got Infrastructure on My Mind</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/142146609/ive_got_infrastructure_on_my_m.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2122</id>
   
   <published>2007-08-08T19:45:45Z</published>
   <updated>2007-08-08T22:10:39Z</updated>
   
   <summary>It's been a rough few weeks for infrastructure. Of course the collapse of the I-35 bridge over the Mississippi in Minneapolis last Wednesday is on all of our minds – how could the inspections fail and the road fall down?...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1350" label="Big Apple" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1352" label="eProject" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1344" label="I-35 bridge disaster" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1141" label="information architecture" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1230" label="infrastructure" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1346" label="Minneapolis" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1348" label="New York City" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1244" label="SchemaLogic" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1342" label="sense and respond" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      It's been a rough few weeks for infrastructure. 

Of course the collapse of the I-35 bridge over the Mississippi in Minneapolis last Wednesday is on all of our minds – how could the inspections fail and the road fall down? Significantly, there's &lt;a href="http://www.youtube.com/watch?v=EjCic0YlJwQ"&gt;some videos that capture the moment&lt;/a&gt;, which hopefully will provide clues for determining the cause. 

Closer to home, we had an eight-hour traffic jam on the I-93 loop in Braintree (a major highway south of Boston) a week ago Monday. A storm grate was thrown loose by a passing truck at the start of the morning rush, and landed on a near-by car. (Fortunately the driver survived.) Reportedly, the Massachusetts State Highway Department spent the rest of the day checking and welding shut all the grates on that highway. The next day, the same loose storm drain problem cropped up on a major road in Newton, near where I live. This time motorists were asked to dial a special code from their cell phones to report problems. 

And then this morning New Yorkers awoke to a monsoon and &lt;a href="http://www.nytimes.com/2007/08/08/nyregion/08cnd-weather.html?hp"&gt;a flooded mass transit system.&lt;/a&gt; The official M.T.A. web site could not keep up with the requests for information, and crashed when it was needed most. 

You've gotta hand it to those hardy folks (and the New York Times) for that snarky, Big Apple attitude. Here're a few priceless ones that I gleaned from NYTimes.Com during the day.&lt;blockquote&gt;“Our transit system is not only frail but if it’s this vulnerable to rain attacks, then how vulnerable is it to terrorist attacks?” &lt;/blockquote&gt;&lt;blockquote&gt;"I walked from the Upper West Side all the way to work in Midtown, but thanks to Starbucks was able to stop in and cool myself every four blocks or so.” &lt;/blockquote&gt; (Now there's somebody with brand loyalty!)&lt;blockquote&gt;"And only the rats had no transportation problems."&lt;/blockquote&gt;All this content about our physical infrastructure (user generated and otherwise) has the potential to bring social computing to a whole new level. 

This got me thinking about the role of collaboration technologies for supporting our physical infrastructure. It's great to be able to talk back -- and let off a little steam. It's even better to be able to call-in, and tell the authorities about the problem before there's another horrible accident. But what else is possible? Could the bridge inspectors in Minneapolis have shared their observation reports, measurements, and perhaps photographs of the bridge's structure  over the past few inspection cycles, and had some semi-automated ways to detect the problems before the disaster? Unfortunately we'll never know.

While I certainly don't have it all figured out, I can begin to see some bread crumbs towards the workable solution we all want and need. We can no longer rely on human intelligence alone. Our worlds are much too complex and interdependent. We need to augment our understandings, and our abilities to take actions, by a variety of automated, concent-centric tools, such as semantic technologies. (With my colleagues Lynda Moulton and Frank Gilbane, we're picking up coverage of this area, the ability to inject "meaning" and "context" into an enterprise environment. Be sure to check out &lt;a href="http://www.gilbaneboston.com/conference_grid.html"&gt;the semantic technologies track at our upcoming conference in November&lt;/a&gt;.) 

I've seen a couple of promising developments this month. SchemaLogic is finally &lt;a href="http://www.schemalogic.com/company/press_center/press_releases/2007-07-16b.php?PHPSESSID=906f2e9825d606123b725b1ef5f8a2d9"&gt;reporting some progress in the publishing space&lt;/a&gt;, enabling publishers such as Associated Press to automatically repurpose content by synchronizing tags and managing metadata schemas. While pretty geeky, this is very neat! Now we need to see how this approach to managing semantics within the enterprise will impact collaboration and social computing.

Then project and portfolio management (PPM) systems -- heretofore heavyweight (often mainframe) applications that are used to track resources for complex, engineering-driven projects -- are being redeployed as Web 2.0 environments. In particular,&lt;a href="http://www.eproject.com/"&gt;eProject &lt;/a&gt;is now transforming its Web-based PPM environment into a broader collaborative tools suite. Seeking to capitalize on it's expanded mission of bringing a PPM model to the Web, eProject's also renaming itself in the process.

Where do these bread-crumbs lead? As a first step, we need to focus on how our collaboration infrastructure (fueled by our information architecture) can augment the work of people responsible for our physical infrastructure (ourselves included). At the end of the day, we need to be able to rely on this collaboration infrastructure to help us sense and respond to the challenges of simply getting from one place to another.
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=oMKAOFpd"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=oMKAOFpd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=fSQhgjOG"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=fSQhgjOG" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=L46MAQQZ"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=L46MAQQZ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=Y5iI0aib"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=Y5iI0aib" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=XVcdmPQR"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=XVcdmPQR" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=8nLq8KPn"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=8nLq8KPn" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=0rBanrO8"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=0rBanrO8" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/142146609" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/08/ive_got_infrastructure_on_my_m.html</feedburner:origLink></entry>

<entry>
   <title>Links and Connections: Finding the Context</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/139206502/links_and_connections_finding.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2108</id>
   
   <published>2007-07-30T21:42:13Z</published>
   <updated>2007-07-31T12:43:41Z</updated>
   
   <summary>A provocative conversation broke out on one of the discussion groups I monitor last week. "I'm curious how you and others you know are using 'LinkedIn.com.'" the person asked. "For me, I like who's in my network, [and] keep asking...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Enterprise 2.0" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1316" label="context" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1261" label="Facebook" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1315" label="Linked-in" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1313" label="social networks" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1318" label="water-cooler conversations" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      A provocative conversation broke out on one of the discussion groups I monitor last week. "I'm curious how you and others you know are using 'LinkedIn.com.'" the person asked. "For me, I like who's in my network, [and] keep asking others to join; but overall I find it to be very static."

A static network -- now there's a new concept! But there's a good deal of truth to wondering how these links work within the business environment. Sure I too have a modest network; I check out my Linked-in account once or twice a month to see who's doing what. For me, this substitutes (poorly) for the water-cooler conversations earlier in my career, when I was surrounded by lots of co-workers. There was always the lunch-time gossip and the hallway exchanges . . . did I know that so and so was working on this new skunk-works project? Had I heard that another sales team just surpassed its revenue goals or that a particular key customer now had a new set of requirements?

While linking-in through Linked-in is a poor substitute for the chatter of the co-located workplace, it's at least the beginning of a business conversation. It maintains its professional aura, boundaries, and rules, in part by continuing to stove-pipe its connections, and not (yet) mashing up its links and membership.

Not so with Facebook, now trying to take the "digital natives" (those who grew up with the Internet ant the Web) into the workplace. This move -- blending the power of networks with mashups -- is raising a number of eyebrows. &lt;a href="http://www.washingtonpost.com/wp-dyn/content/article/2007/07/18/AR2007071802460_2.html"&gt;"Friend? Not? It's One or the Other" Rob Pegoraro, the personal technology columnist &lt;/a&gt;wrote provocatively in the Washington Post last week. 

&lt;blockquote&gt;You could stay in touch with your drinking buddies at MySpace, then schmooze with your business partners at LinkedIn.

But life isn't always that neat. And when the private and professional overlap at these sites, you can spend more time worrying about your image than building your network.&lt;/blockquote&gt;

To be sure Facebook has a slew of privacy setting -- at least 135 according to Pegoraro -- but having to define how I want to expose some of my activities to one group of friends and other actions to business colleagues adds complexity to what should be cast as a rather fluid interchange.

What's missing to my way of thinking is not simply privacy but context. We all have our business personas and our personal personas. We have certain expectations when in a business context, others when in a social context, and still others when "being personal." Many of our social networks are, in fact, rather complex. 

To make these networks useful within a collaborative (and online) business environment, we need to be able to add (and manage) our business contexts. We need to be able to describe (and map) the business purposes for our social networks. 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=sI3HGzOU"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=sI3HGzOU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=qoFrox3U"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=qoFrox3U" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=qwXyk1em"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=qwXyk1em" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=1vetZZQj"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=1vetZZQj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=YIfEBB1u"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=YIfEBB1u" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=eSQ9MfTx"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=eSQ9MfTx" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=TynfYDNY"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=TynfYDNY" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/139206502" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/07/links_and_connections_finding.html</feedburner:origLink></entry>

<entry>
   <title>Counting How the Game is Changing</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/137373344/counting_how_the_game_is_chang.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2097</id>
   
   <published>2007-07-25T20:02:50Z</published>
   <updated>2007-07-25T21:37:31Z</updated>
   
   <summary>Nora Barnes (director of the Center for Marketing Research at UMass, Dartmouth) and Eric Mattson have a new survey report out on social computing -- The Game Has Changed: College Admissions Outpace Corporations in Embracing Social Media. They compare how...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1144" label="blogging" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1143" label="business process" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1292" label="survey research" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="84" label="wiki" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Nora Barnes (director of the Center for Marketing Research at UMass, Dartmouth) and Eric Mattson have a new survey report out on social computing -- &lt;em&gt;&lt;a href="http://www.umassd.edu/cmr/studies/blogstudy3.cfm"&gt;The Game Has Changed: College Admissions Outpace Corporations in Embracing Social Media.&lt;/a&gt;&lt;/em&gt; They compare how universities and companies in the Inc. 500 are using social media -- blogging, social networking (whch I take to mean sites like Facebook and MySpace), message boards, online video, podcasting, and wikis. In a nutshell &lt;blockquote&gt;Social media has arrived in college admissions. The ivory tower is innovating even faster than the elite Inc. 500. And the game has changed forever. &lt;/blockquote&gt; 

I cannot wait to see their detailed analysis.

Picking through their numbers so far, two things jump out. First, universities are almost as likely to use social networks as search engines when evaluating potential students (26% vs 21%). Admission offices can find out all kinds of information about their prospects by googling them on the web. Tracking and tracing their social networks is close behind. Hum, I wonder what enterprises are going to be doing, both when reviewing job candidates and business partnerships, and when tracking performance. I can see it now -- a new generation of "socially conscious" HR and business applications.

Second, we've been talking about blogs and wikis in almost the same breadth (thanks in part to &lt;a href="http://www.wikinomics.com/"&gt;Don Tapscott and Wikinomics&lt;/a&gt; and "how mass collaboration changes everything"). But not so fast. While blogging is more widely used in universities than in corporations (33% vs 19%), wikis are more widely deployed in corporations than in universities (17% vs. 3%). So we ought to take another breadth, turn down the hypemeter, and better understand how these different modes of collaboration are used in practice.

Here's my vote. It's all about the difference between self-publishing and supporting a business process. Blogging's easy -- I'm standing at my virtual Hyde Park corner (as in this blog), using my own time. Others who want to invest their time can read what I have to say. (Thank you, my readers!) But putting up a wiki is all about sharing information that's part of a business process -- I post, you modify, and our colleagues elsewhere in the world add their two cents. The outcome is a group project, the results of our "collective intelligence." It's a bit like co-authoring a report or developing a project plan for a group or . . . . you get the point -- we share in the results through an interactive process. 

Oh, one other thing. Business processes are tough to implement. They happen not by accident but by design. When the bloom is off the rose, we're going to have to do a lot more work to make wikis really useful within the enterprise.
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=Dfe2lzyu"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=Dfe2lzyu" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=KwdLcLkm"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=KwdLcLkm" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=KMu8rCLf"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=KMu8rCLf" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=4QwwbU83"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=4QwwbU83" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=sCpUYW1P"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=sCpUYW1P" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=I96CFEOq"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=I96CFEOq" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=J3gcdm7r"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=J3gcdm7r" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/137373344" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/07/counting_how_the_game_is_chang.html</feedburner:origLink></entry>

<entry>
   <title>Let's Get Serious about Social Computing</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/134355036/lets_get_serious_about_social.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2070</id>
   
   <published>2007-07-16T21:47:53Z</published>
   <updated>2007-07-16T22:04:46Z</updated>
   
   <summary>You'd think the CEO of a public company would have better things to do with his time than to blog anonymously about his company's performance and trash the competition. But this seems not to be the case with John Mackey,...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
   <category term="731" label="blog" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1250" label="enterprise collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="24" label="IBM" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1246" label="Lotus Connections" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1248" label="sock puppet" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      You'd think the CEO of a public company would have better things to do with his time than to blog anonymously about his company's performance and trash the competition. But this seems not to be the case with John Mackey, chief executive of Whole Foods Market, whose "sock puppeting" behavior, &lt;a href="http://www.nytimes.com/2007/07/16/technology/16blog.html"&gt;"the act of creating a fake online identity to praise, defend or create the illusion of support for one's self, allies or company" &lt;/a&gt;has now landed him in hot water with the Feds and competitors in the natural foods grocery business. Probably a gaggle of lawyers will figure out a way to solve the Mackey issue . . . at least for now.

Yet, this latest escapade got me thinking (once again) about the double-edge sword of social computing. Sometimes we can be too social – not just speaking out of turn but also crossing important organizational boundaries. In our era of instant communications, it is possible to communicate too freely.

What we need are a few good models for how we're going to "collaborate" with one another over the Net—figuring out the boundaries without building walls. (By enterprise collaboration I mean exchanging and sharing both information and insights, to do our jobs better.) Behind all the Web 2.0 hype, I suspect there are a few pointers towards new models. 

One of my current favorites for a new model is Lotus Connections, an integrated suite of five services for social software (IBM's moniker for the market). These services are (a) communities, (b) social book marking, (c) enterprise profiles, (d) activities, and (e) blogs. Not surprisingly, these services are based on the ways that IBM typically does business. In fact, Connections productizes several internally developed IBM technologies. 

I realize that I have the same feelings for Connections that I had with Lotus Notes in the early days of the groupware revolution – a terrific concept for a new computing paradigm, yet where the devil's in the details. With a $110 per user price tag, IBM is focusing (for now) on the large enterprise marketplace.  Designed to run inside an enterprise, Connections bundles restricted versions of WebSphere Application Server, DB2 Enterprise Database, and Tivoli Directory Integrator. To be sure, large organizations have large internal collaboration problems – such as quickly assembling ad hoc task teams of company experts who do not necessarily know one another to solve a pressing problem, or coordinating constantly changing schedules and deliverables. 

But I am still bothered by the boundary problem of social computing – which Connections (despite all its promise) does little to address. Yes, as soon as we are authorized and authenticated by our networked environment, we can collaborate and share information. With current technologies, we're living in a binary world. Either we're inside the firewall/enterprise or we're public on the Net. Either things are "private" or "public." 

In real life though, we're dealing not with just black or white. Social computing's going to have to do better, and be able to deal with many shades of gray. This means being able to manage content, schedules, and relationships across an "extended" enterprise – and being able to adjust the degree of connectedness we want to have with colleagues across different organizations.
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=ONvH7jjj"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=ONvH7jjj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=4oRNRsOV"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=4oRNRsOV" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=Z5mkobrT"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=Z5mkobrT" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=ZkjAkJm7"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=ZkjAkJm7" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=tZxXFyzz"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=tZxXFyzz" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=DDb9hqCE"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=DDb9hqCE" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=GsyhIw3B"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=GsyhIw3B" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/134355036" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/07/lets_get_serious_about_social.html</feedburner:origLink></entry>

<entry>
   <title>What's Web 2.0 All About? Let's Start with the Infrastructure</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/132389963/whats_web_20_all_about.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2063</id>
   
   <published>2007-07-10T16:15:40Z</published>
   <updated>2007-07-10T19:43:10Z</updated>
   
   <summary>Jacques Bughin and James Manyika at McKinsey have just published another thought-provoking report, "How Businesses Are Using Web 2.0." They're working with a beefy survey (2,847 executives worldwide, 44% who hold C-level positions), supplemented by an online discussion. Their conclusions:...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
      <category term="Enterprise 2.0" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="1233" label="business models" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="149" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1234" label="ecosystem" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1231" label="flexibility" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="455" label="information sharing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1230" label="infrastructure" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="120" label="Web 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="831" label="web services" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Jacques Bughin and James Manyika at McKinsey have just published another thought-provoking report, &lt;a href="http://www.mckinseyquarterly.com/article_abstract.aspx?ar=1913&amp;l2=16&amp;l3=16&amp;srid=17&amp;gp=0"&gt;"How Businesses Are Using Web 2.0."&lt;/a&gt; They're working with a beefy survey (2,847 executives worldwide, 44% who hold C-level positions), supplemented by an online discussion. Their conclusions:

"Expressing satisfaction with their Internet investments so far, [respondents] say that Web 2.0 technologies are strategic and that they plan to increase these investments. But companies aren't necessarily relying on the best-known Web 2.0 trends, such as blogs; instead they place the greatest importance on technologies that enable automation and networking." Companies that are using Web 2.0 technologies "have developed a new way of bringing technology into business . . . This new approach is easier to implement and more flexible than traditional top down approaches."

Wow, so at the end of the day, our focus on Collaboration 2.0 is all about developing new, more flexible models for deploying business applications! Could it be that this year's two-dot-oh rave is all about light-weight development models? 

Well, perhaps -- this is certainly the underlying logic of Google's $625 million acquisition of Postini, an email security and management company, consumated today. As today's NYTimes observed, &lt;a href="http://www.nytimes.com/2007/07/10/technology/10google.html"&gt;"The deal underscores Google’s ambitions to become a serious player in the business of selling software to companies and organizations, in competition with Microsoft and others."&lt;/a&gt; But as much as I am a fan of Gmail, I don't think it is going to be the Exchange killer. There's still going to be a big market for enterprise applications, enterprise email included. (I'm not sure how I would feel about my doctors using Gmail in the hospital when discussing my health and well being.)

Here's the issue. We can rely on the Internet and the Web to provide an ever increasing set of business services. Some are advertising supported (such as Gmail); others are subscription based (such as Salesforce, Foldera, and Longjump). The savvy Web 2.0 vendors -- including Google, Amazon, Facebook, Yahoo, and various startups -- are rapidly exposing their APIs for meaningful mashups, each promising to anchor a vibrant ecosystem for content sharing and collaboration. We're going to have a lot more flexibility. Yet as business leaders and technology visionaries, we are going to have to plan very carefully how we will use the Internet's power of instant connectivity for our strategic business advantage.

We often forget the amount of infrastructure we have readily available when we go online and exchange email. DNS, TCP/IP, some basic security, SMTP, HTTP -- it all works now; earlier generations of technologies limited the scope of these services to enterprise islands. (Remember DECnet, PROFS, and WangNet.) Now we're concerned about privacy, security, findability, records retention, manageability, and a whole host of knotty systems infrastructure issues. 

The challenge facing the collaboration ecosystem vendors for the enterprise (whoever they may be) is to build the infrastructure required to support the "automation and networking" environments that the McKinsey execs have in mind. The jury is still to be convened. 

I bet that we're going to be hearing a lot from the mainstream enterprise vendors--Microsoft, Oracle, IBM, SAP, EMC, Cisco--by the end of the year. With our continuing focus on enterprise collaboration and social computing, we are going to have to pay even more attention to the infrastructure services available over corporate intranets, partner extranets, and the public Internet. It remains to be seen how flexible these loosely coupled core services can be--and how they can be packaged into vibrant business propositions. 
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=efHHw3Hd"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=efHHw3Hd" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=zxafFDnP"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=zxafFDnP" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=L71DlH5Q"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=L71DlH5Q" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=aAGH628p"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=aAGH628p" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=4HjaSOW8"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=4HjaSOW8" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=98P9rv5t"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=98P9rv5t" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=rUfX6Mdi"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=rUfX6Mdi" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/132389963" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/07/whats_web_20_all_about.html</feedburner:origLink></entry>

<entry>
   <title>What's the Future for User Generated Content?</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/128780191/whats_the_future_for_user_gene.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2048</id>
   
   <published>2007-06-28T21:26:30Z</published>
   <updated>2007-06-29T14:59:28Z</updated>
   
   <summary>I was part of a Web 2.0 panel in New York City earlier this week, moderated by Bryant Shea, Director of Content Management at Molecular. It was an intimate affair - we had about thirty people in the room, drawn...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Collaboration" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="731" label="blog" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1176" label="Molecular" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1178" label="user generated content" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="120" label="Web 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      I was part of a Web 2.0 panel in New York City earlier this week, moderated by Bryant Shea, Director of Content Management at &lt;a href="http://www.Molecular.com"&gt;Molecular&lt;/a&gt;. It was an intimate affair - we had about thirty people in the room, drawn largely from media/entertainment, financial services, and insurance firms. 

We wanted to encourage audience participation -- about five minutes into the event, one person piped up, "We know that Web 2.0 is all about user generated content. We certainly agree - we've put up a blog for our customers. Now what do we do with all this content?" Good question - we spent the rest of the evening trying to answer.

I'm not sure we ever reached a resolution but this got me thinking. What's equally important is the prior question - why put up a blog in the first place? Business strategies need to drive technology choices; technology options can then drive business opportunities.

Now there are certainly plenty of plausible reasons for companies to want to encourage blogging about their products and services. Building brand loyalty, supporting the fans, wanting to learn about customers experiences (both the good and the bad), facilitating a peer group who can support one another, perhaps even turning to loyal end users to help with product development – the list goes on. Companies have many options for engaging their customers. But they first have to be open to having the conversation with them, and have some inkling of how they'll use all the insights they acquire. 

Note, an inkling is a clue or a hunch - it's not (yet) a plan. Allowing customers to blog back, blog about, and blog with one another is only the first step in a larger process. With Web 2.0, there's lots of room for experimentation - trying things out, and seeing what works, moving on. What's new is the ability to link things together. 

Implementers and the business managers who support them need not have a formal plan about how they're going to use all the user generated content. What they do need, I believe, is the  willingness and the time to listen, and then to figure out how best to join the conversation. 

      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=8EIDAydW"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=8EIDAydW" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=RfcEDVn5"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=RfcEDVn5" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=OAqfHVZc"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=OAqfHVZc" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=1Gnx32CW"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=1Gnx32CW" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=AcqKVRea"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=AcqKVRea" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=IEXu4Mgu"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=IEXu4Mgu" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=WV4dRLcf"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=WV4dRLcf" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/128780191" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/06/whats_the_future_for_user_gene.html</feedburner:origLink></entry>

<entry>
   <title>After Enterprise 2.0</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/126736524/after_enterprise_20.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2034</id>
   
   <published>2007-06-21T14:43:15Z</published>
   <updated>2007-06-21T15:40:56Z</updated>
   
   <summary>The Enterprise 2.0 conference is winding down in Boston today so it's a good time to reflect on the "two dot oh" phenomena. As industry watchers and marketers, we've come a long way since Tim O'Reilly coined the concept two...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
   <category term="1144" label="blogging" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1143" label="business process" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="149" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="864" label="enterprise 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1141" label="information architecture" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="814" label="metadata" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="84" label="wiki" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      The Enterprise 2.0 conference is winding down in Boston today so it's a good time to reflect on the "two dot oh" phenomena. As industry watchers and marketers, we've come a long way since Tim O'Reilly coined the concept two years ago. With hordes of people crowded into the new Westin Hotel in South Boston and the exhibit hall packed like Grand Central at rush hour (I've yet to hear an attendance count) I felt a rush of excitement in the air. There's a certain sense of headiness when talking with entrepreneurs about their latest products and solutions. I was floored by the breadth of creativity.

But what struck me most is the vision thing – the gulf between the claims about Enterprise 2.0 and the realities of how work gets done. Enterprise 2.0 seems to be about blogging for a living, putting up a wiki, realizing that email is broken, and communicating with customers. Oh yes, then there's unleashing the power of teams, user generated content, and building communities. The list goes on . . . 

Yet two words are missing – management and process. In our always on world, we are inundated with information, and constrained by the limits of the twenty-four hour day. We need to take a hard look at how sharing information online creates new sources of value and better modes of organization. David Weinberger said it best in his &lt;a href="http://enterprise2conf.vportal.net/"&gt;opening keynote &lt;/a&gt;– everything is now metadata. We need to figure out how to harness this incredible openness at our fingertips. Developing a compelling information architecture is going to be even harder than an effective technical architecture. 

What comes next? I'm now planning the collaboration and social computing track for our fall conference. (Stay tuned, we'll be announcing the program later this summer.) I think we need to take a look at the hard issues of designing collaborative business processes. What do you think? I'm open to suggestions. Let me know, beginning by responding to this post. I look forward to our continuing conversation.

      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=n8Vrqamh"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=n8Vrqamh" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=KkhacTIJ"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=KkhacTIJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=rKwDVJ8g"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=rKwDVJ8g" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=WiocIJCJ"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=WiocIJCJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=wCKcU2pc"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=wCKcU2pc" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=G1tBbDrr"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=G1tBbDrr" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=8SUygG7f"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=8SUygG7f" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/126736524" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/06/after_enterprise_20.html</feedburner:origLink></entry>

<entry>
   <title>Enterprise 2.0 Conference Collaboration Technologies</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/126206576/enterprise_20_conference_colla.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.2021</id>
   
   <published>2007-06-19T21:29:16Z</published>
   <updated>2007-06-19T21:38:35Z</updated>
   
   <summary>Geoff and I and Leonor are at the Enterprise 2.0 Collaborative Technologies conference in Boston, and I'm sure we'll have some things to report. In the meantime I used the new facebook polling feature to ask facebookers what they think...</summary>
   <author>
      <name>Frank Gilbane</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Enterprise 2.0" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="149" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="189" label="conference" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="864" label="enterprise 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="1107" label="web 2.0" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Geoff and I and Leonor are at the &lt;a href="http://www.enterprise2conf.com/?priorityCode=MLSLEB16"&gt;Enterprise 2.0 Collaborative Technologies conference&lt;/a&gt; in Boston, and I'm sure we'll have some things to report. In the meantime I used the new facebook polling feature to ask facebookers what they think about a few collaboration technologies and their importance in the workplace over on our &lt;a href="http://gilbane.com/blog/2007/06/facebook_generation_on_enterpr.html"&gt;main blog&lt;/a&gt;.
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=09I7TOsh"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=09I7TOsh" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=RzDZnhGC"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=RzDZnhGC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=UK70plVQ"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=UK70plVQ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=LROhF4jM"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=LROhF4jM" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=nBrEQ1fz"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=nBrEQ1fz" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=EvcDPOWB"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=EvcDPOWB" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=98xvyG0C"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=98xvyG0C" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/126206576" height="1" width="1"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/06/enterprise_20_conference_colla.html</feedburner:origLink></entry>

<entry>
   <title>Wikis and Mashups--QEDWiki from IBM</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/95887936/wikis_and_mashups--news_from_ibm.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.1707</id>
   
   <published>2007-02-14T15:58:53Z</published>
   <updated>2007-02-14T19:50:40Z</updated>
   
   <summary>Here's some interesting news from IBM that caught my eye -- new enterprise mashup technology, QEDWiki from IBM labs.</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
      <category term="Enterprise Wikis" scheme="http://www.sixapart.com/ns/types#category" />
   
   <category term="525" label="enterprise wiki" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="24" label="IBM" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="523" label="mashups" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Here's some interesting news from IBM that caught my eye -- new enterprise mashup technology, &lt;a href="http://www-03.ibm.com/press/us/en/pressrelease/21034.wss"&gt;QEDWiki from IBM labs.&lt;/a&gt; To quote from the press release, it seems that wikis can front-end business process redesign initiatives.
&lt;blockquote&gt;QEDWiki, which is based on Web 2.0 technologies, is applicable for business situations. IBM's Enterprise Mashup Technology breaks down the barriers of traditional application development and provides a framework that uses information from the Web and wiki technology to allow people to create a customized application in less than five minutes. For instance, many businesses rely on weather conditions when planning daily operations. QEDWiki can help a logistics manager plan the most efficient way to send rock salt, shovels and snow blowers to the Northeast to stock the store in time for a forecasted record snow storm. By using the enterprise mashup maker, the manager can "drag and drop" weather reports, online maps and the company's national hardware inventory data into an application that will show which stores will be effected by the storm and which stores need inventory. The technology can quickly enable a store manager to prioritize product deliveries to meet customer demand within a small timeframe. &lt;/blockquote&gt;

Per chance, wikis provide a more intuitive presentation of information than simple lists. This is going to be an important development for collaborative technologies. Moreover, mashups when linked to wikis can facilitate rapid application development--quickly putting up an ad hoc information sharing environment and then tweaking it, on-the-fly. 

But all this begins by having access to well-tagged, self-describing content. The hard part is designing the underlying information architecture, developing the relevant content schemas, and tagging all of the content and their varied contexts in the first place.  
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=6gU0ZJaS"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=6gU0ZJaS" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=GTOobKIC"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=GTOobKIC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=H5MRLCwG"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=H5MRLCwG" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=PCZfCTtj"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=PCZfCTtj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=UfQWhjSo"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=UfQWhjSo" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=hrz14Uho"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=hrz14Uho" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=0k9Vc3Ug"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=0k9Vc3Ug" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/95887936"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/02/wikis_and_mashups--news_from_ibm.html</feedburner:origLink></entry>

<entry>
   <title>Welcome to the Collaboration Blog</title>
   <link rel="alternate" type="text/html" href="http://feeds.gilbane.com/~r/CollaborationBlog/~3/95887937/welcome_to_the_collaboration_b.html" />
   <id>tag:gilbane.com,2007:/collaboration//15.1677</id>
   
   <published>2007-02-05T22:33:51Z</published>
   <updated>2007-02-06T00:20:40Z</updated>
   
   <summary>Another blog? On collaboration? No this is not a mistake. Welcome to the Collaboration Blog at the Gilbane Group. I'll be focusing on business collaboration – the techniques, tools, and technologies that you and I use in our work-a-day worlds...</summary>
   <author>
      <name>Geoffrey Bock</name>
      <uri>http://gilbane.com</uri>
   </author>
   
   <category term="149" label="collaboration" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="24" label="IBM" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="455" label="information sharing" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="130" label="Microsoft" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="128" label="MOSS" scheme="http://www.sixapart.com/ns/types#tag" />
   <category term="453" label="social computing" scheme="http://www.sixapart.com/ns/types#tag" />
   
   <content type="html" xml:lang="en" xml:base="http://gilbane.com/collaboration/">
      Another blog? On collaboration? No this is not a mistake. Welcome to the Collaboration Blog at the Gilbane Group. I'll be focusing on business collaboration – the techniques, tools, and technologies that you and I use in our work-a-day worlds to share information online. 

Along the way I'm probably going to spend some time talking about "social computing" – the new buzz word for sharing information online which IBM is adding to its latest marketing campaign. And inevitably I'll touching on MOSS and VISTA—the Microsoft juggernaut that includes Microsoft Office SharePoint Server 2007 (MOSS), the rewrite of Windows for the 21st century (VISTA), and the other Office 2007 applications. And then there are the neat new tools and applications coming down the pike, from innovative start-ups and established vendors alike. 

More is at stake than this year's marketing hype. Let's put the discussion in context. 

Collaboration is one of those old ideas about the future of technology, going back more than thirty years to the dawn of networked computers. (Yes once upon a time, not so many years ago, even email was new and revolutionary.) Many of us in the industry, developing products in those pre-Internet days, talked a lot about the "three C's" – communication, coordination, and collaboration. We had this crazy idea that once we could connect electronically with one another, we could easily communicate and share information. Then eventually we would ascend to the nirvana of collaboration, and be able to work together with our colleagues to achieve common goals. 

Yes, the easy communication and the information sharing certainly has happened. Yet there's still a lot of overhead when we try to work closely with one another, at a distance. Along the way we're finding that our colleagues are no longer our co-workers and employees in the same company--and that our actions and activities routinely span time zones and organizational boundaries. In fact, many of us now work as independent agents within a distributed (and networked) extended enterprise, in ways that would astound – and perhaps delight -- our fathers and mothers. 

I don't think anybody will dispute the fact that the Internet changes how we work – and how we play. Yet making good use of our endless capabilities to communicate and share information is another matter. We still need to figure out how we can best collaborate with one another to achieve meaningful outcomes—particularly when we have the benefits (and the challenges) of working in a distributed fashion over the Web. Going forward, I hope to have more to say about the business impacts of collaboration, and why some collaborative computing environments are going to be more successful than others.
      
   &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=Mfm3u8iI"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=Mfm3u8iI" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=p7EgaMBC"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=p7EgaMBC" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=dgUx1x0X"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=dgUx1x0X" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=rxHTqG8m"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=rxHTqG8m" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=WnZH9wwM"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=WnZH9wwM" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=2SejJglO"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=2SejJglO" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.gilbane.com/~f/CollaborationBlog?a=fwWdr0El"&gt;&lt;img src="http://feeds.gilbane.com/~f/CollaborationBlog?i=fwWdr0El" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.gilbane.com/~r/CollaborationBlog/~4/95887937"/&gt;</content>
<feedburner:origLink>http://gilbane.com/collaboration/2007/02/welcome_to_the_collaboration_b.html</feedburner:origLink></entry>

</feed>
