What is the difference between career progression and career development?

Career development is the broader category — it encompasses all activities that improve an employee's skills, knowledge, and capabilities, regardless of whether those activities lead to advancement. Career progression refers specifically to upward or lateral advancement in role, level, title, or scope. All career progression requires development, but not all development results in progression. Training a skill that is not tied to a promotion is career development; getting promoted is career progression.

What is a career progression framework?

A career progression framework defines the levels within each job family, the competencies expected at each level, and the criteria an employee must demonstrate to advance. It makes progression explicit and objective — rather than employees guessing what advancement requires, they can look at the framework and see exactly what behaviors, skills, and scope are expected at the next level. See our complete guide to building one.

How do you measure career progression?

Career progression can be tracked along several dimensions: role level changes (L2 → L3), scope expansion (from managing two direct reports to managing six), competency rating improvements across review cycles, and salary band progression. Most organizations track progression through performance review data — competency ratings over time are the most objective indicator of whether an employee is developing toward the next level or plateauing at their current one.

How often should career progression happen?

There is no universal cadence — it depends on role, level, and organizational norms. Typical ranges: entry-level to mid-level progressions in 18–24 months; mid-level to senior in 24–36 months; senior to staff or lead in 3–5 years or more. Progression timelines should be driven by demonstrated capability, not tenure alone. Organizations that tie progression to calendar anniversaries rather than capability criteria tend to accumulate performance debt — the same problems at a higher title.

What Is Career Progression? Definition & Examples

Q: What is career progression?

Career progression is the process through which an employee advances in their career over time — taking on greater responsibility, deeper expertise, or broader scope. It can happen vertically (promotion to a higher level within the same role family), horizontally (moving into an adjacent function), or diagonally (combining a level change with a function change). Effective career progression is structured around a clear framework that defines what each advancement requires.

What is career progression?

Career progression is the movement of an employee's career forward over time — taking on greater responsibility, developing deeper expertise, or expanding the scope of their impact. The word "progression" implies direction, but not necessarily a single direction: career growth can happen vertically (promotion), horizontally (function change), or diagonally (combining both).

In modern HR, career progression is considered a core driver of employee retention, engagement, and performance. Employees who feel their careers are moving forward are significantly more engaged than those who feel they have plateaued — and organizations with visible, structured progression frameworks retain high performers at higher rates than those relying on informal, manager-by-manager conversations.

Career progression vs. career development

These terms are often used interchangeably but mean different things:

	Career Progression	Career Development
Scope	Advancement in role, level, or scope	All activities that improve skills and capabilities
Example	Promoted from L2 to L3 Engineer	Completed a systems design course
Requires advancement?	Yes	No — skills can grow without promotion
Tracked by	Role level, title, salary band history	Competency ratings, training records, IDP milestones

Types of career progression

The traditional image of career progression is a vertical ladder — moving up through increasingly senior titles within a single function. Modern career frameworks recognize three distinct types:

Vertical progression. Advancement within the same role family to a higher level — Engineer → Senior Engineer → Staff Engineer. This is the most visible form of progression, typically accompanied by a title and salary change.
Horizontal progression. Moving into an adjacent function at a similar level — Support → Customer Success, or Data Analyst → Product Manager. This expands breadth without necessarily changing seniority. Organizations that document and support horizontal paths retain more employees who want variety but not necessarily management responsibility.
Diagonal progression. Combining level change with function change — for example, moving from a mid-level individual contributor in Marketing to a senior IC role in Product, leveraging domain knowledge while taking on greater scope.

Organizations that only recognize vertical progression effectively tell employees that career growth means management — which produces managers who are promoted past their preference, and individual contributors who leave because they see no other path.

What makes a career progression framework work

A career progression framework defines the levels within each job family, the competencies expected at each level, and the criteria that distinguish advancement from simply performing well at the current level. Without this structure, progression depends on manager advocacy and organizational visibility rather than merit — which systematically disadvantages employees who are less connected, less vocal, or in less visible roles.

The most effective frameworks have three properties:

Observable criteria. Advancement requirements are stated as behaviors employees can demonstrate and managers can observe, not abstractions like "shows leadership" or "thinks strategically."
Published and accessible. Employees can see the framework without asking their manager. Transparency changes the nature of development conversations — from "what do I need to do to get promoted?" to "here's how I'm tracking against the published criteria."
Connected to reviews and IDPs. The framework anchors calibration sessions (managers use it to evaluate everyone consistently) and individual development plans (employees use it to identify which criteria to work toward).

For a step-by-step guide to building one, see our career progression framework guide. For templates to get started immediately, see our competency matrix template.

How to support career progression as a manager

Managers have more influence over an employee's career progression than any other organizational factor. Three practices make the biggest difference:

Career conversations at least quarterly. Not annual review feedback, but dedicated conversations about where the employee wants to go and what they are doing to get there. Most employees will not initiate these conversations — managers need to.
Stretch assignments calibrated to the next level. Competency growth requires deliberate practice at the edges of current capability. Assigning work that is slightly above an employee's comfortable level — with appropriate support — accelerates development far faster than keeping them in their area of strength.
Specific, behavioral feedback tied to the framework. "Good job on the project" does not build a promotion case. "You led the cross-team coordination without prompting, which is a clear demonstration of the L4 ownership criterion" does. Specificity turns feedback into progression capital.