My feedback

  1. 21,271 votes
    Sign in
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1761 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    One of the use cases for us, as a professional services department, is to have a Team that includes all of our consultants, and a specific channel per customer or project. That way I could assign only certain team members to the channel (i.e. only if they are actually assigned to the project). Then they wouldn't be notified about all the other projects that they are not a part of.

    The way we are doing it right now is to make a team per project, which is ok in the short run, but as more and more teams are created, they are getting less visible and more difficult to track. A project team with only a few staff members is at the same hierarchical level as the overall 'Services' team, and even the overall 'Company' team, which makes it difficult to sort through the noise. This also means that executives who want access to project information have to become member of MANY teams - i.e. what happens is, they just don't bother using it.

    We absolutely want to utilize Teams, and are piloting/rolling it out anyway, but this makes the business case for continuing to use for project management difficult to sell. At this point, we need to evaluate other systems for purchase, which I think would be unfortunate, as I love the integration with everything else O365.

Feedback and Knowledge Base