How do I write my content to be compatible with Progression?

Content in Progression fits into multiple buckets. A progression framework in the Progression app is made up of:

  1. Skills: the measurable attributes required by the team
  2. Positions: The steps on each career pathway, into which we put the skills
  3. Teams: The collections of positions and skills, displayed as 'parallel tracks' which explain possible ways to grow. A team ties everything together!

All skills in Progression follow the same basic structure. If you're thinking of using Progression for your framework, you'll want to make sure you follow that structure to make it easy to upload your skills when the time comes.

First of all though, what are skills?

A skill is broadly any piece of content that you want people in your team or organisation to be able to be measured against. Skills can be anything from the hard requirements of a specific team (for example writing code, or analysing data) to more general interpersonal or 'soft' skills (communication, empathy etc.). You should even think about including any company values and broad cultural expectations as skills if you want your team to be actively thinking about them as they grow within their roles.

Anything that describes what the responsibilities of that role are (to help people understand what people in different teams do) might be better in the description of a position. It's really up to you!

Each skill has a set of common fields:

Name: The name of the skill, competency or behaviour.

Description: The high level definition of the skill, why it's important, with maybe some general links out to further reading.

Image: This is an opportunity for you to brand your skills as your own. Particularly useful if you want to make your skills publicly available in the future.

Skill Levels: This is a collection of different 'levels' of the skill. You can create as many as you want (though many of the skills in our library have five levels). When you come to defining the positions in each of your teams, you'll pick an individual skill level to add to that position. Your skill levels can exactly match the seniority levels in your framework, or you can choose to have fewer levels and assign levels to multiple positions.

What is in a skill level?

Each numbered skill level is made up of a description (the larger text) and a set of examples (the bullet point list in the image above). Both of these fields are optional, but we think it works best when you have both the description and the examples.

Skill Level Description: This should be short, high level and describe the outcome or impact this level should have.

Skill Level Examples: You can add as many of these as you want, and they should aim to bring the description to life through real-world examples that people can relate to. Importantly, this shouldn't be a check-list of what you have to have done, but more suggestive of the general complexity, impact or influence of that level.

OK, do you have a template?

Sure! Here's our template as a google doc. Feel free to clone and use!

Still need help? Contact Us Contact Us