Collaboration works when community thrives
August 26, 2008
Right now I’m gearing up for TechEd and DemoJam. This is a technical conference where I am on a couple of panels. Who would have thought that a suit (and a bean counter by trade at that!) would qualify let alone turn up for for geek gig. I’ve been before but this is a special occasion because the team I’ve been part of the last two-three months has been selected to demonstrate ESME in front of a highly critical audience.
I can’t say too much about it because there are some surprises in store but the bigger story is how the project went from casual conversation to a project that has not only ended up as a product in less than 90 days but also as an exercise in the power of community.
The long version (and it is long as I’ve written it case study style) is over at SDN. The short version goes something like this:
- When affinity groups decide to swing into action they can become powerful forces for delivery.
- Communities allow informal, loose networks to self organize in ways that seem to attract the best people for the job.
- Since all projects require expertise, the ‘experts’ also self organize when necessary to form sub-groups.
- There is no competition among players because there is a common goal but cooperation and collaboration is intense.
- Defined goals and strict deadlines concentrate the mind on what needs to get done.
- Regular communications across a variety of channels including phone, Skype, email, Twitter, GoogleGroups and others complement one another.
How much friction might be removed if these forms of self organization were allowed to flourish? That’s the burning question. We’ve found that almost all the friction you’d expect in a project has vanished because the electronic means of communicating create their own audit trails and they serve to move us along.
There is however a gotcha - community precedes collaboration and cooperation. It cannot be forced or imposed. Imagine therefore if the Big Four could get their act together. It’s unlikely given what I know, but the model I’ve described is one that I now know is proven. There is still much to glean and learn but this is a solid start. It is a form of emergent behavior but I wouldn’t go overboard on that aspect.
Related articles by Zemanta
- Lifecycle of Emergence
- Community is Open Source: On SAP Developer and Business Process Communities.
- SAP Sapphire - Berlin
- ESME: Is This What an Enterprise Twitter Could Look Like?
- Today’s project is ESME
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=d738aa40-d5c9-4891-aabc-f8b168f2e369)
Comments
3 Responses to “Collaboration works when community thrives”
Got something to say?
On FriendFeed, this post was liked by 1 person and commented on 0 times hide
I’m more and more passionate about the collaboration-inside-the-firewall space, but as I’m thinking about it, I’m also thinking about just how rapidly these types of networks need to form, dissolve, and reform. We have to develop something that doesn’t feel like we’re putting up a network just to make a call.
Hmm. Now there’s the analogy. At 1:50AM my time, I get an idea. Now, to sleep and forget it.
[Reply]
Dennis Howlett reply on August 26th, 2008 7:13 am:
Chris - in the full case study you’ll see the team has a very specific goal and therefore it likely will dissolve but could easily reform. To be honest, this team could do a TON more stuff and still be relevant, sassy etc. But I get your point. Interestingly, this was a self imposed firewall.
[Reply]
Best of luck with the demo Dennis. Go get ‘em.
M
[Reply]