In brief
- An HR service delivery model decides where HR work sits and who owns it. A system decides how that work moves and how it feels to the people on the other end.
- A model can organize the work. Only a system can create a consistent experience.
- Most companies fix the model or buy new technology and never design the system in between.
When most leaders hear “HR service delivery,” they picture one of two things. An org chart with business partners, specialists and a shared services team. Or a piece of software.
Both are part of it. Neither one is what your people actually experience. That’s the part most companies never design, and it’s the part that decides whether HR feels like a help or a hurdle.
And every company already has that experience, whether anyone designed it or not. I explain what fills the gap in HR Already Has a System. Nobody Designed It.
Here’s how the model and the system compare.
A: The model
What it is: where HR work sits and who owns it. Business partners working with leaders, specialists in centers of expertise, a shared services team for transactions, local HR at each site. Centralized or decentralized.
What it answers: who does what?
What it’s good for: fixing structure. If work is duplicated across teams, nobody knows who owns what, or strategic work is stuck in transactional roles, the model is the place to look.
Signs your problem is the model:
- Work is duplicated across teams or locations.
- Nobody is sure who owns what.
- Business partners, specialists, shared services and local HR step on each other.
- Strategic work is stuck in transactional roles.
- Leaders keep debating centralized vs. decentralized.
- The structure can’t support the size or complexity of the business.
What it can’t do: create the experience. Two companies can draw the exact same org chart and deliver completely different HR. The model tells you where the work lives. It says nothing about how it feels when it reaches someone.
B: The system
What it is: how HR work actually moves, gets delivered and is experienced. The steps, the handoffs, the channels, the service standards, the tone and how you know it’s working.
What it answers: what is it like to get help from HR here?
What it’s good for: making the experience consistent, no matter who in HR is answering, which location someone works at or how they reach out.
Signs your problem is the system:
- Employees get different answers depending on who they ask.
- Managers don’t know how or where to get help from HR.
- HR is reacting instead of following a consistent way of working.
- Requests get lost, bounced around or handed off poorly.
- Service varies by HR person, location or business unit.
- New technology went in, but the experience still feels fragmented.
- There are no service standards, no clear channels and no measures of how HR is doing.
- The structure looks fine on paper, but delivery still doesn’t work.
And the technology
There’s a third layer worth naming, because it’s the one most often mistaken for the whole thing: the technology. The HRIS, the ATS, the portal.
Technology supports the system. It doesn’t replace it. Technology automates whatever process you already have. If nobody designed that process, the software just makes it faster. I walk through all three layers in Why It’s Time to Rethink How Your Company Delivers HR.
Side by side
| Model | System |
|---|
| The question it answers | Who does the work? | How does the work reach people? |
| What changing it looks like | A reorganization | Redesigning how requests, answers and processes flow |
| What people notice | New names and new reporting lines | Whether they get a clear, consistent answer |
| When it’s the fix | The work is in the wrong places | The work is in the right places but still doesn’t land |
If both lists sound familiar
You may need both. A new model won’t fix inconsistent delivery if you haven’t designed the system underneath it. And a great system can only go so far if the work is sitting in the wrong places.
The mistake is fixing one when the problem is the other. Don’t redesign the org chart when the real problem is delivery. And don’t redesign delivery when the real problem is structure.
The verdict
A model can organize HR. Only a system can create a great experience, because the system is the part people actually touch.
That matters beyond HR. Employees who can’t get a straight answer from HR carry that frustration into their work, and eventually to your customers. How HR is delivered shapes how people experience the company, and how they treat the people they serve.
That’s what HRX™, the HR experience, is built to do. It’s a system, not a model: a designed way of delivering HR that carries your company’s culture into every interaction. It works with whatever model you already have. And it starts with knowing who your company is.
Questions worth asking
- When HR isn’t working, has your company reached for a reorganization, new software or a redesign of how the work flows?
- Do employees get the same answer no matter who in HR they ask?
- If you changed your HR structure in the last few years, did the experience actually change?
Read next: Why It’s Time to Rethink How Your Company Delivers HR
Frequently asked questions
What is an HR service delivery model?
It’s how HR work is organized: where it sits and who owns it. Common pieces include HR business partners, centers of expertise, shared services and local HR.
What is the difference between an HR service delivery model and a system?
The model decides who does the work. The system decides how the work moves and how it feels to the people receiving it. You can change one without changing the other.
Is HR software the same as an HR service delivery system?
No. Software supports the system by automating its steps. If the system was never designed, the software automates an inconsistent process.
Do we need to change our HR structure to improve the employee experience?
Not always. If the work is in the right places but people still get inconsistent answers, the problem is the system, and you can redesign it inside the structure you have.
