Manufacturing Training: What to Standardize Across Plants

Reflections from my conversation with Luz Lozano on balancing global consistency with local judgment in manufacturing training.

In my conversations with global L&D leaders, one question returns in different forms: how do we create consistency across locations without designing training so centrally that it loses relevance at the point of work?

Manufacturing makes this tension especially visible. A company may introduce one leadership program across three plants, yet each site receives it under different conditions. One plant may have several newly promoted supervisors. Another may rely on experienced managers who are continually onboarding operators. A smaller, more automated facility may need those same leadership capabilities applied to a different operating environment.

The organization needs a common standard, but identical delivery is rarely the answer. Newly promoted supervisors may need to practice giving feedback to former peers. Experienced managers may need to coach employees through unfamiliar tasks. Even an accurately translated course can feel remote when its examples, terminology, and practice activities do not resemble work at the plant.

My podcast conversation with Luz Lozano brought this tension into sharp focus. Introduced in the episode as HR Director, North America Talent and Development at Albéa Group, Luz has worked across manufacturing operations in several countries. Our discussion kept returning to the relationship between a global framework and local application.

“And the local needs might be similar, but they're never the same.”

Her words get to the heart of the matter. Global L&D should establish the capabilities employees need, the company-specific messages they must understand, and the requirements that cannot change. Local teams should help employees make sense of those fundamentals in their own language, plant, and working conditions. The quality of the program depends on both.

What belongs in the shared training framework?

I find it useful to separate two ideas that are often treated as one: standardizing the course and standardizing the capability. The first can produce uniform content. The second keeps everyone working toward the same performance expectation while allowing the learning experience to reflect local reality.

Luz described manufacturing operations that produce beauty packaging through injection molding, assembly, and decoration. Across plants, the basic workforce structure is recognizable: leaders, technical specialists, and operators responsible for production. This common structure makes shared development programs possible. Yet workforce experience, employee turnover, automation, plant size, and local conditions differ.

That is why a requirement such as “provide leadership training” does not give a design team enough direction. We need to define the leadership behavior being developed, the company expectations attached to it, and what a participant should be able to do after the program. A training needs analysis can help translate performance gaps into clear learning objectives.

The approach Luz outlined uses a global framework of technical and interpersonal fundamentals, supported by development roadmaps, without prescribing every deployment detail. I would turn that principle into an explicit agreement between the central team and the sites before development begins.

This division is a planning model derived from the episode’s distinction between global fundamentals and local application. It is not a description of Albéa’s formal governance.

This distinction is practical, not theoretical. A site can replace an unfamiliar example while preserving the learning objective. A facilitator can adjust the pace of a discussion without dropping the points employees must understand. Approved procedures, regulatory content, and company policy remain under the authority of the relevant owner.

Unless these decision rights are clear, local teams are left to guess. Some will deliver material that does not fit their workforce because they are afraid to change it. Others will adapt freely without knowing which elements carry organizational or regulatory importance. Neither outcome gives the enterprise the consistency it intended.

Where does local adaptation add the most value?

One statement from Luz captured the issue precisely: having the course is not enough. The content becomes meaningful when people can connect it to a context. That connection usually happens during application, and much of it must happen locally.

She explained that site HR managers and their steering committees determine how programs are deployed. Some plants involve internal or external trainers from the same city or country because they can connect with employees culturally and linguistically. These trainers are not merely presenting central content. They are helping people interpret it through situations they recognize.

Take the leadership example. Newly promoted supervisors at one plant may need to discuss how they will manage former peers. Experienced managers elsewhere may gain more from working through a coaching problem involving a new operator. These are illustrative applications, but they show why workplace-based scenarios matter. The capability remains common; the route into it becomes locally credible.

I would therefore treat local application as part of the learning design, not as an activity to be improvised after launch. The central team can provide the purpose, essential discussion points, and expected outcome. A local facilitator can select the situation, language, and pace that will work with that group.

What must happen at the site for employees to apply this learning, and who will support it?

The answer may be a discussion, a demonstration, supervised practice, or feedback on a real task. In manufacturing, a blended learning approach can connect digital instruction with hands-on practice and reinforcement. What matters is that someone owns this part of the experience. Otherwise, employees can complete the formal course without receiving the support required to use what they learned.

Who should support learning at the plant?

During our conversation, I asked Luz where the organization spends most of its training energy. Her answer revealed an important division of work. Local HR teams devote much of their everyday effort to operators. Her small global talent development team concentrates more on leadership programs and consistent implementation because plant leaders manage and influence everyone else.

Luz described self-paced online leadership programs alongside regional classroom development for selected employees, including people entering leadership roles. Her answer reinforces a principle that matters across enterprise learning: when L&D relies on supervisors and managers to reinforce training, their ability to support others becomes part of the learning system.

A supervisor may know a production task thoroughly and still find it difficult to explain the task, observe someone practising it, or give feedback that improves performance. A local facilitator may understand the workforce well but need guidance on the purpose and boundaries of a centrally designed activity. Subject expertise and the ability to develop people are related, but they are not interchangeable.

For that reason, every program that depends on local reinforcement should define the supporting role. Supervisors and facilitators need to know what employees are learning, what follow-up is expected, which content is fixed, and where questions should be escalated. The guidance can be light or detailed depending on the complexity of the task and the facilitator’s experience.

There is also a capacity implication that L&D should not ignore. If managers must lead discussions, observe practice, or provide feedback, their time belongs in the rollout plan. When this work is treated as an informal expectation, production pressures will often take priority.

How should language, meaning, and access be handled?

Language was another practical test of the global framework. Luz explained that online learning projects must be deployable worldwide and available in the languages used by the organization’s major employee populations. This requirement has to influence the project from the beginning; it cannot be handled as a production step added at the end.

I would also caution against treating translation as the full answer. Company terminology may need agreed wording across languages. A scenario that makes sense at headquarters may need contextual review elsewhere. Instructions that appear obvious to the central team may assume knowledge employees at another site do not have. A sound eLearning localization strategy addresses these linguistic, cultural, and practical differences before they become rollout problems.

Our conversation also surfaced a useful make-or-buy distinction. An external program may work well for language learning, injection molding, or general leadership development. Content about a company’s own leadership model, finance vocabulary, or code of conduct has to carry the organization’s precise meaning.

That does not mean every component needs custom development. A program may combine an existing specialist resource with a company-specific module, translated versions, and a locally facilitated activity. The design decision should follow the learning requirement rather than a preference for one content model.

Access is part of the same discussion. Luz spoke about a language-learning program that initially used nominations. The process was taking too long, so the organization moved toward making development opportunities more open where possible. I found this example valuable because friction is easy to overlook when we concentrate on content and technology.

A course can be available in the LMS and remain difficult for a manufacturing employee to use. Shift patterns, devices, production schedules, and access to help all affect participation. Local teams are best placed to identify these constraints. Required training will still need assignment and completion controls, but optional development should not be slowed by approvals that serve no clear purpose.

Review the rollout through evidence from the sites

If I were reviewing a multi-site rollout, I would begin with one program already operating across several plants. That is usually enough to reveal where the global framework is helping and where local teams are compensating for gaps.

I would ask site colleagues where employees need additional explanation, which examples they have adapted, and what happens after the formal course. Their changes should then be reviewed against the original objectives and required content. An adaptation at one plant may be useful elsewhere. The same misunderstanding appearing across several sites probably points to a weakness in the common resource rather than a local delivery problem.

The evidence collected should match the capability being developed. For leadership training, realistic situations, facilitated practice, and recurring questions can reveal where further support is needed. For applied skills, performance-based assessments can show what employees can do rather than what they remember. A physical task still requires suitable practice and observation. Course completion by itself does not demonstrate performance.

The evaluation approaches above are my application of the discussion, not outcomes reported by Luz. Our conversation did not establish measured performance improvements or a formal evaluation model.

The review should end with decisions, not a general call to “improve relevance.” The central team may need to clarify a resource, revise an example, or strengthen facilitator guidance. A site may need a better application activity or a workable arrangement for employee access. Recording these decisions prevents other plants from having to diagnose the same problem independently.

Set the standard for the outcome, not every interaction

The conversation reinforced a principle I have seen throughout my work in training and development: global consistency should be judged by the outcome, not by whether every plant delivers the same interaction in the same way. The enterprise needs agreement about the capability being developed, the meaning that must remain intact, and the evidence that employees can apply the learning.

Once these expectations are clear, local teams can make sound decisions about language, examples, facilitation, scheduling, and practice. Their judgment does not weaken the global framework. It is what allows the framework to work under different operating conditions.

Before the next rollout, I would ask one final question: have we told every participant which decisions are fixed, which belong to the site, and who is accountable for each? If the answer is unclear, the training is not yet ready to scale.

Related Podcast

Building Skills at Scale in Global Manufacturing

Frequently Asked Questions

What should manufacturing training standardize across plants?

Standardize required learning objectives, approved company messages, essential procedures, and expectations for applying the learning. Where content cannot be altered, state that clearly. Local teams can then adapt examples, facilitation, scheduling, and practice within the agreed boundaries.

How can L&D tell whether local adaptation has gone too far?

Compare the adapted material with the original objectives, required content, and performance expectations. An adaptation should help employees meet those requirements without changing their meaning. Revisions to approved procedures, policies, or other controlled content should return to the appropriate owner.

Who should be responsible for local training adaptation?

The central team should maintain the common resources and define the limits of adaptation. Designated site colleagues can review local relevance, organize delivery, and select appropriate application activities. The episode describes site HR managers, steering committees, and local trainers contributing to deployment, although each organization will need to assign responsibility according to its structure.

Is translating a course enough to make it locally relevant?

Translation provides language access, but employees may still need familiar examples, explanations of company terminology, and opportunities to apply the learning. Local review and facilitation help identify where that additional support is necessary.