Domain creation & attribution

Domains serve as an effective method to delineate clear responsibilities within your team. If there's ever ambiguity about who is responsible for managing a budget, issuing key cards, monitoring the info@ email address, or updating a persona, establishing a domain is a practical solution. Domains can be associated with specific skills or roles. For example, the "Adobe License" domain could be linked to the "Design" skill. Similarly, in product management (which is a role), each product or feature could represent a distinct domain, ensuring clear accountability and streamlined operations.

• in the domains list
• in the skills/roles tools 

Click on "Add new domain":

Then fill out the details on the domain tool:

More details about the domains tool in the domains article, see link below.

You can create a domain directly inside the skills/roles tools:

The idea is, that is often makes more sense to think about domains, when creating a role or a skill. In this example the team created the skill "design" and when defining this skill, they also came up with domains, that the deisgners should be responsible for.

So, instead of leaving the skills tool, adding the domains in the domains list, and then coming back here to connect them, they can also be created inside the skills and roles tool. They cannot be edited here, though!

If you click on the "+" in the domains section inside the skill/role tool you'll see this:

When you click on "Add domain" a dropdown will show you all available, existing domains. That is all domains that have already been created inside the domains list and do not yet have an owner (remember: a domain can only have ONE owner!). 

To create a new domain right here right now, just start typing and the "create" option appears. Finish writing, then click "Create "...":

This domain will now also show inside the domains list and will automatically be attributed to the skill "design" - shown by the grey pill:

In V1 of teamdecoder you needed to name a person as owner of a domain. Since v2 you have the possibility to chose a role or a skill to be owner of a domain. So the domain always stays with the skill or role, not with the person. Like the editorial plan (domain) is always with a copywriter (skill).

Let's go through an example - a circle called "Product management":

• We have the role of the product manager (generic) - everyone who manages a product, whichever it is, owns this role.
• and we have the head of product management as single owner role, if you have one (otherwise maybe the team can be self managing)
• you have 3 products created as domains: A, B and C
• plus the domain "new product development pipeline" as an example of what domains this circle could also be responsible for
• and they all meet in the circle "product management" - put it in focus and add all elements like this:

Inside the role "product manager" add all products in the "domains" section. 

You can define owners for the domains, once you have added people to the role itself!

When you go back into circle focus mode you will see this:

• products A, B and C have the grey pill "product manager (role)", which indicated that these domains have been attributed the mentioned role.
  
  
• and you can see the "lead" pill in the role "head of prod mgmt" as this role has been defined "lead" in the circle tool
  
  
• you also see the blue "1", which means that this is a single-owner role. Only single-owner roles can be made circle or project lead!