Last Update: May 07, 2024 | Published: Apr 22, 2024
It can seem at times we all have an overwhelming amount of things to do and information to deal with. Solutions like Microsoft 365 are supposed to help us collaborate and be more productive. But unless you understand the tools and how to best create a process that works for you and your team, it can still be difficult to stay on top of your workload. In this article, I look at 5 ways you can get things done in Microsoft 365.
Frequent context switching between applications is known to drive down productivity. And it can be frustrating to have to search for information across many different systems. Microsoft has an article What context switching is and how it’s messing up your workday with more information about the negative impact of context switching.
Keeping as much of your data inside Microsoft 365 has several advantages:
Managing access and permissions in Microsoft 365 can seem daunting, especially when it also includes external guest access. Understanding how you build a process around Planner can help you work things out. Planner is a lightweight project management app for teams that don’t have a dedicated Project Manager. Planner is based around the idea of a Kanban board, which is a series of cards that represents each task. The cards are moved along a process that you define from left to right towards completion. The great thing about Kanban boards is that they provide you with an overview of your team’s work in an easy to digest visual format. Task lists are great when you have a simple project with only a handful of tasks. But they can become overwhelming quickly.
If the idea of using a Kanban board sounds scary, don’t be put off. Once you get the idea, they’ll be no going back to task lists. And Planner lets you view your Kanban board in the form of a task list when you need to. Task lists can be useful when you need to sort and filter large amounts of tasks into a single view. With Planner, you get the best of both worlds.
The Planner app in teams aggregates all the tasks you create, or that are assigned to you, across Microsoft 365. Even emails you flag for follow up, providing you are using Microsoft 365 for your email, appear as a task. You can turn Teams messages into tasks, flagged OneNote pages also appear in your Planner tasks list. You get the idea.
Before you run off to start creating Kanban boards, it’s best to consider how you will organize your projects. I recommend creating a single Planner board for each team. Not for each project. There are a few reasons:
But doesn’t that get messy quickly? It could do. But not if you organize the board properly. I recommend creating a label for each project and assigning each card you create with the correct label. Then you can easily filter the board if you need to see a visual status of a particular project, or several related projects, in a single view. You can also color code your labels to make the board easier to digest when no filters are applied.
While creating and assigning labels is important, so is making sure the title of each task is descriptive enough that you can easily find it by searching. Bear in mind that labels are not included in search, so you might need to repeat the name of the project in the task title.
What’s the best way to create a Planner board and give access to users?
Here are several more tips to consider when using Planner:
Stop creating multiple versions of a file and physically attaching it to emails. If you are working on a document internally or with an external team, Outlook gives you the option to send a link to the file. From there on, OneDrive for Business will handle file versioning. Once you have many versions of a file, which often end up located in several different locations, not only are you creating more data bloat with unnecessary files but also confusion about where the file is located and which is the latest version. Plus, collaboration features in Office apps work best if you and your team are all working on the same copy of a file.
With ‘one source of truth’ for your files, search can surface what you are looking for more efficiently and Copilot can better digest the information to give more relevant results. I can cannot count the number of times that multiple versions of the same file has caused changes to be lost, mistakes to be made, and revisions to take longer.
Let’s start with Loop because that doesn’t require you to have a separate subscription.
Last year, Microsoft released a new feature for Teams meetings that allows you to attach an agenda to each meeting as a portable Loop component. Creating an agenda, and then being able to refer to it before and after a meeting, can help you stay focused on what you need to achieve and what was decided along the way. Loop agendas cannot be added to existing meetings.
If you are using Google Workspace or other email and calendaring solution, you cannot add Loop meeting agendas to Teams meetings at this time.
Like with Loop, Copilot can be enabled for new meetings. And it is only available for meetings created in the Teams app. Copilot transcribes meetings and then provides a summary of what was discussed. You can also use Copilot to quickly find information from past meetings.
To enable Copilot using Google Workspace or other email and calendaring solution that supports the creation of Teams meetings, you’ll need to click Meeting Options below Join Microsoft Teams Meeting.
This will open a separate tab where you get the option to enable settings like recordings, transcriptions, and Copilot.
Finally, and this is optional, you can use Power Automate to create workflows across Microsoft 365. For example, if somebody adds a document to a Teams channel or updates a table in Loop, you can use a simple process to create a workflow that sends an update to the necessary people. One of the biggest challenges organizations have is communicating the different parts of a process to team members.
The more you can automate processes, the more likely you will be successful in getting tasks complete efficiently. Nobody wants to have to communicate every small change that is made to a document to team members. But those changes could be important and have a knock on effect to something else.