ai translated
ai translated
In this article, we explore how change management in operations is now one of the most decisive levers for building an agile and competitive factory. We start by defining what it really means to govern change in the new manufacturing context, then analyze the operational phases of the transformation journey: from initial awareness to understanding the value chain, from organizational preparation to the concrete transformation of the plant. We delve into the role of daily management, structured escalation systems, and problem solving, up to the mechanisms for maintaining results over time, such as Kamishibai and process audits. Finally, we dedicate space to developing the winning skills to achieve Operational Excellence in the new competitive arena.
Volatility, rising costs, a shortage of skills: manufacturing companies today face unprecedented pressures. Those who do not govern change in a structured way risk chasing problems instead of anticipating them.
In contemporary manufacturing, it is no longer enough to have efficient systems, advanced technologies or an ambitious industrial plan. In markets marked by volatility, cost pressure, supply difficulties, a shortage of skills and the growing need for speed in decision-making, the true competitive advantage is built through the organization’s ability to apply a true change management process in operations in a structured way. This is where the concept of the agile factory takes shape, an organizational and managerial model in which every level of the production organization is able to detect deviations, trigger rapid responses and transform continuous improvement into an organizational routine.
The agile factory is not just a fast factory. It is a factory that knows how to read priorities, make problems visible, assign clear responsibilities, trigger effective escalation, develop people, and transform continuous improvement into an organizational habit. The transformation journey is addressed through a Change Management framework that acts simultaneously on people, the organizational model, processes, and technologies, with the goal of guiding the enterprise from its current state to a desired future.
In other words, the agile factory does not emerge from a single project; it emerges from a method.
Change management in operations is a structured set of activities and tools with which an organization introduces a governed approach to change among individuals, groups, and the entire company, with the goal of making a concrete and sustainable transition possible over time.
Often, organizational transformation is confused with the introduction of a new procedure, software, or internal reorganization. But the scope of change management is much broader: it is not about "managing a new thing,“ but about acting on behaviors, managerial routines, the communication system, training, and the clarity of roles.
In Operations this aspect is decisive. When operational evolution is not accompanied by true organizational direction, the effect is almost always the same: fragmented initiatives, scattered energy, confused people, recurring problems, micro-management, and poor responsiveness. Conversely, when structured transition is planned and guided, the plant stops chasing anomalies and begins managing them systematically.
One of the strengths of this approach is its methodological clarity. Operational transformation is not treated as a one-shot intervention, but as a process divided into precise stages:
1 Awareness
2 Preparation
3 Transformation
4 Sustainability
5 Development of skills
6 Maintenance.
It is a multi-year plan in which involvement, understanding, risk management, communication, organization, and action are linked in a coherent manner.
| Size | Fabbrica Impacciata | Agile Factory |
| Visibility of the problems | Implicit, in emails or perceptions | Explicitly, on shared visual boards |
| Responsibility | Confused, frequent overlaps | Chiara, defined by level and role |
| Escalation | Slow, informal, discretionary | Structured, activated by defined triggers |
| Problem solving | Controlling the urgency | Quick/Standard/Major Kaizen |
| Leadership | Prevalent micro-management | Leader Standard Work + Gemba Walk |
| Competences | Verticals, focused on a few people | Diffuse Policompetence (3x3x3 model) |
| Improvement | Occasional exception | Measurable daily routine |
This is a fundamental message for those who lead Operations: an agile production organization is not built with a motivational workshop or a simple efficiency project. It requires a progressive design that starts with understanding the scenario, defines a shared vision, identifies key roles, activates governance mechanisms, and makes change observable in daily behaviors.
Change is never abstract. It is always linked to concrete goals, indicators, responsibilities, and control routines. It is precisely this connection between strategic vision and operational execution that makes the difference.
The first phase is the phase of Awareness. Before transforming an establishment, it is necessary to help people read reality differently.
Two very significant tools are the Kaikaku Experience — a factory tour based on real examples of transformation — and the Orientation Workshops, structured moments to build a matrix of priorities based on impact and corporate maturity. The factory tours we organize represent a privileged point of access to this type of experience: open meetings where to discuss methodologies, real cases, and operational priorities. The goal is to create engagement, a sense of urgency, clarity about objectives, and willingness to act.
This step is often underestimated. In many organizations, it is taken for granted that the need for operational evolution is obvious to everyone. In reality, this is not the case. Without a phase of awareness, the risk is that the initiative is perceived as a "management project" and not as a shared need. A high-reactivity lean system begins when improvement becomes understandable, visible, and desirable even for those who experience the process every day.
The Understanding phase consists of a systematic analysis of the value chain to map the main dimensions of the Operations processes — particularly manufacturing, but without losing sight of decisive elements such as maintenance, quality, logistics, forecasting and planning — with the aim of identifying the gaps between the current state and the desired one.
The key tool in this phase is the X Matrix of Hoshin Kanri, which links strategic objectives, indicators, top-level teams, and transformation projects. For those who want to deepen their understanding of the method, the Hoshin Kanri White Paper, developed by our Knowledge Office, provides practical guidance on how to translate strategy into daily actions.
This approach avoids two common mistakes: on the one hand, improving too much at a small scale without a systemic vision; on the other hand, defining strategic objectives without translating them into operational behaviors. Operational Excellence works precisely because it brings the two levels together.
An operational transformation almost never fails due to a lack of sophisticated tools. More often, it fails because the organizational risks were not anticipated. In the Preparation phase, our framework puts at the center: stakeholder mapping, communication plan, governance, and Leader Standard Work. The stakeholder map serves to understand who will be involved in the structured transition, what impact they will have, what level of commitment they possess, and what communication actions reduce the risk of resistance.
The communication plan becomes a concrete lever: the vehicles are floor meetings, periodic management communication, corporate communities, internal posts, videos, monthly meetings on the shopfloor, and visible leadership through Gemba Walk and Kamishibai. All of this makes the operational evolution present, readable, and continuous.
The preparation is completed with the Leader Standard Work, the set of managerial practices that allow leaders to dedicate time to the true value: observing the process, seeing abnormalities, supporting people in problem solving, measuring and improving. The guiding principle is: there is no high-performance operation without leadership that frequents Gemba and transforms improvement from an exception to a daily discipline.
Every real operational transformation starts with people. Developing skills is a key theme for building versatility and multi-competency. The Hitozukuri model is the logic for "building teams" through the 3x3x3 principle: every skill possessed by at least three resources, every resource possessing at least three skills, and at least three resources capable of covering all critical skills.
The goal is not only organizational, but strategic: increasing flexibility, the ability to absorb changes in demand, and resilience against planned absenteeism or absence. Many plants talk about operational agility, but they remain fragile because they depend on a few key people or too vertical skills. A resilient manufacturing organization, on the other hand, is able to redistribute knowledge, make the system less vulnerable, and build widespread autonomy. At this stage, building an Enterprise Academy can make the difference.
The cluttered factory is one where there is a dominance of disorganization, uncertainty, doubts about who should do what, difficulties in understanding who to warn, poor control, frequent anomalies, little structured problem solving, and a tendency towards micro-management. This is a picture in which many organizations can recognize themselves.
The answer is Agile Factory Management: a structured system that allows those responsible at every level to promptly identify deviations in processes and resolve them with high discipline and minimal effort. In this model, daily management is not an operational detail: it is the very engine of the transformation towards operational excellence.
The Daily Management is the structured meeting system, visual board, and distributed control routine across multiple organizational levels (tier logic) that allows each Team to detect deviations from standards and initiate the necessary corrective actions within the working shift.
It’s a tier-based logic, where cell meetings, support teams close to the line, daily meetings, and subsequent levels of escalation build a network of control and reaction much closer to the real problems.
At the operational level, key tools come into play such as:
The value of this system lies in its concreteness. The problems do not remain implicit or confined to emails. They become visible, discussable, and assignable. A reactive operations is not one in which problems do not emerge: it is one in which they emerge early, are quickly taken on board, and follow a clear escalation process.
Special events, such as abnormalities with the Andon switch on, or KPIs that are out of standard range, are normally two triggers to trigger a specific escalation path, consistent with the principle of Jidoka – Stop & Fix. The organizational structure must therefore be designed to be close to the problems and reactive in their management.
Speed is not an improvisation: it is the result of clear roles, defined levels of supervision, competent Team Leaders and a problem-solving culture that does not limit itself to containment but aims to formalize solutions through Quick Kaizen, Standard Kaizen or Major Kaizen. The choice of the Team Leader becomes therefore decisive: this figure must monitor the results of the plant at short intervals, intervene at the first sign of small problems, trigger escalation for larger ones and possess proactivity, listening skills and a team-working attitude.
Many transformation programs produce initial enthusiasm but results that deflate over time. Mechanisms such as Kamishibai and process audits significantly reduce this risk. The principle is simple: Leaders at different levels systematically monitor processes to verify that standards are met and that improvement is not lost. Kamishibai makes auditing widespread, frequent, and visible, transforming it into a daily practice of maintaining operational discipline.
Alongside this, the ARCA – Absenteeism Root Cause Analysis tool shows how even an indicator like absenteeism can be read as a measure of people’s motivation and treated with a structured approach, within a vision that aims to make the plant the best working environment capable of generating sustainable performance. The sustainability of an agile production organization does not depend solely on processes, but also on the quality of the work experience that the organization builds.
The Manufacturing Training System is a People Development system supported by Bronze, Silver and Gold levels of certifications – with assessments that measure not only theoretical knowledge but the ability to apply and even teach the tools – supporting the building of lasting capabilities. This approach shifts the focus from episodic training to systematic training: a flexible manufacturing system does not just introduce new routines, but creates the conditions for people to understand them, practice them, improve them, and pass them on.
Digital Transformation and skills development are not parallel paths, but dimensions that reinforce each other in every establishment that aspires to operational excellence.
Conclusions
The agile factory is not a label. It is an organizational and managerial model that makes Operations more readable, more accountable, and more responsive, and more solid in maintaining results.
The key point is that agility does not come from chaos, but from discipline applied at all levels: a clear vision, a roadmap for change, a distributed leadership system, rigorous day-to-day management, a structured process of escalation and problem solving, a strong focus on skills and a constant vigilance regarding the sustainability of change. For manufacturing companies that want to face the future with greater resilience, the question is no longer whether to change, but how to change. The agile factory offers a concrete answer: transforming the organization into a system capable of seeing first, deciding better, and acting faster.
It is a structured set of activities and tools with which an organization introduces a governed approach to change — in individuals, in groups, and throughout the entire company — with the goal of making a concrete and sustainable transition possible over time.
An agile factory is an organizational and managerial model in which every level of the production organization is able to detect deviations, trigger rapid responses, and maintain continuous improvement as a systematic habit, not as an exception.
The main phases are: awareness, preparation, transformation, sustainability, skills development and maintenance. It is a multi-year process in which involvement, communication, organization and action are interconnected in a coherent way.
It is a system of structured meetings, visual boards, and routine control at multiple organizational levels that allows each team to detect deviations from standards and trigger the necessary corrective actions within the working shift.
Through tools such as Kamishibai and process audits, which make standard control widespread, frequent, and visible, transforming the maintenance of operational discipline into a daily practice at all levels.
Because a resilient manufacturing organization must be able to redistribute knowledge and reduce dependence on a few key individuals. The Hitozukuri model and the 3x3x3 criterion ensure widespread multi-competence, flexibility, and resilience to changes in demand.
In the cluttered factory, disorganization, confused responsibilities, slow escalation, and limited problem solving dominate. In the agile factory, problems are visible, responsibilities are clear, escalation is structured, and improvement is a measurable daily routine. What are Kaizen in Change Management?
They are methods of continuous improvement that are divided into three levels: Quick Kaizen for quick interventions, Standard Kaizen for recurring problems, and Major Kaizen for structural transformations. They represent the tool with which problem solving is formalized and made systematic.
Did it help you? Add it as your preferred source on Google
