Quality 4.0 is Industry 4.0 which is really just:
- A ton of sensors (cheap, reliable sensors for everyone)
- Data everywhere! (So much data. Honest data is good. Trust us.)
- Collaboration (Because that never happened before technology)
- Machine learning (this never ends well in the movies)
However, Quality 4.0 is really a lot more than the technology, it is all about using that technology to improve our quality management systems. So Quality 4.0 is really all about understanding that the world around us, and thus the organizations we work in, is full of complex and interconnected challenges and increasingly open systems of communication, and that we can no longer afford to address complex issues as we have in the past. The very simple idea behind Quality 4.0 is that current and future challenges requires thinking that is consistent with a living world of complexity and change.
As such there is nothing really new about Quality 4.0; it is just a consolidation of a lot of themes of change management, knowledge management and above all system thinking.
System Thinking requires quality professionals to develop the skills to operate in a paradigm where we see our people, organizations, processes and technology as part of the world, a set of dynamic entities that display continually emerging patterns arising from the interactions among many interdependent connecting components.
There are lots of tools and methodologies for managing systems. Frankly, a whole lot of them are the same that have been in use in quality for decades; others are new tools. The crucial thing to remember about Quality 4.0 is that it is an additive and transformative way to look at quality, and quite frankly one can go back and read Deming and see the majority of this there.
When I work on systems (which is according to my job description my core function), I keep some principles always in mind.
||The system creates value for the multiple stakeholders. While the ideal is to develop a design that maximizes the value for all the key stakeholders, the designer often has to compromise and balance the needs of the various stakeholders.
||The degree to which the system components are aligned and consistent with each other and the other organizational systems, culture, plans, processes, information, resource decisions, and actions.
||The system is designed to be as convenient as possible for the participants to implement (a.k.a. user friendly). System includes specific processes, procedures, and controls only when necessary.
||System components are interconnected and harmonized with the other (internal and external) components, systems, plans, processes, information, and resource decisions toward common action or effort. This is beyond congruence and is achieved when the individual components of a system operate as a fully interconnected unit.
||Complexity vs. benefit — the system includes only enough complexity as is necessary to meet the stakeholder’s needs. In other words, keep the design as simple as possible and no more while delivering the desired benefits. It often requires looking at the system in new ways.
||Participants in the system are able to find joy, purpose and meaning in their work.
||Knowledge management, with opportunities for reflection and learning (learning loops), is designed into the system. Reflection and learning are built into the system at key points to encourage single- and double-loop learning from experience to improve future implementation and to systematically evaluate the design of the system itself.
||The system effectively meets the near- and long-term needs of the current stakeholders without compromising the ability of future generations of stakeholders to meet their own needs.
In order to be successful utilizing these principles when designing systems and processes we need to keep user at the forefront — striving to be sensitive to the user, to understand them, their situation and feelings: to be more empathetic.
We leverage both the affective component and the cognitive component of empathetic reasoning, in short we need to both share and understand.
We are in short asking 5 major questions:
- What is the purpose of the system? What happens in the system?
- What is the system? What’s inside? What’s outside? Set the boundaries, the internal elements and elements of the system’s environment.
- What are the internal structure and dependencies?
- How does the system behave? What are the system’s emergent behaviors and do we understand their causes and dynamics?
- What is the context? Usually in the terms of bigger systems and interacting systems.
Think holistically, think empathetically with the user, and ask questions about system behavior. Everything else falls into place from there.