Writing Great Skills
For HR Business Partners and Function Leads.
Skills are the criteria people use to track progress. They show what's expected now, and what it takes to grow. HRBPs and Function Leads usually decide the skills together, then Function Leads write the content.
What makes a good skill
Description: one or two sentences that explain the skill at a glance.
Levels: usually one to five, getting more demanding as they go up. Give every level a short description of one or two sentences, written in the third person.
Examples: observable behaviours for each level, which make the skill actionable. Start with at least three per level, written in the second person. Keep them consistent across levels: if level 1 has a "Drives buying decisions" example, level 5 should too.
Decide which skills to include
Number of skills: aim for 8 to 12 per position.
Core skills: your Project Lead may have added core skills to the template. Use them as they are, or create a variant for your team if the skill allows it.
Category mix: spread skills across your categories. IC positions usually have fewer leadership skills than management positions.
Start small: build the most common position in the team first. It'll make the others easier.
Research and write
List the job titles in the team and gather their job descriptions.
Pick out the skills each position needs and rank them by importance.
Group related skills into one. For example, "Closes the sale", "Can negotiate a price" and "Overcomes objections" could become Negotiating and Closing.
List at least three example behaviours for each skill.
Create the skill: start from a library skill, write your own, or let the AI Assistant draft the description and levels. See Adding skills. If your skills are already in a spreadsheet, you can import them by CSV.
Review and edit the result so it sounds like your organisation.
Share skills across positions where you can. Fewer skills are quicker to build, roll out and maintain, and easier to compare.
Tips for a usable first version
Don't aim for perfect. Get to something usable fast, start using it, and improve it over time.
No fluff. Essential skills only, up to 12 per position.
Think OKRs. The description is the objective, the examples are the key results. Keep both realistic.
Keep the first draft short. Get the basics down, then sit with the team's managers and ask what's missing or irrelevant. People back content they helped create.
Consult, don't vote. Gather everyone's views, but don't design for the loudest voice in the room. Ship what you have and improve it later.
