Keeping it together... when you're not

The WSJ had a great article about working together in virtual teams - since you have to be a subscriber to read the whole article - I'll give you the highlights along with my compelling commentary!:

1. invest in an online resource where members can learn about each other - can anyone say... Social Media!
2. choose a few team members who already know each other - this makes a lot of sense, but they do say that if you have too many people that know each other - then there is a tendency for the group to become stale and predictable. You need fresh people and ideas to keep interest and energy up.
3. identify boundary spanners (people who have and make a lot of connections) and make sure they make up at least 15% of the team - these people serve as social glue,and are seen as SO valuable that they make it into #4 as well
4. cultivate boundary spanners as a matter of practice within your organization - having these people throughout the company helps ensure that more people will meet and collaborate
5. break the team's work up into modules so that progress in one location isn't overly dependent on progress in another - some members will be out sick, some will be more productive than others, and some tasks just plain take longer. If you can plan activities so many things can be done in parallel, it helps ensure no one is sitting around waiting for other groups to catch up. In short, everyone can be productive all the time.
6. create an online site where a team can collaborate, exchange ideas, and inspire one another - this is an offshoot of item #1. We live our lives online. Give us a way to collaborate!
7. encourage frequent communication, but don't try to force social gatherings - social gatherings early on - bad - get to work first. Social gatherings later on are good - when you already have a working relationship.
8. assign only tasks that are challenging and interesting - well sure - that would make everyone's job a lot better - but I don't think this one is actually do-able in practice. Some things just have to get done - and they might have to get done by a virtual team - and they might not be very interesting.
9. ensure the task is meaningful to the team and the company I'd argue that if the company doesn't care - why do it? But meaningful to the team? Again, you might be asking too much. Some things you don't care that much about just have to get done. I really don't care much about my lawn being mowed, but it's got to be done. So I make sure it gets done. Same with going to the dentist 2x a year. Some things are just necessary, yet not very interesting.
10. solicit volunteers as much as possible. This is a great way to make sure people want to be involved. This is the root of the open source movement - as well as Wikipedia and other online collaborative projects. If people are inspired, they will get involved, stay involved, and give it their all.

Most of the best practices here aren't that different from basic working best practices: meaningful work, frequent interaction, and a place to collaborate.

A lot of what I've read says that teams that share the same values do better together - and teams that get together often are more productive - but I think it's more about being on the same page. If you want to be there, you're working on something you want to work on, you touch base on a regular basis - and you have the tools to do so effectively - I think any team can be pretty successful. I am noticing - and taking note - of some sorts of conversations that should be had in person. I'm going to keep a running list of those and publish them in a few weeks.