Navigating Reorgs: How to Be Your Team's Steady Anchor

The Slack message came on a Tuesday at 4:47 PM. "Org announcement tomorrow at 10 AM all-hands. Please make sure your teams attend." No context. No preview. Just that ominous, corporate-vague sentence that every engineer learns to dread.

Within minutes, my DMs exploded. "Do you know what's happening?" "Is our team being split up?" "Am I getting a new manager?" "Should I be worried?"

I did know what was happening. I'd been in a confidential meeting the week before. I knew that our team was being restructured, that two people would report to a different manager, and that our scope was changing significantly. But I wasn't allowed to say any of that.

So there I was: caught between my obligation to leadership confidentiality and my obligation to the humans who trusted me to be honest with them. That tension is one of the most uncomfortable parts of middle leadership, and if you've felt it, you know exactly what I mean.

Why Reorgs Hit Engineers Differently

Engineers build deep context in their domains. They invest months understanding systems, building relationships with specific collaborators, developing expertise that's highly contextual. A reorg can wipe all of that out overnight.

When a marketing team reorgs, people mostly keep doing similar work with different reporting lines. When an engineering team reorgs, people might suddenly be working on completely different codebases, with different teammates, solving different problems. The dislocation is deeper.

Add to that the fact that many engineers chose their specific team deliberately — for the tech, the people, the problems. A reorg removes that agency. It says: the choice you made doesn't matter anymore. We're choosing for you now.

Understanding this is the first step to leading through it with empathy.

The Three Phases of a Reorg (And What Your Team Needs in Each)

Phase 1: The Rumor Period

This is the worst phase. People know something is coming but don't know what. Anxiety fills every information gap with worst-case scenarios. Productivity drops. Hallway (or Slack) conversations become consumed by speculation.

What your team needs: Honest acknowledgment of the uncertainty.

You probably can't share details. But you can say: "I know there's uncertainty right now, and I understand that's stressful. Here's what I can tell you: [whatever you're allowed to say]. Here's what I don't know yet: [be honest]. Here's what I'm doing: [advocating for the team, gathering information, etc.]. And here's my commitment: I will tell you everything I can, as soon as I can."

That's not much. But it's infinitely better than silence or deflection.

What NOT to do: Don't pretend you don't know anything when you do. People can tell. It breaks trust in a way that's very hard to rebuild.

Phase 2: The Announcement

The change is communicated. Now people are processing. Some are relieved. Some are angry. Some are numb. Most are trying to figure out what this means for them personally.

What your team needs: Individual attention.

Within 24 hours of a reorg announcement, I schedule a one-on-one with every person on my team. Not a group meeting. A private conversation where they can ask questions, express feelings, and get as much clarity as I can provide.

My script for these conversations:

1. "How are you feeling about the announcement?" (Then shut up and listen. Really listen.)
2. "What questions do you have?" (Answer honestly. If you don't know, say so.)
3. "Here's what I know about how this affects you specifically." (Be as concrete as possible.)
4. "Here's what I'm going to do to support you through this transition."
5. "What would help you most right now?"

What NOT to do: Don't lead with corporate cheerfulness. "This is great for the company!" might be true, but it dismisses the very real emotional disruption your team is experiencing. Acknowledge the loss before selling the vision.

Phase 3: The Transition

The reorg is official. Now begins the messy work of actually making the new structure function. New reporting lines, new collaborators, new processes, new context to build.

What your team needs: Stability in the things you can control.

You can't control the org structure. But you can control:

• How you run your one-on-ones (keep them consistent)
• Your availability and responsiveness
• Team rituals and norms
• The clarity of their immediate priorities
• Your advocacy for their growth in the new structure

Phase	Duration	Primary Emotion	Your Role
Rumor Period	Days to weeks	Anxiety, speculation	Honest anchor
Announcement	24-48 hours	Shock, loss, anger, relief	Individual attention
Transition	4-8 weeks	Disorientation, adjustment	Stable foundation
New Normal	Ongoing	Gradual comfort	Future-focused support

What I Wish I'd Known: The Emotional Labor

The part nobody prepares you for is how exhausting this is emotionally. You're processing your own feelings about the reorg while simultaneously being everyone else's emotional support. You might be losing teammates you love. You might be gaining new responsibilities you didn't ask for. You might be scared about your own position.

And you have to hold all of that while showing up as steady, calm, and present for your team.

This isn't sustainable alone. You need your own support system — a peer, a mentor, a coach, a partner at home — who can hold space for your feelings without judgment. You cannot pour from an empty cup, and reorgs drain cups fast.

Advocating for Your Team (Without Being Difficult)

One of your most important roles during a reorg is advocacy. You're the one who knows your people — their strengths, their growth areas, their career aspirations, their personal situations. Leadership making reorg decisions often doesn't have this context.

Here's how to advocate effectively:

Be specific about impact. Don't say "my team won't like this." Say "Sarah has been building deep expertise in the payment domain for 18 months. Moving her to a different area now would waste that investment and likely frustrate her enough to leave."

Propose alternatives. Don't just object — offer solutions. "I understand the need to consolidate. What if we kept Sarah on payment systems but had her report to the new team? Same structural change, preserved domain expertise."

Choose your battles. You can't fight every aspect of a reorg. Pick the 2-3 things that matter most for your team's wellbeing and effectiveness, and spend your political capital there.

Document the commitments. When leadership makes promises during reorg discussions ("nobody's getting laid off," "scope will stay the same"), write them down. If those promises get broken later, you'll need the receipts to protect your team.

The Things You Should Never Do

Don't badmouth the decision to your team. Even if you disagree with the reorg. Even if you think it's stupid. Your team takes their emotional cues from you. If you're cynical and resentful, they will be too — but without your context, they'll be worse.

You can say: "This wasn't my first choice for how I'd structure things." You cannot say: "Leadership has no idea what they're doing." The first is honest. The second is destructive.

Don't make promises you can't keep. "Don't worry, nobody's leaving the team" — and then two people get moved. Now you're a liar. Only commit to what you actually control.

Don't disappear. The worst thing a leader can do during a reorg is become less available. Be more present, not less. Check in more frequently. Be visible. Your presence is a signal of stability even when everything else is shifting.

Don't pretend it doesn't affect you. Showing appropriate vulnerability — "This is hard for me too. I'm going to miss working with those team members" — builds trust. Being a robot doesn't.

After the Storm: Building Forward

Once the dust settles, resist the urge to just "move on." Take time to:

1. Acknowledge what was lost. Teams, collaborations, domain expertise, comfortable routines — these losses are real. Name them.

2. Re-establish purpose. Help your team understand why the new structure exists and what's possible now that wasn't before. Not corporate spin — genuine possibilities.

3. Invest in new relationships. If new people joined your team, invest heavily in integrating them. If your team now collaborates with new partners, facilitate those connections.

4. Watch for lingering pain. Some people process reorgs quickly. Others carry resentment for months. Check in individually. If someone is stuck, help them either find peace with the new structure or find a better fit elsewhere.

A Letter to Leaders in the Middle

If you're reading this in the middle of a reorg, feeling squeezed between what you know and what you can say, between your team's fear and your own uncertainty — I see you. This is one of the hardest positions in leadership.

You're doing something important. You're being the steady ground that scared people can stand on. That matters more than you know. Your team might not say it now, but years from now, someone will tell you: "The way you handled that reorg is why I stayed."

Be honest when you can. Be present always. Take care of yourself in the margins. And know that this — like every storm — will pass. What will remain is how you made people feel while it was raining.

That's the part that matters. That's the part they'll remember.