Step 1: Create Your Domains

Create your domain structure as the first step in your documentation initiative.

• First things first, create your domain structure in the Knowledge section
• For each domain, generate a tag
• Don't forget to assign the domain owner

Start Small

Don't boil the ocean. Start with one domain that can be used as an example.

What Is a Data Domain?

A data domain is a broad grouping of data assets based on its function, usage, or subject matter. Each domain is typically associated with specific governance policies, ownership, and quality standards.

Typical examples of domains:

• Customer: including data assets and metrics related to customer lifecycle, customer health, customer attributes, etc.
• Finance: that includes data assets related to financial transactions, budgets, revenue, or expenses
• Employee: including job information, talent retention, hiring, etc.
• etc.

Multiple Teams

You can have multiple teams contributing or using information from a single domain.

Domain Count

Typically, there are no more than 10 data domains as part of an organization. If your organization is not used to the concept of domain, you can start by simply using your department hierarchy instead.

Start With Few Levels

It is a good idea to start just with 1 or 2 levels in the domain hierarchy before expanding further.

How To Structure Your Domains

A basic structure in the domain can follow the domain list and the key areas for each domain. For example:

• Typically an organization will have activities split by lifecycle and you can split it based on its stage: prospect, customer, etc.
  • For prospects we will have qualification stages and sales stages each with its own processes and KPIs
  • For existing customers we will have onboarding processes, but also data assets related to customer deals