Skill Taxonomies & Proficiency Levels
As an administrator, you have access to the dynamic 'Skill Taxonomies' feature within the EVA platform to effectively organise and categorise skills - based on hierarchies, interrelations, and competency levels. You can create and manage your organisation-specific skills library, i.e. group various skills into distinct categories and their sub-categories.
Advantages of skill taxonomies include:
Each taxonomy has different security settings
Each taxonomy has separated eva bot target
Each taxonomy has different proficiency levels
Creating and Managing Skills and Skill Taxonomies
You can access Skill Taxonomies under “System Settings” and add new taxonomies.
Navigate to “System Settings” > “Skill Taxonomies”
Click the “+” icon near 'Skill Taxonomies'.
Enter the required skill name, and brief description, and click 'Submit.'* Your new taxonomy will then be listed with the specified name.
*By default, the status of the create skill taxonomy will be “deactivated”. You can enrich the taxonomy by adding proficiency levels and descriptions at this point of your skills set-up.
For editing the existing taxonomies, navigate to “System Settings” > Skill Taxonomies. Here you can select the taxonomy which needs to be edited and click on the “General Information”. “Edit” icon is available in each section for updating any changes.
General Information Section:
Basic Data:
Here, you can review the Skill Taxonomy Name and update the description
Configuration Section:
Customise the taxonomy’s visibility within various pipeline workflows and set limits on the number of skills assignable to different entities like Candidates, Jobs, or Job Requests.
Pipeline Workflow Type: Choose the appropriate workflows (like Promotion or Internal Mobility) to ensure that the Skill taxonomy is available for the jobs in a pipeline workflow
Consider a scenario where jobs in your organisation are categorised under various workflows such as "Promotion," "Internal Mobility," or "Tracking Workflow." For instance, if you select "Tracking Workflow" in the Skill Taxonomy settings, this taxonomy becomes specifically available for jobs classified under the Tracking Workflow.
When a user, who has the necessary permissions, accesses the Full-Screen Entity Management (FSEM) for a job within this workflow, they will have the capability to view and edit the associated skill taxonomy. This feature is instrumental in ensuring that the skill requirements are aligned with the specific needs of each job workflow.
THE MAXIMUM NUMBER OF SKILLS THAT CAN BE ASSIGNED TO A CANDIDATE: Set a limit on the number of selectable skills per candidate. Leaving this unspecified allows agents to assign unlimited skills. For instance, a limit of 5 means a candidate can have only up to 5 skills assigned.
THE MAXIMUM NUMBER OF SKILLS THAT CAN BE ASSIGNED TO A JOB:
Determine the maximum skills that can be linked to a job. Without a set limit, agents have the flexibility to assign any number of skills. A cap of 5, for example, restricts a job to having only 5 skills that are associated with the job.
THE MAXIMUM NUMBER OF SKILLS THAT CAN BE ASSIGNED TO A JOB REQUEST:
Specify the maximum number of skills that can be assigned to each job request. If this field is left unspecified, agents can choose any number of skills. For example, setting this to 5 limits assigning a maximum of 5 skills to a job request.
View and Edit Access to User Groups
To manage view and edit permissions for Skill Taxonomies across different user groups:
Agent Groups: Assign specific agent groups with edit permissions for the Skill Taxonomy inJob, Job Requests and Candidates. This is done by selecting these groups in the “Can Edit” field.
Contact Groups: Similar to agent groups, select the contact groups that will have the authority to manage the taxonomy in Job Requests and Candidates, again using the “Can Edit” field.
Candidate Groups: There are two levels of access here. For groups with 'Can View Only' access, users can only see the Skill Taxonomies in their profile, without editing capabilities. On the other hand, groups with 'Can Edit' access can both view and edit the Skill Taxonomies in their respective candidate profiles.
To ensure that these Skill Taxonomies are properly visible and usable for candidates, jobs, and job requests, you'll need to integrate them within the 'Configuration' settings and then distribute them across the relevant 'Agent Groups' and 'Contact Groups'. This process involves careful navigation through each section to assign the necessary groups, thereby aligning skill visibility and editing permissions with the organisational requirements.
Dictionary in Skill Taxonomy
Create Skill Groups: To begin, access the 'Dictionary' section and click on “Add a Group” to establish a new Skill Group, like 'QA Skills' under a broader category such as 'IT Skills'. Name the group and click 'Save'. Repeat this to create multiple groups under any Skill Taxonomy.
Child Skills: Within a Skill Group (e.g., 'QA Skills'), you can add specific skills (like 'Test Planning and Execution'). Select the group from the dropdown on the 'Dictionary' page, enter the skill name, and save. This process can be repeated to populate the group with various skills.
Editing Skill Groups and Skills:
Reorganising Skills: Skills and Skill Groups can be easily rearranged. You can either drag and drop them into different groups or use the “Edit” icon to move them by selecting a new group from the dropdown.
When skills are dragged and dropped within the dictionary section, the changes will be reflected in the associated entities. If a sub group no longer has any associated entities after skill being moved, subgroup will be automatically removed from those entities.Nested Display: Child skills are displayed under their respective parent Skill Group in a nested format. They can be shifted from one parent group to another as needed.
Modifying Groups and Skills: Renaming any Skill Group or skill is possible through the “Edit” option. Once it is renamed, it will be reflected in every existing linked entities.
Deleting Skill Groups and Skills: User will not be able to delete the skills/skill groups when it is linked to any entity. However, the skills which are not linked to any entity can be deleted and it will not be displayed in the “Edit” mode of entities.
Through these steps, you can effectively manage and customise the Skill Taxonomy to align with your organisation's specific skill requirements and structures.
Activation: Note that new Skill Taxonomies are initially set to 'Deactivated'. After setting up your Taxonomies, groups, and skills, remember to activate them by clicking the 'Activate' button.
Proficiency Levels
EVA's Skill Taxonomy supports various proficiency levels to accurately reflect the skillsets of individuals in your organisation.
Adding Proficiency Levels
To add proficiency levels, select 'Add new proficiency' in the Skill Taxonomy section.
Define the proficiency levels as per your company's assessment standards. Common examples include 'Interested to Learn', 'Beginner', 'Intermediate', etc.
Displaying Proficiency Levels
In the Full-Screen Entity Management (FSEM): When proficiency levels are assigned to skills, these levels will be displayed under each skill in the entity's FSEM. This provides a clear view of the skill proficiency for jobs, job requests, and candidates.
Without Proficiency: If a skill doesn't have associated proficiency levels, only a checkbox will be displayed next to the skill in the FSEM, indicating its presence.
Editing and Deleting
Flexibility: Both Skill Taxonomies and their respective Proficiencies can be edited at any point and it is updated in the assigned entities BUT it can ONLY be deleted as long as they are not currently assigned to an entity (such as a Job, Job Request, or Candidate).
Proficiency can be deleted even when it is assigned to any entity and once deleted, the proficiency level selected earlier for any of the skill would be reset.
Note on Rearranging Proficiency Levels
After defining proficiency levels, you can drag and rearrange them as you wish
If you rearrange the order of proficiency levels, any previously selected levels in entities (Jobs, Job Requests, Candidates) will be reset or removed. This ensures that the proficiency evaluations remain current and accurate as per the latest taxonomy structure.
By incorporating these steps, you can effectively tailor the proficiency aspect of your Skill Taxonomy to meet the specific needs and standards of your organisation