Change no longer waits. Why simply managing it is no longer enough.

Transformation is underway. The first friction points emerge: contested decisions, frayed cooperation, managers under pressure, teams struggling to keep up. In response, organizations ramp up communication, roll out training, and bring in change management support.

These measures are often necessary. But why wait for tensions to surface before examining what could have been prepared for?

When transformations overlap, success can no longer rely solely on the ability to troubleshoot issues on the fly. It depends just as much on what has been anticipated, tested, and built beforehand.

This is the core premise of UNREST: preparing organizations for continuous change, and their transformations before those changes put them to the test.

Change no longer fits between two periods of stability

The model is familiar: define a target state, organize the transition, support the people involved, and then stabilize the new operating model.

This logic still has its place. A merger, a reorganization, or the rollout of a new tool will always require structured change management. But it becomes insufficient when multiple transformations simultaneously demand the same people, the same resources, and the same decision-making bandwidth.

As early as 1999, Karl Weick and Robert Quinn distinguished between episodic change and continuous change. Their analysis shows that these two interpretations of change require different modes of intervention. It does not signal the death of discrete projects; rather, it invites us not to reduce every organizational evolution to a succession of isolated transitions.

An enterprise might roll out a new information system while simultaneously restructuring its operations, integrating artificial intelligence, and evolving its management model. Each program has its own timeline. The teams, however, live out their cumulative effects.

The unit of governance is the project. The unit of experience is daily work. It is in the gap between the two that friction takes root.

The problem isn’t change management. It’s change management as the sole answer.

Good change practitioners don’t wait for difficulties to materialize before stepping in. They conduct impact analyses, prepare managers, and engage stakeholders upstream.

The challenge is therefore not to pit outdated change management against a fresh methodology that has just discovered the virtue of anticipation.

Instead, the goal is to challenge a paradigm where human and organizational preparation remains secondary: the project is designed, deadlines are set, resources are committed, and only then do we figure out how to secure buy-in and support execution.

By that stage, certain fundamental questions become difficult to reopen:

• Have the assumptions justifying the project been sufficiently tested?
• Can the organization meet these demands on top of its existing commitments?
• Are leaders prepared for the friction they will have to navigate?
• Which existing practices and rules risk contradicting the announced transformation?

Support can never indefinitely compensate for a lack of preparation.

From firefighting to prevention

The difference between a reactive mindset and a preventive one is visible in the questions we ask.

Prevention does not mean eliminating all friction. It means spotting what can be spotted earlier and preserving room for maneuver.

The research of Bernerth, Walker, and Harris on change fatigue illustrates the importance of this vigilance. Their study develops an initial measure of the phenomenon and examines its relationship with burnout, organizational commitment, and turnover intentions. The multiplication of changes deserves to be studied as a cumulative lived experience, not merely as a series of independent programs.

From this perspective, preparation may involve building skills, but it can also mean slowing down a rollout, shelving a priority, or simplifying a process.

Prevention is not about teaching people to endure more and more. It is about rethinking what the organization asks of them.

Anticipating is not predicting

A proactive approach is not built on the promise of knowing the future.

A diagnostic does not erase uncertainty. A simulation does not predict a leader’s behavior with absolute certainty. A failure scenario does not prove that failure is inevitable.

Their value lies elsewhere: making assumptions debatable before they become binding commitments, exploring multiple responses, and identifying the conditions necessary for action.

Two forms of preparation must therefore be articulated:

1. The first concerns identifiable situations: an upcoming reorganization, a sensitive decision, a predictable conflict between objectives.
2. The second concerns what cannot be precisely anticipated: knowing how to revise a decision, asking for help, voicing dissent, cooperating despite incomplete information, or finding maneuvering room under pressure.

It is not enough to prepare for the change we know. We must also build the capabilities required to face the change we cannot yet see.

Being ready for a project vs. becoming capable of change

Preparing for a specific transformation and developing a lasting organizational capability are linked, but they are not the same thing.

In his theory of organizational readiness for change, Bryan Weiner distinguishes between shared commitment to implementation and collective belief in the capability to execute it. This readiness depends heavily on task perception, available resources, and context.

On another level, research on organizational change capability examines the capacities an organization can mobilize across multiple projects. While this field encompasses various definitions, it forces a decisive question: what does an organization retain from one transformation to better approach the next?

This distinction shapes our approach to change enablement.

An organization can carefully prepare a project without having developed deep adaptive capacity. Conversely, having experienced leaders and competent teams does not exempt you from examining the specific demands of the next transformation.

You have to work on both.

Building capabilities before they become critical

UNREST’s first response is the long-term development of cognitive, behavioral, and collective capabilities.

Diagnostics, organizational development consulting, coaching, and targeted programs serve this exact purpose. The goal is not merely to transmit theoretical knowledge about change, but to cultivate what individuals and groups can actually do when put to the test.

For example:

• Inviting objections before validating a decision
• Adjusting management style in the face of an unusual situation
• Addressing a disagreement without damaging cooperation
• Identifying overload and arbitrating priorities
• Experimenting with a new practice without waiting for complete certainty

These behaviors do not depend solely on individual traits. The COM-B model highlights the joint role of capabilities, motivation, and environmental opportunities. Training people in autonomy while leaving the rules that block it intact leaves part of the problem untouched.

At UNREST, the S.H.A.R.P.® model structures this approach: examining initial conditions, building engagement, targeting behaviors, developing them through active work, and evaluating their evolution.

Preparation begins upstream, but it continues in real work. It is not a box to check once and for all.

Stress-testing a transformation before launching it

Our second response is targeted preparation built around a defined project or situation.

This is the role of the UNREST Suite, which combines behavioral science and artificial intelligence across three autonomous yet complementary digitized protocols.

TST: Stress-testing the project

The Transformation Stress Test offers an ex ante diagnostic based on a structured premortem. It examines project vulnerabilities, critical assumptions, and divergences among stakeholders. The goal is not to grant a green light, but to identify areas that need deeper review or correction before commitment.

OST: Preparing the organization

The Organizational Stress Test confronts the demands of the transformation with the organization's agility and resilience. The objective is to shed light on adaptive capacities, tension zones, and reinforcement needs. The question is not just whether the project is desirable, but under what conditions the organization can actually sustain it.

LST: Preparing leadership

The Leadership Stress Test delivers a personalized behavioral simulation based on a real, upcoming situation. It helps decision-makers explore potential responses, examine instinctive patterns, and prepare alternative options. The simulation serves as a tool for reflection and preparation, not a deterministic prediction of behavior.

These three scales complement each other: a project may be sound yet too demanding for the organization; an organization may have resources without its leadership trade-offs being adequately prepared.

Instruments don’t replace judgment. They sharpen it.

The value of preparation does not lie in the mere production of a report, a mapping exercise, or a simulation. It depends entirely on what is done with it.

Instrumented behavioral consulting involves framing the question, choosing the appropriate protocol, protecting the conditions for participation, separating data from assumptions, and testing interpretations. It then translates these insights into governance trade-offs, development priorities, and prepared actions.

The return to reality is indispensable: Which difficulties were anticipated? Which ones were missed? Were the prepared responses practical? What needs to change?

In this way, consulting builds capabilities while supporting decisions. Digitized protocols make hidden vulnerabilities visible and examinable. Their integration aims to improve current preparedness while feeding continuous learning for the future.

Prepare more to endure less

Change management will always remain necessary. No amount of preparatory work will eliminate the unforeseen, the tensions, or the need to adjust a transformation midstream.

But it should no longer be the sole response to an organization under continuous pressure.

Waiting for difficulties to arise before developing the capabilities required to solve them means learning under conditions where maneuvering room is at its lowest.

UNREST champions a different priority: stress-testing projects, reinforcing organizational capabilities, and preparing behaviors before they are placed under strain.

Change is here to stay. Preparation must become a continuous practice.

Stop discovering in the heat of the trial what you should have prepared beforehand.

Scientific references

The following works illuminate the mechanisms presented here. They do not, on their own, constitute a validation of the entire UNREST offering or each of its individual protocols.

• Weick, K. E., & Quinn, R. E. (1999). Organizational Change and Development. Annual Review of Psychology, 50, 361–386.
• Bernerth, J. B., Walker, H. J., & Harris, S. G. (2011). Change Fatigue: Development and Initial Validation of a New Measure. Work & Stress, 25(4), 321–337.
• Weiner, B. J. (2009). A Theory of Organizational Readiness for Change. Implementation Science, 4, 67.
• Supriharyanti, E., & Sukoco, B. M. (2023). Organizational Change Capability: A Systematic Review and Future Research Directions. Management Research Review, 46(1), 46–81.
• Michie, S., van Stralen, M. M., & West, R. (2011). The Behaviour Change Wheel: A New Method for Characterising and Designing Behaviour Change Interventions. Implementation Science, 6, 42.

Complementary methodological reference

• Klein, G. (2007). Performing a Project Premortem. Harvard Business Review, September.