Looking for best practices (NOT howtos) on Microsoft Planner and Teams
September 15, 2023 5:37 AM Subscribe
My organization is working to standardize on Microsoft Planner and the O365 ecosystem to manage work. My personal approach is a combination of Getting Things Done and kanban boards. I know what the tools can do from a technical perspective, and I need guidance on how to implement the tools to accomplish what I want. Lots of details inside!
Our current setup feels on the right track with Planner's board view replicating a kanban, and buckets labeled for various workstreams (in projects) or types of work (in our operational elements). The next step for us is getting the "work about work" into the system (eg, files relevant to tasks, or discussion comments on a work item) so people can find everything they need in one place instead of having to sort through a combination of emails, Teams posts, Planner comments, etc.
Whatever we end up doing needs to consolidate information and reduce extraneous notifications, and this is where we need guidance. Right now, we have a single planner working as a kanban board for our department. This board is great for seeing workload of all of our team members, but putting task comments or attachments into specific items creates unnecessary notifications for everyone who is in the department (and hence on the plan) but isn't invovled with that task. We also have what I'll mini-projects, where it's mostly the department and up to 4 other people involved in an initiative for 1-2 months. Those projects feel too small to get their own Teams team (and that may be an inaccurate assumption), but we haven't figured out how to get those external people visibility to the tasks that they need without getting involved with everything else. I know there's an option to create additional planner boards, but that runs into problems with being able to see workload across the team and being able to roll up progress across all the plans so we know where everything is.
Finally, as a GTD person I often think about my own tasks in terms of contexts. The planner tasks are great for project tracking, but for what I personally need to do I want to slice things in more ways than just seeing My Tasks in Todo. The perfect solution for me would be if I could sort (team) tasks assigned to me into my own Todo lists (that no one else has to see) so I can quickly prioritize my day without wading through everything assigned to me.
The kinds of answers I'm hoping to get are things like:
* Here's some decision criteria for when to create a new team vs add a new plan within a team
* The best way to store everything in one place is to (put it in the planner task/add to teams and put a link in the planner/update planner and post an update in the teams posts/etc)
* Here's some useful features that allow you to see progress or assignments across multiple plans
* Here's some ways to add private lists or other organization to your assigned tasks
Our current setup feels on the right track with Planner's board view replicating a kanban, and buckets labeled for various workstreams (in projects) or types of work (in our operational elements). The next step for us is getting the "work about work" into the system (eg, files relevant to tasks, or discussion comments on a work item) so people can find everything they need in one place instead of having to sort through a combination of emails, Teams posts, Planner comments, etc.
Whatever we end up doing needs to consolidate information and reduce extraneous notifications, and this is where we need guidance. Right now, we have a single planner working as a kanban board for our department. This board is great for seeing workload of all of our team members, but putting task comments or attachments into specific items creates unnecessary notifications for everyone who is in the department (and hence on the plan) but isn't invovled with that task. We also have what I'll mini-projects, where it's mostly the department and up to 4 other people involved in an initiative for 1-2 months. Those projects feel too small to get their own Teams team (and that may be an inaccurate assumption), but we haven't figured out how to get those external people visibility to the tasks that they need without getting involved with everything else. I know there's an option to create additional planner boards, but that runs into problems with being able to see workload across the team and being able to roll up progress across all the plans so we know where everything is.
Finally, as a GTD person I often think about my own tasks in terms of contexts. The planner tasks are great for project tracking, but for what I personally need to do I want to slice things in more ways than just seeing My Tasks in Todo. The perfect solution for me would be if I could sort (team) tasks assigned to me into my own Todo lists (that no one else has to see) so I can quickly prioritize my day without wading through everything assigned to me.
The kinds of answers I'm hoping to get are things like:
* Here's some decision criteria for when to create a new team vs add a new plan within a team
* The best way to store everything in one place is to (put it in the planner task/add to teams and put a link in the planner/update planner and post an update in the teams posts/etc)
* Here's some useful features that allow you to see progress or assignments across multiple plans
* Here's some ways to add private lists or other organization to your assigned tasks
For certain core Teams issues, I found this thread quite helpful: https://ask.metafilter.com/374259/Microsoft-Teams-Teams-and-Channels-versus-Chat -- both for useful ideas, and also for resetting expectations about what a reasonable bar is.
posted by advil at 6:42 AM on September 15, 2023 [1 favorite]
posted by advil at 6:42 AM on September 15, 2023 [1 favorite]
The best way to store everything in one place is to....
...put it in a folder in the SharePoint site associated with the Team where your planner boards live. Have one folder for Planner documents. Create a sub folder for each Planner board. Create a sub-sub-folder for EITHER each project in that board, or each ticket in that board, whichever is more appropriate.
The structure looks like:
Afolder
Bfolder
...
Planner Documents
..........Board1
....................Ticket1
....................Ticket2
....................etc
..........Board2
....................Project1
....................Project2
....................etc
etc
...
Sfolder
Tfolder
etc
Because you have created this structure in the SharePoint site for the Team associated with the Planner boards, everyone in the team should have access to these docs.
That's the best way. But....let's be realistic, most teams are very unlikely to follow and use this kind of folder structure long term.
If you use Trello or Jira you get exactly the same problem - stuff is everywhere. Most people end up putting a link to a doc into their Trello/Jira/Planner ticket. If you can at least get people to throw their docs in the SharePoint site associated with the Team, even if it's not in the structure described above, at least it's in that site so everyone in the team will (by default) have permission to see the document when they click the link. And that's a hell of a lot better than most business setups (sadly).
Also, create one channel in your team for each Planner board, and add the Planner board to that channel as a tab. Encourage all discussions about items in the board to take place in that channel to try and keep everything together. If you don't want to use the folder structure above, get people to share documents in your Planner board channel, that way they'll be easily searchable and still stored in the SharePoint site where everyone can access them by default.
Planner/SharePoint/Teams best practice is a huge topic with little consensus because the tools can do SO MUCH that there are a million ways to combine functionality and do things, only a few of which will be useful for you. This kind of setup has worked for me in the past but YMMV of course.
posted by underclocked at 11:13 AM on September 15, 2023 [2 favorites]
...put it in a folder in the SharePoint site associated with the Team where your planner boards live. Have one folder for Planner documents. Create a sub folder for each Planner board. Create a sub-sub-folder for EITHER each project in that board, or each ticket in that board, whichever is more appropriate.
The structure looks like:
Afolder
Bfolder
...
Planner Documents
..........Board1
....................Ticket1
....................Ticket2
....................etc
..........Board2
....................Project1
....................Project2
....................etc
etc
...
Sfolder
Tfolder
etc
Because you have created this structure in the SharePoint site for the Team associated with the Planner boards, everyone in the team should have access to these docs.
That's the best way. But....let's be realistic, most teams are very unlikely to follow and use this kind of folder structure long term.
If you use Trello or Jira you get exactly the same problem - stuff is everywhere. Most people end up putting a link to a doc into their Trello/Jira/Planner ticket. If you can at least get people to throw their docs in the SharePoint site associated with the Team, even if it's not in the structure described above, at least it's in that site so everyone in the team will (by default) have permission to see the document when they click the link. And that's a hell of a lot better than most business setups (sadly).
Also, create one channel in your team for each Planner board, and add the Planner board to that channel as a tab. Encourage all discussions about items in the board to take place in that channel to try and keep everything together. If you don't want to use the folder structure above, get people to share documents in your Planner board channel, that way they'll be easily searchable and still stored in the SharePoint site where everyone can access them by default.
Planner/SharePoint/Teams best practice is a huge topic with little consensus because the tools can do SO MUCH that there are a million ways to combine functionality and do things, only a few of which will be useful for you. This kind of setup has worked for me in the past but YMMV of course.
posted by underclocked at 11:13 AM on September 15, 2023 [2 favorites]
This thread is closed to new comments.
posted by rockindata at 5:45 AM on September 15, 2023 [1 favorite]