By function: HR
Kaizen for HR and people teams
In short
Kaizen for HR teams is continuous improvement applied to people processes: hiring, onboarding, leave, contract changes and probation are made a little better each week by the people who run them, and every change is checked later to see whether it held.
In HR the customer of the work is usually a colleague: a candidate waiting for an answer, a manager waiting for a contract, an employee waiting for a letter. Below are eight frictions typical of HR work, each matched to one of the 8 wastes of Lean in office work, two rules for improving a function that handles personal information, and one friction taken through a 5 Whys to a change the team can make.
Eight recurring frictions in HR, and the waste behind each
| Friction | Waste | First question to ask |
|---|---|---|
| Finding one interview slot for a candidate and three interviewers takes a week of emails | Waiting | Who has to answer before the next step can happen, and why one at a time? |
| A leave request is approved by the manager by email, then forwarded to HR to enter | Handoffs | Could the person who decides also be the one who records it? |
| Training records are collected and entered in a rush before each audit | Backlog | What stops a record being entered the day the training ends? |
| Employees ask HR the same policy questions because the answer is hard to find | Searching and switching | Where would someone look first, and is the answer there? |
| Onboarding forms come back with a tax or bank detail missing and are returned | Errors and rework | What on the form lets it be sent incomplete? |
| A monthly headcount report is sent to managers who keep their own list anyway | Work nobody uses | What decision does this report feed, and whose? |
| A list of probation end dates is rebuilt by hand from an export every month | Extra steps | Why is this worked out again each time instead of stored once? |
| An HR partner spends Monday re-formatting absence data instead of talking to managers | Skills not used | Which part of this needs what they know about the teams? |
Several of these often show up in a single request. Label the one that, once gone, takes the others with it, and start the whys there.
Describe the process, never the person
HR frictions come with names attached: the manager who approves late, the new starter whose form was wrong. Two rules keep improvement work safe and useful in a function that handles personal information.
- Write the friction about the work. "Managers approve leave late" blames a group; "leave is approved by email and typed into the system by someone else two days later" describes something that can be changed. The lesson blame the process, not the person shows how to turn one into the other.
- Leave personal details out. A problem statement needs the step, the count and the delay. It does not need an employee's name, salary, health information or the reason for a leave, on paper or in any tool.
- Stop the chain at something the team can change: a form, a checklist, a rule, a missing owner. If the last answer is a person's character, ask why the process let it matter.
A worked 5 Whys from HR operations
The chain below starts from a symptom that reaches the employee, the late probation review, and ends at the hand-built list from the table. It ends after four whys, at a checklist. The lesson 5 Whys examples from office work teaches the method step by step.
Illustrative example, not a real company.
Problem. A probation review should be held before the probation period ends. Of the last eight probation periods, three ended before the review took place.
- Why were the reviews late? Each manager learned the end date only when HR asked for the review form, in the final week.
- Why did HR ask so late? HR sends reminders from a list of probation periods ending that month, built on the first working day. A period that ends early in the month appears with only days to spare.
- Why is the list built once a month, by hand? The end date is not held in the HR system, so someone works it out for every recent starter from the start date and the contract type in an export.
- Why is the end date not in the system? The system has a field for it. Nobody fills it in, because the checklist for creating an employee record was written before the field existed, and the checklist has no owner.
Root cause. The checklist for creating an employee record has no owner and predates the probation end date field, so the date is worked out again by hand every month.
Should this step exist? The monthly list should not exist: once the date is stored when the record is created, there is nothing to rebuild. The reminder to the manager stays, because the review itself is needed.
Countermeasure.
- The probation end date becomes a line on the record-creation checklist, and the checklist gets a named owner in HR.
- The date is filled in once for everyone currently on probation.
- The manager is reminded four weeks before the end date, from the stored date.
- The monthly export is stopped after one month in which both ran side by side.
Check. For every probation period ending in the next three months, HR notes whether the review was held before the end date, and whether anyone still needed the monthly list. The team writes its prediction first: none late.
The first answer most teams give to this problem is "managers forget". It is true and it changes nothing. Asking why the manager did not know the date leads to a checklist, which the team can change. To plan and follow a change like this one, the countermeasure plan template has a line for the owner and a log for the three checks.
Where an HR team should start
- Pick a request HR receives every week, such as a letter, a contract change or an access request, rather than a yearly cycle like the performance review. A weekly request shows within a month whether a change worked.
- Follow one real request from the moment the employee or manager asked to the moment they had what they needed. Note every inbox it sat in; the lesson on the gemba walk for office work shows what to write down.
- Count the two times apart: how long people worked on it, and how long it waited. The waiting is often the longer of the two, and it is what the employee feels.
- Ask why at the longest wait, then try one small change with one team before changing the process for everyone. Daily Kaizen explains why small and reversible beats a redesign.
Templates and lessons that fit HR work
- Countermeasure plan template: the cause, the change, its owner, and a log for the checks at day 7, 14 and 30.
- 5 Whys template: for the chain, with a second page for the cases where two causes meet.
- Standard work template: for the checklist itself, with an owner and a next review date.
- Lesson: standard work for office teams, on writing a standard a new colleague could follow.
- Lesson: lead time vs process time, on why a request that needs minutes of work takes weeks.
- Lesson: lean coaching questions, for HR partners helping a manager find a cause instead of handing over an answer.
Questions
What is an example of Kaizen in HR?
Storing the probation end date when an employee record is created, so that the manager is reminded four weeks ahead and nobody rebuilds a list of dates by hand each month. One line on a checklist changes, and the review no longer depends on a list someone has to remember to build.
What is Lean HR?
Lean HR applies Lean thinking to people processes: see each process from the side of the employee or manager it serves, remove the steps that add nothing for them, and improve in small, checked changes. Kaizen is the part of Lean about those small changes.
Which HR process should we improve first?
One that repeats every week and that employees wait for. It gives quick feedback on a change, and the people affected can say whether it got better.
Try it on your own work
Pick one task that wastes your team's time every week. Describe it in a sentence; KaizenProof names the waste, asks why until you reach the cause, and writes the fix. No account is needed to start.