Job architecture without a consulting project

Job architecture sounds like an expensive corporate initiative. It usually involves a steering committee and a large consulting firm. At an organization under one thousand people, it is just a spreadsheet. You need two people and six weeks.

You need this structure before you can build pay bands. You need it before you define career paths or facilitate internal mobility. Pay transparency compliance requires this exact foundation. Everything else waits on this execution.

Many HR leaders delay this project. They assume it requires months of stakeholder interviews and complex point factor analysis. That approach belongs to multinational conglomerates. Midsize companies simply need a functional taxonomy.

A standardized structure prevents managers from making up titles during the hiring process. It stops compensation drift where tenure replaces merit. It provides the core data structure required to manage a modern workforce fairly.

Consultants often borrow your watch to tell you the time. They interview your executives and place your existing operational problems into a presentation. You already know the work happening in your company. You just lack a framework to organize it. This framework scales with you. It gives every compensation decision a logical anchor. Without it, you are flying blind.

The compliance clock requires speed

The legal landscape is shifting rapidly. North America started the trend with pay ranges on external job postings. Colorado led the way with the Equal Pay for Equal Work Act on January 1, 2021. California followed with Senate Bill 1162 on January 1, 2023. Washington enacted similar requirements concurrently. New York State implemented its specific pay transparency law on September 17, 2023.

Canada is moving in the same direction. British Columbia mandated wage transparency on November 1, 2023. You must post accurate ranges on all open roles in these jurisdictions.

The New York State law requires employers to post the minimum and maximum annual salary. You must include this on internal transfer announcements and external advertisements. California requires employers with 15 or more employees to include pay scales in all job postings. Washington law dictates that postings must include a general description of all benefits. You cannot rely on a generic company statement. You need specific data tied to specific roles.

You cannot post accurate ranges if you do not know what level a job occupies. You need a system to categorize the work.

Europe is forcing a massive operational shift toward systemic internal transparency. The EU Pay Transparency Directive changes how companies manage compensation data. Member states must transpose this directive into national law by June 7, 2026.

The directive gives workers the right to request average pay levels broken down by sex. This applies to workers doing the same work or work of equal value. It requires companies with over 100 employees to report on their pay gaps.

If a company finds a gender pay gap of 5 percent or more that cannot be justified by objective criteria, they face a heavy burden. They must conduct a mandatory joint pay assessment with worker representatives.

The European approach fundamentally alters the burden of proof. Historically, an employee had to prove they were underpaid due to discrimination. Under the new directive, the employer must prove that no discrimination occurred.

Objective criteria mean a documented job architecture. You need defined levels and families to prove two people do entirely different work. Your job architecture provides this proof. It demonstrates that pay differences stem from objective differences in problem scope and required autonomy. If you lack this structure, every pay difference becomes a potential legal liability. Regulators will not accept vague explanations about cultural contributions. They demand structural evidence.

Build families around contribution instead of reporting lines

Start the project by defining job families. Families group work by the type of contribution to the business. They ignore the current organizational chart entirely.

A typical midsize organization needs six to ten job families. Common examples include engineering, product, design, commercial, and operations. Keep the categories broad and descriptive.

Do not create a distinct family for every small department. Departments change constantly. A reorganization will shuffle reporting lines next year. Job families must remain stable through multiple structural redesigns.

Consider a data analyst. Today, they might report to the marketing director. Next year, they might join a centralized data science team reporting to the chief technology officer.

Their department changes based on executive preferences. Their core contribution remains analyzing data and building predictive models. Their job family is data.

Keep the architecture clean in your core systems. Platforms like Workday or BambooHR require logical data groupings to function properly.

If you create forty highly specific job families, you create a permanent data maintenance problem. You also dilute your market compensation data. Compensation platforms like Pave and Lattice need broad categories to match your jobs to external market benchmarks. Broad families make external mapping highly accurate. Specific families force you to guess. Guessing ruins your compensation strategy. Establish these foundational groupings first. They form the horizontal axis of your entire organizational grid.

Anchor levels to scope and ambiguity

Once you have families, you must define levels. Levels indicate the complexity and business impact of a role. Build separate tracks for individual contributors and managers.

This separation prevents a classic organizational failure. You should never force great technical experts into management just to secure a pay increase.

A company under one thousand people typically needs four to six individual contributor levels. You also need three to five management levels.

Too many levels create arbitrary micro promotions that lack meaningful differences in daily responsibility. Too few levels leave employees feeling trapped for years without visible progression.

Describe each level by the size of the problem the person owns. Define the amount of ambiguity they must absorb. Outline who they influence internally and externally.

Level one employees solve defined problems with clear instructions. Level three employees identify recurring problems and propose scalable solutions. Level five employees define the strategic direction for entire categories of business problems.

Never use years of experience to define a level. Years of experience act as a proxy for time passed rather than actual competence. Some people learn more in two years than others learn in a decade.

Using tenure as a requirement also creates direct legal exposure. It triggers age discrimination liabilities in the United Kingdom and several US states. Evaluate capability instead of time served.

Write the level descriptions plainly. A manager should be able to read the rubric and place a real person in five minutes. If a manager needs a specialized workshop to understand the difference between levels, your descriptions are too abstract. Clear language prevents leveling debates. Vague language encourages endless negotiations.

Separate market titles from internal architecture

Titles carry heavy emotional weight across the organization. Employees care about titles because titles signal status to their peers. Titles also dictate how external recruiters perceive them on professional networks.

Levels are purely internal and structural. Levels dictate compensation bands and equity grants. You must separate these two concepts entirely.

Keeping titles and levels separate allows you to give an employee a sensible external title without distorting your internal pay architecture. It solves immediate hiring problems without creating long term compensation debt.

Imagine a startup where the first marketing hire was given a chief marketing officer title. They are functionally operating at a director level based on your new rubric.

If you tie title strictly to level, you face a terrible choice. You must either pay them like a true executive or demote them publicly. Both options create unnecessary conflict.

If you separate title and level, they keep the external title. They sit in the internal director level for compensation. You avoid title inflation ruining your financial models.

This separation also allows you to handle local market expectations. Title inflation is a persistent reality in the US talent market. A vice president at a US technology company might manage three people.

In Germany or the United Kingdom, titles remain conservative. A vice president typically oversees hundreds of people and manages massive budgets.

Decoupling titles from levels lets you grant a US employee an inflated title to remain competitive locally. Internally, they sit at management level three. A German employee at management level three holds a director title. Their internal pay bands map to their shared level. This mechanism normalizes your global compensation structure.

The European and North American divergence

You must account for regional differences in how this architecture operates. The regulatory focus diverges significantly between Europe and North America.

In North America, the primary regulatory focus is candidate attraction and public job postings. State laws dictate that you must display a realistic salary range on external advertisements.

Your job architecture directly feeds your applicant tracking system. When a recruiter opens a requisition for an engineering role at level three, systems like Greenhouse or Lever automatically pull the approved pay band.

You use the architecture as an offensive tool in North America. It attracts candidates with clear expectations while keeping the company compliant with specific state laws. This structured data prevents recruiters from making ad hoc salary promises during initial screening calls.

In Europe, the focus centers entirely on internal equity and collective employee rights. The EU Pay Transparency Directive fundamentally changes the power dynamic between employer and employee regarding compensation data.

Your job architecture in Europe acts as a defensive legal framework. It is the primary document you will use to prove that two roles are not of equal value.

If a European employee challenges their pay, you will point directly to the level descriptions. You will demonstrate that one role absorbs more ambiguity and carries wider operational scope. You will use the architecture to show why a level three operations analyst earns less than a level four financial analyst.

North American teams should focus on integrating the architecture with hiring systems to automate posting compliance. European teams must focus on documenting the objective criteria that place each current employee in their specific level. You must build a system that satisfies both regulatory environments simultaneously.

Map the organizational reality before publishing

You have defined families. You have written clear level descriptions. The next critical phase is calibration. You must take your entire employee population and map them to the new framework.

Do this in a private spreadsheet. This phase is where your theoretical architecture meets messy organizational reality. You cannot execute this step in isolation.

You need to sit down with department leaders and review their teams line by line. Do not ask leaders to suggest levels for their people.

Provide them with the rubric. Ask them to describe the actual work their people execute daily. You then map that specific work to the corresponding level.

This structured conversation maintains consistency across different departments. It prevents a sales leader from inflating levels while an engineering leader grades harshly.

During this mapping process, you will discover significant anomalies. You will find a few people who clearly do not fit any defined job family.

You will discover distinct titles that mean entirely different things in different regional offices. Most commonly, you will find a team where everyone is somehow classified as senior despite doing junior work.

Managers often inflate performance reviews and responsibilities to secure higher pay raises for their team during budget cycles. The mapping exercise forces these hidden organizational debts into the light. You must confront this reality directly. Leaving these debts hidden will destroy your new compensation strategy before it begins.

Resolve anomalies in private

You must resolve every structural anomaly before you announce the framework to the wider company. A job architecture published with obvious logical flaws will be judged entirely on those flaws.

If you publish a framework stating senior engineers lead large technical projects, but leave a junior developer with a senior title in place, credibility vanishes. The company will dismiss the entire exercise as administrative fiction.

Fixing these anomalies requires difficult conversations. You might need to freeze base pay for individuals who are currently paid above their newly defined level band. This is known as red circling. You cap their salary until the market band catches up to their current pay rate.

You might discover a sales enablement manager who was given a vice president title during a desperate hiring push. Their actual scope covers a single product line. Their internal level maps to a manager.

You must explain that the external title remains, but their compensation band aligns with the internal manager level. Document this conversation thoroughly. You need a written record showing they understand their actual internal classification.

You might find an engineering team where six people hold senior developer titles, but only one person actually designs new system architecture. The other five maintain existing codebases.

You must adjust their internal levels to reflect their daily reality. If you fail to make this adjustment, you will overpay for basic maintenance work and fail to reward true architectural design. This misalignment destroys your compensation budget rapidly.

Do this quietly before the public launch. Give managers the exact talking points they need to explain these structural adjustments to affected employees. Provide scripts that focus strictly on problem scope and business impact.

Ensure executive leadership fully backs these required corrections. Without firm executive support, managers will blame your team for the changes. This undermines the integrity of the new system immediately. Managers must own the leveling decisions for their respective departments.

Publish the broad framework only when the internal mapping aligns with the written descriptions. Show every employee the levels and what each stage requires. Show them the progression criteria.

Keep individual placements private between a person and their manager. You gain the operational benefit of transparency without subjecting employees to a week of public comparison.

Once launched, leave the core architecture alone for two years. Do not tweak it every quarter to accommodate special requests. Architectures that get revised constantly teach employees that levels are merely suggestions. They become political tools rather than objective measures.

Next steps for the current quarter

Practical implementation starts immediately. Do not wait for the next annual budget cycle to begin this work.

Step 1. Extract your current employee census from your employee data systems. Ensure you have current compensation and title data for every active worker.

Step 2. Group every active role into a maximum of ten job families based strictly on the type of work performed. Ignore the current reporting structure entirely.

Step 3. Draft five levels for individual contributors and four levels for managers. Base these descriptions solely on problem scope and required autonomy.

Step 4. Map your current workforce against this draft framework in a restricted spreadsheet. Work directly with department heads to validate the daily reality of each role.

Step 5. Identify employees who fall outside logical level placements. Schedule private correction meetings with their managers to determine the resolution path.

Step 6. Finalize the internal mapping before communicating the broad framework to the company. Train managers on how to discuss level expectations during regular performance conversations.