![]() If these other Teams don’t currently exist, then it’s worthwhile to plan for the creation of these – depending on how you plan to use the Teams created in the future – first. The same will apply to teams such as the North and South area managers, and the HQ teams at the top of the hierarchy. For example, a store may only require a single Team (with a private channel for the manager and assistant manager) that can be used for other purposes such as Shifts, Walkie Talkie, Apps, Files and – of course – conversations. We do not want to do this for Task Publishing.īecause the hierarchy reflects distinct departments or teams within the organization, it’s likely these map well to other use-cases in Teams. If you’ve rolled out Teams without any planning in the past, you might have suffered from Teams sprawl – Teams created tactically by either IT or employees for specific purposes. The most crucial configuration we need to check before we implement our hierarchy is to ensure we have Teams created that align to the organization. Most store managers explain that they have been printing out the emails and placing them into physical in-boxes, with sticker labels that align to the buckets defined below: Figure 2: Our Planner buckets for task publishingĪrmed with this information, we now understand what needs to be within our Task Publishing hierarchy, and we’ll need to make sure the correct pre-requisites are in-place so that we can align the hierarchy to Teams and deploy it. To understand the task buckets, we spoke to store and area managers to glean some insights into how they currently apportion the work they receive by email from these teams. We’ll use this to help our store employees understand more about the tasks that have been sent to them so they can delegate efficiently. Planner uses the concept of buckets to separate out tasks. Within the hierarchy, we’ve consulted with both Marketing and Health & Safety departments who have highlighted that they both deploy new initiatives (such as new safety signage or marketing campaigns) to flagship stores separately on regular occasions, so we’ll want to be able to filter based upon flagship stores. ![]() Therefore, the hierarchy we create reflects how tasks are distributed, rather than simply who manages who: Figure 1: Our example task publishing hierarchy However, the area managers are the direct line managers of each store manager, and each store manager will be responsible for delegating tasks they receive in their own store. This is because neither the Marketing department, nor the Health & Safety department are necessarily higher up in the organizational structure, but they are operating on the directive of the senior management team when they request their colleagues in stores perform tasks. The Task Publishing hierarchy will not reflect the exact organizational structure and line-manager hierarchy in the organization. The stores are split into North and South areas, and the area managers for each respective set of stores also need to be able to publish tasks, too. Everyone – from the CEO to every shop assistant has a Microsoft 365 F1, F3 or E3 license and is enabled for Teams.Ĭurrently there are two departments that need the ability to send tasks out to the stores, the Marketing department, and the Health & Safety department. They have stores throughout the UK and a single HQ. We’ll use a retailer as our example scenario, Practical Living, who specialize in clothing. Implement the hierarchy using the Microsoft Teams Module for PowerShell.Enable features on Teams clients for ease of use.Ensure we’ve got an appropriate Teams information architecture in place.Plan how we’ll categorize tasks into buckets. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |