Skip to main content

About the skills database

YOUR CHARTER

Full charter: required

Flexible charter: as indicated in the charter

Fast charter: not used

The skills database lists all of the competencies, skills, and learning objectives that theoretically describe everything that anyone will ever want to learn about Unity.

Of course, our database is incomplete, and perhaps it always will be. However, as we add to it, we create a structure for Unity learning that can be used for the Learn platform, Unity Certifications, Educator Hub materials, professional training, internal onboarding, job assistance programs, and possibly more. The database gives us a platform for collaborating with many subject matter experts, and it ensures consistency throughout the entire Unity Learning Ecosystem.

Competencies​

A Competency equals a learner level plus a subject domain. In other words, it describes someone's level of competency in a particular area.

For example:

  • Absolute Beginner Version control
  • Beginner Particles and visual effects
  • Intermediate User interface design

The subject domain is a term from the Unity Taxonomy, which is under development. The list of subject domains is in flux while the Taxonomy is being completed and implemented.

Competencies align with the requirements you might see listed in a job description, such as "Familiarity with particle systems and visual effects" and "Solid experience designing user interfaces."

Each competency has a number of skills.

Skills​

Skills are abilities that require critical thinking, iteration, and troubleshooting to achieve a desired outcome, which can be evaluated against specific criteria, such as a design document.

For example:

  • Implement a particular visual style in a project by configuring a post-processing profile (Beginner Post-processing).
  • Create a simple shader and material using Shader Graph (Beginner Shader scripting).
  • Collaborate with the disability and gaming community (Intermediate Accessibility).

Each skill has one main verb. The verbs we use for skills typically require judgment, higher-order problem solving, and/or creativity.

In the world of learning design, skills are also called terminal objectives. Skills align with the responsibilities you might see listed in a job description, such as "Create shaders and materials using Shader Graph" and "Configure post-processing profiles to customer requirements".

Each skill belongs to only one competency and has a number of learning objectives.

Learning objectives​

Learning objectives (LOs) describe discrete tasks that the learner must do, or facts the learner must know, in order to practice a skill.

For example:

  • Add a new global post-processing volume to a scene.
  • Navigate in the Shader Graph editor window.
  • Identify job roles to consider in preparation for refining your personal goals.

Like a skill, each LO has one main verb. The verbs we use for LOs describe things that a learner would either know or not know how to do. We use observable verbs, even for knowledge LOs, such as "Explain" or "Identify" (and never "Understand," which is not observable).

In the world of learning design, learning objectives are also called enabling objectives.

Each LO belongs to only one skill. Once a learner has achieved all the learning objectives for a skill, they should be able to practice the skill.