How to move to the cloud messenger
Recently, we launched a series of materials on various management tricks that should be paid attention to IT managers.
Today, our attention was attracted by the Khan Academy case , in which a story about moving to a new corporate messenger is provided.
/ Photo Kārlis Dambrāns / CC
')
Messengers for corporate tasks - a new trend, which you can already start to get used to. Such tools allow you to structure the communication team and in many ways replace the usual e-mail.
The absolute leader in this segment of applications is Slack. Its innovative solutions, convenience and integration capabilities have done their job - today it is most popular in the field of IT.
In a situation where some companies are still actively using email, while others have already switched to something like Slack, there is a problem when you need to do something first. Transferring all communication processes to the messenger seems to be quite a simple task, but as always, there are some pitfalls here.
The Khan Academy team just shared a similar integration case for two instant messengers. The fact is that they rather tightly integrated their software deployment system for working in HipChat, but decided to completely switch to Slack.
To accomplish this task, the team only needed to take advantage of the already created integration solutions that have already been implemented by third-party developers for Slack. The only thing I had to do on my own was setting up the integration of the Sun Wukong and Slack deployment system.
/ Photo: Gustavo da Cunha Pimenta / CC
On the other hand, in addition to technological difficulties, there are always organizational nuances. Khan Academy prefers to adhere to certain rules associated with different groups of employees, each of which has its own level of access to data.
Thus, the use of individual rooms sets a good opportunity to communicate with former colleagues, which is customary to do in the Khan Academy, and not open access to sensitive company data to freelancers who do not always linger in a team for a long time.
To transfer such principles of work that had already been formed in the old messenger of the company, it was decided to draw up a specific document that would become a formal presentation of these approaches. Further, it was used to recreate the necessary structure already in the new messenger.
It turns out that even such a seemingly simple task as a transition from using one messenger to another can be quite a serious challenge even for such a flexible and innovative company as Khan Academy. Accelerate this process by carefully preparing and documenting all necessary actions.
PS A little about the work of our IaaS provider:
Today, our attention was attracted by the Khan Academy case , in which a story about moving to a new corporate messenger is provided.
/ Photo Kārlis Dambrāns / CC
')
Messengers for corporate tasks - a new trend, which you can already start to get used to. Such tools allow you to structure the communication team and in many ways replace the usual e-mail.
The absolute leader in this segment of applications is Slack. Its innovative solutions, convenience and integration capabilities have done their job - today it is most popular in the field of IT.
In a situation where some companies are still actively using email, while others have already switched to something like Slack, there is a problem when you need to do something first. Transferring all communication processes to the messenger seems to be quite a simple task, but as always, there are some pitfalls here.
The Khan Academy team just shared a similar integration case for two instant messengers. The fact is that they rather tightly integrated their software deployment system for working in HipChat, but decided to completely switch to Slack.
To accomplish this task, the team only needed to take advantage of the already created integration solutions that have already been implemented by third-party developers for Slack. The only thing I had to do on my own was setting up the integration of the Sun Wukong and Slack deployment system.
/ Photo: Gustavo da Cunha Pimenta / CC
On the other hand, in addition to technological difficulties, there are always organizational nuances. Khan Academy prefers to adhere to certain rules associated with different groups of employees, each of which has its own level of access to data.
Thus, the use of individual rooms sets a good opportunity to communicate with former colleagues, which is customary to do in the Khan Academy, and not open access to sensitive company data to freelancers who do not always linger in a team for a long time.
To transfer such principles of work that had already been formed in the old messenger of the company, it was decided to draw up a specific document that would become a formal presentation of these approaches. Further, it was used to recreate the necessary structure already in the new messenger.
It turns out that even such a seemingly simple task as a transition from using one messenger to another can be quite a serious challenge even for such a flexible and innovative company as Khan Academy. Accelerate this process by carefully preparing and documenting all necessary actions.
PS A little about the work of our IaaS provider:
Source: https://habr.com/ru/post/296382/
All Articles