Change Isn't Coming. It's Already Happened.

Because today the real problem is no longer merely adaptation, but truly understanding what is actually changing.

For a long time we spoke of change as something to prepare for. An incoming event, a transition to manage, a topic to include in the next strategic plan. It was a reassuring representation: change seemed like a clear passage, something that could be placed in time and addressed with order.

Today this representation no longer holds up.

Change is not ahead of us, it is already embedded in what we do every day: in markets, in processes, in the technologies we use, in the way we work and in people's expectations. In many contexts the sensation is obvious: we are chasing something we thought we could control.

You see it in politics, where equilibria move faster than our ability to interpret them. You see it in economics, crossed by continuous tensions and interdependencies difficult to manage. But the transformation concerns far more than these areas alone. It touches culture, art, society. References change, languages change, the way we recognize what has value changes.

In culture and art, for example, traditional channels no longer hold the monopoly on legitimation. For a long time, recognition followed relatively clear trajectories: publishers, critics, cultural institutions, established media. Today it can emerge elsewhere, with greater speed and in fragmented, distributed forms, often guided by communities, platforms, and digital dynamics. The way content is received and spread has also changed: timeframes are shorter, interpretations more unstable.

Something similar happens in society. Some certainties that provided stability are no longer so solid. Work is no longer experienced only as a linear path. Authority no longer derives automatically from position. People move between more fluid belongings and ask for something different: more meaning, more coherence, more possibility for participation. Trust also behaves differently: it can arise quickly, but can vanish with equal speed.

On the technological front, it is not simply about acceleration. Change arrives in leaps, often difficult to absorb. In the past, innovations had time to consolidate, while today they succeed each other so rapidly that they are often not fully understood before being superseded. Artificial intelligence is just one of the most obvious signs of this dynamic, but the phenomenon is broader: it concerns the very way we construct knowledge and make decisions.

For engineering, all of this is not background context—in fact it is the setting in which we work.

Over the past twenty years I have had the opportunity to work with very diverse teams, in sectors ranging from finance to defense, from aerospace to automotive. I have followed the introduction of new technical and organizational paradigms, I have seen companies reorganize, redefine roles, seek to evolve their way of operating. And I have engaged with people at all levels: from corporate leadership to the most operational profiles.

In contexts very far apart from each other, I have observed a recurring dynamic. Everyone asks for speed. Everyone asks for performance. But rarely do we stop to consider what we lose along the way.

When understanding diminishes, speed stops being an advantage. It becomes noise, generates friction, produces rework. Sometimes it creates the illusion of efficiency, but real value remains limited.

The point is that today's engineering no longer works on isolated objects. It works on systems that influence each other, often guided by software and data, embedded in regulated and interdependent contexts. In these systems, effects do not remain confined, but rather propagate.

An error (at any level in the creation of a product or complex system) is no longer merely a local error. It can emerge much later, when intervention is more costly. It can create tensions between teams, slow down integrations, compromise relationships. Sometimes it even affects external perception, with consequences that extend beyond the project itself.

A poorly written requirement, for example, does not stop at the "document." It enters the development cycle, drags itself through verification, reemerges in integration. And if it arises from a partial understanding of the use context, the problem is not technical: it is systemic.

This is why today I firmly believe that it is no longer enough to simply be "good at your trade." Do not misunderstand me: specialized competence remains fundamental, but it is no longer sufficient on its own, because we also need the ability to see how our work fits into a larger picture and to understand that every decision has effects that go beyond our own perimeter.

This is where, for me, systems engineering changes in nature and does not remain confined within the canonical disciplines of literature, but instead becomes a way of reading reality itself.

I do not come from a strictly engineering academic background. Yet I have been working within these contexts for twenty years. This has led me to see engineering less as a set of definitions and more as a continuous effort to hold together diverse elements: objectives, constraints, people, consequences.

Recently I found a useful key for understanding in a book: Life and Nature – A Systems View, by Fritjof Capra and Pier Luigi Luisi. Not so much for the answers it provides—don't read it for that—but for the "way" it helps us look at things.

The fundamental point is simple: what we observe cannot be truly understood if we isolate it from its context. Systems live through relationships, not through independent parts. It is an idea that seems intuitive, yet in organizations it is often disregarded.

Many companies continue to operate as if all "problems" could be separated and decontextualized. Each function concentrates on its own domain, each team optimizes its own work and consequently on the surface the system seems to function. But something is lost: the overall vision, the understanding of mutual impacts, the sense of value generated.

For a long time this approach was sufficient. Today it shows its limits. Not because specialization is no longer needed, but because fragmentation has an increasing cost. When each person sees only one part, problems emerge late and responsibilities become diluted.

We work a lot, but we don't always understand enough.

This is why it is necessary to develop a different perspective—it does not mean knowing everything, but understanding enough of the system in which we operate to make more conscious decisions.

The point, after all, like all changes is cultural.

Organizations tend to respond to complexity by introducing tools: new procedures, new models, new tools. Sometimes they work, but they are not sufficient. Real change occurs when the way people interpret their work changes.

It happens when a team stops seeing itself as a set of separate functions and begins to reason like a system. At that moment conversations also change—indeed, we no longer speak only of activities, but of choices and questions become deeper, less automatic. They are not always comfortable, but they are more useful, making work more conscious.

In this scenario, Systems Engineering has a role that goes beyond tools. It is a reference that helps us remember that every decision fits into a network of relationships. And that without a shared understanding it becomes difficult to be truly effective.

There is then another aspect, often less discussed: the preparation of people.

For years we took for granted that technical training was sufficient to face the complexity of work. In part it still is. But today a limit emerges, dictated by the fact that complexity is not only technical but rather requires interpretation skills, the ability to make connections, and the capacity to manage ambiguity.

These competencies are not acquired automatically. They must be developed over time, through experience and also through the practice of systems thinking.

This is why systems thinking can no longer be considered an addition, but should be a foundational competency. It also requires a certain humility: accepting that your own perspective is partial and that understanding a system means above all knowing how to observe it.

If we want to build teams capable of facing change, it is not enough to select technical competencies. We need to create the conditions for people to develop this kind of vision, and this path does not begin in organizations, but with people themselves.

Every professional today has the possibility to broaden their way of seeing things. It is not a change that is imposed from above, but one that must start with the individual to have a real reflection going "upward." Systems thinking is a so-called soft skill that is built over time, in the way we approach problems and in the questions we choose to ask ourselves. When this happens, something truly changes—the way we work, decide, and collaborate changes.

And it is precisely at that moment that organizations and society change, not as a result of formal reorganization, but because they are made of people.