apply-hay-job-evaluation

name	apply-hay-job-evaluation
description	Use when comparing very differently-titled roles for compensation banding, leveling, or organizational design — score each role's inherent Know-How (knowledge, skills, experience required), Problem Solving (complexity and freedom of thinking, scored as a percentage of Know-How), and Accountability (freedom to act and magnitude of impact), because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.
source	Edward N. Hay, "Hay Guide Chart-Profile Method", developed at Hay Associates (1950s), now maintained by Korn Ferry Hay Group
tags	["hr","compensation","job-evaluation","organizational-design","job-leveling"]
related	["apply-merit-selection","apply-peter-principle-check","design-compensation-structure"]

Apply Hay Job Evaluation

Score a role's inherent Know-How, Problem Solving, and Accountability requirements — not the person currently performing it — to compare very differently-titled roles for compensation banding or organizational leveling on a consistent, structurally-derived basis, because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.

Why This Is Best Practice

Why best: Comparing roles by title or informal seniority perception fails specifically because titles and seniority signals are not standardized across departments or functions — a "senior" title in one department may reflect substantially different actual requirements than a "senior" title in another. The Hay method's specific contribution is decomposing a role into three structurally distinct factors that can each be scored against a common guide chart regardless of the role's title or department: Know-How (the depth and breadth of knowledge, skill, and experience the role inherently requires), Problem Solving (the complexity and freedom of thinking the role demands, expressed specifically as a percentage of the role's Know-How, since problem-solving complexity is bounded by the knowledge base it draws on), and Accountability (the freedom to act and the magnitude of impact the role is responsible for). Scoring these three factors independently of title produces a composite score that can be meaningfully compared across very different roles.

Edward N. Hay, "Hay Guide Chart-Profile Method" (1950s): Hay developed the three-factor evaluation framework and a structured guide chart with defined levels for scoring each factor, explicitly designed to evaluate the role itself — its inherent requirements — independent of the specific person currently occupying it. The method's Problem Solving factor is deliberately scored as a percentage modifier applied to Know-How rather than as an independent score, formalizing the observation that a role cannot demand problem-solving complexity beyond what its underlying knowledge base can support.

Adopted by: The Hay Guide Chart-Profile Method, now maintained and licensed by Korn Ferry following its acquisition of Hay Group, is one of the most widely used job-evaluation methodologies globally, used extensively by large multinational organizations, including a substantial share of Fortune 500 companies, for compensation benchmarking and organizational leveling. Impact: The method's decades-long, large-scale, cross-industry adoption for compensation benchmarking reflects its practical value in enabling consistent comparison of very differently-titled roles across departments and business units — a comparison problem that informal, title-based approaches cannot reliably solve, since job titles are not standardized in their actual meaning across organizations or even across departments within the same organization.

Steps

1. Evaluate the role's Know-How requirement independent of who currently holds it. Assess the depth and breadth of technical or specialized knowledge, managerial skill, and interpersonal skill the role inherently requires, using the structured guide chart's defined levels rather than an informal judgment.

2. Evaluate the role's Problem-Solving requirement as a percentage modifier of its Know-How score, not independently. The role's thinking complexity and freedom to approach problems originally is bounded by the knowledge base it draws on — a role cannot be scored as demanding harder problem-solving than its Know-How level can support.

3. Evaluate the role's Accountability — its freedom to act and the magnitude of what it's responsible for (budget, team size, business impact) and how directly its actions influence that magnitude. Score this using the guide chart's defined accountability levels, again independent of the current occupant's personal track record.

4. Combine the three factor scores into a composite point total using the guide chart's standard method, producing a score that positions the role on a common scale usable across departments and functions.

5. Use the resulting scores to compare roles across different functions and levels on a structurally consistent basis, rather than relying on job titles or informal seniority perceptions. Two roles with very different titles and day-to-day work can land at a similar composite score, indicating comparable actual requirements.

6. Recalibrate role evaluations periodically, since actual requirements can shift over time even without a formal title change. A role that has genuinely accumulated broader Know-How, Problem-Solving, or Accountability requirements should be re-evaluated and re-leveled to reflect that shift.

Rules

• Evaluate the role's inherent requirements, never the specific person currently performing it — an unusually capable incumbent doesn't make the role itself more valuable unless its actual requirements have changed.
• Score Problem Solving strictly as a percentage of Know-How, never as an independent factor — problem-solving complexity is bounded by the knowledge base the role actually draws on.
• Apply the same structured guide chart and defined levels consistently across every role being compared, so cross-functional comparisons are actually meaningful.
• Recalibrate role evaluations periodically rather than treating an initial evaluation as permanent, since actual role requirements evolve over time independent of title changes.

Examples

Cross-functional compensation banding: An organization evaluates a technical specialist role and a people-management role — very different day-to-day work, very different titles — using the three-factor method, and finds their combined Know-How, Problem-Solving, and Accountability scores land in a similar range, justifying comparable compensation bands despite the titles suggesting otherwise.

Avoiding title inflation without substance: A department proposes a title upgrade for a role with no actual change in its underlying knowledge, problem-solving, or accountability requirements. Applying the method, evaluators find no change in the role's factor scores and decline to adjust its compensation band, since a title change alone doesn't reflect a genuine change in the role's substantive requirements.

Periodic recalibration: A role that historically involved narrow technical execution has, over several years, accumulated substantially broader cross-functional accountability without any formal title change. A scheduled re-evaluation using the guide chart identifies this shift and re-levels the role's compensation band accordingly, rather than leaving it under an outdated assessment.

Common Mistakes

• Evaluating the person currently in the role rather than the role's inherent requirements, inflating a role's assessed level because its current occupant happens to be unusually capable.
• Scoring Problem Solving independently of Know-How, rather than as a bounded percentage modifier reflecting that problem-solving complexity is limited by the knowledge base it draws on.
• Using inconsistent, informal criteria across different departments instead of the same structured guide chart, producing scores that aren't actually comparable across the organization.
• Treating an initial role evaluation as permanent and never recalibrating as a role's actual requirements evolve over time, leaving compensation and leveling decisions based on outdated assessments.

When NOT to Use

• For organizations too small to need formal cross-functional role comparison or compensation banding — the overhead of a structured three-factor evaluation system isn't justified at very small scale.
• As a tool for evaluating an individual's performance rather than a role's structural requirements — this method evaluates job content, not how well a specific person is currently performing in it.
• When an existing, functioning job-leveling system already provides adequate cross-functional comparability — introducing a new formal evaluation system carries real switching costs that should be weighed against the actual comparability gap it would solve.