There is a long time (about three years) I haven’t published this type of article on this blog about dos and don’ts and social business. But when Gartner released a prediction that through 2015, a whopping 80% of social business efforts will fail to achieve their intended benefits, hampered by « inadequate leadership and an overemphasis on technology », back to basics is may be not a bad idea. So here is a  commented list of dos and don’ts.
Accenture firm has released a new study on its technologies vision and their impact in 2013 on companies, with the central idea that any business becomes digital. This is not the first time I come back on this issue with some IBM studies, MIT, Sloan Management review, Mc Kinsey … the idea of digitizing the company is increasingly highlighted. But as nothing is worth pedagogy, and pedagogy is also repetition, here are the main points, which are related to the ideas presented in this blog, and not the entire study. I pass on all the tool side, data … (Even if it is interesting, but distant from the editorial line of this blog).
When you meet top managers for a collaborative project, the two fears that come up most often on the table is the loss of control and the idea that « collaboration = anarchy or self management. »Â I’ll gloss over the loss of control (if there is no trust in its employees it can’t work and managers have to understand that employees have other means to put you in the mess if they wish).
But this idea of ​​self management, I can hear it more and more often from people more familiar with the concept of management / enterprise 2.0. So finally Enterprise 2.0 = self management ?
When you read articles about enterprise 2.0, we always seem to live in a world where everyone is helping others, collaborate, remove power relations …Â As a famous singer sang :
what a wonderful world
Really ?
I often speak about collaboration or community management, but finally I realize that I have never discussed the various stages of development of a team working in a collaborative way. Maybe your teams are already working this way, but generally they have to cross various stages of maturity before succed to be a real community. Everything is a cycle, a process, which often begins again with the end of a project or changes within the team (hopefully you do not start all over again). If you are interested by that topic, just go and check the community maturity model of the community roundtable, a real work of art, more focus about community maturity inside the all organization.
It goes generally through 4 stages: they can be more or less long, you can spare one of course, it remains a model with all that a model has of restrictive.