Make progression fair and understandable

Collect examples of meaningful contribution: owning a service, improving a difficult system, coordinating several teams, mentoring a colleague, or reducing an operational risk. Describe the scope, independence, judgment, and collaboration each example required. Then ask which distinctions recur often enough to be useful in a career framework.

Keep technical and management progression visible as different kinds of work. A person should not need direct reports to demonstrate growing influence. Be careful with language such as “company-wide impact” in a small organization where almost every change reaches everyone. Define what the responsibility means in your context instead of relying on the apparent prestige of the phrase.

Performance concerns the expectations of the current role. Growth concerns developing capability. Promotion also depends on the role and scope the organization can support. Mixing all three creates misleading promises: someone may grow substantially without a new title being available, or occupy broader scope without receiving clear expectations.

Explain the process and timing before the review. Name who proposes a promotion, what evidence is considered, who calibrates it, and how a person can question the outcome. Compensation discussions need their own clear process. Do not disguise a budget limit as a personal development deficiency.

Use normal work artifacts: design discussions, incident reviews, customer outcomes, peer collaboration, and decisions that helped other people move forward. Record the person’s contribution and context so a team result is not attributed solely to the most visible presenter. Include the maintenance and prevention work that leaves fewer dramatic artifacts.

A manager should maintain this account with the employee throughout the period. Calibration then tests whether similar evidence produces similar judgments across teams. Ask what opportunities each person had, not only what they delivered. A framework is unfair if one person receives the necessary scope and another is told to demonstrate it without access to suitable work.

Choose one or two capabilities to develop and identify work where the person can practice them. Specify support, boundaries, and how you will review the experience. “Show more leadership” is not a plan; leading a bounded cross-team migration with a sponsor and feedback checkpoints is closer to one.

Revisit the framework when the company changes. Remove distinctions that managers cannot explain consistently and add examples where the same ambiguity keeps returning. A small understandable framework that people use is more valuable than a large competency matrix nobody can interpret without a private explanation.