Dealing with fear during strategic change processes in organizations.
This Change File comes from our consulting practice: We are sharing it to support HR, change, and organizational development managers, not with heroic stories, but with what really happens in reality.
The problem
We hear the same thing over and over again in projects: “I'm afraid of what's coming.” Two things are striking here.
Firstly, the change is often not yet concrete. There are no decisions on job cuts, no clear new targets, sometimes not even a final project plan, and yet the fear is already there. It seems to anticipate possible overload, loss of control, “another change debacle,” and the suspicion that something unpleasant will happen at some point.
Secondly, those responsible for change take this fear very personally. Many feel it is their job to “take away” their colleagues' fears. This is human nature and, unfortunately, a sure-fire way to become overwhelmed. After all, fear rarely has a single cause. It is fed by individual biographies, experiences, role models, stress, comfort, and sometimes also by a very understandable unwillingness to really change one's own way of working.
In practice, this looks like this: Managers and project leaders invest enormous energy in reassuring people, explaining things again, promising transparency, and taking every emotional response as a task. And yet the feeling remains: “It's not enough. I'm not reaching them.” This is exactly where the system tips into an unproductive dynamic: some externalize their fear, others internalize it.
Why is fear so persistent in such situations?
A condensed look at typical psychological causes that we see time and time again:
- Threat to security and habit: The unknown triggers alarm, routines provide predictability.
- Uncertainty and loss of control: “I can't control what happens” greatly increases fear.
- Fear of not being good enough: Worry about new demands, fear of failure, fragile self-efficacy.
- Bad previous experiences: Previous changes “ended in disaster,” the nervous system remembers.
- Fear of loss: Status, influence, competence, identity, sometimes simply: “I'm losing my ground.”
- Reactance: Change “from above” without participation is experienced as a threat to autonomy.
- Biography and socialization: Personal responsibility was never really practiced, so new things seem overwhelming more quickly.
- Pre-existing psychological stress and rumination: High basic tension makes any change “too much.”
These causes are real. But they lead to a crucial question: Who is responsible for what, and who is not?
Our hypothesis
The system would make significant progress if... Those responsible for change defined their task more clearly: not to “take away” fear, but to design a professional process in which people become capable of acting and individual fears are dealt with through individual responsibility.
This is not a cold “don't be so silly.” On the contrary: it is a mature form of care. Because fear must be taken seriously, but it cannot be delegated. Organizations can create conditions that reduce fear (transparency, participation, learning spaces). But they cannot control the inner experience of each individual. Anyone who tries to do so takes on a burden that cannot be borne and, incidentally, reinforces the message: “You can't do it alone.”
Two guidelines are crucial here:
- Individual fear needs to be dealt with individually. The individual is not to blame for their fear, but they are responsible for dealing with it.
- Professional change management is not optional. Especially when change is inevitable, process quality, participation, and learning architecture must be particularly good.
Our solution/intervention
In our mandates, an intervention that deliberately takes a two-pronged approach has proven successful: process excellence in change and personal responsibility in dealing with fear. Not as an appeal, but as a system design.
1. Clarify roles: “I am not responsible for your fear, I am responsible for the framework.”
The most important step often happens in a single conversation with project management and leadership: a clear distinction between responsibility and accountability.
Responsibility of those responsible for change: goals, decision-making processes, participation formats, communication, resources, learning opportunities, protection against overload.
Not their responsibility: “creating” emotional states (security, confidence, freedom from fear).
This clarification provides immediate relief. And it changes the tone: away from reassurance and toward serious work on the ability to act.
2. “Defog” fear: From global feelings to concrete risks
“I'm afraid” is often a collective term. In workshops, we therefore use short formats that do not treat fear, but make it more concrete:
- What exactly? (Name the scenario)
- What is likely, what is possible, what is fantasy?
- What can I influence? What can't I influence? (Circle of control)
- What support do I need, and what is my next step?
- This translation alone lowers the temperature. Fear is transformed from a fog into something that can be worked on.
3. Send “safe signals”: Transparency that doesn't reassure, but provides orientation
Neuroscience can easily explain why reliable guidance reduces fear: the brain reacts to uncertainty with alarm. “Safe signals” are therefore not just nice words, but structure.
What works in large organizations:
- Clear rhythm: fixed communication rhythms (“update every other Wednesday, even if there is little news”)
- What we know/don't know: mark openly instead of filling gaps with optimism
- Test before scaling: pilot logic instead of “big bang” (“We try, learn, adapt”)
- Take overload seriously: link the pace of change to realistic capacities
This is a professional imposition: not knowing everything, but managing it cleanly!
4. Participation as a way of dealing with fear: don't just listen, let people shape things
Many fears are closely linked to loss of control and threats to autonomy. Participation is therefore not “nice to have,” but a central intervention.
From practice (and well suited to many organizational contexts):
- Pilot projects instead of big bang: test first, then roll out, learn visibly
- Dialogue formats: World cafés, future workshops, feedback rounds, with clear feedback (“What was adopted, what was not, and why”)
- Visibly integrate leadership: don't delegate, but be present, including “We don't know everything yet”
- Change competence as a separate learning subject: Changeability itself becomes a project, not a by-product
The last element in particular is often underestimated: if people have not learned to actively cope with change, no project plan will help.
5. Cognitive relief: anxiety decreases when working memory is not overloaded
Complex changes quickly lead to overload: new tools, new processes, new terms, new rules. When working memory is full, the fear of making mistakes increases.
We therefore consistently focus on:
- Handouts, checklists, standard processes (small, suitable for everyday use)
- Practical on-the-job training instead of PowerPoint training
- Repetition and routines: shadowing, short reflection rounds, fixed practice windows
This may sound trivial, but it is often the difference between “I can do this” and “This is overwhelming me.”
6. Create social and psychological security: Allow criticism without embarrassment
In hierarchical systems (and this includes many government agencies), the fear of losing face is great. That's why we need formats in which uncertainty can be expressed without being sanctioned.
We often work with:
- Hierarchy-free exchange formats (mixed, moderated, clear framework)
- Change champions/promoters: respected colleagues as translators and companions in everyday life
- Clear contact persons for specific questions + information portal: being able to ask questions without “standing out unpleasantly”
The result
In projects where this logic is consistently implemented, “fear” as a feeling rarely changes, but the relationship to fear does. And that is crucial.
A typical picture after a few weeks: In a large group, someone no longer just says “I'm afraid,” but rather, “I see three risks: overload in the team, unclear roles, and the concern that I won't be able to master the new system. I need a learning loop for this and someone to look over my shoulder for the first two weeks.” That's a different state. Not fearless, but capable of action.
At the same time, those responsible for change feel a noticeable sense of relief: they no longer have to “deliver emotionally,” but rather provide a framework. This reduces pressure, prevents overworking, and makes them clearer in their communication. Paradoxically, this often increases trust: not because everything is talked up, but because it is managed cleanly.
And another effect regularly becomes apparent: when participation is taken seriously and pilot logic takes effect, small successes (“quick wins”) arise that make the new more attractive. This does not motivate everyone, but enough to create a pull effect. Fear is then not argued away, but relativized through experience.
In the end, we are left with three very practical core messages:
- Fear is a signal, not a call for reassurance.
- Those responsible for change are responsible for process quality, not for inner states.
- Personal responsibility can be learned if organizations make it structurally possible.
