X
Business

Taking productivity lessons from open source

Even if your organization doesn't produce software or work with open source development, you can still take some lessons from open source communities -- in particular, how to get work done with fewer meetings and less real-time.Steven J.
Written by Joe Brockmeier, Contributor

Even if your organization doesn't produce software or work with open source development, you can still take some lessons from open source communities -- in particular, how to get work done with fewer meetings and less real-time.

Steven J. Vaughan-Nichols covers some of the things that outsourcing companies can learn from open source, but this really applies to any organization -- whether it has remote locations or not. But they're particularly useful for organizations with a distributed workforce with non-English speakers. In particular:

  • Don't have a meeting when an email will do. Coordinating schedules is an often unnecessary headache when an email exchange would provide the same information.
  • Any method with an "audit trail" is better than a phone call or face to face meeting for those who may need to catch up later. (It's also far better for remembering who has what action items, and what has been decided."
  • As Vaughan-Nichols writes, "E-mail and Web communication make it far easier for a non-English speaker to read or translate e-mail and Web text than to understand several English speakers chatting on the phone." (Frankly, this is also true when all of the participants are English speakers, too. Trying to understand five people on a conference call, with several huddled around a speaker-phone, is usually less than pleasant even if they are all speaking the same language...)

Of course, the flip side of this is that it works well up to a point for a distributed team. Phone calls and the occasional face to face meeting are really necessary to form the kind of bonds that a team needs to function well. The distributed method is great for projects that don't require a lot of close coordination, but if you have a team that is expected to function well together over multiple projects in an ongoing capacity -- you need the occasional real-time meeting.

And, as I mentioned, the asynchronous methods of communication aren't limited to distributed teams -- they work just as well to help people get more work done, even if they're just down the hall.

Editorial standards