The Anxiety of Change
Most of us don’t get anxious about change in the abstract; we get anxious when change shows up in our workflow, our visibility, and our sense of control. When a new system increases transparency or introduces innovation, it often feels less like “progress” and more like “I’m about to be judged.”
This isn’t a character flaw; it’s how the human brain responds to uncertainty and perceived threat. The good news is that there are specific, practical ways to respond—whether you’re a front-line team member, a manager, or a senior leader who can’t share every detail.
When You’re Not the Leader
When you’re not the one making the decisions, change can feel done to you, not with you. The first move is to separate the story in your head from the facts in front of you.
A few grounded responses you can choose on purpose:
Ask curious questions instead of making assumptions: “What problem is this new workflow trying to solve?” or “How will we know it’s working?”
Name what you’re worried about in neutral language: “I’m concerned I’ll miss something in the new system and that will delay care—can we walk through a couple of examples?”
Notice where the change might actually protect you: tools that increase visibility also make it easier to show your workload, spot bottlenecks, and document that you did your part.
You may not control the decision, but you do control your posture: you can be the person who participates, asks for clarity, and helps catch the rough edges early. That is quiet leadership, even without a title.
Your Role as a Manager
Managers get squeezed in every change: your team is looking for safety, and senior leadership is looking for movement. Your obligation is to both—and you can’t fully satisfy either by pretending nothing is happening.
To your direct reports, you owe:
Clarity where you can give it. Explain the “why,” the timeline, and what is not changing, in plain language.
Psychological safety: repeated permission to ask “basic” questions, admit “I don’t get this yet,” and surface problems without being labeled resistant.
Realistic support: training time, a slower ramp-up on productivity expectations, and a plan for who helps when something breaks in the new workflow.
To senior leadership, you owe:
Honest signal, not noise: what’s actually working, where people are stuck, and which risks are emerging.
Solutions, not just complaints: “Here’s the pattern I’m seeing, here’s the impact, here are two options we could try.”
Follow-through: once decisions are made, model commitment even if you personally would have chosen a different path.
Think of yourself as a translator. Your job is to translate strategy into daily reality for your team, and daily reality back into usable information for leadership.
As a Leader: Mitigating Stress While Getting Cooperation
Leaders can’t always share every detail about why changes are happening—there are contractual issues, HR realities, and strategic decisions that aren’t ready for prime time. But “I can’t tell you everything” is not the same as “I can’t tell you anything.”
Here are levers you can pull:
Say what you can say, clearly and repeatedly: the purpose of the change, the guardrails, and how success will be measured.
Acknowledge the emotional reality: “I know more visibility can feel like more scrutiny. That’s real. My commitment is to use this data to improve the system, not punish individuals.”
Involve people where it’s safe to involve them: ask front-line staff to help define workflow steps, pilot new processes, or identify practical training needs. Engagement lowers resistance.
Make it safe to surface problems: explicitly thank people for raising issues and separate “the person” from “the process” when something goes wrong. That’s psychological safety in action.
You’re not promising comfort; you’re promising fairness, transparency where possible, and a real voice in how the change lands in day to day practice. That’s usually enough to move a reasonable team from “Why are you doing this to us?” to “Okay, how do we make this work?”
As a Human: Managing Your Own Stress
Change that you don’t fully understand will always create some tension in your nervous system. You can’t think clearly about workflows if your body is stuck in fight or flight.
A few simple practices that actually help:
Name it: “I’m anxious about looking incompetent in this new system.” Just putting it into words reduces the physiological spike.
Shrink the time horizon: Instead of “How will I survive this new software forever?” ask, “What’s one thing I can learn or practice this week?”
Protect the basics: sleep, food, movement, and a few minutes of quiet are not luxuries; they are your buffer against burnout during change.
Find your non-negotiable value: technology and visibility can change tasks, but they don’t replace your judgment, relationships with referral sources, or the trust you build with patients.
You do not have to love the change to engage with it. Your goal is to stay resourced enough—mentally and physically—to make thoughtful choices instead of reactive ones.