Best Practices: Naming Conventions of Looks

[J_R1]

I wanted to get a feel from the Looker Community on how to approach naming Looks to ensure they are unique and clear.

My team is in the process of pushing Looker throughout our company and I wanted to get a head start on best practices of defining looks to allow users to navigate the platform easily and utilize each Look correctly. Also, the naming convention portion of the Looks, I believe will be helpful from an organization of Looks and ensure there isn’t duplication.

Example: Region: Top Product Sales by Year
Naming Convention: [Subject area]: [top/bottom] [description] by [grouping]

Looker Community - what are your best practices of naming conventions of Looks? What are the benefits you see or do you think there is a better approach?

[Tom_Russell1]

For shared looks & dashboards, we try to include the name of the person who owns/maintains it, in parentheses at the end of the title. This way, viewers with questions about the data or report know who to ask.