Ask The Analyst: If job architectures are inconsistent, what does this mean for the reliability of every people-related data point an organization has – and the decisions based on this data?

Each week for The Briefing, UNLEASH’s weekly intelligence email for senior business decision-makers, we ask the true experts – our community of analysts – to solve the biggest HR challenges.

Got a question for the analysts? You can up it directly to them via The Briefing – make sure you’re signed up.

This week’s question: If job architectures are inconsistent, what does mean for the reliability of every people-related data point an organization has – and the decisions based on this data?

Here are their perspectives.

David Green, Co-Founder and Managing Partner, Insight222

If you can't define work uniformly, you can't measure it accurately. And if you can't measure it accurately, you can't make reliable workforce decisions. Inconsistent job architectures undermine the integrity of every people-related data point.

Job architecture provides the common foundation that connects roles, levels, skills and pay across the organisation. Without that foundation, you're never comparing like with like.

The biggest risk isn't bad data. It's false confidence in data that looks credible but isn't. Leaders believe they're making evidence-based decisions, yet the underlying comparisons are fundamentally flawed. The result is costly organisational blind spots: capability is overestimated in one area while unnecessary hiring takes place in another; pay equity analyses compare different work; internal mobility stalls because adjacent roles aren't recognised as connected; and workforce plans are built on inconsistent assumptions.

As organizations redesign work and adopt skills-based talent strategies, job architecture becomes the foundation of workforce intelligence.

Get it right and people data becomes a strategic asset. Get it wrong and every dashboard, forecast and talent decision becomes a little less trustworthy.

Technology may accelerate decision-making, but it can't compensate for weak foundations. It simply exposes them faster.

Kathi Enderes, Senior Director of Research, The Josh Bersin Company

Job architecture is often treated as an HR taxonomy exercise. In reality, it allows organizations to compare roles consistently, connect talent processes, and generate reliable workforce insights.

When that foundation is inconsistent, every people metric built on top of it becomes less reliable because the underlying unit of analysis is not consistent across the organization.

This is already challenging in organizations where data remains siloed between functional HR teams.

An inconsistent job architecture magnifies both problems. Even if data is brought together, it cannot be compared with confidence because different parts of the organization are effectively describing work in different ways.

This becomes even more important as organizations continue to scale enterprise AI. AI does not resolve poor data quality: it scales it. Models trained on inconsistent job data are more likely to produce inconsistent recommendations, whether for hiring, internal mobility, workforce planning, or skills inference.

Before organizations can generate meaningful insights, they need confidence in the structure of the data itself. Job architecture provides that structure.

Without it, organizations are not simply working with incomplete information: they are making workforce decisions on foundations they cannot fully trust.

Tami Nutt, Systems, People & Workforce Strategist

Every HR data point represents a person. If job architectures are inconsistent, the issue isn't just that reports become less reliable. It's that people may be hired, paid, promoted, developed, or evaluated differently because the underlying structure doesn't accurately reflect the work they do.

That's why I think job architecture is as much a people strategy as it is a data strategy.

A consistent job architecture creates a common language for work across the organization. It helps ensure similar jobs are evaluated consistently, career paths are transparent, compensation decisions are based on comparable roles, and workforce planning reflects the work that actually needs to be done.

When that foundation is inconsistent, every people-related metric becomes less reliable because the organization is no longer comparing like with like.

Job architecture isn't just supporting HR processes. It's influencing decisions that shape an employee's experience throughout their career.

From a compliance perspective, that consistency matters. Job architecture informs decisions around exempt versus non-exempt classification, pay equity analyses, accommodations, and other employment practices that depend on accurately understanding the nature of a role.

An inconsistent foundation increases the likelihood that similar situations will be treated differently, creating both organizational risk and employee frustration.

When we talk about people analytics, we're really talking about decisions that affect people. If we can't trust the foundation, we shouldn't assume we can trust the decisions built on top of it.

That's why job architecture isn't just an HR framework. It's part of building an organization where people can trust that decisions are made consistently, fairly, and based on the work they actually do.

Anita Lettink, Managing Partner, HRtechradar

If the job architecture underneath your people data is inconsistent, the data itself might not be wrong, it's just not comparable. And using incomparable data in an analysis is worse than having no data at all, because it gives you false confidence.

Every metric that depends on grouping people by role, promotion rates, span of control, pay equity gaps and market benchmarking, inherits whatever mess sits in the architecture. You're not measuring what you think you're measuring; you're measuring title inconsistency and calling it insight.

And under the European Pay Transparency Directive this stops being an internal data-quality embarrassment and becomes an external compliance risk. The Directive's equal-value comparisons, the gender pay gap reporting, the employee's right to request pay data by category – all of it assumes the grouping is defensible and based on a solid job architecture.

If it isn't, the reported numbers become unreliable, not because the pay calculations were wrong, but because you compared the wrong people to each other in the first place. A 3% gap could really be 8%, or could disappear entirely, once roles are grouped correctly.

A bad job architecture doesn't just distort one report; it undermines every decision made on top of it. This accumulates over the years, until someone finally scrutinizes the data and it all falls apart. Fix the architecture first, because every data story you tell, and every decision you make, only holds once that foundation does.