Don’t share if you don’t want to
Over the past few weeks I have done a number of presentations of AlignSpace and I had an even greater number of conversations around it. All these discussions are lively and healthy and they help me understand how the concept of Social BPM is perceived.
The number one concern that I hear every single time is something like this: “We don’t want to do process discovery for our processes on a public site. In fact, we don’t want to expose any internal process information to others as these processes are the essence of our competitive advantage. A collaborative platform is fine, but we only want to collaborate internally. Can we please have a version of AlignSpace that can be installed on our servers?”
Well, if you create a group on a site like LinkedIn or XING, you decide if it should be a public group that is visible and open to everyone. If you want to create a private group over which you want to have full control in terms of who is allowed to see and access it, you simply set it up that way.
With BPM projects on AlignSpace it is going to be the same way: Invite only the people to your project that you want to participate and hide it from the rest of the world.
Having said that, there was a time when open source software did not exist and where companies protected their code. I am not saying that we’ll soon have process design in an open source fashion, but then again you never know.
Feedback and comments are welcome.
Thanks,
Thomas

28.04.2009 15:03
It's my belief that the community will start to find a natural equilibrium between the content that is non-differentiating and generates value for the community through re-use/sharing and content that is differentiating and needs to be held private. There is a tremendous amount of content out there already that falls into the former category but there are limited mechanisms that allow it to be shared effectively.