Skip to main content
Org Chart Studio

When everyone is Head of something

Job title inflation makes roles harder to read, distorts hiring, and creates awkward career ladders. Use titles to communicate the work truthfully.

Org Chart Studio TeamPublished10 min read
  • leadership

A job title makes a small promise.

It tells the employee what kind of judgment the role is expected to carry. It tells colleagues where authority may sit. It tells candidates whether a job matches their experience, and the outside world roughly who they are dealing with.

Then a 14-person company appoints its fourth "Head of."

Nobody has necessarily lied. Each person may genuinely lead an area. The titles feel generous, cost less than compensation, and make a growing company look more established. The trouble arrives later, when the company needs to hire someone above a Head of, compare roles across functions, or explain why 2 people with similar titles make decisions at entirely different levels.

Job title inflation begins as flattery and ends as information decay.

This is not an argument for bland titles or a universal corporate ladder. "Lead," "director," and "Head of" can describe real scope. Small companies often need people to carry broad responsibility earlier than large ones do. The problem is not senior language. It is a title that communicates status the role does not yet support, or conceals work the organization would rather not name accurately.

Titles are part of the company's operating language. Inflate the words, and every reader has to learn the private exchange rate.

Titles are information, not office decoration

An organization can function without elaborate titles. It cannot function for long without some way to communicate differences in role, authority, expertise, and accountability.

Titles are one part of that system. They compress a great deal of information into a few words.

"Senior accountant" suggests something different from "accounting assistant." "Sales manager" implies responsibility that "account executive" does not. "Head of operations" suggests organization-wide ownership of a function, not merely skilled participation in it.

The signal is imperfect. Industries use language differently, companies vary in size, and a director at one firm may have broader scope than a vice president at another. Even so, people rely on titles because the alternative is reading every job description and interviewing the entire org chart.

Ioana Marinescu and Ronald Wolthoff examined this information role in research on online job vacancies and applicants. In their CareerBuilder data, titles explained more than 90% of wage variation among vacancies, far more than detailed standard occupation codes. Titles also explained more than 80% of variation in the average education and experience of applicants across vacancies.

Those percentages describe the researchers' particular data and models, not every labor market. The finding still shows why title accuracy matters. Candidates use the words to decide which jobs fit them. Employers use the words to attract a certain labor pool.

A title is not merely how someone feels about their role. It is part of how the labor market and the organization route information.

Inflation works because the symbol has value

If titles meant nothing, companies would not use them as rewards.

Arthur Martinez and colleagues defined job title inflation as a deliberate breach of the cooperative expectations that make titles informative, used to extract organizational gains. Their 2008 paper is conceptual rather than an empirical estimate of prevalence. Its central insight is useful: titles work because people collectively treat them as meaningful symbols.

That meaning creates several tempting uses.

A company can offer a title when compensation is constrained. It can attract a candidate with language that sounds more senior than the work. It can reward retention without changing authority. It can make a small team appear to have a complete leadership bench. It can calm a status dispute without resolving the overlap underneath it.

The exchange may feel harmless. The employee receives recognition, and the company spends nothing.

But symbols retain value only while other people trust them. If "director" can mean department leader, senior individual contributor, project coordinator, or person the company did not want to lose last spring, the title stops reducing uncertainty.

Every conversation then needs a translation:

  • Is this person a people manager?
  • Do they control budget?
  • Can they make the decision?
  • Is their scope company-wide or local?
  • What role would actually be a promotion?

The organization saved a difficult conversation once and scheduled smaller versions of it indefinitely.

The ladder eventually runs out of rungs

Early title decisions create later structural constraints.

Suppose the first salesperson becomes Vice President of Sales. At 8 people, that may feel proportionate. They own all sales because they are all sales.

At 80 people, the company needs a leader who has built a larger function, designed territories and compensation, hired managers, and forecast across several segments. The original title is occupied. The company can place a new executive above the vice president, invent a more senior title, redefine the old role, or ask someone to accept what feels like a demotion despite no change in their work.

None of these choices is impossible. All are harder than distinguishing recognition from level at the beginning.

The problem repeats across functions. A company accumulates Heads of, then needs a layer above them. "Chief" roles multiply. Directors manage nobody while managers lead departments. Career paths become a sequence of adjectives because the underlying levels were never defined.

This affects internal mobility. If an employee already holds a senior title, the organization has fewer honest ways to recognize growth. A bigger title may require pretending the new role is executive when it is simply broader. Compensation, scope, and title begin moving on separate tracks.

The chart still displays hierarchy. It just stops explaining it.

Sometimes the title is doing worse than flattering

Title inflation can cross from ambiguity into exploitation.

Lauren Cohen, Umit Gurun, and N. Bugra Ozel studied the strategic use of managerial titles to avoid overtime pay. Using U.S. job postings from 2010 to 2018 and the federal salary threshold in force during the period, they found an almost 5-fold increase in managerial-title use just above the cutoff for overtime exemption.

The suspect titles included "Director of First Impressions" for work otherwise equivalent to a front-desk role. The pattern was stronger where firms had more bargaining power and workers had weaker outside options. The researchers estimated that firms avoided roughly 13.5% in compensation costs for each strategic "manager" and found no evidence of long-term wage or career benefits for the affected employees.

The paper was revised in 2025 and later published in The Review of Financial Studies. It examines a specific U.S. regulatory setting and historical threshold, not all managerial titles everywhere. It does, however, provide unusually direct evidence that title inflation can be used to transfer value away from workers.

This is not a clever compensation strategy. Job duties, pay rules, and legal classifications cannot be made honest by putting "manager" on a business card. Organizations should obtain current legal guidance for classification decisions rather than treating a title as an exemption spell.

The broader lesson applies beyond compliance. When the label and the work diverge, ask who benefits from the divergence and who bears the cost.

"Head of" is a scope claim

"Head of" can be a clear and useful title. It normally claims that the person owns a function or domain at the relevant organizational level.

The ambiguity comes from the missing boundary.

Head of People for the whole company is different from Head of People Operations for one region. Head of Product can mean the most senior product leader, a leader of one product line, or the only product employee. Each may be legitimate. The title alone does not tell the reader which.

Before granting it, state:

  • the domain the person heads;
  • the organizational level at which they head it;
  • the decisions the role owns;
  • the people, budget, or outcomes within scope;
  • the role above it, if one exists;
  • the conditions under which the title would need to change.

This protects the employee as much as the company. A grand title with narrow authority can create expectations the person cannot meet. External partners may assume decision power they do not have. Candidates may join expecting a leadership role and discover a senior individual-contributor job. Future employers may struggle to compare the experience.

Clarity is kinder than symbolic promotion followed by private disclaimers.

Separate level, role, and recognition

Many title problems begin because 1 label is being asked to do 3 jobs.

Level describes the scale and complexity at which a person operates. Role describes the work and domain. Recognition communicates that the organization values a contribution.

These should influence one another, but they are not interchangeable.

Someone can make an exceptional contribution without moving to a role with broader scope. A specialist can grow in judgment, impact, and compensation without becoming a people manager. A person can lead a temporary initiative without permanently becoming Head of it. A company can recognize retention and performance directly rather than making the org chart carry the message.

When recognition requires title inflation, the organization may have weak alternatives: poor compensation flexibility, no expert career path, inconsistent promotion criteria, or a culture that treats management as the only form of progress.

Fixing the title without fixing those conditions will not last. Another exception will arrive with a good reason.

Clear ownership helps here. Define what the role owns before naming it. If the work has no distinct scope or decision rights, a larger title will not create them.

Audit the title system before adding another exception

A title audit does not require an enterprise job-architecture program and 14 months of consulting diagrams.

Start with the current org chart and role list. For each title, record:

  • role purpose;
  • scope of outcomes;
  • decision authority;
  • people-management responsibility;
  • budget or resource authority;
  • level of complexity and independence;
  • comparable titles elsewhere in the company;
  • the next plausible step.

Then look for contradictions.

Do 2 directors operate at different levels without a reason? Do some managers manage nobody while equivalent individual contributors have lower-status titles? Does "Head of" mean whole-company leadership in one function and team leadership in another? Are titles being used to compensate for pay decisions the company will not make?

Do not force identical language across genuinely different disciplines. Engineering, legal, sales, academia, healthcare, and creative work carry established conventions. Consistency should make roles comparable, not erase useful professional meaning.

Also ask new hires what the titles led them to assume. They have not yet learned the internal exchange rate. Their errors show what the system communicates to a reasonable outsider.

Use the least impressive title that tells the truth

This is not a call for deliberate understatement that makes experienced people sound junior. The title should help the employee, colleagues, candidates, customers, and future employers understand the role.

Choose language that answers 3 questions reasonably well:

  1. What kind of work is this?
  2. At what level is it performed?
  3. What scope or authority does it carry?

Then put the rest in a clear role description and decision record. A title cannot carry the whole operating model.

Review titles when work changes, not whenever status anxiety peaks. Make compensation, development, and recognition honest enough that a larger noun is not the only available reward.

The point is not to deny people good titles. It is to give them titles that remain good when someone asks what they mean.

When everyone is Head of something, the company has not removed hierarchy. It has made the hierarchy harder to read.