1. VALUE AT ALL COSTS THE PERSONAL IMPACT OF SOCIAL COMPUTING
2. PEOPLE AS NOT RESOURCES TO BE EXPLOITED
3. REALIZE THAT THE CROWD IS NOT ALWAYS RIGHT
Those would be my first three statements in a code for the new Enterprise 2.0 practitioner. Why do we need a code? Because the implications of social computing go far beyond a piece of technology. The personal nature of social computing means we have a moral responsibility.
Being at the beginning of Enterprise 2.0 means that we will undoubtedly see several failures in addition to the triumphs. A Code (built through collaboration of course) will help the advancement of Enterprise 2.0 as a discipline.
I was reminded of the awesomeness of the impact we can have during a discussion over coffee with Jevon MacDonald of firestoker.com. Jevon and I shared stories of our experiences in social computing as practitioners and lessons learned. Both of us had experiences which started with an ambitious objectives in the earlier years that produced results very different than what we were hoping to achieve.
The BIG lesson though wasn't about "being overly ambitious / progressive goals with social computing", or even "how to be successful in an Enterprise 2.0 implementation". The BIG lesson was that the beliefs, thoughts, ideas of individuals was more than just data and information. It was a representation of themselves personally. Depending on the topic at hand, the implications are that 'heated comments, critics, rants, and worse' bcome personal attacks. These could have long lasting and severe implications.
I am however, more than ever, a huge proponent of the positive aspects of Enterprise 2.0 having witnessed amazing results in both a cultural sense and a business value perspective. My point isn't to scare people away, it's to remind all of us practitioners that we're dealing with more than just some interesting technology. We're dealing with people. That's just background on the first statement, I'll talk to the other two statements in future blogs but I really would love to hear your thoughts.
Are you a practitioner?
What do you think of such a code?
What lessons have you learned?
What other 'rules' would you add?