Note · Job architecture · Updated on

Why job architecture goes stale

Most job architectures are not outgrown. They are worn down by exceptions, one reasonable request at a time.

Short answer: Job architecture goes stale through exceptions, not age: A new title to close a hire, a level raised to fit an offer, a role that grew but kept its old level. It needs one named owner who approves every new job, title and level change against written rules and reviews the exceptions each year.

What the data and the rules say

Most organizations have a job architecture and many are unhappy with it. In a global survey run by a consulting firm between late 2024 and early 2025, over three in four organizations had one in place. Over half were dissatisfied with their framework, often because of poor governance. The common problems named were outdated job content, inconsistent application by HR managers and the risk of bias when employees are mapped to it [1].

The rules assume the structure matches the work. Under the EU pay transparency directive, pay structures must let an employer assess whether workers are doing work of equal value on objective, gender-neutral criteria [2]. In California, an employee may ask for the pay scale for the position they currently hold [3]. If a person's level no longer reflects their job, neither answer holds up.

What it means for a company of 50 to 500 people

Exceptions do the damage, not time. A new title to win a candidate, a level raised to justify an offer, a role that doubled in scope without being looked at again. Each one is reasonable on the day. Together they make the levels describe past negotiations instead of the work.

Everyone can change it, so no one owns it. Recruiters create titles in the applicant tracking system, managers in the HR system, finance in the headcount plan. Within a year there are three versions and none is the reference.

The project ends and the team moves on. The architecture is built in a project, then handed to whoever is free. Without an owner, the first exception sets the precedent for the next. Our guide on mapping titles to levels covers how the first months after a rollout go wrong.

Rebuild instead of upkeep. Companies wait until the structure is clearly broken and then start again. A rebuild costs far more than a small amount of steady upkeep and resets trust in the levels each time.

Our view

We would name one owner, usually the head of people or a compensation lead, who approves every new job, title and level change against written rules and keeps a log of the exceptions. Once a year, alongside the pay review, the owner reads the log. If one job family keeps producing exceptions, the architecture is wrong there: Fix the rule rather than grant another exception. Where no one inside has the time, that is the work our guide on what a fractional comp lead does describes.

Sources

  1. Mercer, The evolution of job architecture in the tech industry (global job architecture survey, fieldwork late 2024 to early 2025), checked 2026-10-31
  2. Directive (EU) 2023/970 on pay transparency, Article 4(4) (EUR-Lex), checked 2026-10-28
  3. California Labor Code section 432.3, subsection (c)(2), checked 2026-10-28

Job titles to levels without a revolt

Title revolts start with a public reveal or one negotiated exception. Five ways title mapping goes wrong and what a fair mapping looks like.

How many job levels do you need?

How many job levels a company needs depends on the work, not the headcount. Five traps in setting the count and what a sound ladder looks like.

What does a fractional comp lead do?

A pay structure starts to drift the day it is delivered. What a fractional comp lead does each week, quarter and year and when you do not need one.

See Resources for every guide and the self-check.