Your taxonomy is essentially a specialized dictionary for your organization. Defining and adhering to its terms is a key ingredient for successful types of metadata. But what if two internal teams (say, your Communications and your Marketing teams) describe the same object or idea using different terminology? Or what if the same language is used two different ways? 

Small linguistic inconsistencies can create long-term confusion within your DAM solution, so it’s best to sort these situations out as soon as they emerge.

Once you’re all on the same page, you can move more confidently toward a solution. If these terms are slightly different ways of expressing the same thing, a collective compromise will save headaches for all (and strengthen your DAM system's status as a single source of truth). If there are real differences, sharpening your terms will reduce clutter when a user is searching for a piece of digitized content.

Thankfully, most DAMs are built to accommodate these scenarios, with role- or project-based filters that will configure the system to display only relevant information to a given end-user. Establish which terms need to overlap and which need to be unique, and then use this information to create helpful role-permissions in the DAM, so that everyone can find what they need, using language that’s intuitive to them.