Build your competency model
A competency model is the set of skills you expect people to show across your organization, such as communication, accountability or leading others.
In Career Bird, you choose the skills that belong in your competency model. Career Bird suggests the proficiency expected at each level of your leveling framework, and you adjust it. When you publish the model, its skills appear on every matching role.
Who can do this: Org admins.
Before you begin
- Set up your leveling framework first, under Role management > Leveling framework. Proficiency is set level by level.
- Decide which skills apply to everyone and which apply only to certain job families. For example, client-facing teams may need negotiation, while every employee needs accountability.
How a competency model works in Career Bird
- Skills, not a separate framework. Your competency model is a collection of skills from your skill library, usually core and leadership skills. These higher-level skills are often what organizations call competencies.
- Organization-wide or by job family. Build one organization model, and add job family models where a family needs something different. If both include the same skill, the job family version applies.
- Proficiency by level. For each skill, Career Bird suggests the proficiency expected at each level, from Foundational to Expert. You can change any of them.
- Demonstrated behaviors. Each skill includes demonstrated behaviors: what the skill looks like when someone has it. Career Bird suggests them and you can edit them.
- Published models update roles right away. There's no need to refresh or republish roles. Drafts don't affect roles until you publish.
Build your organization model
- Go to Skills management > Competency model.
- Click Edit.
- Add skills from your skill library. If a skill doesn't exist yet, create it first.
- Review the proficiency Career Bird suggests for each level and change any that don't fit.
- Click Save draft to keep working, or Publish when you're ready.
Add a job family model
- On Skills management > Competency model, switch from Organization to Job family.
- Click New model, pick a job family and click Create competency model.
- Click Edit, add skills and set proficiency, then Save draft or Publish.
What happens to your roles
- Every role with a level assigned picks up the model's skills and the proficiency for its level as soon as you publish.
- If a role already has one of the model's skills, the skill appears once and uses the model's proficiency.
- Skills that come from the model can't be removed from an individual role. Change them in the competency model.
- If you remove a skill from the model, it drops off roles that only had it from the model. Skills that were already on a role stay.
- Competency model skills are added on top of each role's own skills, so a role can have more skills of a type than the maximum you've set for role generation.
Who sees the competency model
- Org admins manage it.
- Role reviewers and editors see it in each role's Competency model tab.
- Employees see the competency skills for their own role under My career > Role description, labeled Everyone (organization-wide), Your track (job family) or This role. When Career Explorer is turned on, its Competency model tab shows how expectations grow at their level and the next two levels.
If something goes wrong
| Issue | What to check |
|---|---|
| Changes aren't showing on roles | Make sure you clicked Publish. Saved drafts don't affect roles. |
| A skill isn't showing in some roles | Check whether it's in a job family model, and that the role belongs to that family and has a level assigned. |
| You can't remove a skill from a role | It comes from the competency model. Remove it there. |
| You want to change a skill or its type | Edit the skill in your skill library. Only org admins can edit skills or change a skill's type. |
Related articles
- Customize the leveling framework
- Manage your skill library: add, import and edit skills
- AI Competencies and Manager Competencies
- Skills, competencies and demonstrated behaviors: what's the difference?