Job titles to levels without a revolt
Titles are promises people have made to themselves and to others. Level the work first, then settle titles person by person.
Short answer: Map jobs to levels by the work, never by the title. Agree the title rules and how downgraded titles are handled before anyone sees a result. Tell each affected person privately before any group announcement. Most title revolts start from a public reveal or from one negotiated exception. Rarely is the new level itself the cause.
One hundred ninety titles
Picture a 260-person logistics software company in Chicago. Two years ago it bought a smaller rival. Today it has 190 different job titles for 260 people. There are three Directors of Customer Success, one with a team of twelve and two with no reports. "Senior" means two years of experience in one office and eight in the other. The acquired company had a habit of making people "Head of" something when it could not afford a raise.
The company has just finished leveling its jobs. The new framework has eight levels and a short list of titles for each one. On paper the work is sound. Then a draft spreadsheet circulates in a manager channel. It shows 31 people whose new title would be lower than the one on their email signature. By the next morning a director has told the head of people she will resign if she becomes a "Senior Manager". Two sales leads say customers will not take meetings with anyone below "Director". The CEO asks whether the whole project should be paused.
Nobody's pay has changed. Nobody's job has changed. The anger is entirely about words. And it is real, because those words are on business cards, résumés, professional profiles and customer contracts.
This company is a composite of situations common at this size. It is not a client and the details are illustrative.
Why mapping titles is hard
A job title does three jobs at once. Inside the company it signals rank: Who decides, who reports to whom, who gets heard. Outside the company it is a market signal: Recruiters, customers and future employers read it as a claim about scope. And for the person who holds it, it is part of their professional identity. They may have negotiated hard for it or accepted it instead of a raise.
A level does one job. It describes the size of the work: Its scope, complexity, autonomy and impact. Our guide on grade vs band vs level sets out why the level, not the title, should carry pay decisions.
When a company levels its jobs, it is asking titles to start following levels. That is the right goal. It also takes something from people that they experience as theirs. Two good goals pull against each other here.
The first is consistency. One title should mean one size of job. Without that, titles cannot support offers, promotions, posted pay ranges or equal pay comparisons. Candidates and staff draw the wrong conclusions from them.
The second is trust. People need to believe the change is fair and that it was not done to them. A technically perfect mapping that nobody trusts will be undone by exceptions within a year.
Messy titles are rarely the result of carelessness. They pile up for understandable reasons. A title was given in place of a raise the budget could not cover. A senior hire asked for a bigger title to match an outside offer. An acquisition brought in a second naming system. A customer-facing team needed titles that open doors. Each choice made sense at the time. The mapping project inherits all of them at once.
The scale of the gap is easy to underestimate. In an August 2025 survey of 1,000 US workers run for a résumé services company, 57% said coworkers with the same title had significantly different pay or responsibilities. In the same survey, 39% said they had been given a more senior title without a pay increase [4]. Those are self-reported views, not audited data. They still describe the starting point most mapping projects meet.
Five ways title mapping starts a revolt
Each of these looks reasonable from inside the project. Each turns a sound leveling into a fight about words.
"Sort the titles first"
What it looks like: The project exports every title from the HR system, groups similar strings together and assigns each group a level. All "Senior Analysts" land on one level and all "Directors" on another.
Why smart teams fall into it: Titles are the only data that already exists for every job. Sorting them feels fast and objective. It also avoids awkward conversations about what each person actually does.
What it costs: It maps the mess, not the work. The director with twelve reports and the director with none land on the same level. The mapping then confirms every inflated title and penalizes every modest one. People who were quietly doing bigger jobs under small titles notice first. They are often the people the company most wants to keep. When the result is challenged, nobody can explain why a job sits where it does, except that its title said so. The mapping has to be redone, this time with everyone watching.
"Announce it all at once"
What it looks like: The new framework, the title list and every person's new title are released together. It might be an all-hands slide, a company-wide email or an update in the HR system that people discover on a Monday morning.
Why smart teams fall into it: One announcement feels transparent and fair. Everyone hears the same thing at the same time. It also ends a long project with a clear launch.
What it costs: The people who lose a title learn it in public, next to colleagues who did not. The first emotion is embarrassment, which turns quickly into anger. Managers hear the news at the same moment as their teams, so they cannot answer questions. A single message cannot explain 31 individual situations. Within a day the story inside the company is no longer "we have a fairer structure". It is "they demoted people". A leaked draft is the same trap without the planning. A spreadsheet in a manager channel announces everything at once, with no explanation attached.
"Negotiate titles one person at a time"
What it looks like: After the pushback, leaders start making exceptions. The director who threatened to resign keeps her title. Then the two sales leads keep theirs. Then a team lead asks why he was not offered the same.
Why smart teams fall into it: Each exception solves an urgent problem. Losing a strong performer over a word seems absurd. Nobody wants the project to cost the company its best people.
What it costs: The first exception becomes the rule. It tells everyone that titles go to whoever pushes hardest. That is the system the project was meant to replace. The people who accepted their new title quietly feel punished for cooperating. The exceptions also tend to follow confidence and closeness to leadership, which makes them a fairness risk as well as a morale one. Within a year the company has a new set of inconsistent titles and a framework nobody believes. Exceptions are not wrong in themselves. Making them up case by case under pressure is.
"Hand out a title instead of a raise"
What it looks like: To soften the change, or to keep someone who is unhappy, the company offers a bigger title with no change in pay or work. "Manager" and "Director" become a currency the company can print for free.
Why smart teams fall into it: Titles cost nothing on the budget. People value them. It seems like a good trade for everyone.
What it costs: Titles stop meaning anything, which is the problem the mapping set out to fix. People notice the gap between title and pay quickly. They then compare their pay with the market for the title rather than the level. Many find it short. There are legal edges too. In the US, a title alone does not make a job exempt from overtime. Exemption depends on the salary and the duties actually performed [1]. A "manager" who manages nobody is still owed overtime if the duties and salary tests are not met. A widely cited research paper found that managerial job titles in US job postings jump sharply just above the federal salary threshold for overtime exemption. It also found no evidence that people holding these titles gained in later pay or careers [3]. A title handed out to save money can end up costing it.
"Keep the old titles on the outside"
What it looks like: To avoid the fight, the company introduces internal levels and keeps the old titles everywhere people can see them: Job ads, email signatures, professional profiles and customer materials. The levels live only in the HR system.
Why smart teams fall into it: It seems to get the benefits of leveling without the pain. Customer-facing teams in particular push for it.
What it costs: The two systems drift apart and the visible one wins. New hires are recruited against the old titles, so the mess grows back. Posted pay ranges come from levels while the job ad shows a title that implies a bigger job. Candidates notice the mismatch. Some state rules tie posted ranges to titles directly. Washington's guidance, for example, expects a range for each title when one posting covers several [5]. In the EU, pay information and pay gap reporting are built on categories of workers doing the same work or work of equal value [6]. Grouping people by inconsistent titles makes those categories wrong from the start. A small set of external titles for customer-facing roles can work. A whole shadow title system does not.
What a sound title mapping looks like
There is no way to change titles without some disappointment. There is a way to make the disappointment feel fair. In our view a sound mapping has these qualities.
- Jobs are leveled before anyone sees a title. Each job is placed by its scope, decisions and impact. The title discussion starts only after the levels hold up to review. Our guide on how to level employees at a startup covers placing people on levels.
- The title rules are few and written down. Each level has a short list of allowed titles. Words like "Manager" and "Director" have one meaning, for example that the person leads people or a budget. The rules can be read in a minute.
- The handling of lower titles is decided once. Whether a title changes now, stays until the next role change or is kept as a courtesy, the same rule applies to everyone. It is agreed before the first conversation, not invented during it.
- The order of telling is planned. Managers understand the result for their team before their team does. People whose title goes down hear it one to one, with the reason, before anything is shared more widely.
- Pay and title are kept apart but explained together. A lower title with unchanged pay is said plainly to be unchanged pay. Where a level change does affect pay, that is a separate conversation with its own reasons.
- Exceptions have a route. Anyone can ask for a review. One person or a small group decides against the written rules and records why. An approved exception is written as a change to the rules, so it applies to everyone in the same position.
- External titles are bounded. Where customer-facing roles need a market title, the company allows a short list of them, tied to a level and written in the same rules.
- There is a date to look again. The mapping is checked after a few months for drift, new exceptions and titles created outside the rules.
None of this is a script to follow. Each quality is a test to put to a mapping before it goes live. The most useful single test is to pick the three people most likely to be upset and ask whether the company could explain their outcome to them in two minutes, face to face. If not, the mapping or the rules need more work.
The calls only you can make
Several of these choices say what kind of company you want to be. Nobody outside can make them for you.
How strictly titles follow levels. A strict policy makes every title predict a level. That is easier to explain and to defend. A looser one lets teams keep some flexibility in naming and accepts more drift. Our guide on how many job levels you need looks at how the level count shapes the title list.
What happens to people whose title goes down. Changing titles now gives a clean structure at once and a harder few weeks. Keeping current titles until the next role change protects goodwill and leaves a visible mismatch for longer. Both can be fair. Mixing them is not.
What "Manager" and "Director" mean. Some companies reserve these words for people who lead teams. Others allow them for senior specialists. The first keeps titles honest. The second keeps a path for experts who do not want to manage, but needs another way to signal seniority.
Whether customer-facing roles get market titles. Sales and account teams often argue that buyers judge them by their title. That can be true. Allowing it is a commercial decision. It should be made openly, for named roles, rather than conceded one argument at a time.
How open to be about the mapping. Publishing the title list for each level helps people see their path. It also invites comparison. Our guide on what to do when an employee asks about pay covers the conversations that follow.
The law and the numbers
This is general information, not legal advice.
- US overtime. Federal rules state that "a job title alone is insufficient to establish the exempt status of an employee". Status depends on whether the salary and duties meet the tests [1]. In May 2026 the US Department of Labor restored its 2019 salary level of $684 per week for most exempt executive, administrative and professional employees, after the 2024 increase was vacated in court [2]. Some states set higher thresholds.
- Research on titles. A National Bureau of Economic Research working paper (first issued January 2023, revised May 2025) found widespread use of managerial titles to avoid overtime and estimated that firms avoid roughly 13.5% in compensation costs for each strategic "manager" hired. It found no long-term benefit to the people holding those titles [3].
- What workers report. In an August 2025 survey of 1,000 US workers for a résumé services company, 92% said companies use titles to give the illusion of career growth. 57% said coworkers with the same title had significantly different pay or responsibilities. 54% said titles influence their decision to accept a new job [4]. This is a commercial survey of opinions, not a measure of practice.
- US posting rules. Washington's job posting guidance expects a range for each title when one posting covers several [5]. Our note on what changed in US pay range laws in 2026 tracks other states.
- EU. The pay transparency directive requires pay structures that allow comparison of work of equal value on objective, gender-neutral criteria. Pay information and pay gap reports are built on categories of workers doing the same work or work of equal value [6]. A title is not a category. The work behind it is.
Our view
We think titles should follow levels. The change is worth making. A title that means one thing is one of the cheapest fairness tools a company has. It also supports every pay decision that follows.
We also think the work is mostly about order. Level the jobs privately and by the work. Write a short set of title rules and the handling of lower titles before any result is shown. Then tell people one by one, starting with those who lose the most. The revolts described here start with a public reveal or a first exception. They rarely start with the levels themselves.
We would argue hardest against negotiating titles case by case under pressure. It feels kind and it rebuilds the old system within a year. If an exception is right, it is right for everyone in the same position. Write it into the rules.
Where we help
Our job architecture work levels jobs by the work first. We then draft the title rules and map today's titles to the new levels, with a list of the people whose title changes and the reason for each. The entry point is our Leveling Starter Kit, for up to three job families. If a conversation would help first, Book a free call.
Sources
- 29 CFR § 541.2, Job titles insufficient (Legal Information Institute), checked 2026-10-25
- US Department of Labor, Wage and Hour Division, technical amendment restoring the 2019 exemption regulations (news release 26-716-NAT, 14 May 2026), checked 2026-10-25
- Cohen, Gurun and Ozel, Too Many Managers: The Strategic Use of Titles to Avoid Overtime Payments, NBER Working Paper 30826 (January 2023, revised May 2025), checked 2026-10-25
- CPA Practice Advisor, report of a MyPerfectResume survey of 1,000 US workers (fielded 7 August 2025; published 12 May 2026), checked 2026-10-25
- Washington L&I, Administrative Policy ES.E.2, Job Posting Requirements (issued 3 December 2025), checked 2026-10-24
- Directive (EU) 2023/970 on pay transparency, Articles 4, 7, 9 and 10 (EUR-Lex), checked 2026-10-25