It seems that the explosion on the Deepwater Horizon oil platform was foreseeable. The workmen on the platform saw a lot of problems with the technique, but were afraid to inform the management of Transocean (owner of the platform). I won’t judge about the company and reasons of the accident (but I am very sad about it), but it shows that you can avoid problems with the right communication culture.
To discuss the advantages of Enterprise 2.0 we are talking about motivation and better processes, but rarely about prevention of problems which can harm a company strongly.
At first glance it seems to be profitable to keep some topics secret or setting pressure on employees to be quiet, but most of the times it isn’t. Cultivation an open communication culture will help to avoid such bad management decisions. Such problems guiding to a disaster will pop up earlier and needs to be fixed before a catastrophe will happen. Sometimes one person with the right knowledge or idea can help a company to survive, if a disaster can be avoided. This person can avoid it, but need a voice which can be heard by enough people.
It’s not possible to install an open culture without the right tools. In bigger companies it can be done by brown bag meetings. Enterprise 2.0 offers the right tools, but the more important part is to adopt it the right way. Things like training are needed, but it’s an important factor to involve the top management. They must support it. It’s in their own interest. Nobody is perfect. Using the wisdom of the crowd will be the attribute of successful companies in future. Enterprise 2.0 does support it perfectly.
26 Comments
New blog post: Enterprise 2.0 helps to avoid desaster http://blog.enterprise2open.com/2010/07/23/enterprise-20-helps-to-avoid-desaster/
This comment was originally posted on Twitter
Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg my article on Enterprise2Open #Enterprise20 #e20
This comment was originally posted on Twitter
Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
RT @enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
Enterprise 2.0: Open Communication Culture Helps to Avoid Disaster http://j.mp/aCQOnQ by @JoachimL via @enterprise20
This comment was originally posted on Twitter
RT @enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
RT @muellero: Enterprise 2.0: Open Communication Culture Helps to Avoid Disaster http://j.mp/aCQOnQ by @JoachimL via @enterprise20
This comment was originally posted on Twitter
Something REALY important, for Merck? Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #yam
This comment was originally posted on Twitter
enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20: enterprise20: Enterp… http://bit.ly/cvtxL1
This comment was originally posted on Twitter
Reading: Enterprise 2.0 helps to avoid disaster http://ow.ly/2fuiU > reminds me of the CIA use case presented in @amcafee’s #E20 book
This comment was originally posted on Twitter
RT @enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
RT @enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
I agree in principle, however, is this truly a case of not aggregating local knowledge? The managers probably knew they were cutting corners, it was just a risk they took in order to decrease costs. It seems there are four reasons, why you would want 2.0-ify a process:
- to aggregate local knowledge (fixmystreet, etc.)
- to access outside knowledge (wikipedia, peer-to-patent)
- to increase legitimacy of a process (customer-led-design, participatory budgeting, etc.)
- to outsource simple tasks (anything mechanical turk)
So it seems we need to ask of any existing process: Which aspects could be replaced by open value chains? How would we do in those four dimensions?
I agree in principle, however, is this truly a case of not aggregating local knowledge? The managers probably knew they were cutting corners, it was just a risk they took in order to decrease costs. It seems there are four reasons, why you would want 2.0-ify a process:
- to aggregate local knowledge (fixmystreet, etc.)
- to access outside knowledge (wikipedia, peer-to-patent)
- to increase legitimacy of a process (customer-led-design, participatory budgeting, etc.)
- to outsource simple tasks (anything mechanical turk)
So it seems we need to ask of any existing process: Which aspects could be replaced by open value chains? How would we do in those four dimensions?
Enterprise 2.0 helps to avoid disaster http://bit.ly/atpLaN
This comment was originally posted on Twitter
Well yes, it is Important to have means that allow to create these signals. But I think it’s even more important and a bigger challenge for the organisation to make sure these signals are scanned regularly and taken seriously. That’s where Technology does not help a lot…
Well yes, it is Important to have means that allow to create these signals. But I think it’s even more important and a bigger challenge for the organisation to make sure these signals are scanned regularly and taken seriously. That’s where Technology does not help a lot…
Michael, I agree totally. Using this option means to install a good monitoring. You need at least a small team which takes care on a daily base about it.
I guess it’s important for all E20 projects. You need always people which takes care and/or mentors. E20 doesn’t work without resources.
Michael, I agree totally. Using this option means to install a good monitoring. You need at least a small team which takes care on a daily base about it.
I guess it’s important for all E20 projects. You need always people which takes care and/or mentors. E20 doesn’t work without resources.
Enterprise 2.0 helps to avoid disaster http://bit.ly/bVxzH2 Could BP have avoided the disaster with E2.0. Far fetched, but…
This comment was originally posted on Twitter
“Enterprise 2.0 helps to avoid disaster by Joachim Lindner” – #E2.0 another use of Enterprise Social Network – http://bit.ly/blE4sN
This comment was originally posted on Twitter
RT @thethinkingape: RT @enterprise20: Enterprise 2.0 helps to avoid disaster http://bit.ly/cSOYMg #Enterprise20 #e20
This comment was originally posted on Twitter
Hello Phillipp.
I aggree with your comment, but I would like to add something. A company with the full adoption of Enterprise 2.0 will get a cultural change. Closed top down communication will change to an open bottom up. Such an enviroment won’t have employees which are afraid to tell their mind about job and company.
I know it’s a little bit idealized picture, but I am pretty sure that companies which are running E20 with openess will develop in this way. It needs some time, but they will. And theses companies will be the winner in future.
This example shows that companies which are working like they did are not the winner.
Hello Phillipp.
I aggree with your comment, but I would like to add something. A company with the full adoption of Enterprise 2.0 will get a cultural change. Closed top down communication will change to an open bottom up. Such an enviroment won’t have employees which are afraid to tell their mind about job and company.
I know it’s a little bit idealized picture, but I am pretty sure that companies which are running E20 with openess will develop in this way. It needs some time, but they will. And theses companies will be the winner in future.
This example shows that companies which are working like they did are not the winner.
Enterprise 2.0 helps to avoid disaster http://bit.ly/cgdTVA
This comment was originally posted on Twitter
Enterprise 2.0 helps to avoid disasters http://bit.ly/du3KJk
This comment was originally posted on Twitter