I don't skimp on naming conventions because:
- I want to make your job easier. You are not a mind reader. You don't know why I created 'test list for email #4' or 'custom object report 21 Sept 2023'.
- I don't have time to look for a specific workflow out of 300+ workflows. I want to Ctrl+F or search bar for the thing I'm looking for and find it.
- I want to know at a glance that this list is connected to this workflow and that both of those assets are connected to this campaign and that report.
- I want to reduce the time it takes and mental cycles it requires to understand what this asset does. Naming conventions are powerful when they hint at the purpose of the asset.
- I don't want to create the same list or report twice (especially because there are limits on how many assets you can create in some platforms). If I named it well I can search for it first and confirm or deny if it already exists.
- Most systems don't use a common method to group assets (folders, tags, categories, containers, filters). I'd prefer to rely on good naming to group my assets.