A considered perspective on people and performance

Key takeaways

  • Define comparable work and relevant factors before comparing pay.
  • Investigate unexplained differences without assuming every difference has the same cause.
  • Document methodology, limitations and follow-through actions.

A salary comparison can reveal a difference, but it rarely explains the difference. Meaningful pay-equity analysis begins by asking whether work is comparable, how roles are valued, which factors influence pay and whether those factors are applied consistently. The objective is not to make every salary identical. It is to identify unjustified differences, understand their causes and establish a defensible process for correction and prevention.

Define the question precisely

Separate equal pay for the same or similar work from equal remuneration for work of equal value. The latter requires a method for comparing jobs that may differ in tasks but contribute comparable value. The International Labour Organization’s guidance on gender-neutral job evaluation explains why objective evaluation is essential to identifying and addressing pay discrimination: https://researchrepository.ilo.org/esploro/outputs/encyclopediaEntry/Promoting-equity-gender-neutral-job-evaluation-for/995219212902676.

Before analysing outcomes, define the population, pay components, comparison groups, time period and relevant employment factors. Include base salary and consider variable pay, allowances and benefits where data and the question justify it. Document exclusions and limitations. A poorly defined analysis can produce a precise number that answers the wrong question.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Build a defensible job architecture

Job titles are weak proxies for job value. Titles vary across teams and organisations, while actual scope, decision-making, knowledge, responsibility and working conditions may differ. Use consistent job descriptions and evaluation criteria to establish meaningful comparisons. Check that criteria do not systematically undervalue work associated with historically under-rewarded groups.

Review the integrity of job levels and families. If two substantially similar roles sit at different levels because of inconsistent historical decisions, statistical adjustment alone may not solve the underlying problem. Conversely, roles with the same title may legitimately differ in scope. Job evaluation creates a clearer basis for analysis, but it still requires informed judgement and review.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Analyse patterns, not just averages

Average pay gaps can be influenced by workforce composition, seniority, occupational segregation, working hours and access to progression. Adjusted analyses may help assess differences among more comparable employees, but model choices matter. A statistical adjustment can hide a problem if it controls for a factor that itself reflects unequal opportunity.

Editorial visual illustrating pay equity requires more than a salary comparison — concept 1
A useful way to frame the organisational question.

Use multiple lenses: pay by grade and job family, starting salaries, progression, variable-pay outcomes, promotion rates and access to high-value assignments. Investigate outliers and recurring patterns. Statistical analysis can flag questions; it cannot determine by itself whether a difference is lawful, justified or fair. Legal advice may be needed for jurisdiction-specific obligations.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Trace the decisions that create pay

Examine how starting offers are set, how salary increases are approved, how performance ratings affect bonuses, how roles are regraded and how exceptions are authorised. Historical salary, negotiation behaviour and manager discretion can perpetuate differences when rules are weak or inconsistently applied.

Create documented pay ranges, decision criteria and exception approvals. Train managers to explain decisions consistently and ensure that pay practices comply with applicable local law. Transparency should be designed thoughtfully: publishing a range without explaining job architecture or progression rules may not resolve employee uncertainty.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Correct and prevent

Where unjustified differences are identified, determine the appropriate response with HR, finance, leadership and legal specialists as needed. Establish a prioritised remediation plan, cost it accurately and protect employee confidentiality. Avoid promising instant resolution before the causes and scope are understood.

Prevention is as important as correction. Repeat the analysis at a defined cadence, monitor new-hire offers and pay movements, review job evaluation and assess whether employees have equitable access to development and advancement. The ILO’s 2026 guide advocates a coordinated approach involving objective job evaluation, pay transparency, policy and social dialogue: https://doi.org/10.54394/UJMT6226.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Applying the analysis in practice

A reward review should bring together HR, finance, business leaders and, where appropriate, legal or employee representatives. Establish a shared view of the current package, its recurring cost, the roles it is intended to support and the principles used to make decisions. Where data is incomplete, identify the limitation rather than presenting a benchmark as definitive.

Editorial visual illustrating pay equity requires more than a salary comparison — concept 2
Consider how the elements connect in practice.

Test the package from the employee’s perspective as well as the employer’s. Can employees explain the main elements? Do they understand eligibility and performance conditions? Can they access the benefits? Are managers applying rules consistently? These questions help separate a problem with the package itself from a problem with communication, administration or local practice.

Use scenario modelling before committing to a change. Compare the near-term cost with recurring obligations, likely workforce changes and the risk of creating new inequities. Define which outcomes should improve and what evidence would prompt a review. Reward decisions should be explainable, affordable and connected to the capabilities the organisation needs.

Separate policy intent from employee experience. A policy may be technically consistent while producing different outcomes because managers interpret it differently, information is unevenly distributed or employees have unequal access to opportunities. Review both the formal rule and its application. Where exceptions exist, examine whether they are justified, documented and reviewed rather than automatically assuming every exception is improper.

Communication should state what employees can expect and where discretion remains. Overpromising uniformity can be as damaging as opaque decision-making. Explain the principles, the process for raising a question and how decisions are reviewed. For sensitive equity work, communicate the method and aggregate progress without exposing individual compensation information or making unsupported conclusions about specific people.

Governance should identify who can approve pay exceptions, what evidence is required, how conflicts are reviewed and how patterns are monitored. Without this discipline, the reward philosophy can be bypassed one offer or one promotion at a time. The aim is not to eliminate all discretion; it is to make discretion visible, reasoned and consistent with the principles leaders have approved.

A review should also consider how reward interacts with performance management and career progression. If performance ratings are inconsistent, variable pay may amplify those inconsistencies. If progression criteria are unclear, employees may interpret pay differences as evidence of favouritism. Reward decisions are more defensible when adjacent talent processes are equally coherent.

The final review should make the rules understandable to decision-makers and employees. Document the rationale, the data used, the limits of the comparison and the next review date. This record supports consistency over time and helps leaders distinguish a deliberate exception from an undocumented precedent that has simply been repeated.

Build a defensible pay-equity review

A raw pay gap is a signal to investigate, not by itself a complete explanation of inequity. This distinction matters because organisations can become very active without becoming more effective. New programmes, policies, dashboards and training sessions may all be well intentioned, yet their combined effect depends on whether they address the actual constraint in the work. Leaders should therefore resist beginning with the intervention they already know how to purchase or deliver. Begin instead with a clearly framed decision: what must improve, for whom, over what period, and what evidence would indicate that the current approach is not working?

Editorial visual illustrating pay equity requires more than a salary comparison — concept 3
Translate the principle into a repeatable operating practice.

A useful diagnostic compares three layers. The first is the intended outcome: the customer, operational or workforce result the organisation is trying to achieve. The second is the operating mechanism: the work, decisions, capabilities, resources and relationships that are expected to produce that result. The third is the observed experience: what employees and managers actually encounter, including delays, exceptions, workarounds and competing demands. The gap between these layers is often more informative than a single performance score.

For example, imagine a service team missing response-time commitments. It would be premature to conclude that the team simply needs more people. The organisation should test whether demand is forecast accurately, cases are routed to the right capability, staff have authority to resolve common issues, knowledge is accessible, and performance measures reward resolution rather than speed alone. The example is illustrative, not a claim about a specific employer. Its purpose is to show how a symptom can have several possible causes—and why diagnosis should precede investment.

A governance and remediation sequence

Translate the diagnosis into a small number of explicit design choices. State the problem in operational language, identify the people affected, and describe the mechanism through which the proposed change is expected to work. Record the assumptions behind that mechanism. If the intervention depends on managers having time to coach, for instance, the plan must address workload and priorities; a manager-training course cannot create time that the operating model does not provide.

  1. Establish a baseline. Agree on definitions and capture the current level of performance, experience, cost, quality or risk. Note where the data is incomplete or unreliable.
  2. Identify the constraint. Use process observation, employee input, operational data and manager judgement together. Treat each source as partial evidence rather than assuming one source explains the whole system.
  3. Choose a proportionate intervention. Consider process redesign, clearer decision rights, role changes, capability development, technology, incentives or staffing. Explain why the chosen option is more plausible than alternatives.
  4. Run a bounded test where feasible. Define the population, duration, expected signal and safeguards. A pilot can reveal implementation issues, but it does not automatically prove that an intervention caused the outcome.
  5. Assign ownership and review. Name the decision owner, the people responsible for delivery, the review date and the conditions under which the organisation will adapt, scale or stop the intervention.

This discipline is not bureaucracy for its own sake. It reduces the risk of solving the wrong problem, makes trade-offs visible and helps leaders learn when conditions change. It also makes the work of HR, operations, finance and technology more coherent: each function can contribute its expertise to a shared problem statement instead of optimising its own activity in isolation.

Editorial visual illustrating pay equity requires more than a salary comparison — concept 4
Use the evidence to guide a deliberate decision.

What to measure—and what not to assume

Use a balanced set of measures. A leading indicator may show whether a necessary practice is happening; a lagging indicator shows whether the desired result is appearing. Pair operational measures with relevant employee or customer experience evidence. Check whether apparent improvement in one measure creates a cost elsewhere—for example, faster case closure accompanied by more repeat contacts, or lower turnover accompanied by declining internal mobility.

Interpret results in context. Differences between teams may reflect workload, customer mix, role complexity, local labour markets or management changes rather than the intervention being evaluated. Where possible, compare like with like, document changes that occurred during the measurement period, and avoid claiming causation from a simple before-and-after comparison. Qualitative evidence can help explain a pattern, but anecdotes should not be presented as proof of prevalence.

Legal obligations vary by jurisdiction; organisations should obtain qualified local advice before interpreting findings or deciding on remedies. Use the original source to understand its scope, methodology and limitations before applying a finding to a different organisation, geography or workforce. External research can inform a decision; it cannot replace local diagnosis. The strongest professional judgement combines credible published evidence with transparent assumptions and the organisation’s own operational facts.

The executive question is therefore not merely, “Did we deliver the programme?” It is, “Did the change improve the condition we intended to improve, for the people and business outcomes that matter, and what evidence supports that conclusion?” That question moves the discussion from activity reporting to organisational learning.

A practical action plan

  • Define the business question and the outcome that should change.
  • Gather relevant quantitative and qualitative evidence; document limitations.
  • Agree on a small number of actions, accountable owners and review dates.
  • Measure intended outcomes and unintended consequences, then adjust.

Questions for leaders

  • What business outcome is this issue affecting in our organisation?
  • What evidence would distinguish a root cause from a symptom in the current situation?
  • Which decision or practice should change first, and who owns it?
  • How will we know whether the change helped, and what unintended effects should we watch for?

The point

Pay equity cannot be established by comparing two averages and declaring the work complete. It requires a defensible method for comparing jobs, careful analysis of outcomes, scrutiny of pay-setting decisions and a repeatable governance process. The test is whether the organisation can explain its decisions, identify unjustified differences and demonstrate credible action. The practical test is whether the organisation can explain the choice it made, show how the evidence informed it and learn from what happened next.

References and further reading

The following sources inform the analysis. They provide evidence and guidance; their findings should be interpreted within their stated scope and context.

Take the conversation further.

Explore how people decisions, organisational systems and leadership practices can support performance in your context.

Discuss an organisational question ↗