Skip to content
Production System | Part 1 of 16

Production System Foundations: Build the House Before the Rooms

What a production system is, who runs it, how standards are governed and how maturity is steered across sixteen modules.

A plant runs a 5S campaign in spring, a kanban pilot in summer and an OEE dashboard in autumn. Each project starts with energy and fades within a year. Nobody can say how they fit together, and the next initiative is already being announced.

A production system solves this. It is not a project but the written way the plant works: a few principles, a set of modules, clear roles and one rhythm for steering. The foundations decide whether everything else sticks.

What the module covers

  • Purpose and architecture. The system fits on a few pages: objectives for safety, quality, delivery, cost, people and energy, the principles behind them and the modules that deliver them. Every leader can explain it in two minutes.
  • Roles and organisation. The plant manager leads the monthly review in person. Area and team leaders have their system tasks written down. A small central office trains, supports and audits, but the line owns the results.
  • Standards and governance. Every standard has an owner, a version and a review date, and can be found at the point of use. Changes follow one short process: proposal, trial, approval, training.
  • Maturity and steering. Each area is assessed across all sixteen modules on one scale from 0 (not started) to 4 (excellent). The profile hangs on the board, next to no more than eight KPIs.
  • Keeping the system alive. Leader standard work, layered process audits and an annual review of the system itself stop it from turning into a binder on a shelf.

The numbers that matter

Keep the steering lean. A maturity profile per area, plus a handful of results: accident rate, first pass yield, on-time delivery, productivity and an engagement measure. If a KPI misses its target, it gets an owner and a countermeasure, not a discussion about the definition.

Where to start

Assess one area honestly, choose two or three modules for the first wave and name one owner per module in the line. Write the one-page system overview before the first workshop, not after. Thirty days is enough to have a baseline, a rollout plan and a first review on the calendar.

Common traps

  • Rolling out all modules at once. Waves of two or three work better than a big launch.
  • A large staff function that does the work for the line. Ownership must sit with the people who run the area.
  • Maturity scores without evidence. A level counts only when you can see it at the workplace.

How it connects

Foundations is the frame for all other modules. Strategy Deployment sets the direction on the roof, People and Teamwork and Standard Work build the floor, and Continuous Improvement keeps the house growing.

Put it into practice

Start with the free Production System Foundations Quick Start Checklist: 25 statements in five blocks, scored 0 to 4, with your result and three priorities in about 20 minutes. The Starter Kit adds a short guide, a worked example and an Excel tracker for the first 30 days in one area. The Excellence Bundle is the complete module: playbook, two-day workshop, shop floor forms, an Excel system and a ready workshop deck.

Newsletter

One Lean idea.
Every week.