decídalo
Documentation
Ask AI
Search Results for

    Show/Hide Table of Contents

    Skill goals

    A skill goal sets how many people in your company should have a skill, optionally from a minimum level and by a date, for example the number of Kubernetes engineers a new platform needs next year. A goal applies either to your whole company or to a subgroup of it, such as the engineers of one business unit. decídalo compares the goal with the people who have the skill today and forecasts, from how that number has grown over the last twelve months, whether the goal will be reached in time. That shows you early which skills you will be short of.

    Each skill in your company’s catalog can have one company-wide goal, which applies to everyone, and any number of subgroup goals, each for a group of people described by their profile fields. The skill catalog itself is described in Skill Overview.

    Opening the skill goals page

    Open Skills in the Skill and CV menu section and click Goals above the skills table. The Skill goals page lists the goals, company-wide and subgroup goals alike. Click Back to skills to return to the catalog.

    Skill goals is a beta feature for now: the Goals button, the Skill goal column and the page are only available to users whose permission profile has the ‘Feature preview’ permission (see Beta features).

    The page, including the development drawer of each goal, and the Skill goal column require the ‘Manage skills, certificates and roles’ permission, because their figures count every holder, including people whose profile you may not open, and a subgroup goal determines its members from all profiles. Without it, the Goals button and the column are not shown. See the Permission concept.

    The skills table also has a Skill goal column. For a skill with a company-wide goal it shows how many people count towards it, for example 12 of 40, with a progress bar; click it to open the skill goals page. A skill without a company-wide goal shows Set a goal, which opens the pop-up for adding a goal with that skill already selected, without leaving the skills table. A skill with subgroup goals also shows how many it has, for example 2 subgroup goals; click it to open the skill goals page.

    How people are counted

    A person counts towards a goal when the skill is on their profile:

    • If the goal has a minimum level, only people at that level or higher count. Without a minimum level, every level counts, including a skill without a level.
    • Skills the AI has only suggested and the person has not confirmed yet do not count. A skill whose level is the same as the one the AI skill assessment proposed for it does not count either, whoever set that level, and not even for a goal without a minimum level, so rolling out the assessment does not look like growth.
    • A person stops counting once their exit date has passed. In the history, a person counts in a month only if they are still employed at the end of it.
    • When skills have been merged, the people who had the merged skill count towards the skill it was merged into, also in the months before the merge. A person who had both counts once.

    A subgroup goal counts only the people who belong to its subgroup, by the same rules.

    Subgroup goals

    A subgroup goal applies to the people whose profiles meet a set of conditions, for example everyone in the Consulting business unit who works in Germany or Austria. Use it when a skill is needed in only part of your company, such as the cloud engineers of one delivery centre.

    Subgroups are shared with certificate goals: a subgroup defined for a certificate goal can be picked for a skill goal and the other way round, and each subgroup has a name that no other subgroup in your company has. A subgroup is neither a team nor a resource group, and it is deleted together with the last goal that uses it, whether that is a skill or a certificate goal.

    A person belongs to the subgroup if they meet all of its conditions, and meets a condition if their profile has any of its values. Which fields the conditions can use, how decídalo calculates membership and what happens when a field becomes unavailable is described for certificate goals, including conditions that need review.

    Note: decídalo does not record who belonged to a subgroup in the past. The recorded months of the development drawer therefore count today’s members in every month: a person who joined the subgroup recently counts in earlier months as well, and a person who has left it no longer counts in any month.

    The goals table

    The table shows one row per goal, so a skill with subgroup goals appears in several rows. The figures of a subgroup goal cover the subgroup’s members only. Narrow the table down with the column filters, for example to find a skill by name with the filter of the Skill column, and choose and arrange the columns with the column settings; decídalo remembers your choice.

    Column Description
    Skill The skill the goal is set for. Click the name to open the development drawer.
    Applies to Everyone for a company-wide goal, otherwise the name of the subgroup. Hover over a subgroup’s name to see its conditions. A warning icon and Conditions need review mark a goal whose conditions need review.
    Needed by The date by which the goal should be reached. Empty for a goal without a date.
    Progress How many people count towards the goal today, out of the goal, with a progress bar. With a minimum level, the level is shown next to it. Hover over it to see how many people are still missing.
    Goal forecast The goal status and, for a goal that is On track, At risk or Off track, about how many people the current pace reaches by the needed-by date, for example ≈ 25 of 40. For a goal with the status No date, it shows the month in which the current pace reaches the goal, or Not reached at the current pace. Hover over it for the full forecast.
    Why Why the goal matters, if it has been filled in.

    The forecast

    decídalo forecasts every goal from the people who counted towards it month by month over the last twelve months:

    • Pace: the typical number of people gained per month in that time. A single month with an unusual jump, for example when many profiles were imported at once, barely changes it.
    • Range: the pace of the slowest and of the fastest full quarter of those twelve months. With less than two quarters of history there is no range.

    From these, each goal gets a status:

    Status Meaning
    Goal reached Enough people count towards the goal today.
    On track Even at the pace of the slowest quarter, the goal is reached by the needed-by date.
    At risk The goal is reached in time only at a faster pace than that of the slowest quarter.
    Off track Not even at the pace of the fastest quarter is the goal reached in time.
    Missed The needed-by date has passed without the goal being reached.
    No date The goal has no needed-by date. The forecast only says when the current pace reaches the goal.
    Too little history Less than three months have passed since the end of the first recorded month in which anyone counted towards the goal, which is too short for a pace. A goal nobody counts towards yet has this status too, as long as its needed-by date has not passed; after that, it is Missed.

    Without a range, the status depends on the current pace alone: On track if it reaches the goal by the needed-by date, otherwise At risk.

    Hover over the status in the table to see the pace, about how many people it reaches by the needed-by date, how many more people per month the goal needs, and around which month the current pace reaches it. The range is shown in the development drawer’s chart.

    Adding, editing and removing goals

    With ‘Manage skills, certificates and roles’, click Add next to the table title, or Add goal while the table is still empty. A pop-up opens:

    Field Description
    Skill Search for the skill in your company’s catalog. For a company-wide goal, skills that already have one are marked Already has a company-wide goal and cannot be selected. A subgroup goal can be added to any skill.
    Goal The number of people who should have the skill: a whole number of at least 1.
    Needed by Optional. The date by which the goal should be reached. Without it, the goal gets no on-track verdict, only the month the current pace reaches it.
    Minimum level Optional. The lowest level on your company’s skill-level scale that counts towards the goal. Any level counts everyone who has the skill.
    Why this matters Optional. Up to 1,000 characters on why the goal exists, for example the project or strategy that needs the skill. It is shown in the table and in the development drawer.
    Applies to Everyone for a company-wide goal, Subgroup for a subgroup goal. If the skill already has a company-wide goal, Everyone is not available, Subgroup is selected and a note says why.
    Subgroup Subgroup goals only. Pick an existing subgroup, also one that certificate goals use, or type a name and click Add “…” to define a new one with up to 100 characters; typing the name of an existing subgroup, whatever its capitalization, picks that subgroup. Subgroups the skill already has a goal for are marked Already has a goal for this subgroup and cannot be selected.
    Conditions Subgroup goals only. Who belongs to the subgroup. Click Add and pick a field, then choose its values; a goal needs at least one condition and can have up to 20, and every condition needs at least one value and can have up to 50. Below the conditions, the pop-up shows how many people currently match them, whether they have the skill or not, including people who have left the company. An existing subgroup is used as it is: its conditions are shown, but cannot be changed here.

    You can also start from the skills table: Set a goal in the Skill goal column opens the same pop-up with that skill already selected.

    To change a goal, click the three vertical dots at the end of its row and select Edit. A side drawer opens with the same fields and the goal’s values; only the skill cannot be changed there. Under Applies to, you can turn a company-wide goal into a subgroup goal, and a subgroup goal into the company-wide goal of its skill. If the skill already has a company-wide goal, Everyone is not available and a note says why. The goal keeps its other values.

    For a subgroup goal, the Subgroup field shows the goal’s subgroup, and you can change its conditions:

    • If no other goal uses the subgroup, the changes apply to this goal alone, and typing a new name and clicking Add “…” renames the subgroup.
    • If other goals use the subgroup too, whether for skills or for certificates, a note names them. Changes to the conditions apply to those goals as well, so when you save, decídalo names them again and asks you to confirm. To change the conditions for this goal only, type a new name and click Add “…”: the goal gets a subgroup of its own under that name, starting with the same conditions, and the other goals keep theirs.
    • To count the members of another existing subgroup instead, pick it or type its name. It is used as it is.

    If no other goal uses the goal’s subgroup, picking another subgroup or Everyone deletes it, so decídalo asks you to confirm that when you save.

    To remove a goal, select Remove in the same menu and confirm; for a subgroup goal, the confirmation names the skill and the subgroup, and says that the subgroup is deleted as well if no other goal uses it. Removing a goal changes nothing on the skill or on the profiles. A subgroup that no goal uses any more is deleted.

    When a skill is deleted, all its goals are deleted with it, and so are the subgroups no other goal uses. This also happens when someone removes from a profile a skill they created themselves, as long as no other profile has it and it is not a core skill, because decídalo then removes the skill from the catalog. When skills are merged, the company-wide goal and the subgroup goals of the merged skills move to the target skill. A skill can have only one company-wide goal and one goal per subgroup: if the target already has such a goal, it keeps its own, and if several merged skills have one, only one of them moves. The goals that do not move are deleted.

    The development drawer

    Click a skill name in the goals table to open its development drawer. It shows how the number of people with the skill has developed and where the current pace leads.

    At the top, the drawer shows the people who count towards the goal today (People now, or At level … or higher now for a goal with a minimum level), the Goal and the Needed by date, followed by the forecast and by Why this matters when it has been filled in.

    For a subgroup goal, the subgroup’s name and conditions appear above these figures, with a warning if some of the conditions need review. The figures and the chart then cover the subgroup’s members only, and the recorded months count today’s members (see Subgroup goals).

    The chart shows the goal month by month:

    Element Description
    Level … and No level The people with the skill per level, stacked with the highest level at the bottom. Levels below the goal’s minimum level are grey and stacked on top, so the coloured part ends at the people who count towards the goal. No level is always grey and at the very top, even for a goal without a minimum level, where these people do count and only its outline is coloured.
    Counting towards the goal For a goal with a minimum level, the people at that level or higher.
    At the current pace A dashed line from today that continues the current pace.
    Slowest to fastest quarter The shaded range around it, from the pace of the slowest to the pace of the fastest quarter.
    Pace needed A dotted line from today to the goal at the needed-by date.
    Goal A horizontal line at the goal.
    Today, Needed by and Reached around Markers at the current month, at the needed-by date, and at the month the current pace reaches the goal, where they fall within the period on display.

    Hover over a month to see its figures. The recorded part covers up to the last 24 months. decídalo has kept the history needed for it only since a certain point, so the recorded part can be shorter, and the chart then starts where the data does.

    By default the chart runs up to the needed-by date or the month the current pace reaches the goal, at least six months and at most five years ahead. For a goal that has already been reached, it ends today and shows no pace lines. The button with the calendar icon above the chart shows the period on display; click it to choose another one, from the start of the recorded history up to five years ahead, or up to today for a reached goal. A period reaching further than the default extends the pace lines accordingly. Choosing a period changes only the chart, never the saved goal or the figures in the table and the drawer summary.

    In This Article
    Version history Back to top Copyright © data assessment solutions · decidalo.com