flowchart LR
T["Toyota Production System:<br>Ohno, kanban cards, waste elimination"] --> L["Lean Thinking:<br>Womack and Jones,<br>five principles"] --> K["Kanban Method:<br>Anderson,<br>knowledge work"] --> H["Lean and Kanban<br>in HR"]
style T fill:#e8eaf6,stroke:#5C6BC0
style L fill:#e3f2fd,stroke:#1976D2
style K fill:#fff8e1,stroke:#F9A825
style H fill:#e8f5e9,stroke:#388E3C
6 Kanban and Lean Principles Applied to HR
ImportantLearning Objectives
You will be able to:
- Trace Kanban and lean thinking to their origins in the Toyota Production System.
- Apply the five lean principles to an HR process and identify the seven forms of waste in HR work.
- Design a Kanban system for an HR team, including board columns, work-in-progress limits, and flow metrics.
- Choose between Scrum and Kanban for a given type of HR work, or combine them deliberately.
6.1 Introduction
Chapter 5 closed with a limitation: Scrum suits goal-directed projects, but much HR work arrives as a continuous, unpredictable flow. This chapter presents the method built for exactly that condition, and the older body of thought behind it. Both trace to post-war Toyota, where Taiichi Ohno developed a production system organized around eliminating waste and producing only what the next step actually needed, signalled by physical cards called kanban (Taiichi Ohno, 1988). James P. Womack & Daniel T. Jones (1996) later distilled the system’s logic into five principles, naming it lean thinking and arguing it applied far beyond manufacturing. David J. Anderson (2010) completed the journey into knowledge work, formalizing the Kanban method as an evolutionary approach to improving any process: visualize the work, limit work in progress, and manage flow.
Lean and Kanban deserve HR’s attention for a reason beyond technique. Unlike Scrum, which asks a team to adopt new roles and events on day one, Kanban begins with the process you already have and improves it incrementally, which makes it the gentlest entry point into agile working for an HR function wary of disruption (David J. Anderson, 2010). And lean’s central question, which of our activities actually create value for the person we serve?, is the customer-centricity principle of Chapter 3 expressed as an operational discipline.
6.2 Lean Thinking
6.2.1 The Five Principles
James P. Womack & Daniel T. Jones (1996) summarize lean in five principles, each translating directly into HR terms. First, specify value from the standpoint of the end customer: what does the candidate, new hire, or manager actually value about this process, as opposed to what the process finds convenient to produce? Second, map the value stream: chart every step between request and delivery, exposing which steps create value and which merely consume time. Third, create flow: remove the queues, hand-offs, and batching that make work wait. Fourth, establish pull: let downstream demand trigger work, rather than pushing work into the system because a schedule says so. Fifth, pursue perfection: treat improvement as continuous, not as a project with an end date, the discipline Toyota calls kaizen (Taiichi Ohno, 1988).
6.2.2 Waste in HR Processes
Ohno’s system defined waste, muda, as any activity that consumes resources without creating value, and catalogued seven forms (Taiichi Ohno, 1988). The catalogue transfers to HR work with uncomfortable precision.
NoteThe Seven Wastes, Translated to HR
| Waste | Manufacturing meaning | HR equivalent |
|---|---|---|
| Overproduction | Making more than is needed | Reports nobody reads; policies covering situations that never occur |
| Waiting | Idle time between steps | Candidates awaiting feedback; requisitions awaiting signatures |
| Transportation | Unnecessary movement of material | Documents routed through approvers who add no judgment |
| Over-processing | More work than the customer values | Five interview rounds where three predict equally well |
| Inventory | Stock waiting to be used | Backlogged ER cases; unscreened CV piles; stale talent pools |
| Motion | Unnecessary movement by people | Re-keying the same data into three HR systems |
| Defects | Rework caused by errors | Payroll corrections; re-opened cases; failed probation from poor role definition |
TipPractitioner Insight: Walk the Value Stream Before You Automate It
Map a real hiring requisition, one actual case, from the moment the manager felt the need to the new hire’s first day, recording elapsed time and touch time at every step. Most teams discover that touch time, when someone is actually working on the case, is a small fraction of elapsed time; the rest is waiting. Automating a process before removing its waits digitizes the waste (Stefan Strohmeier, 2020). Remove queues first; automate second.
6.3 The Kanban Method
6.3.1 Visualize the Work
Kanban begins by making work visible on a board whose columns represent the stages of the team’s actual process, with each work item a card moving left to right. For an HR team the columns might run: requested, ready, in progress, waiting on others, done. The board is the transparency principle of Chapter 3 made physical: the true state of every case, visible to the whole team and its customers at a glance, replacing the private to-do lists in which work silently accumulates (David J. Anderson, 2010).
6.3.2 Limit Work in Progress
The method’s central discipline is the work-in-progress (WIP) limit: a maximum number of items allowed in a column at once. When the limit is reached, the team finishes something before starting anything new. The rule feels counterintuitive, refusing new work seems unhelpful, but the mathematics of flow are unforgiving: the more items in progress, the longer every item takes, because each receives a thinner slice of attention and spends longer waiting. Limiting WIP converts hidden overload into a visible signal that the system is full, forcing the prioritization conversation that unlimited to-do lists let everyone avoid (David J. Anderson, 2010).
WarningCommon Misconception: A Board Without Limits Is Kanban
Many HR teams install a three-column board, call it Kanban, and change nothing else. A board without WIP limits is a visualization, valuable, but only the method’s first step. The improvement engine is the limit: it is what creates flow, exposes bottlenecks, and forces finishing over starting. If the board never makes anyone wait before starting new work, it is decoration (David J. Anderson, 2010).
6.3.3 Manage and Measure Flow
With work visible and WIP limited, the team manages flow using a small set of metrics. Lead time is the elapsed time from request to delivery, the only duration the customer experiences. Cycle time is the time from starting work to finishing it. Throughput is the number of items completed per period. Tracked over time, these numbers replace argument with evidence: the team can see whether this month’s process change actually shortened the candidate’s wait, and can give customers reliable answers, based on measured history rather than optimism, to the question “when will my case be done?” (David J. Anderson, 2010).
flowchart LR
R["Requested"] --> RD["Ready<br>(pull when capacity)"] --> IP["In Progress<br>WIP limit: 4"] --> W["Waiting<br>on others"] --> D["Done"]
style R fill:#e3f2fd,stroke:#1976D2
style IP fill:#fff8e1,stroke:#F9A825
style W fill:#ffebee,stroke:#C62828
style D fill:#e8f5e9,stroke:#388E3C
6.3.4 Choosing Between Scrum and Kanban
The choice follows the work. Scrum batches work into time-boxed goals and suits projects; Kanban manages continuous flow and suits services. Most HR functions contain both kinds of work, and mature teams run both systems side by side, or blend them, sprints for the redesign project, a WIP-limited board for the daily case load (Natal Dank & Riina Hellström, 2020).
NoteScrum and Kanban Compared for HR Work
| Dimension | Scrum | Kanban |
|---|---|---|
| Cadence | Fixed time-boxed sprints | Continuous flow, no required iterations |
| Commitment | Sprint goal selected in planning | Pull next item when capacity allows |
| Roles | Product owner, scrum master, team | No required roles; existing roles kept |
| Change philosophy | Adopt the framework, then improve | Start where you are, evolve incrementally (David J. Anderson, 2010) |
| Best HR fit | Design projects: onboarding redesign, new appraisal build | Services: ER cases, hiring pipeline, query handling |
| Key metric | Sprint goal achieved; velocity | Lead time, cycle time, throughput |
6.4 Case Studies
6.4.1 Case Study 1: Toyota, The System Behind the Cards
Toyota’s production system paired the kanban card, a signal authorizing the upstream step to produce exactly what the downstream step had consumed, with a deeper people practice: any worker could stop the line on detecting a defect, and every worker was expected to propose improvements through kaizen (Taiichi Ohno, 1988). The cards are the famous artifact, but the system’s power lay in respect for the person doing the work: those closest to the process were trusted to see its problems and empowered to fix them. HR functions adopting Kanban inherit both halves of this legacy, the flow mechanics and the improvement culture, and the second is harder to copy than the first.
Discussion Questions:
- Why does a pull system require more trust in frontline workers than a push system?
- What is the HR equivalent of “stopping the line,” and what psychological safety conditions from Chapter 3 does it require?
- Which half of Toyota’s legacy, the mechanics or the culture, explains more of its performance, and why?
6.4.2 Case Study 2: A Talent Acquisition Team Adopts Kanban
A technology company’s twelve-person talent acquisition team, drowning in sixty simultaneously “active” requisitions, mapped its hiring value stream and found average lead time of 74 days, of which candidates spent 51 waiting, mostly for interview feedback and approvals. The team built a board mirroring its real stages, set a WIP limit of four active requisitions per recruiter, introduced a 48-hour explicit policy for interview feedback, and reviewed flow metrics weekly. Within two quarters, median lead time fell below 40 days and candidate-experience scores rose sharply, not because anyone worked faster, but because work stopped waiting.
Discussion Questions:
- Why did limiting each recruiter to four active requisitions speed hiring up rather than slow it down?
- Which of the seven wastes did the 48-hour feedback policy attack?
- What resistance would you expect from hiring managers when WIP limits delay opening their requisition, and how would you handle it?
6.5 Summary
NoteChapter Summary
Lean thinking distils the Toyota Production System into five principles, value, value stream, flow, pull, perfection, and defines waste as any activity consuming resources without creating value for the customer (Taiichi Ohno, 1988; James P. Womack & Daniel T. Jones, 1996). Applied to HR, the seven wastes expose the queues, rework, and over-processing hidden inside people processes. The Kanban method operationalizes lean for knowledge work: visualize the process on a board, limit work in progress so that flow replaces overload, and manage the system with lead time, cycle time, and throughput (David J. Anderson, 2010). Kanban’s evolutionary philosophy, start where you are, makes it HR’s gentlest entry into agile working, and its natural domain is continuous-flow service work, complementing Scrum’s fit for projects (Natal Dank & Riina Hellström, 2020). With the foundations and frameworks of Part I complete, Part II applies them function by function, beginning with recruitment.
TipKey Terms
Lean thinking · Toyota Production System · Kaizen · Muda (waste) · Value stream mapping · Flow · Pull system · Kanban board · WIP limit · Explicit policies · Lead time · Cycle time · Throughput
Summary
| Concept | Description |
|---|---|
| Lean Foundations | |
| Toyota Production System | Ohno's production system organized around waste elimination and downstream pull |
| Kanban card | A signal authorizing upstream work to replace exactly what downstream has consumed |
| Kaizen | The discipline of continuous incremental improvement proposed by those doing the work |
| Lean thinking | Womack and Jones's five-principle distillation of lean: value, stream, flow, pull, perfection |
| The Five Principles | |
| Specify value | Defining what the process's end customer actually values, not what the process finds convenient |
| Value stream mapping | Charting every step from request to delivery to expose value-creating and wasteful steps |
| Flow | Removing queues, hand-offs, and batching so that work moves without waiting |
| Pull system | Letting downstream demand trigger work rather than pushing work in on a schedule |
| Waste | |
| Muda (waste) | Any activity that consumes resources without creating value for the customer |
| Seven wastes in HR | Overproduction, waiting, transportation, over-processing, inventory, motion, and defects in people processes |
| The Kanban Method | |
| Kanban method | Anderson's approach for knowledge work: visualize, limit WIP, manage flow, improve |
| Kanban board | A visual process model whose columns mirror real stages and whose cards are work items |
| WIP limit | A maximum on simultaneous items that converts overload into a visible, actionable signal |
| Lead time | Elapsed time from request to delivery, the only duration the customer experiences |
| Cycle time | Time from starting an item to finishing it |
| Throughput | The number of items completed per period |
| Evolutionary change | Kanban's start-where-you-are philosophy, HR's gentlest entry into agile working |
| Scrum versus Kanban fit | Scrum for goal-directed projects; Kanban for continuous-flow HR services |
| Case Evidence | |
| Toyota's people legacy | Line-stop authority and kaizen as respect for the person closest to the work |
| Talent acquisition Kanban case | A recruiting team halving lead time through WIP limits and explicit feedback policies |