|
|
New Paradigm - Lessons for those attempting collaboration projects belongs to Industry  by Brittain on Nov 02, 2007 - 11:31 AM read 1198 times |
Just finished "The Wiki Workplace: Leveraging Collaborative Technologies in the Enterprise", an excellent piece from our friends at New Paradigm. It's a concise and impactful read that I highly suggest. They may dwell too long on implementation tools at times, but overall they present a strong NGE message.
One particularly relevant part I wanted to excerpt for our team concerns six lessons learned for implementers:
- Invest in an early adoption community. Or put another way, lead by example.
- Expand communities organically and in small increments.
- No forced participation, instead create value with your project: better communication, easier sharing, faster file access, etc, etc, etc.
- Let the community decide it's path when migrating tools. Sound distinctly familiar? SocialText <cough, cough>.
- My personal favorite, different communities and models require different tools to get started.
- Everyone else in BSG's personal favorite, companies need a sense of how permeable the enterprises' boundaries could and probably will become as these tools evolve.
All great lessons to have in mind as we move forward.
Lastly, I'd be remiss if I didn't throw in my personal favorite quote from the entire paper:
"Regardless of which implementation strategy is selected, it's important to focus on the business benefits, not the technology enabled by the tool."
-
Wikis wikis
a reply to New Paradigm - Lessons for those attempting collaboration projects
by Steve Douty on Nov 02, 2007 - 12:08 PM read 85 timesThanks for putting these nuggets out for all to see.
New Paradigm has done a LOT of research in this area and have meaningful input to any collaborative process.
I'm still going to push for the addition of Wikis - NP is not saying that Wikis should not be included in the options presented to the user - in fact, the argument that is made is that the user should be able to choose from among a number of options. NP happens to be really big on Wikis - so it would be a serious gap in our product if we were to omit it altogether.
In fact, they use the term "wiki" everywhere - having everything else but Wiki would seem to be a disconnect from their philosophy.
-
Actually I agree
a reply to Wikis wikis
in a conversation thread started here
by Brittain on Nov 02, 2007 - 12:22 PM read 80 timesCouple of major comments:
- I've clarified my post: "wiki <cough, cough>" has become "socialtext <cough, cough>". Specifically, we're dealing with a migration issue ourselves and IMO the NP suggestion applies.
- The business need of whiteboard-style collaboration would likely dictate the inclusion of wiki-style functionality. This is perfectly consistent with the NP philosophy (solve the biz problem with the appropriate tool).
- I'd think you'd agree their use of "wiki" is more emblematic than literal. Throughout this paper they encourage the idea that the "wiki workplace" is a more compact way of saying the "blog, forum, IM, social network, wiki, e.laborate workplace".
-
Featured
Author Profile
Subscribe
Feed for nGenera Community:
Public 
Secure
Why subscribe? What is RSS?