by Jeremy Thomas
Aaron Newman and I have been working for several months on putting an Enterprise 2.0 implementation guide together. Aaron Fulkerson, CEO of Mindtouch, has been doing the tech editing for us. And we’ll have another all-star, Jevon MacDonald, doing the forward for us. This is my first book, and let me tell you the process is extensive. Figures and illustrations have to follow a special naming pattern, chapters have to meet pre-determined page counts, and the tone of the book has to be consistent (which is tough when you have two authors writing it). Aaron and I edited each other’s chapters as they were completed, then sent them on to Aaron F. for more editing.
Then it’s the publisher’s turn to edit which means even more revisions and re-organization. But I must say this process, though tedious, adds tremendous value.
What’s really interesting is I’ve never met my co-author in person nor have I had a phone conversation with him. We used Basecamp to manage our deadlines and share deliverables. Twitter, IM and email were used for everything else (Basecamp rocked). I am continually amazed at how efficient it is to collaborate using social technologies.
I’ve been spending a lot of time with the book over the past few months (they didn’t give us any chance to give our input into the cover design. I’m not sure what I think of it), which is largely why I’ve been neglecting this blog.
But besides the book I’ve spent time adapting to the consumer world with my job at active.com. We’ve got a lot in the works to overhaul the site and make it more social, engaging and single-purposed. But we’ve got a long way to go and I’ve got a lot of people to manage.
Through the transition away from consulting towards a proper job I’ve learned a lot of things about how E2.0 may or may not add value to an organization. I must say I’ve been somewhat unbalanced with this blog tending to lean in favor of Enterprise 2.0 without adequately considering alternative perspectives. Going forward I plan to entertain opinions from the dark side a bit more to drive debate into a growingly homogenized E2.0 “industry”.
by Jeremy Thomas
My buddies over at e2oh.com were recently asked to blog over at wikipatterns as guest bloggers. These guys have been instrumental in educating a very traditional management consulting firm on the values of social computing, not only for internal use but for external use with clients. They fought many an IT battle to get the entire firm (17,000) to adopt an enterprise wiki.
Well done Nate and Jay.
by Jeremy Thomas
Recent discussions at work have prompted me to re-iterate something very fundamental that often gets overlooked when it comes to Enterprise 2.0. An organization will never adopt a single social productivity tool. Knowledge will ALWAYS be scattered. We’ve come to accept this on the Internet where search engines make information on a myriad sites searchable, but for some reason organizations think they can get everybody to use “wiki X”, and that the search feature in “wiki X” will be good enough.
“Discoverability isn’t an after thought , it’s the core”
Organizations need to embrace the fact that their data will be federated. Sure, workers will put their documents in “wiki X”, but they’ll also put them on the file share, in content management systems, and on email servers. Data that cannot be found is useless. Enterprise search will unlock data and increase the propensity for information (and the knowledge workers who create it) to be discovered. Discoverability leads to recognition, and recognition leads to increased participation. Enterprise 2.0 must be approached holistically.