Your merger isn’t done until people can move between teams
A job title is shorthand. It tells you what you are trusted with, who your peers are, and what you might do next. While most folks couldn’t recite their boilerplate job description, they know what their title is worth on their team.
When companies combine, the systems integration get a plan, an owner, and a budget. Job titles get a standardization pass in the HR system and that piece is declared finished.
What that pass can’t reach the meaning that those job titles carry within the teams that use them. Each company arrives with its own definition of Senior, Lead, Manager, and Principal, built out of years of local precedent. The official architecture harmonizes the labels. The teams keep operating on the definitions they already had.
Untangling that takes intentionality and time, and it sits well beyond the title harmonization that was budgeted.
The bill for skipping it shows up later:
Mobility stops. Moving someone from one team to another is lateral on paper but perceived as a promotion or demotion in practice. People stay where they are, get bored, and leave for the growth they could’ve had internally.
Hiring goes incoherent. Five managers write five job descriptions for the same role, run five interview loops, and hold five different bars.
Compensation becomes indefensible. Two people, one title, two ranges. They find out eventually.
Promotion turns into advocacy. With no shared definition of the next level, advancement depends on how well your manager argues for you, which penalizes the people least inclined to argue for themselves.
Managers cannot calibrate. Performance conversations across the old company lines are measured against individual managers’ bars.
Worst of all, people quietly learn their title means something only locally, so it stops meaning anything at all. Status falls back to which company you came from, which defeats the purpose.
The lack of mobility has the biggest price tag. Replacing someone runs at least half their salary once you factor in the search, ramp up, and work that didn’t happen in between. In an org where a majority of folks landed with a “senior manager” title, where upward mobility is murky and perceived fair lateral moves don’t exist, the cost is high.
It stays broken because the work appears like administration, so it gets sized that way. The work costs real money, crosses HR, finance, and every function, leaving it without a natural owner. On top of that, it’s politically loaded, because harmonizing means some people hear that their title means less than it used to.
We did this in a 500-person design organization assembled from multiple orgs. Over 50 roles went onto a single leveling framework, replacing dozens of inconsistent title conventions, with a clear split between what managers owned and what individual contributors did.
What worked for us is repeatable. Do it in a time window so there’s a defined cut-over time. During a merger, change is expected, and adjustments read as part of the transition. Publish the framework before anyone’s placement so that people can accept the system before they accept their own spot in it. And work top-down, mapping roles to levels before you map people to levels. Doing it in the other direction turns a design exercise into 500 negotiations.
Two things carry the rest of the human element. Say early that no one’s pay will go down, and give managers the words before the announcement. They get asked what it means for them within the hour; having no answer is how a rumor wins.
Titles are what’s visible, and decision-rights go with. If you harmonize only the job titles, you get tidy labels with the same confusion underneath about who owns what.
In our experience, integrations are declared finished when systems are in one platform. A better test is whether a person can move from one team to another without redefining their job. The measure is whether the people still there can grow without leaving.