We selected by:
1) Teams currently using an open source wiki tool. (Know the process & value; remove rouge software from company)
2) Teams that publish to large, but contained to a single department, email lists. (Process in place for writing frequent, quality content; focus is giving the readers a small, safe read-only introduction to community)
3) Teams with heavy document collaboration needs -- especially if team was globally dispersed. (Development)
4) Teams with a strong, passionate, voluteer leaders.
This is excellent, thanks for sharing! I know many out there can struggle to figure out which groups to target.
Our pilot membership was determined through the following highly scientific process:
1) Ask people we had to include
2) Ask people we wanted to include
3) People that found us.
This turned out to pretty much break out in the following manner
1) IT, Legal, HR, Communications
2) Anyone with a penchant for bucking the system, starting self-initiated IT projects, or possessing the unique mix of charisma and vision for open collaboration. This last group also had to prove it, not just say it. As in if they didn't actively participate, they were marginalized.
3) Other rogues hoping for a change.
For us, it worked to keep the pilot "underground". Once we had our core folks lined up, we didn't turn anyone away and provided no direction on who to invite. We had no messaging, no marketing, no official backing. The viral approach took longer but eventually with 1/4 of the company still in the underground pilot, deploying "officially" was much easier.
We selected a small group of collaborators who were feeling the most pain from trying to survive with a byzantine network filefolder hierarchy. We had to involve remote people, collect research, and have discussions in order to provide the ringleader with enough input to do his work.
We also engaged our technical/development team in order to work on some innovation projects & capture some tacit knowledge as we moved from silo teams to a more cross-trained technical team.
We'd also been wrestling with the idea of a better communication platform for about a year, and we changed our "solve everyone's problems" approach to a "solve a few important problems immediately, and let it grow from there" approach.
It was a combination of "Just Do It" & "Necessity is the mother of invention." I guess pain is a good motivator, too.
In every pilot IT, HR, Legal and Communications should be involved. The next step is much more difficult. Include people who do the 'work' and that's different for every company. The people you want to inlcude should be a complete organizational unit, so if they want to collaborate different on projects you have to be able to include the whole projectgroup (mostly being within an organisational unit).
Hey Carl Samberg, sorry, this notification got missed in my inbox! I no longer think about these things for a living, but I imagine if you post a fresh question in this group you'll get the latest thinking from our awesome customers.