Back to Your Feed

What is the best format to create a data dictionary for the company to align everyone on terms so we speak the same language?

I was thinking of creating this as a word doc and sharing.
6 Answers
Sid Kumar
Sid Kumar
HubSpot SVP, Revenue Operations (RevOps)February 7

I'd consider a format that is easily accessible and that is easy to keep up to date. As such, I'd suggest something like a company wiki and/or link directly from your BI tool or whichever platform teams across your company access data and analytics. When creating this data dictionary, I'd spend the time upfront to get alignment from all the key stakeholders across the company that touch data that this will be the single source of truth and align on the process, timing and owners for updates to maintain the relevance of the content.

2181 Views
Cambria Moreno
Cambria Moreno
Highspot Director of Revenue OperationsMay 31

This answer depends on what sort of tools you have available to you. I think a google doc with key terms and definitions is always the quickest solve. Wherever you can incorporate these terms will help reinforce aligning the company. Outside of a google doc and sharing it you should take those terms and make sure they show up in all your presentations, your help text in SFDC and your training and enablement of your field team.

501 Views
Eduardo Moreira
Eduardo Moreira
LinkedIn Director of Sales Strategy and Operations (EMEA & LATAM)July 6

In most documentation efforts, internal and cross-functional alike, RevOps objective is typically to simultaneously achieve widespread adoption, relevance and freshness.

For a data dictionary, various options are possible: from a static PDF, to a live collaborative piece (Word, Wiki, GDoc, spreadsheet - enabling comments, revisions, use cases/queries/code logging); all the way to a data governance platform - typical for large orgs with complex schemas. There are many choices here: long-form vs. spreadsheet, collaborative vs. static, systematic vs. 3P app-supported. To lock an answer, consider your tech stack and org complexity and balance those with end users' experience and desired outcomes.

For widespread adoption, ensure buy-in from users, and give them sufficient airtime and opportunity to provide input - success here means all teams in the revenue engine should have this tool in their bookmarks (and ideally you track their usage). For relevance, make sure it tackles the key go-to-market model dimension (at a high, top-down level) while also dissecting the most used tables and fields/variables in clear language (for consultation). For freshness, assign ownership and drive accountability: either you or an appointee must periodically review, gather feedback, update, and re-publish regularly.

Finally -- make a call fast, you can always adjust later. Added alignment benefits are company-wide and often beat rebuild costs by a wide margin. 

640 Views
Justin Trana
Justin Trana
Databricks Senior Director Sales OperationsAugust 29

The best data dictionaries live in a system of record connected to the data source itself. Tools like Unity Catalog on Databricks or Alation surface the dictionary and governance on the same platform as the end query. This makes is more efficient for users as well as more transparent to keep updated.

That being said, I have found it useful to start with a simple, collaborative tool like Google Sheets to get things started. Use this as your structure for a few months until the necessary information is curated and you align on the data elements that really matter. You can do your research on a more robust system at the same time as you generate version 1.

487 Views
Mollie Bodensteiner
Mollie Bodensteiner
Sound Agriculture Revenue Operations LeaderMarch 14

I tend to like to use a Google Sheet to build this to make sure you have a more table-based structure. Setting not only the attribute name, definition, source of data, systems that store, edit, create, etc.

This tends to be the easiest format in my experience for managing and being able to have tabs to support various tables (customers, product, activity, etc.) attributes.

377 Views
Kayvan Dastgheib
Kayvan Dastgheib
Tegus Global Head of Revenue Strategy & OperationsMarch 28

A data dictionary holds remarkable importance, often overlooked because it's perceived as low-value documentation. However, I've found that neglecting it can lead to critical issues. Definitions, KPIs, and leading indicators may become consolidated in a few minds within the organization, posing significant risk. Alternatively, as organizations scale, maintaining consistency becomes challenging, hindering alignment across functions.

There's no one-size-fits-all format for creating a data dictionary; what matters is starting the process.

  • The best format is one that's accessible, easily digestible by various audiences, and easily updatable.

  • A data dictionary isn't static; it must evolve alongside changing definitions. New metrics are introduced, old ones deprecated, making it a living document essential for meeting the evolving reporting needs across the organization.

The most effective data dictionaries I've encountered were built using simple tools like Google Docs or Sheets. By logging different terminologies, their definitions, calculation methods, usage contexts, and examples, you create a foundational resource. Incorporating version control and regular updates, along with stakeholder collaboration, ensures alignment and consistency in language across the organization.

4 Views
Top Revenue Operations Mentors
Ignacio Castroverde
Ignacio Castroverde
Cisco Senior Director, Global Virtual Sales Strategy and Operations
Akira Mamizuka
Akira Mamizuka
LinkedIn Vice President of Global Sales Operations, SaaS
Ken Liu
Ken Liu
Databricks Director - Sales Strategy & Operations
Josh Chang
Josh Chang
HubSpot Director, GTM Strategy & Revenue Operations
Tyler Will
Tyler Will
Intercom VP, Sales Operations
Mollie Bodensteiner
Mollie Bodensteiner
Sound Agriculture Revenue Operations Leader
Azim Mitha
Azim Mitha
HubSpot Interim Sales Director (Asia)
Shirin Sharif
Shirin Sharif
Adobe Sr. Director, Revenue Operations
Sowmya Srinivasan
Sowmya Srinivasan
HubSpot Vice President of Revenue Operations
Brian Vass
Brian Vass
Paycor VP, Customer Experience Operations