Hello,
I’m looking for some advise on how to best use Teams when organizing projects.
Short background, My company started to transition from doing our work with emails and a local server to MS Teams about 2 months ago. We are an AV company that does installation of digital signage and more. Generally we have a “project” that is sold, then must go through the process of engineering reviews, Project Managers planning the installation, Order Entry doing all the data entry and Techs on site doing the work. We initially set up our structure of Teams by creating a new team per project coming through. That works great for keeping all communication consolidated. BUT now our problem has turned into a huge list of dozens and dozens of Teams. And that is only going to grow as we sell more projects. Many of the Projects are also for repeat customers.
Is there a better way than having one huge list to organize our workload? I thought of a single Team per customer and use channels for individual projects. But that presents 2 questions that I don’t believe have good answers.Â
- Can we do the things we currently down with separate channels in separate Tabs of one channel? – Not necessarily.
- Do we want everyone to have access/visibility to every Team? – No we don’t.
I’d appreciate any ideas or advise on how to best work with Teams to limit the number of Teams we create.
Thank you!
Just a reminder that there is a limit of 200 channels per Team including deleted ones. Thus, your decision may hinge on how many projects you do per customer, etc.
Fred
In our team we tend to use huge paper to-do lists.
That helps teammates to set goals, get inspired, make plans, and keep track of their progress.Â
Remove unnecessary work and prioritize right. This is a great first step.
Ask yourself, how many work orders done this week in the plant don’t really need to be done at all? Often, the work that does not really need to be done is small improvements unrelated to equipment reliability and what I call “honey do” jobs.
How much of the work assigned today (a.k.a. unplanned and unscheduled) could wait until tomorrow or even next week?
One initial step is to reduce the amount of work that has “emotional priorities” and the work that does not need to be done at all. Operations and maintenance should decide on priority rules and time limits for work.
This means that you have to take the priorities from your computerized maintenance management system (CMMS) and make them mean something for operations and maintenance.
It makes sense not to create a new team for every project. Having different channels makes sense thinking of the scale. But at present private channels are not available. But thats in the roadmap & recently launched within MS. Look out for that! Refer below link
https://www.linkedin.com/feed/update/urn:li:activity:6500601797244223488/
