Forum Discussion
Solved
Microsoft Teams Naming Conventions
I have a slight dilemma and I can't seem to find useful resources online so I was hoping to pick your collective brains? The problem I have is around naming conventions. The directives we establishe...
We have two suggestions.
PREFIX (the IT department first choice, due to 'search-ability'):
ORG-management-namePRJ-management-name
There is also a suggestion to have shorter prefixes, ORG=O, PRJ=P
SUFFIX (the users first choice):Name (ORG-management)
Name (PRJ-management)
If you have suffix it's more simple for the user to see what team they are in and you can @mention the team with better names, for ex @prj-management vs. @thenameyouhavechosen
This is a good question and I think the beauty of teams is that it allows you communicate with these remote sites/offices more effectively. Personally I would probably go with Function based teams ( sales, tech support.. etc ) and invite users who correspond to those teams. But you can equally configure Region based teams ( UK, France, Germany etc ) with more function based channels within that team...
WelshViking Thanks for your response. To illustrate further the problem in a previous company one user created a team called MyTeam. This was before I arrived!
I have devised codes before;
1st Three Char = Geo Location
Then 3 Char = Function
Then 4 = Scope
etc....
but here I have let's say Global Marketing Who want to work across functions ie R&D and Sales, to get input for campaigns and have guests.
JohnKelly I think your convention looks good. You just need to add a special code for teams that work across locations (e.g. Global), and for teams that work across functions (e.g. Corp).
Another trick we have used: custom logos. You could for example have a color for the location and a symbol or acronym for the function.
Also remember to use pinning to help people focus on their core activities.
- I can see how things get convoluted. I think using channels helps in this manner... using @mentions or links to the channel can allow staff to alert others to info they may think is interesting. As far as Teams naming is concerned in this instance... I would go with regional teams with function channels and leave it at that.. but that's just me. Then question would then be, can you restrict channels?
