Pay transparency meets AI-driven work

How can organisations define job requirements transparently when AI is changing the work itself? A practical perspective on pay transparency, skills and living role architecture.

2026-09-09 · Janne Ruohisto

Your job title may be the same as it was a year ago. The job is not.

A year ago, you knew what your work looked like. Which tools you used. Which processes you followed. What was expected of you.

Then AI arrived at work. And one thing became clear: things were going to change.

Only recently, you may have produced the analyses, content or client materials yourself. Now you direct AI, evaluate its suggestions, verify the output and take responsibility for quality.

Your title may be the same, but the skills, responsibility, problem-solving and even decision-making involved in the work may already have changed.

These are not simply the same jobs with new tools. Increasingly, they are new jobs with old titles.

Is that change visible in the job description?

And do we know what people need to learn next?

These questions are becoming particularly urgent across Europe.

Pay transparency starts with understanding the work

The EU Pay Transparency Directive aims to strengthen equal pay for equal work or work of equal value. Member States were required to transpose the Directive into national law by 7 June 2026, although implementation now varies across Europe.

Pay transparency is not only about salary ranges and pay-gap reporting.

Employers also need objective, gender-neutral ways to assess equal work and work of equal value. The Directive identifies criteria including skills, effort, responsibility and working conditions.

In March 2026, the European Commission and the European Institute for Gender Equality, EIGE, launched updated EU-wide guidance on gender-neutral job evaluation and classification to help organisations put this principle into practice.

This leads to a fundamental question:

Before we can meaningfully compare pay, we need to be able to compare work.

A job title alone does not tell us enough.

Two people with different titles may perform work of equal value. Two people with the same title may in practice carry very different responsibilities or solve very different problems.

Organisations therefore need a shared and transparent way to describe what work actually requires.

And AI is making those requirements increasingly dynamic.

Europe is asking organisations to become more systematic about defining job requirements at the same time as AI is making those requirements more dynamic.

Job requirements and employee skills are not the same thing

There is an important distinction to make.

When evaluating a job, we ask: What does this work require?

When looking at an individual, we ask: What can this person do today, and where do they want or need to develop?

The two are connected, but they are not the same question.

If a role starts to require new AI capabilities, an organisation can examine whether those capabilities already exist, where they need to be developed and which people might be interested in growing into new or changing roles.

But the purpose of the assessment needs to remain clear.

In a skills assessment, people should be able to identify gaps in their capabilities openly. When the purpose is learning and development, trust in how that information will be used matters.

A useful architecture therefore keeps three perspectives distinct:

• What does the job require?
• What can the person do, and where do they want to grow?
• What transparent criteria does the organisation use for pay?

They are related. They do not need to become one score.

From static job descriptions to living role architecture

In the middle of rapid change, a one-off project in which every job description is documented in great detail and then locked into a system is unlikely to be sustainable.

What organisations need instead is living role architecture: a shared framework for describing roles and keeping their requirements up to date as work changes.

The requirements still need to be clear and jointly understood. But organisations also need to decide:

• Who notices that the work has changed?
• Who assesses whether the change is significant?
• Who approves an updated description?
• Where does the current information live so that it can also support skills development?

This connects directly with what Skillhive already enables.

Organisations can maintain roles and job structures, connect them with required skills and define the required proficiency levels for those skills. An individual's current skills and their interest in developing further can remain a separate view.

This makes it possible to see both: What does the work require? and What can our people do, and where do they want to grow next?

If your organisation has already documented skill requirements for different roles, you may not need to start from scratch. A useful first step can be to review what you already have together with the people actually doing the work.

Skills, however, are only one dimension of job requirements.

Responsibility, impact, independence, problem-solving and working conditions also matter. We are currently exploring how these broader job requirements can be connected to a flexible role and skills architecture without creating another heavy HR system.

One thing is clear to us: managing skills, roles and changing job requirements is not simply a payroll question.

Payroll, statutory reporting and pay administration belong in systems designed for those purposes.

But roles, job requirements, skills, development and how they change over time belong naturally within skills management and organisational development.

A recent example from Finland

Finland offers one concrete example of how this European discussion is becoming operational.

On 3 September 2026, the Finnish Ministry of Social Affairs and Health published a voluntary gender-neutral job evaluation model. It assesses work through six dimensions: skills, responsibility and impact, interaction, problem-solving and independence, psychosocial workload and working conditions, and physical workload and working conditions.

National implementation will differ across Europe, but the underlying challenge is shared: How do we create sufficiently consistent and transparent job structures without turning changing work into static HR bureaucracy?

Start with one job family

You do not need to redesign the whole organisation at once.

Choose one job family that is already changing rapidly and ask:

• What does this work actually involve today?
• What has changed during the last 12 months?
• Are those changes visible in the current job descriptions?
• What skills does the work require now?
• How will we keep these requirements up to date?

Reviewing even a handful of jobs can reveal how well your current structures are keeping pace with the work itself.

Pay transparency makes this an urgent question today. AI-driven change makes it an ongoing one.

Would you like to examine one job family in your organisation? We can look together at what you already have in place and identify the most useful next step.

This article reflects the situation as of 9 September 2026. Implementation of the EU Pay Transparency Directive varies across Member States, and national requirements may continue to evolve. This article is not legal advice.

Sources

• Directive (EU) 2023/970 – Directive on strengthening the application of the principle of equal pay for equal work or work of equal value through pay transparency and enforcement mechanisms.
• European Commission & EIGE, 26 March 2026 – EU-wide guidelines on gender-neutral job evaluation and classification.
• Finnish Ministry of Social Affairs and Health, 3 September 2026 – Gender-neutral job evaluation model to support organisations in assessing equal work and work of equal value.