Setting standards for naming roadmaps, fields, and views supports strong data governance, provides clarity for your users, and makes it easier to navigate your roadmaps.
While each company’s needs will differ, the following suggestions can help guide your approach to setting naming standards.
Roadmap Names
For roadmaps, we suggest using names that specify who uses the roadmap, what is represented, and what data is visualized:
-
<Department_Name> // <Team_Name> // <Product_or_Feature>
For example:
-
Product Marketing // Mobile // iPhone23 release
Adding dates to a roadmap title can provide additional clarity.
View Names
When naming roadmap views, it's important to specify which data is included (or not included) and what is being visualized.
For example:
-
All Data // Product Roadmap // Demo
-
Features // Status // 2024 Progress
Field Names
For fields, it’s important to remember that multiple teams will likely need similar fields, but those fields might not always represent the same thing or be calculated in the same way. For this reason, adding the department, company, or team to the field name can be useful:
-
Fields used by a specific team or department: <Department_Name> // <Field_Name>
-
Fields used by the entire company: Company // <Field_Name>
For example:
-
Kraken Division // Status
-
Company // OKR