People and frontline ownership: skills, team leaders and a frontline that runs its own line

What this pillar covers, and why the frontline carries the other five

The other pillars quietly assume that someone at the line can do the job, spot an abnormality, run a five-minute meeting and fix small things without waiting for engineering. When that assumption fails, the boards go stale and every problem climbs to the supervisor. This pillar measures whether the assumption holds.

We score five things: how skills are managed (ppl1), how involved operators are in solving problems (ppl2), how team leaders are developed (ppl3), how good work is recognised (ppl4) and how the plant listens to the frontline (ppl5).

The link to results is direct. A position with only one qualified person turns every absence into a loss or a quality risk. A team leader promoted for technical skill and never taught to lead spends the shift repairing machines, so the daily routines degrade into status updates. An operator who has to fill in a form to move a tool holder stops suggesting anything after the second attempt.

The five levels as you would see them on the floor

Most plants sit at different levels on different questions here. A strong skills matrix alongside a weak listening channel is common, and so is the reverse. The assessment scores each question separately, and the levels page explains how the pillar index and the weakest-pillar rule work.

The five questions, and how to check your own answer this week

ppl1. How are skills managed? We are asking whether you can run every position on every shift with qualified people, and whether you know in advance where you cannot. The matrix is a planning tool, not a training archive.

The typical over-rating is a matrix filled in once for an audit, where anyone who has ever worked a station is marked autonomous. The typical under-rating comes from small teams where the team leader keeps a whiteboard grid, updates it weekly and plans the shift from it. That is closer to Level 4 than an HR system nobody at the line consults.

ppl2. How involved are operators in solving problems? We are asking whether an operator can change something at their own workstation without a request climbing three levels, and whether they take part in solving the line's problems rather than only reporting them.

Plants with an active idea system and a guaranteed response time often score themselves at Level 4. That is Level 3. Level 4 requires operators to take part in daily problem-solving and implement small improvements themselves. Collecting ideas and passing them to engineering is a different thing.

ppl3. How are team leaders and supervisors developed? We are asking whether leading a team is treated as a skill that is taught and coached, or as something a good operator is expected to pick up.

A two-day leadership course is often counted as a development path. The model places occasional training at Level 2. Level 4 means coaching on real problems from the team leader's own line, on a regular rhythm, by their manager or an experienced peer.

ppl4. How is good work recognised? We are asking whether recognition names a specific contribution and is tied to the behaviours you want more of, such as raising a problem early or following a standard under pressure.

An employee-of-the-month board is often taken as a recognition system, but it rarely says what the person did or why it mattered. Plants also under-rate themselves by assuming recognition needs a budget. The model rewards specificity and visibility, not prizes.

ppl5. How does the plant listen to the frontline? We are asking whether what operators say changes anything, and whether they can see that it did. Having a channel is Level 2; closing the loop is what moves you up.

A high survey response rate is the usual reason for over-rating. Level 3 requires actions to follow the survey, and Level 4 requires structured channels such as floor walks and skip-level conversations with their actions tracked.

What Level-4 plants do differently

The practices below are the ones we look for in plants at Level 4 on this pillar. The thresholds are rules those plants set for themselves.

• One skills grid, used for planning. Every line has the same grid: people against positions, with three levels (learning, autonomous, can train). A person moves up only after the team leader has watched them work against the standard, not after attending a course. The grid is updated at a fixed moment, for example at each sign-off and in a monthly check.
• A coverage rule. Any position with fewer than two autonomous people on a shift goes on the risk list reviewed in the weekly meeting, and the training plan is built from that list rather than from a catalogue.
• Protected leadership time. The plant decides how much of the team leader's shift is for leading the team and protects it, for example by not counting team leaders in the headcount needed to run the line.
• A written 'change without asking' list. Agreed with safety and quality, it states what a team may change on its own (tool positions, labels, board layout, cleaning routes) and what always needs approval (safety devices, product specifications, machine parameters). A small team budget goes with it.
• An answer to every idea. Every idea gets a reply within a fixed time, and a decline is explained in person by the person who decided.
• Coaching at the line. Each team leader's manager spends time with them at the line on a set rhythm, coaching on one real meeting, handover or problem. The team leader keeps the notes.
• Skip-level conversations with a trail. Managers meet shift teams one level down without an agenda. Every action goes on the plant's main action list, tagged with its source, and the answer is reported back to that team.
• Specific recognition. Once a week the team leader names one contribution and says why it mattered. Improvements are shown on the line board with the names of the people involved, when they agree.

A 90-day plan to move up one level

The plan assumes most answers sit at Level 2 or 3. Start with the lowest-scoring question in your report from the assessment, which gives a specific next move for each gap.

1. Weeks 1–2Rebuild the skills matrix for the bottleneck line by observation, not from training records, and count the single-person positions per shift. Ask each team leader to write down what is expected of them in a shift, and compare it with what their manager writes. Start asking at each daily meeting: 'what slowed you down yesterday?'
2. Weeks 3–6Use the matrix in shift planning and start training for the single-person positions. Draft the 'change without asking' list with the teams, safety and quality. Introduce a fixed answer time for ideas. Hold the first open conversation between the plant manager and a shift team. Begin monthly coaching for each team leader.
3. Weeks 7–12Extend the matrix to the other main lines and track the number of positions covered by two qualified people per shift. Make weekly recognition a standing agenda item and record it. Post on the board which actions came from the frontline and where they stand. In week 12, recount the single-person positions and retake the assessment.

Evidence a jury looks for in verification

In verification you upload artefacts, then take two jurors through them in a 45-minute video interview. Expect to be asked for a specific case, such as the last time a single-person position was covered at short notice, or the last idea that was declined and how the person was told.

Artefacts that count:

• A photo of the skills matrix at the line, with the dates of recent updates and sign-offs.
• A shift plan that shows the matrix being used, and a training plan built from its gaps.
• An idea log with the date each idea was raised and answered, and the outcome.
• Two or three small improvements made by operators, with before-and-after photos and the names of those involved (with their consent).
• The team-leader onboarding programme, notes from coaching sessions and a succession list for team-leader positions.
• Recognition records from team meetings.
• An action log from skip-level conversations or floor walks, showing the answer that went back to the team.

What does not count: total training hours; an engagement survey score on its own; leadership course certificates without any coaching record; a suggestion box with no log; a matrix kept only in the HR office or produced for the application; posters of company values.

Pitfalls that keep plants stuck on this pillar

• The matrix as a compliance document. Filled in for the customer audit, never used to plan a shift, and out of date the week after.
• Everyone can train. When half the team is marked at the top level, the grid no longer tells you anything.
• Counting ideas. Targets on the number of ideas produce a flood of trivial ones and a backlog nobody answers, which teaches operators that ideas go nowhere.
• Ownership without influence. Handing a team a measure it cannot affect, such as a figure driven by material supply, creates frustration rather than ownership.
• Promote and abandon. The best operator becomes team leader on Monday with no onboarding, and the plant loses a good operator without gaining a leader.
• Rewarding heroics. Recognition that only goes to people who saved the night after a breakdown teaches the plant to value firefighting over prevention.
• Listening sessions where the manager talks. Or input collected and never reported back, which does more damage than not asking.
• Naming people without asking. Some people do not want public recognition. Ask first, and agree the approach with employee representatives where they exist.

Where to go next

Take the assessment to see this pillar's index next to the other five, with a specific 90-day move for each of your three biggest gaps. Team leaders are the hinge between this pillar and daily management and shift routines, where their standard work, meetings and handovers are scored, so read that one next. The improvement engine covers how the standards they train people on are kept current.

Questions