Knowledge Management resources

Interesting Blogs

Google Analytics

« My App Gap Posts for July 2009 | Main | Paula Thronton’s Enterprise 2.0 Blogcast Series and Context of “Intent.” »

August 04, 2009


Feed You can follow this conversation by subscribing to the comment feed for this post.

Samuel Driessen

Interesting topic! If you would've asked me this a couple of years ago I would have said: If you don't integrate with email, you're going to loose.
What I see in my personal work life, and I see this with others too, is that people like to have new cools close by (integrated). This is the easiest way to get the new tool in your routine. On the other hand, people use different interfaces for different purposes. For instance I don't understand people using the site to post updates. Using Tweetdeck is much easier, more functionality, groups, etc. But sometimes I too use Twitter (e.g. because I'm working on someone else's pc). Hope this helps!

bill  Ives

Samuel - Thanks for your experiences. I certainly agree on twitter. I look forward to speaking next week. Bill

Jordan Frank

There are a handful of important distinctions between Web 2.0 and E2.0. I think one of them is a drive towards greater integration on platforms. This is not just for the sake of putting everything in one big E2.0 silo but rather for the sake of the actual use case involved.

Web 2.0 is made up of a few key pillars like Wikipedia, Twitter, standalone blogs, tagging services, feed services and search. For the web 2.0 scenario were people are more personally driven than group driven and there are a few key channels for search, feeds tags and encyclopedia of reference. However in the E2.0 case, the predominant use is project team work - which involves a need for a go-to space that allows for over-time communication, joint work on timeless documentation, discussion, tagging and micro-messaging type communication. In an E2.0 scenario, you could separate your blogs from your wikis (and micro-messaging and whatever comes next), but in many if not most cases this may fragment workspaces unnecessarily.

With respect to email - I think you can't win unless your recognize email and its role - as a channel for publishing (to a blog, to a wiki, to a micro-messaging system), notification (from all the above), and response. The only problem with email is when you use it as the platform for storing, rather than simply messaging, information.

bill  Ives

Jordan - Thanks for your thoughtful comment. Bll

The comments to this entry are closed.

My Photo

RSS Subscribers

Share Portals and KM on Facebook

  • Share on Facebook


AddThis Social Bookmark Button

Some Recent Articles

Linked In

  • View Bill Ives's profile on LinkedIn

Site Meter