« Email overload: what went wrong? | Main | Supply and demand 2.0 »

January 22, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e54fa4700a883300e54fed04788833

Listed below are links to weblogs that reference McAfee on Widening the Flow:

Comments

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

Jason

Michael,

I think you and Andrew are absolutely correct. The thing I would add is that new Enterprise 2.0 solutions need to address how people have worked historically and account for habits and current tools. For example, you mention that email is "old world." I couldn't agree more. However, it is the lowest common denominator and difficult to supplant. I work for a company that addressed this issue by adding email into the collaboration flow (GroupSwim). When someone has content or knowledge that should be added into the collaboration tool, they simply email the community or add the community to an ongoing email thread. When the email goes into GroupSwim, the sofware analyzes the semantics of the message and automatically assigns tags to it for easy search and connection with other related content. I blogged on this strategy as well (http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/). We went back and forth on whether to add this feature or not, but our customers eventually forced us and we are glad they did.

Jason

Michael Idinopulos

Jason, I agree. The Socialtext wiki (www.socialtext.com) supports emailing into the wiki, and we have many customers for whom this is the killer app.

The comments to this entry are closed.

My Photo

Twitter Updates

    follow me on Twitter