Group Naming Best Practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2025 01:48 AM
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}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2025 02:05 AM
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)
