Reflections on a move to MS Teams™ to support home working during the Covid-19 Pandemic
We hired a new IT manager just before the recent Covid-19 pandemic lock-down, who completed a project moving us to MS Teams. This has proved inspired, enabling an almost seamless move to remote working for an R&D staff of around 15 engineers.
We use MS Teams™ for meetings, and I believe the video is important for small team or one to one conversations because otherwise the facial expressions and body language which we as humans use to interpret the emphasis of verbal communication is lost. Screen sharing has proved useful to facilitate group work on a document, and for presenting.
In larger meetings video can be switched off ( to save bandwidth of course), enabling involvement in a meeting by listening whilst also rapid typing in order to attend to other important tasks.
MS Teams™ supports effective communication management because all information (conversations and documents) is accessible in one location, and searchable. Previously information might have been lost as we moved from an email thread, to a skype conversation, or even a telephone call.
It is necessary to map the business process to the use of MS Teams, to organize the information carefully in the back-end repository (usually Sharepoint™), and to logically arrange the teams and channels to match the business structure. If each user was allowed to create their own data organization scheme, before long the application would degenerate into a confusing mass of information, in which it was difficult to find and track relevant information, and would become very ineffective to use.
Users must be educated about how to use MS Teams™ effectively, since simple features such as tagging colleagues in a conversation to trigger an automatic prompt and enable them to easily find and join a conversation in which they should be engaged are available.
The obvious disadvantage of integrating such an application into the company business operations is the potential lock-in with one the provider, and the difficulty of subsequent migration to another platform.