Art of Lean
Back to Reference
People Development

Skills Matrix

A visual grid showing each operator's qualification level for each process in a work area — making it immediately clear who can do what, where training gaps exist, and how flexible the team is for rotation and coverage.

Japanese

力量表

rikiryō hyō

capability table

Also known as

Skill Matrix, Training Matrix, Competency Matrix, Multi-Skill Chart

Definition

A skills matrix is a grid chart that maps operators (rows) against processes or tasks (columns), with each cell indicating the operator’s current qualification level for that process. Typically, qualification levels range from “not trained” through “in training,” “can perform independently,” to “can teach others.” The chart is posted visibly in the work area and updated regularly. It serves three purposes: it shows the team leader who can fill which positions for daily rotation and absence coverage, it identifies training gaps that need to be addressed, and it drives the development of multi-skilled workers who can perform multiple processes.

Japanese Origin

Rikiryō (力量) means capability or competence — 力 (riki, power/ability) and 量 (ryō, measure/quantity). The 表 (hyō) suffix means table or chart. The concept connects to Toyota’s broader philosophy that developing people is as important as developing processes.

History at Toyota

Multi-skill development has been a cornerstone of Toyota’s production system since Ohno’s early experiments with multiprocess handling in the 1950s. When Ohno arranged machines in U-shaped cells and required operators to tend multiple machines of different types, he needed a way to track which operators could perform which processes. The skills matrix became the standard tool for this tracking.

At Toyota, the skills matrix is managed by the team leader or group leader and is a working document, not a report for human resources. It is reviewed during team leader standard work and updated as operators gain qualifications through on-the-job training. Toyota’s goal is for every operator to eventually be qualified on every process in their group — creating maximum flexibility for rotation, absence coverage, and kaizen.

How It Actually Works

Typical format:

  • Rows list each operator in the team
  • Columns list each process or task in the work area
  • Cells contain a symbol indicating qualification level, commonly:
    • Empty or “1” — not yet trained
    • Half-filled or “2” — in training, can perform with supervision
    • Filled or “3” — fully qualified, can perform independently
    • Star or “4” — can teach others

How it drives action:

  • The team leader uses the matrix daily to assign operators to positions, ensuring every station is covered by a qualified person
  • Gaps in the matrix reveal training priorities — if only one person can perform a critical process, that is a vulnerability
  • The goal over time is to fill every cell — every operator qualified on every process
  • Training plans are built directly from the matrix

Visual impact: When posted on the team board, the skills matrix makes capability and vulnerability visible at a glance. A column with mostly empty cells is a single-point-of-failure risk. A row with mostly empty cells is an undertrained operator who needs development attention.

Common Mistakes

Not updating the matrix. A skills matrix from six months ago does not reflect current reality — operators have been transferred, new people have joined, skills have been gained or lost. The matrix must be a living document updated as conditions change.

Confusing “has been shown” with “is qualified.” Qualification means the operator can perform the process independently to standard, consistently. Watching a demonstration or performing the task once under supervision is training, not qualification. The distinction matters for both quality and safety.

No training plan to close gaps. The skills matrix identifies gaps but does not close them. Without a deliberate training plan — who will be trained on what, by when, using what method — the matrix becomes a static display of unchanging deficiencies.

Tracking too many tasks at too fine a level. The matrix should cover the processes and tasks that matter for daily rotation and coverage. Breaking tasks down too finely creates an unwieldy chart that is difficult to maintain and loses its visual clarity.