Social software means not having to know who knows what
I recently listened to an excellent podcast on Technation from Rob Levy, the CTO of BEA systems. They have software development teams in Silicon Valley, China and India. He was talking about the challenges of communicating over distance and timezones. He discusses how in conventional modes of communication you have to know who to ask, or risk spamming everyone in the company with broadcast email. Even if you do know who to ask, timezone differences can mean a 2 day delay between each post a conversation, and they might not even have the best answer to your question. With social software like wikis he says, you don’t have to know who knows what. If the knowledge community is actively using the tool, anyone who’s interested and has a useful contribution will respond.
He also talks about how if a new idea comes up, in the past the champion of the idea would have to ‘socialise’ it. This meant talking to lots of people, delivering presentations, and lobbying senior management for support to consider it in a wider forum. In the world of social software if the idea comes up, and people listen and start discussing it, that means it may well be a good idea. If they don’t, it’ll die on its own due to lack of attention. Senior management will be far more likely to fund further exploration if lots of people are already enthusiastic about it and are talking to each other across operational silo boundaries. If the idea can thrive and survive in a space mediated by social software, the argument goes, it’s more likely to be a good one.
The podcast is definitely worth a listen.
We had New Zealand’s first
They tend not to be as goal directed as Open Space sessions, and are more focused on sharing knowledge, building social networks, and bouncing ideas off each other. They do have a lot of the same attributes as OST though, in terms of developing the agenda at the beginning of the day, things taking as long as they need to, everyone is a contributor, voting with your feet.