Group Naming Best Practices

[MiY]

What are some best practices for naming groups?

In my current project, we are implementing a ServiceNow change request process.

We have a group responsible for implementing and approving changes for each product provided by the client (AWS, CrowdStrike, etc.). Separate from these groups, there is also a product operations group.

We are planning to define groups for each product using the following names. Are there any other good naming or best practices?

・Change Working Group: {Product Name} Change
・Change Approval: {Product Name} Change Approver
・Operations Group: {Product Name}

[Nikhil Bajaj9]

Hi @MiY ,

Your naming convetion approach is ok as what we are using in our organization ex:-

XYZ-Adoption-Change Managers

XYZ-IS-Test Managers-Change Assignment

XYZ-CLOUD-LINUX_L2

Where XYZ is the name of the company so you can use any relevant name which will convey proper information.

[Ankur Bawiskar]

@MiY 

My thoughts

-> your current naming convention looks fine but you should give descriptive names

-> something like this

{Scope/Dept/Function} – {Product/Service} – {Role/Responsibility}

check these links for better explanation

6 Tips for Understanding and Managing ServiceNow Groups 

ServiceNow Group Best Practices 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Rafael Batistot]

Hi @MiY 

May you consider adding prefixes for easier sorting and identification:
• CHG-WG-{Product Name} (Change Working Group)
• CHG-APP-{Product Name} (Change Approver)
• OPS-{Product Name} (Operations)