We, a small (50) company have enabled Mattermost in GitLab Omnibus, and then ran a short trial among software engineers, and liked it and want to stick with it. I am trying to figure out the best way to slice the information space; narrowly, the question that I am unable to answer is: when should I prefer creating a team to creating a channel?
I could not find any guidelines on that; the Teams FAQ is concerned with the how, not the why of team creation; the Documentation on organizing Mattermost promises to talk about teams and channels, but only goes on on the latter; it does speak of subteams getting a channel each, however.
At the moment, we will be using Mattermost only for internal communication. That we here stands for a few company teams: software engineers (SWE), product managers (PM) and IT. Currently that excludes e. g. sales and marketing; those we will be looking at later. To me, an argument for a single team is that all these people communicate quite often on common channels. For example, SWE and PM (a PM connects a customer and SWE) together discuss customer applications; they certainly should be in one team. Similarly, SWE and IT interact quite often. The IT also makes company-wide announces. But that might be a naive understanding of a novice, that would make our life difficult later.
So I am looking primarily for any guidance on this question, but am also interested in general best practices resources that are helpful in planning a Mattermost installation.