When Organizations Make People Carry Change

Human sustainability begins where resilience stops being used as a substitute for thoughtful system design.

Organizations often speak about transformation, agility, resilience and sustainability, but many of them quietly transfer the real work of adaptation onto individuals.

They redesign structures, introduce new tools, accelerate processes, change priorities, add platforms, redefine expectations and call all of it progress, while the actual psychological, cognitive and relational work of making those changes livable is left to people who still have to perform, decide, communicate, care, deliver and remain “professional” inside a system that has often restructured faster than it has explained itself.

For example, introducing a new organizational structure every eleven months, as if eleven months were a long enough period for a structure to be understood, inhabited, tested, corrected and honestly evaluated.

And perhaps in a culture addicted to speed, eleven months may already sound like a reasonable amount of time. But at the level of organizational design, human coordination, role clarity, trust, decision-making habits and the slow learning through which people actually discover how a structure works in practice, eleven months can easily become only a cosmetic cycle – long enough to redraw boxes, rename departments, shift reporting lines, update presentations and create the visible impression of progress, but not necessarily long enough for the organization to learn whether the change has created clarity, value, better cooperation or simply another layer of confusion.

And then, when people hesitate, slow down, ask too many questions, hold on to familiar routines, become skeptical, confused, tired or less enthusiastic than the transformation narrative expects them to be, the explanation often becomes strangely simple: they are resistant to change.

Not because anyone has seriously examined what was actually asked of them, how much sense-making was required, how many contradictions they had to absorb, or how much invisible coordination was needed to keep the work moving, but because it is easier to individualize the friction than to admit that the system may have transferred the cost of poor design onto the people expected to carry it.

And somewhere in that conversation, another sentence usually appears: “We are in a fast-changing industry.” As if that should end the discussion and explain everything.

As if transportation, mining, logistics, pharmaceuticals, finance, technology, education, retail, consulting or any other sector were now exempt from the responsibility of designing work thoughtfully, simply because the market is moving, the client is demanding, the regulation is changing, the technology is accelerating, or the competition is becoming more aggressive.

But perhaps this is one of the great illusions of contemporary organizational life: that because everything is changing, everything must constantly be redesigned; that because the environment is dynamic, the internal system must remain in permanent agitation; that because speed is valued, reflection becomes a luxury; and that because productivity must be visible, movement begins to imitate progress.

So we create new tools before people have understood the previous ones. We introduce new processes before old contradictions have been resolved. We design new organizational structure before we see true results. We ask for agility while preserving structures that punish honest feedback. We speak about innovation while exhausting the very people whose attention, judgment and creativity are needed for innovation to happen.

We call people adaptable only when they silently absorb the instability, and resistant when they finally reveal the cost of absorbing it. And in that way, the idea of a “fast-changing industry” can become less a description of reality and more a managerial shield:

a sentence used to protect the system from the uncomfortable question of whether all this change is actually necessary, coherent, well-designed, or simply another form of organized restlessness.

And behind that managerial shield, there is often another hidden anxiety: “What do we do if we are not constantly changing? How do we prove that we are progressing?”

Not every movement inside an organization deserves to be called transformation, and not every acceleration is proof that the system is becoming more mature, more intelligent or more capable; nor does it reflect the genius of a person in charge; sometimes it is only a sign that the organization has become addicted to motion, to the visible appearance of productivity, to the comfort of announcing something new before it has understood what the previous reorganization actually did to people, processes, attention, trust and the quality of work itself.

We have all witnessed that not every new process improves work, not every platform creates efficiency, not every reorganization brings clarity, and not every strategic shift produces real development; sometimes it only redistributes confusion, creates additional layers of interpretation, leaves people with the silent task of connecting decisions that were made at one level with consequences that appear at yet another and more “paper”. The newly added layer , most of the time, does not solve the old contradiction; it only moves it somewhere else.

And this is why I think we have to be much more careful with the way we describe people as resistant to change.

Because sometimes people are not resisting the future at all. Sometimes they are resisting confusion that has been packaged as progress, noise that has been presented as urgency, poorly translated strategy that has arrived into daily work without enough context, and the expectation that they should continuously make sense of decisions that were never properly made sense of at the system level.

Then the image of resistance is actually an attempt to preserve coherence. Sometimes what looks like hesitation is an attempt to understand what is truly being asked.

Sometimes what looks like skepticism or a negative attitude is not a lack of openness or positivity, but a memory of too many previous “new ways” that were announced with certainty, implemented with pressure, and then quietly abandoned when the next wave of transformation arrived.

And sometimes a tired person is not someone who lacks resilience. That tired person may be someone who has been used for too long as the place where the system resolves its own unfinished thinking.

And this is where the conversation about human sustainability has to become more serious than the popular language of well-being, balance, motivation or individual resilience.

Because if human sustainability remains only something we discuss through workshops, benefits, mental health initiatives, occasional training sessions or inspirational communication, while the basic design of work continues to consume people’s attention, judgment, emotional regulation and adaptive capacity faster than it restores them, then we are not really dealing with sustainability.

Human sustainability, in this sense, is not an additional well-being layer placed on top of work; it is the question of whether the work system itself is designed in a way that preserves or consumes human capacity.

We are decorating exhaustion. Giving it better language to mask the same old demand: please continue carrying what the system has not learned how to organize.

Human sustainability should not mean that people become endlessly capable of surviving unclear priorities, permanent restructuring, fragmented communication, unrealistic expectations and leadership decisions that arrive as finished conclusions but have to be translated by everyone else.

It also means that organizations should begin to ask different questions.

• Not only: Are people resilient enough? But also: Is this change coherent enough?
• Not only: Do people have the right mindset? But also: Have we created enough clarity for that mindset to be useful?
• Not only: Why are people resisting? But also: What kind of friction have we designed into the system?
• Not only: How do we make people more adaptable? But also: How much adaptation are we asking from them, how often, and at what cost?

You see, it is easy to blame inefficiency on someone else, especially when the harder question is whether the system itself has created the conditions in which inefficiency becomes almost inevitable.

Because every movement consumes capacity. Even the good, the necessary or change that is strategically correct. A well-designed adjustment still requires attention, learning, emotional adjustment, coordination, decision-making and time. But a poorly designed change requires all of that plus something more: people have to compensate for the missing thinking of the system itself.

They have to interpret what was not clearly explained, to reconcile contradictions that were not resolved, to maintain relationships while roles are unclear, to continue producing results while priorities are unstable, to protect the client, the team, the process, the reputation, and often the organization itself from the consequences of decisions that were introduced faster than they were integrated.

And do it as if this were simply their normal way of working for the past two years. If they do this well enough, the system may not even notice the cost: work will continue, reports are submitted, meetings happen, deadlines are met… and the organization looks functional.

But that visible functionality may be supported by a layer of invisible human effort that does not appear in dashboards, project plans or transformation narratives.

And this is exactly where many organizations misunderstand productivity. They measure what moved, what was launched, what was implemented, what was reported, what was reorganized, what was digitalized, what was communicated… but rarely how much sense-making was required to make it all work, how much trust was spent, how much attention was fragmented or how much informal coordination was needed.

Nor will they notice, how many managers translated unclear strategy into tolerable daily instructions. How many HR professionals softened the human consequences of decisions they were not invited to shape or how many employees stopped asking questions, not because they understood, but because they learned that asking questions would be interpreted as negativity.

And when this becomes a pattern, the organization may still look active, modern, dynamic and ambitious from the outside, but internally it may be teaching people a very different lesson:

do not expect coherence, do not expect continuity, do not expect the system to remember what it asked from you last year, and do not expect every change to be evaluated before the next one arrives.

That is not agility, that is institutionalized restlessness.

And people are people, they can live inside restlessness for a while. Especially capable people, responsible people and those who care. They will bridge gaps, create informal order, protect others from confusion, keep the work moving and give the system more time than it deserves.

But if the organization keeps interpreting that effort as normal, instead of seeing it as a warning signal, then eventually the strongest people may become the most tired ones – and often, the organization only recognizes their value when replacing them becomes expensive.

---

This text was originally published on LinkedIn as part of the Invisible Bridges newsletter and is republished here as part of my professional blog archive.