Organisational change arrives in many forms. Sometimes it’s a restructure that moves reporting lines. Sometimes it’s a new system that replaces familiar processes. Sometimes it’s a shift in strategy that makes people question what they’ve been doing for years. What I’ve noticed across these situations is that the actual change – the new structure, the new tool, the new direction – is rarely the real problem. The problem is almost always what happens to people’s sense of stability and competence when that change lands.
When you manage a team during change, you’re not really managing the change itself. You’re managing the gap between where people are now and where they need to be. That gap has emotional weight. It has practical friction. And it has a timeline that rarely matches what leadership expected when they announced the change three months ago.
I’ve seen teams move through change smoothly and teams fall apart during the same restructure. The difference is rarely about how well the change was planned at the top. It’s about what happens in the space between announcement and normal operation. That space is where managers either stabilise their teams or let them drift into confusion.
The First Few Weeks Are Not About Acceptance
One of the most common mistakes I’ve observed is treating the announcement period as if it’s a moment for people to accept the change. It isn’t. The first few weeks are a period of shock, information-gathering, and self-protection. People are asking themselves questions you can’t answer yet: Will I still have a job? Will I have to move teams? Will my skills still matter? Will I have to learn something completely new?
During this period, clarity matters more than enthusiasm. If you try to sell the change as positive before people understand what it actually means for them, you lose credibility. I’ve watched managers spend energy on motivational messaging when what their teams actually needed was a straightforward answer to basic questions.
What works better is being direct about what you know and what you don’t know. “Here’s what’s changing. Here’s what stays the same. Here’s what we’re still waiting to hear from leadership about.” That honesty creates a small pocket of stability in an uncertain situation. People can work with uncertainty if they know you’re not hiding information from them.
Resistance Is Usually Information, Not Obstruction
When people push back on change, the instinct is often to override the resistance or to explain why the change is necessary. Both approaches miss what’s actually happening. Resistance usually points to something real: a process that will break, a skill gap that hasn’t been addressed, a timeline that’s unrealistic, or a loss that hasn’t been acknowledged.
I’ve seen a team resist a new system because they understood something the implementation team didn’t: the new system couldn’t handle the volume of work they processed daily. The resistance wasn’t about fear of change. It was about a genuine operational problem. When that was finally addressed, the resistance dissolved.
The other kind of resistance is about loss. A restructure might make operational sense, but it also means the end of a team dynamic that worked well, or the loss of a manager people respected, or the dissolution of a familiar routine. That loss is real even if the change is necessary. Ignoring it doesn’t make it go away. It just makes people feel unseen.
When you listen to resistance without immediately defending the change, you often learn something useful. You also signal to your team that their concerns matter and that you’re not just a messenger for decisions made elsewhere. That distinction is important for maintaining trust.
The Competence Dip Is Predictable and Manageable
Every significant change creates a temporary drop in team productivity and confidence. People who were efficient suddenly feel slow. People who knew their role suddenly feel uncertain. This isn’t a sign that the change was wrong. It’s a normal part of learning something new.
What I’ve noticed is that teams that acknowledge this dip explicitly handle it better than teams that pretend it isn’t happening. If you say to your team, “For the next month, we’re going to be slower. That’s expected. We’re learning,” you create permission for that slowness. People stop feeling like failures and start feeling like they’re in a learning phase.
The timeline for moving through this dip varies depending on how complex the change is. A new reporting structure might take weeks. A new software system might take months. A fundamental shift in how work gets done might take longer. The key is not to panic during the dip and not to declare victory too early. I’ve seen teams told they’ve “adjusted” to a change after two weeks when they’re really just in the shock phase.
During this period, your role shifts slightly. You’re less focused on output and more focused on building competence. That might mean allocating time for training, pairing people with colleagues who understand the new system, or simplifying workload temporarily so people can focus on learning. It’s an investment that pays off when the team regains speed.
Communication Needs Repetition, Not Variety
One pattern I’ve observed is that managers often feel they’ve communicated something when they’ve said it once. They mention the change in a team meeting, send an email, maybe bring it up again. Then they feel like they’ve done their part and move on. But people are processing change at different speeds. Some people need to hear something multiple times before it lands. Some people miss the first communication entirely because they were distracted or absent.
Repetition isn’t about being annoying. It’s about reaching people where they are. I’ve found that saying the same thing in different formats – a team meeting, a one-on-one conversation, a written summary, a check-in question – actually helps information stick. It also gives people multiple chances to ask questions or voice concerns.
What doesn’t work as well is varying the message. If you say the change means one thing in a meeting and something slightly different in an email, people notice. They wonder what’s really true. Consistency in the core message, repeated across different channels, builds understanding.
One-on-One Conversations Are Where Real Work Happens
Team meetings are necessary, but they’re not where people actually process change. That happens in one-on-one conversations. In those conversations, someone might reveal that they’re thinking about leaving because they don’t see a future for themselves in the new structure. Or they might explain that they’re worried about a specific skill gap. Or they might ask a question they wouldn’t ask in front of the group.
I’ve learned that scheduling one-on-ones specifically to talk about the change, rather than waiting for it to come up, signals that you take people’s concerns seriously. It also gives you a chance to understand how each person is being affected and what they need from you.
During these conversations, listening matters more than reassuring. If someone is worried about their role, the instinct is to say, “Don’t worry, you’ll be fine.” But what they actually need is to be heard. They need to say what they’re worried about and have you take it seriously. Sometimes that means you can address the worry directly. Sometimes it means you need to escalate something to leadership. Sometimes it just means acknowledging that the change is difficult for them.
Protecting Your Team’s Stability Creates Space for Change
One of the most valuable things a manager can do during change is to hold steady on the things that don’t need to change. If your team’s processes are being disrupted by a restructure, keeping their day-to-day routine as consistent as possible gives them something familiar to hold onto. If standards are shifting across the organisation, maintaining clear expectations for your team prevents additional confusion.
This doesn’t mean resisting all change or protecting people from necessary disruption. It means being intentional about what you’re asking people to adjust to. If they’re learning a new system, don’t also change their meeting schedule. If they’re moving to a new team, don’t also change how they report on their work. Give them one major thing to adjust to at a time when possible.
I’ve also noticed that teams move through change more effectively when they have a sense of continuity in their manager. If you’re visibly stressed or frequently absent or constantly changing your mind about priorities, that instability spreads. If you’re present, calm, and clear about what you’re doing, that steadiness helps people find their footing.
Change is a normal part of organisational life. The teams that handle it well aren’t the ones that love change or embrace it enthusiastically. They’re the ones that understand what’s actually happening, acknowledge both the practical and emotional dimensions of the shift, and have a manager who stays present and clear throughout the process. That’s not a formula. It’s just what I’ve seen work repeatedly in real situations.
