Career & Growth

What this achieves

Career and growth is where an employee’s ambitions meet the roles your company actually has. It turns “where could I go next” into something measurable, by comparing a person against a target role and showing what is missing.

Readiness is a comparison, not an opinion

The idea underneath this whole section is that a role states what it requires and a person records what they have, so the distance between the two can be calculated rather than debated.

Readiness scoring compares any employee against a target job profile, using skills, experience, and training. It can be run for one person or as a matrix across several.

Example: James Whitfield names a senior engineering role as his target. Readiness scoring compares him against that job profile and shows which requirements he already meets and which he does not.

This depends entirely on job profiles naming their requirements and employees recording their skills. Where either side is thin, readiness is thin too.

The pieces

Option	Description
Career paths	Multi-step progressions between roles. Humavera can also discover pathways automatically. See Create a career path.
Aspirations	The target roles an employee declares for themselves.
Development plans	Personalised plans with milestones and tracked progress, aimed at closing a specific gap.
Career conversations	Documented career discussions between a manager and an employee.
Mentorship	Matching mentors with mentees. See Run a mentorship programme.
Promotion readiness and requests	Assessing whether someone is ready, and routing a promotion for approval.
Rotations and stretch assignments	Planned moves and developmental projects that build experience deliberately.

Example: Olivia Bennett and James Whitfield hold a career conversation, agree a target role, and a development plan records the milestones between where he is and what the role requires.

Aspirations change the conversation

An employee declaring a target role is more useful than it first appears. It gives the company a demand signal it would otherwise only learn at a resignation, and it lets development spending be aimed at roles people actually want.

Example: if several engineers at HC Corp name the same target role, that is worth knowing before any of them leave to get it elsewhere.

Growth without promotion

Not every step is a promotion, and treating them as the only currency creates a queue nobody can clear. Rotations and stretch assignments give people new experience without a title change, and they build the evidence a future promotion decision needs.

Example: a stretch assignment gives James Whitfield scope beyond his current role. It builds capability now and makes a later promotion case concrete rather than speculative.

Promotion is a request, not an edit

A promotion routes for approval rather than being applied directly to a record. That keeps a decision with pay and structural consequences on the same governed path as other significant changes, with a record of who approved it. Raise a promotion request covers doing it.

What happens next

Development plans generate learning, so this section feeds courses and training requests. Readiness feeds two things beyond the individual: succession planning for critical positions, and matching people to internal opportunities. Approved promotions write back to the employee record and its compensation history, and pay changes themselves are handled through compensation cycles rather than here.