HR articles

HR Process Improvement: How to Map, Simplify and Fix an HR Process Before You Automate It

2026-10-18 12:51
SHORT ANSWER

HR process improvement means making an HR process faster, simpler and more reliable before you touch any software. Map how the work really happens, record working time and waiting time for each step, and remove steps and approvals that produce no output. Then give the process one owner, set service times, measure two or three metrics before and after, and only then automate the cleaned-up version.

Course on this topic: Business Process Improvement Course: BPMN Training

Most HR processes were never designed. They grew: a form here, one more approval there. Then the company buys a system and gets the same mess, only faster.

This guide is about the step before software: how to see what really happens in an HR process, find where time is lost, remove what is not needed, give the process an owner and measure it. To check one of your processes right now, use the free HR process health check.

What is HR process improvement?

HR process improvement is the work of making an HR process — hiring, onboarding, leave, transfers, offboarding, employee records — faster, simpler and more reliable. In my course a described process answers six questions: what work is done, where, when, why, how, and who is responsible for it.

It is not the same as automation. Automation moves steps into a system. Improvement decides which steps should exist at all. I covered what to automate and how to count the payback in HR Automation: What to Automate First. Here we deal with the process itself.

Which HR process should you improve first?

Take on everything at once and you get bogged down. The order I use:
  1. Main — hiring, onboarding.
  2. Supporting — records, leave, documents.
  3. Management — planning, reporting.
  4. Improvement — how you change everything else.
Within that order, start where the problem is visible. Before you map anything, describe the problem in five questions: who is affected, which service it concerns, where it happens, when it was noticed and how big it is. “Hiring is slow” is not a problem statement. “Hiring managers wait a month for a recruiter to start on a request” is.

How to map an HR process

  1. Watch a real case from start to finish. Sit next to the person doing it.
  2. Split it into 7–12 main steps at one level of detail. Each step is a black box: something comes in, something goes out.
  3. Name steps as actions: not “Contract” or “To sign a contract”, but “Signing the contract”.
  4. Describe it as it is, from the point of view of the person responsible for the whole process, plus what you plan to change in the next 1–3 months.
  5. Draw roles as lanes. A cross-functional, or swimlane, map shows who does each step — and every arrow that crosses a lane is a handoff where things get lost.
  6. Write two times for every step: how long people actually work on it, and how long the case waits before the next step. This is the core of a value stream map.
Most problems sit at the boundaries between departments and roles. Where it is unclear who passes what to whom, and when, a SIPOC table — suppliers, inputs, process, outputs, customers — helps. Use it only where handoffs are messy: it takes a lot of agreement work.
FROM MY PRACTICE · STARLIGHTMEDIA (STB)

At STB I described and optimized different processes. I described recruiting and onboarding, but HR records administration also needed improving. I was not the owner of that process — I was the head of the department. The head of the records team did not have the skills to describe processes, so we brought in the business optimization department and its optimization manager.

She started by simply coming into the records office, sitting next to an employee and watching a typical working day, writing down what happened from beginning to end. She noticed that the employee was standing in a queue and was not prepared.

Then we removed unnecessary steps. For example, a standard personnel form was filled in by hand, although the law did not require it — only the autobiography had to be handwritten, for handwriting examination; the other documents could be printed. We simplified it, because all that data was being printed anyway.

Optimization starts not with a description but with watching the real work on site. That is where you see the queues, the lack of preparation and the manual steps you can remove.

— Mike Pritula

How to find bottlenecks and unnecessary steps

Lean calls losses muda. The categories come from manufacturing, but each has an office version. The ones I see most in HR:
  • Waiting — for an approval, for information from another person, for a correction from the previous step.
  • Transportation — moving paperwork, passing the same information again and again, extra approval steps, copies to people who do not need them.
  • Redundant processing — inspections and approvals instead of a process that prevents errors, the same data typed into several systems, reports nobody reads.
  • Defects — data entry errors and cases passed down the chain only to come back for correction.
  • Inventory — requests piling up in an inbox.
Then test every step. Put it into one of four categories: it adds value for the client of the process; it is not needed by the client but adds value for the company; it adds no value; it causes harm. The fastest test is to look at the step’s output. If a step produces no output, remove it. Sometimes the output exists and was simply forgotten — then add it to the map.

One more red flag: if your honest map shows department heads or top managers among the people doing the steps, you have excessive control.
FROM MY PRACTICE · STARLIGHTMEDIA (STB)

Many hiring managers complained that we took too long to find candidates. When we started analyzing the vacancies, it turned out that some of them had been in work for a week or two.

I asked: “Why do you think we are slow if we have only been working on it for a week?” They answered: “But we submitted the request a month ago.”

We found out that the request had been submitted, but some manager had not logged into the system and approved it. Because of one manager the situation became tense: the hiring manager thought the request was submitted, and the recruiter never received it. And we started fixing this.

Time is often lost before the work even begins — in an approval nobody sees. Make the status of every request visible.

— Mike Pritula
FREE TOOL · HR PROCESS HEALTH CHECK

What to fix first in your HR process

Describe one process as it runs today. You get its maturity level from 0 to 5, how much of the cycle time is waiting, what to remove first and whether it is ready for automation. Cycle time is counted at 8 working hours a day. The example numbers are made up — replace them with yours.

Fill in the fields above to see the result.

The full method — process maps, value stream mapping, waste analysis, the improvement project and the tools to run it — is in the Business Process Improvement Course: BPMN Training.

How to set SLAs for HR processes

Once you know where time is lost, agree how long each stage should take. In the recruiting standards I show in the course, every job level has a standard in days for each stage. For mass recruitment: 0 days of internal competition, 15 of passive search, 7 of active search, no agency, 7 for selection and approval and 14 waiting for the start — six weeks in total. Senior roles get longer standards. A single total hides where the delay is; stage standards show whether you lose time in search or in approval.

Put obligations on both sides. At STB managers often knew in advance that they would need someone — a resignation they knew about, a role planned for the future — but told recruiting nothing, and then came saying they needed a person yesterday. So I wrote down how far in advance of the desired start date a request had to be submitted, introduced it to all managers and kept reminding them. Over time managers started coming in advance.

Who owns an HR process?

A process without an owner lives only in documents. The process owner is not the author of the diagram and not the keeper of the regulation. It is the person accountable for the result of the whole process, who decides on changes and priorities and settles conflicts where roles and functions meet. Every process has exactly one owner. The owner tracks the metrics and starts improvements — but does not draw diagrams or remind everyone to follow the process.

A typical mistake is making HR the owner “because it is an HR process” or IT “because it runs in a system”. HR should own a process where it really controls its logic, metrics and changes — not just its paperwork.

Inside the process, map responsibility with RACI built on steps and roles, not names: people change, roles stay. In the recruiting example from the course, the hiring manager is accountable for starting the request and for the decision on the candidate, the recruiter is responsible for most steps, and finance is accountable for the financial approval of the offer. One A per step, as many R as needed. A ready template is in RACI Template & Guide.

Then review the process on a schedule. In my course: critical processes every 3–6 months, supporting processes once a year, regulatory processes every time the requirements change. Keep versions: v1.0 is the first working version, v1.1 and v1.2 are small changes without new logic, v2.0 means new steps, roles or metrics. At iDeals the recruiting process we described with the team reached its seventh version: we tested and changed it, and as we hired a sourcer and then an assessment manager, sourcing and competency-profile steps appeared.

HR process metrics: what to measure

Separate two kinds of indicators:
  • Effectiveness — results in absolute values: how long a client of the process waits for the result, how satisfied they are.
  • Efficiency — the result divided by the resources spent on it: Efficiency = Result ÷ Costs.
For most HR processes start with cycle time — the total time from request to result — and split it into working time and waiting time from your map. Add one quality measure, such as the share of cases returned for correction. Two or three indicators that balance each other are enough: speed alone pushes people to cut corners, quality alone lets cycle time grow. For each, decide why you need it, who will use it and what decision it will drive.

How to improve an HR process step by step

  1. Measure the process indicators before the change.
  2. Set a clear goal for the improvement.
  3. Form hypotheses about the causes of the problem and test them.
  4. Propose solutions.
  5. Try the options in practice.
  6. Measure the indicators after the trial.
  7. If the hypothesis is confirmed and the results are clearly better, roll the change out across the business.
Avoid the revolution — designing the ideal model and implementing it all at once. It takes long and meets the most resistance. Change in versions: design with everyone affected, test in a pilot area, prove with numbers that it is better, then roll it out.

Simplify first, then automate

Automation strengthens the current logic of a process, good or bad. If the process is broken, automation makes it broken faster and more expensive.

A process is not ready for automation when it keeps changing, has no owner, has no clear metrics, is done differently by different people or exists only in people’s heads. My rule: if a process cannot be done the same way twice in a row, it is too early to automate it. Then ask: which metric should automation improve?

When to kill an HR process instead of improving it

A process is dead when it exists only in documents, nobody looks at its metrics and people go around it.

The honest test: what happens if you switch the process off for 30 days? Will the business or the client notice? If not, close it. The opposite rule matters too: if a process works, its metrics hit their targets and it is not a bottleneck, do not break it without a reason.

Five mistakes in HR process improvement

  1. Mapping from documents. Watch a real case instead.
  2. Answering every error with one more approval instead of fixing the step where the error is made.
  3. No owner, or an owner chosen by department name rather than by who decides.
  4. Changing without a baseline. Without the “before” numbers, you cannot prove the “after”.
  5. Automating first. A system will not fix a process; it only makes its problems visible.
How to map processes, find and remove waste, run an improvement project with the right tools and build a culture where processes keep getting better is what my Business Process Improvement Course: BPMN Training covers in eight lessons.
FAQ

Frequently asked questions

What is HR process improvement?

It is the work of making an HR process — hiring, onboarding, leave, offboarding, records — faster, simpler and more reliable. You map how the process really runs, remove steps that add no value, fix the places where cases wait or come back for correction, and measure the result before and after the change.

How do you identify bottlenecks in an HR process?

For every step record two numbers: how long people actually work on it and how long the case waits before the next step. The bottleneck is usually not the work itself but the waiting — most often for an approval or for information from another person.

Who should own an HR process?

The person accountable for the result of the whole process and able to make decisions about it. Not automatically HR because it is an HR process, and not IT because it runs in a system. Every process should have exactly one owner.

Which metrics show that an HR process is working?

Pick two or three that balance each other — for example, cycle time from request to result plus a quality measure such as the share of cases returned for correction. For each metric decide why you need it, who will use it and what decision it will drive.

Should you automate an HR process before improving it?

No. Automation speeds up whatever logic the process has, good or bad. If you cannot run the process the same way twice in a row, simplify and stabilize it first, then automate the cleaned-up version.