Whether you’re a new hire or your organization has finally consolidated all of its technology needs into Microsoft 365, there are challenges when it comes to adoption, including collaboration across team members and departments, learning and more with Microsoft Development Services. How can end users get up and running as quickly as possible and how can admins help the overall adoption process, especially remotely?
Know when to use what
One of the most important things to consider when it comes to remote adoption is learning and knowing when to use what. The difference between “learning” and “knowing” in this case is important.
In this context, “learning” means understanding the purpose of each Microsoft 365 workspace. “Knowing” means applying what you’ve learned and understanding how your organization takes its unique approach to collaboration. Working remotely makes this practice even more important because you won’t have access to the learning observed in an office.
With Microsoft 365, this can get a bit tricky due to the different workspace solutions that come together. Luckily, we’ve detailed common collaborative workspaces . Here is the graph of this article :
Know what your team is using effectively
It’s important to differentiate between Microsoft 365 options and why they exist, but also to know what your organization uses specifically . If you’re new to the job, you’ll need to use your intuition and educate yourself (especially if your entire organization is adopting Microsoft 365).
The first part, intuition, involves analyzing how you and your colleagues prefer to collaborate on an individual level. Similar to the graphic above, there are key differences between using a tool like Yammer for company-wide communication and individual collaboration with Microsoft Teams.
The second part, inquiries, is something you can and should do as soon as you start. In the context of remote workers, this means moving to one-on-one conversations and engaging in Teams channels and Yammer groups. If someone doesn’t offer help right away, it’s best that you take the lead and start the conversation. Consider not only how everyone works together, but also the cadence . Here is an example:
Manner: “We use Microsoft Teams to collaborate every day. »
Cadence: “We typically make announcements in Teams channels to initiate projects, then follow up using Planner and one-to-one conversations. »
Chances are everyone prefers one-on-one conversation, although you should expect your co-workers to prefer blocking out their time for a meeting or a call! It’s always best to ask for opinions, but analyzing and seeing what makes each person more responsive is a surefire way to make Microsoft 365 adoption and collaboration easier without even being in an office!
Once you’ve identified commonly used workspaces for collaboration , the next step is to simplify processes. To do this, we recommend that you recreate document versions and always have reference places.
This may include leveraging the Teams architecture to facilitate content sharing and collaboration while reducing redundancy. For example, people may prefer one-to-one collaboration, but if you notice a tendency to share important documents within the team or department, it may be better to host them in a Teams channel rather than constantly sharing a document. of your OneDrive with each person. Quick fixes like this not only streamline processes, but also help other people collaborate effectively!
Admin support This article has primarily focused on what remote end users can do to accelerate their adoption of Microsoft 365, but admins can and should help guide the adoption process! It’s important to communicate with management to identify key areas of business collaboration, not only to help new hires, but also to provide a more consistent way of operating across the business. This is exactly where governance comes into play