Enterprise 2.0 in small steps ...
Tante sono le barriere (e di diversa natura) che ci si trova a dover superare nel momento in cui introduciamo in un'Azienda un qualche cambiamento. Non sempre, nonostante gli intenti dichiarati, tutti riescono a superare le paure indotte dalle novità e dalle innovazioni (novità che portano cambiamenti in positivo).
Niente di cui stupirsi, è del tutto naturale.
I progetti che introducono i social media all'interno di un'Azienda portano moltissimi cambiamenti, soprattutto culturali. In alcuni casi il nuovo "paradigma" è talmente differente da quello esistente che sembra quasi naturale chiudersi in un atteggiamento difensivo che salvaguardi le (tranquillizzanti) procedure ormai consolidate.
Tuttavia è sufficiente varcare appena la soglia del cambiamento, che tutti i pregiudizi e le paure svaniscono improvvisamente. La spirale positiva changes brought about by greater collaboration among employees, from a cross communication much more clear and efficient, the involvement and participatory discovery of new horizons, break down barriers and make you forget any preconceptions.
But how to give the first impulse to fly Enterprise 2.0 within the company?
My advice is to overcome the mistrust first starting "small", with something simple
the usefulness of which is immediately perceived by all.
short, starting with small steps
.
Personally I found it very effective to start with an internal blog. Probably already in the planning stages project you may find the need to start at the same time more 'of un0 (some departments have specific requirements).
The benefits of using an internal blog are many and may involve different sectors of the company.
Here are some of the examples that I quoted in a recent project:
- shorten the distances between offices , encouraging conversation topics of common interest.
- stimulates participation and gives voice to all users. Anyone can post a reply to a comment.
- can become a valuable training tool, launching a process of "Continuing Education " within the company (Have you ever thought about a series of posts dedicated to the use of various software tools in the company?)
- favors the emergence of a " Business Community", allowing the sharing of both business and leisure moments.
- reduces the workload and archives of e-mail server . All the messages that interest groups or the entire company, are organized into a single enterprise repository and no more 'replicated on each mailbox.
means less network traffic and a lesser amount of space used, and lower costs. - not contribute to congestion on our boxes mail, which are already strained by the daily work and spam.
- not forcing players to open a message and having to manage (delete or archive in some way).
- keeps track of corporate communications much better than does our mail box (especially after the reorganization of the archives and cleaning of the messages considered unnecessary).
These are just some of the benefits of using an internal blog.
Each has its own reality, and many come directly from the editorial.
I promise the next post I will try to further deepen the concept of "Internal blog, offering examples of using additional and perhaps giving some indication of how to make the publishing schedule (or not needed?)