Job Architecture Is the Anchor to Conquer That Mountain of Data

If you’ve ever watched someone climb the sheer rock face of a mountain, there’s a moment when you wonder how in the world they trust their safety to an anchor wedged into the rock.

The climber may have great conditioning, years of experience, a carefully planned route and plenty of data about the mountain. But when things get difficult, the entire system depends on something solid connecting it all together.

Organizations have the same challenge.

HR professionals have more workforce data than ever, covering compensation, payroll, performance, recruiting, benefits, engagement, turnover, learning, finance, workplace planning and more. And now, artificial intelligence (AI) is promising to find insights across all of it.

There’s just one little problem. Most of that data doesn’t naturally connect. That’s precisely where job architecture becomes the anchor.

The Big Picture

Job architecture can sound like one of those HR projects that involves a bunch of spreadsheets, job descriptions and meetings, debating whether someone is a Level 3 or a Level 4. And, yes, there can be some of that — but that misses the bigger picture (and opportunity).

At its best, job architecture creates a common language for understanding work across the organization. It connects jobs to families, functions, levels, career paths, skills and (ultimately) people. That common structure provides something incredibly valuable: a consistent way to connect data that was created in very different parts of the business.

Think about a software developer:

Recruiting likely sees that job through candidate supply, time to fill and starting salaries.
Compensation sees market position, range penetration and internal equity.
Learning sees skills and development.
Finance sees labor cost.
Talent management sees performance and succession.
Payroll sees what employees with that title are actually paid.

They’re all looking at the same worker/workforce through different lenses.

Without a shared architecture, connecting those views can become a heroic exercise in spreadsheets, matching tables and crossed fingers. With job architecture, you and others in these functions can begin telling one story.

Facilitating Answers to Common Questions

Now imagine the business asks a seemingly simple question: “Where are we at greatest risk of losing critical talent?” Turnover data alone won’t answer it. Neither will compensation data. But if you connect turnover with job family, level, market position, critical skills, tenure, recruiting difficulty and internal mobility, you suddenly have something much more useful. You’re not simply counting who left. You’re beginning to understand where risk exists and what might be driving it.

Or, consider workforce planning. The chief financial officer may ask what happens if the organization needs to reduce labor costs by 5%. Looking only at payroll gives you numbers. Connecting payroll to job architecture gives you context:

What capabilities are growing?
What roles are difficult to replace?
Where do we have overlapping work?
What jobs contain scarce skills?
Where could technology create leverage?

It’s the same payroll data but a completely different conversation.

Even More Important in the AI Age

All of this becomes even more important as organizations adopt AI.

AI “loves” data. But dumping more disconnected data into increasingly sophisticated technology doesn’t magically create insight. One system may call someone a senior analyst while another calls them an analyst III, another groups them under finance and another under corporate services. Technology still needs a way to understand how those things relate. And, this is before you start to delve into some items or terms that may seem so simple (e.g., location). For the same developer working remotely, they may have, for instance, a different location in different systems (e.g., recruitment, payroll, talent management, benefits); one human in four locations isn’t odd.

Comfort in Connection

Job architecture provides the anchor so everyone can scale the same proverbial mountain along the most efficient and productive route.

It doesn’t need to be perfect. This is where organizations sometimes make the climb harder than it needs to be. They decide they need to redesign every job, rewrite every description and resolve every historical inconsistency before they can move forward. You don’t.

Climbers don’t place one giant anchor at the bottom of the mountain and hope it gets them to the summit. They establish secure points along the route and keep moving. Start with enough structure to connect the most important things — job families, levels, core roles, skills where they matter. Then, improve it as the organization evolves. The goal isn’t a beautiful job architecture sitting inside HR. The goal is better decisions. It’s being able to connect:

What you pay;
What skills you have;
What skills you need;
Where people are leaving;
Where you’re hiring;
What work costs; and,
Where you should invest next.

There always will be new systems, datasets and technologies promising to help you scale your challenges faster. (This is fine; use them.)

But before you head up that next mountain, make sure your connection is present and solid. Your job architecture is the anchor.

Editor’s Note: Additional Content

For more information and resources related to this article, see the pages below, which offer quick access to all WorldatWork content on these topics: