Career frameworks people can actually use

A career framework has one true reader. That reader is an employee who wants to know what to do next. Most organizations build frameworks for a different audience entirely. They write them for compensation committees. It shows in every paragraph. The language is dense. The criteria are vague. Adjectives replace concrete expectations. A ladder that requires interpretation by an HR leader is not a ladder. It is a puzzle.

Next quarter brings new legal pressures to career leveling. Legislative shifts in Europe and North America force organizations to defend their leveling decisions publicly. Vague frameworks are no longer just an internal annoyance. They are a legal liability. You must change how you document career progression.

In the European Union, the Pay Transparency Directive 2023/970 fundamentally rewrites how companies manage progression. Member states must transpose this directive into national law by June 7, 2026. Any pay gap exceeding 5 percent requires objective justification. A subjective career framework will fail this legal test. Employers will need standardized criteria to prove why one employee is level four and another is level five. The burden of proof rests entirely on the employer.

North America faces a similar regulatory shift through state and municipal legislation. These laws demand public pay bands. California passed Senate Bill 1162 requiring pay ranges on job postings as of January 1, 2023. New York City implemented Local Law 32 on November 1, 2022. Washington State updated its Equal Pay and Opportunities Act on January 1, 2023. British Columbia enacted the Pay Transparency Act on November 1, 2023.

Public pay bands demand rigorous leveling. If an external candidate can see the compensation band for a senior product manager, internal employees will compare their own pay against it. You must explicitly define what separates a mid level role from a senior role. You cannot rely on manager discretion to explain the difference.

Write criteria in the second person

Write your leveling documents in the second person. Address the employee directly. You own delivery for a specific product area. You resolve ambiguous technical problems independently. You influence architectural decisions outside your immediate group. These statements read as clear guidance. Employees know exactly what the organization expects of them.

Contrast this with traditional third person descriptions. The employee demonstrates cross functional influence. The candidate exhibits strong leadership capabilities. These read as rubrics for a promotion committee. They require subjective interpretation from managers. Subjectivity invites bias. Bias creates legal exposure under the new transparency legislation.

Rewrite your criteria as direct actions. Tell the employee exactly what they must do to advance. Remove all adjectives from your documentation. Words like strong, excellent, and significant possess no objective meaning. Replace them with scope boundaries. Define whether the person manages a single feature, a whole product line, or an entire portfolio.

Restrict the framework to three dimensions

Limit your framework to three core dimensions. Scope of work, autonomy, and impact on others provide enough resolution to separate levels. Most corporate frameworks include eight to twelve separate dimensions. They measure communication, technical depth, leadership, culture, and innovation individually. This produces a massive document nobody reads. It creates a promotion case nobody can actually assemble.

Scope of work defines the size of the problems the employee solves. Autonomy defines how much oversight they need to solve them. Impact on others defines how their work improves the output of their peers. These three axes scale predictably from entry level to executive.

An entry level employee handles a narrow scope. They require heavy oversight. They impact nobody but themselves. A principal individual contributor commands an organizational scope. They operate entirely independently. They lift the performance of entire departments.

The acid test for your framework is simple. An employee should read their current level and the level above it. They must be able to name three specific things they should start doing on Monday. A descriptive framework fails this test. An actionable framework passes it easily.

Ground expectations in real examples

Language will only get you so far. Anonymized examples of actual work at each level do more than any rubric. Create an internal library of calibrated promotion cases. Show the organization what a real level five project looks like.

People calibrate from concrete examples far better than from abstract descriptions. Your framework might state that a senior engineer handles complex system architecture. Nobody knows what that actually means in practice. If you link to the design document for a specific database migration, everyone understands the expectation immediately.

Ask your best managers to submit one piece of work that perfectly captures the expectations for a specific level. A product manager might submit a launch plan. A financial analyst might submit a quarterly forecast model. Compile these artifacts into a single repository.

When an employee asks what it takes to reach level four, send them the repository. They will instantly see the difference in quality, depth, and scope. This practice also exposes bad leveling across teams. If the level four artifact from the marketing team looks like level two work in the sales team, your framework is broken.

Curate these examples carefully. Redact sensitive commercial information. Ensure you select examples from diverse teams. A career framework for marketing must include examples from product marketing, demand generation, and communications. Update these examples annually. Stale examples lose credibility quickly.

Manage the senior individual contributor path honestly

Handle the senior individual contributor path with absolute honesty. Most technology companies claim to offer a technical track that goes as high as the management track. Most do not actually promote anyone above the first senior level on it.

Industry data confirms this severe disparity. Roughly 14 percent of companies maintain an active dual track for engineers above the staff level. The principal and distinguished levels remain practically empty at most organizations.

If your top individual contributor level has been empty for three years, do not advertise it. Either commit to using it or admit the ceiling. Pretending a path exists when it does not destroys trust. Employees look at your organizational chart. They see that all vice presidents manage people. They realize the technical track is a fiction.

Redesign the upper levels of your technical track to reflect reality. Define the actual business need for a principal engineer. Allocate headcount for these specific roles. Do not treat them as honorary titles for tenured employees. If your business model does not require distinguished individual contributors, cap the track at the staff level. Be clear about the terminal level.

Define the exact meaning of a promotion

Establish clear rules for advancement. Define exactly what a promotion represents in your organization. A promotion either recognizes that someone is already operating at the next level, or it is a bet that they will step up to it.

Pick one philosophy. Apply it consistently across all departments. Mixing these two philosophies is the single largest source of perceived unfairness in promotion cycles.

The engineering department might require employees to perform at the next level for six months before promotion. The sales department might promote employees on potential alone. Employees talk across department lines. They will notice the discrepancy immediately.

In North America, organizations often promote on potential to retain staff in competitive markets. In Europe, strict employment contracts often demand proven performance before a title change. Align your global policy where possible. If regional labor laws force a divergence, document the difference publicly.

Navigate European labor structures

Implementation details differ sharply across regions. European organizations must engage works councils early in the design process. In Germany, the Betriebsrat has co-determination rights over evaluation criteria under the Works Constitution Act. You cannot roll out a new career framework without their formal approval.

Present your three dimension model to the works council as a tool for objective fairness. Emphasize how the removal of subjective adjectives protects employees from arbitrary management decisions. A failure to consult the Comite Social et Economique in France before changing leveling structures can result in legal injunctions. Plan for a mandatory six month consultation period.

North American implementations face less friction from organized labor but more pressure from rapid market shifts. At will employment makes employees flight risks if they disagree with their leveling. North American teams should focus heavily on the examples and the artifacts. Prove that the framework reflects the actual work being done in the market right now.

Address terminal levels openly

Address the concept of terminal levels openly. Not everyone wants to be promoted. Not everyone should be promoted. Organizations need competent employees who are happy doing steady work.

Define the level where progression is no longer mandatory. In many engineering organizations, this is the senior software engineer level. An employee can remain at this level indefinitely as long as their performance remains satisfactory. Up or out policies damage morale. They force good individual contributors into terrible management roles.

Document the terminal level for every job family. Make it acceptable to reach this level and stay there. Adjust compensation bands to allow for long term tenure at the terminal level. Annual merit increases must still apply to employees who are not actively seeking promotion.

Establish compensation overlap logic

Link the career framework directly to compensation bands. Publish this link internally. If you operate in California, Washington, or New York, you already publish ranges externally. Internal employees deserve the exact same clarity.

Show the mathematical overlap between bands. A high performing level three employee often earns more than an entry level level four employee. Explain why this overlap exists explicitly. It prevents artificial urgency for promotions. Employees will not rush a promotion case just to get a raise if they know their current band has room to grow.

Under the upcoming European rules, you must explain exactly how you calculate pay at each level. Use your career framework as the mathematical foundation. Base pay aligns with the framework level. Variable pay aligns with performance against that level expectations. This simple formula defends your organization against pay equity lawsuits.

Separate performance from progression

Your career framework measures progression. Your performance review measures execution. You must separate these two concepts entirely. A career framework defines the size and complexity of the role. A performance review measures how well the employee executed that specific role over the last cycle.

An employee can deliver exceptional performance without demonstrating the capacity for promotion. A level three engineer might write perfect code for small features. They deserve the highest possible performance rating. They might also show zero ability to design large systems. They do not deserve a promotion to level four.

Managers confuse these concepts constantly. They promote high performers as a reward for past hard work. This creates the Peter Principle. Employees rise to their level of incompetence. You must train your managers to separate the two conversations. Use the performance review to discuss the past six months. Use the career framework to discuss the next two years.

When you decouple performance from progression, you protect the integrity of your framework. You stop handing out titles as retention bonuses. You ensure that every person at a senior level actually possesses senior capabilities. This discipline is uncomfortable in the short term. It builds an incredibly capable organization in the long term.

Define the manager transition explicitly

The transition from individual contributor to manager ruins more careers than any other move. Your framework must treat this as a lateral career change, not a promotion. An employee moving from a senior individual contributor role to an engineering manager role is starting a new discipline. The framework must reflect this reality.

Define the manager track using the exact same three dimensions. The scope of work shifts from technical problems to organizational problems. Autonomy shifts from managing personal time to managing team resource allocation. Impact on others shifts from mentorship to formal accountability for team output.

Force employees to read the manager framework before they apply for a management role. If they cannot name three management tasks they want to do on Monday, deny the transition. Many employees only pursue management because the individual contributor track caps out too early. Fix the individual contributor track first. Do not use the management track as a reward for technical tenure.

Integrate leveling directly into core systems

A career framework must live where work happens. A document stored on an intranet portal will gather dust. Integrate your leveling directly into your performance management and compensation software.

Systems like Workday, Lattice, and Pave allow you to map competencies directly to employee profiles. When managers write performance reviews in Lattice, the criteria for the exact level should appear next to the text box. When recruiters generate offer letters in Workday, the compensation band must link dynamically to the job level.

Next quarter, audit your system mapping. Ensure every job code in Workday connects to exactly one level in your career framework. Orphaned job codes create legal liabilities under the incoming transparency laws. They make compensation equity analysis impossible.

Maintain stability across performance cycles

The value of a career framework accumulates through repeated use. Rewriting it every year resets the mental model of your workforce. It teaches people not to invest time in understanding the system.

Fix genuine defects immediately. Resist the urge to rewrite the entire document because a new executive prefers different terminology. Revisit the core structure properly every two or three years.

When you do update the framework, version it like software. Release the new framework with a detailed changelog. Explain exactly what moved. Perhaps you merged the communication and collaboration criteria. Perhaps you split the management track from the technical track earlier. Tell the organization why the change serves them better.

Equip recruiters with objective criteria

Recruiters are the first people to test your framework on the market. They use it to map external candidates to internal bands. If your framework is disconnected from market realities, recruiters will struggle to close candidates.

Candidates will ask recruiters detailed questions about progression. A strong candidate wants to know exactly what it takes to reach the next level before they sign the offer. Equip your recruiting team with the second person criteria. Let them share the anonymized examples of real work.

When candidates see a clear path for growth, offer acceptance rates increase. A structured framework proves that your organization takes development seriously. It serves as a major competitive advantage in candidate conversations.

Practical next steps

Audit your highest technical level. Count the actual population. If the number is zero, remove the level from your published framework this quarter. Do not advertise a path that nobody actually walks.

Convert one job family to the second person perspective. Start with a small, contained team like product design. Rewrite the criteria as direct actions. Test the reception with the team before rolling the format out globally.

Identify any pay gaps over 5 percent within the same level. European teams must document the objective justification for these gaps before the 2026 deadline. Use your three dimensions of scope, autonomy, and impact to explain any variance.

Map your current leveling document to your core systems. Ensure every active employee in Workday has a designated framework level attached to their profile. Fix any orphaned job codes immediately.

Build an internal library of three calibrated promotion cases. Redact the names and sensitive commercial details. Publish the examples internally before your next performance cycle begins. Let employees see exactly what success looks like in practice.