You walked into work on Monday and something felt off. Maybe it was the all-hands meeting that appeared on your calendar at 8 AM. Maybe it was the Slack messages from coworkers asking “did you hear?” Or maybe your manager just told you, point-blank, that your team is being dissolved, merged, or “realigned to better serve business objectives.”

Whatever the delivery method, the message is the same: your IT department just got reorganized. And now you’re sitting there wondering what this means for your job, your projects, and the career trajectory you’ve been building.

Take a breath. You’re not powerless here. But you do need to move with intention over the next few weeks, because the choices you make during a reorg determine whether you come out stronger or get quietly sidelined.

Why IT Departments Get Reorged (And Why It’s Not About You)

Before you spiral, understand this: most IT reorgs have nothing to do with individual performance. They happen because of forces way above your pay grade.

Budget pressure is the most common trigger. When the CFO needs to cut costs, IT is often first on the chopping block because leadership views it as a cost center rather than a revenue driver. This is frustrating and wrong, but it’s reality. If you’ve ever tried to make leadership care about technical debt, you already know how this dynamic works.

New leadership is another big one. A new CIO, CTO, or VP of IT almost always wants to put their stamp on the organization. They’ll restructure teams to match their preferred operating model, regardless of whether the current structure is working fine. It’s political, not practical.

Mergers and acquisitions force IT consolidation. Two companies merge, and suddenly there are two help desk teams, two network teams, and two sets of infrastructure. Somebody has to go. If your company just got acquired, a reorg is almost guaranteed to follow.

Strategic pivots happen when the business decides to go all-in on cloud, outsource managed services, or adopt a new technology stack. Your team’s purpose might shift overnight from managing on-prem servers to supporting a hybrid cloud environment.

The “efficiency” play is what happens when consultants show up. They’ll map your org chart, identify “redundancies,” and recommend a flatter structure. Sometimes this makes sense. Often it just creates confusion while the same amount of work gets distributed across fewer people.

The point: understanding why the reorg is happening gives you information about what’s coming next. A budget-driven reorg means cuts are likely. A leadership-driven reorg means new priorities and new favorites. A strategic pivot means your skills either align with the new direction or they don’t. Knowing which scenario you’re in shapes how you respond.

The First 48 Hours: What to Do Right Now

The first two days after a reorg announcement are when most people make their biggest mistakes. They either freeze up and do nothing, or they panic and do something rash. Here’s what to do instead.

Figure Out the New Structure

Before you react emotionally, gather information. Who’s your new manager? What’s the new team structure? Which roles are being eliminated, created, or merged? What’s the timeline for changes to take effect?

If leadership hasn’t provided these details, that’s a data point too. Vague reorgs with unclear timelines usually mean more changes are coming. Leadership either hasn’t finished making decisions or they’re rolling out bad news in stages to avoid a mass exodus.

Talk to Your Manager (Current or New)

This is not the time to hide. Schedule a one-on-one within the first 48 hours. Ask direct questions:

  • “How does this affect my role specifically?”
  • “What does success look like in the new structure?”
  • “Are there opportunities I should be aware of?”
  • “What’s the timeline for team assignments?”

Your manager may not have all the answers yet, but the act of asking signals that you’re engaged and thinking about the future rather than dwelling on what’s changing. This is exactly the kind of proactive leadership behavior that gets noticed during transitions.

Don’t Trash-Talk the Reorg

You’re probably thinking it. Maybe the reorg is genuinely stupid. Maybe it breaks a team that was functioning well. Maybe the new structure makes no technical sense. Keep those opinions to yourself, at least publicly.

Every reorg has political winners and losers. The people who designed this new structure are watching to see who’s on board and who’s resisting. Being labeled as “resistant to change” during a reorg is a career-limiting move, even if your resistance is justified.

Vent to your spouse, your friends outside work, or your dog. Not on Slack. Not in the break room. Not on LinkedIn.

Document What You’re Working On

This is practical, not paranoid. During reorgs, projects get reassigned, deprioritized, or forgotten entirely. Create a clear record of your current work, its status, and its business value. This protects you in two ways: it shows your new leadership what you bring to the table, and it prevents someone else from taking credit for work you’ve already done.

Good documentation practices always matter, but they matter most during organizational chaos.

How to Protect Your Position During a Reorg

Let’s be honest about what’s happening beneath the surface of every reorg. Leadership is evaluating people. They’re deciding who fits the new structure, who has the right skills, and who they want on their team. You are being assessed whether anyone says so or not.

Here’s how to make sure the assessment goes your way.

Make Your Value Impossible to Ignore

If you’ve been quietly doing excellent work without much fanfare, this is the moment where that approach hurts you. Reorgs benefit people who are visible. Your new manager might have no idea what you do or how well you do it.

Start creating visibility without being obnoxious about it. Send status updates on your projects. Volunteer for cross-team initiatives that align with the new direction. Offer to help with the transition itself, whether that’s migrating documentation, onboarding team members, or bridging knowledge gaps between merging teams.

This is what separates senior-level IT professionals from everyone else. They don’t wait to be told where they fit. They demonstrate where they belong.

Align Yourself with the New Priorities

Every reorg comes with new talking points from leadership. They’ll say things like “we’re moving to a DevOps model” or “we’re consolidating infrastructure” or “we’re focusing on security posture.” Listen to these talking points carefully, because they tell you where the investment is going.

If the new direction aligns with your skills, make that alignment explicit. If it doesn’t, start filling the gap immediately. Take a course. Build a lab project. Get a relevant certification. The window for positioning yourself is short, usually 30 to 60 days before the new structure solidifies.

For example, if your company is pivoting hard toward cloud and you’ve been an on-prem sysadmin, now is the time to get serious about AWS or Azure. Not next quarter. Now.

Build Relationships with New Stakeholders

Your old network within the organization may no longer be as useful. The people who had influence before the reorg might not have influence after it. Pay attention to who the new decision-makers are and start building relationships with them.

This isn’t about being political or fake. It’s about recognizing that relationships are how things get done in organizations. If you’ve always relied on technical skill alone to carry your career, a reorg is the wake-up call that soft skills and relationship-building matter just as much.

Don’t Volunteer for the “Integration” Team Unless It’s Strategic

During reorgs, someone always needs to do the grunt work: merging ticketing systems, consolidating Active Directory forests, migrating shared drives, reconciling asset inventories. This work is necessary and often thankless.

Before you volunteer, ask yourself whether this work will give you visibility with decision-makers or just bury you in busywork. Migrating a knowledge base might be a good move if it puts you in front of the new CTO. Spending three months reconciling license spreadsheets probably won’t advance your career.

When a Reorg Is Actually a Layoff in Disguise

Let’s address the elephant in the room. Sometimes a “reorg” is corporate-speak for “we’re cutting headcount and we don’t want to call it layoffs.”

Here are the warning signs:

Your role is “TBD.” If everyone else has been assigned to a team in the new structure and your placement is still undefined after two weeks, that’s not a good sign. Companies that plan to keep you will tell you where you fit.

Your projects are being redistributed. If the work you’ve been doing is getting assigned to other people without explanation, you’re being phased out gradually rather than let go all at once.

Your access is getting restricted. Losing admin rights, being removed from distribution lists, or finding yourself excluded from meetings you used to attend are all signals.

The “transition period” keeps extending. If leadership can’t give you a clear answer about your role and keeps saying “we’ll know more next month,” they’re either genuinely uncertain (bad) or stalling until they figure out how to exit you (worse).

If you’re seeing these signs, don’t wait for confirmation. Start updating your resume, refreshing your LinkedIn profile, and reaching out to your network. You can always stop the job search if things work out. You can’t get back the weeks you spent hoping while the writing was on the wall. Our guide on job searching without getting fired covers how to do this discreetly.

And if the worst does happen, remember: IT layoffs are not a reflection of your ability. They’re a business decision.

The Emotional Side Nobody Talks About

Reorgs mess with your head. Even if your job is safe, the disruption to your daily routine, your team dynamics, and your sense of stability takes a real toll.

You might feel angry that a functioning team got broken up for no obvious reason. You might feel anxious about proving yourself to a new manager who doesn’t know you. You might feel betrayed by leadership that promised stability and delivered chaos. You might feel guilty about keeping your job when coworkers got cut.

All of this is normal. None of it means you’re weak or overreacting.

The tricky part is that you’re expected to maintain full productivity while processing all of this. Nobody gives you a grief period after a reorg. The expectation is that you’ll immediately embrace the new structure and perform at your best.

If you’re feeling burned out on top of all this, don’t ignore it. Burnout compounds when you push through without addressing it, and reorgs are a common trigger. Talk to someone you trust. Use your EAP if your company offers one. Take your PTO, even if the timing feels bad.

And watch out for imposter syndrome sneaking in during this period. When your role changes or your team shifts, it’s easy to feel like you don’t belong anymore. You do. Your skills didn’t evaporate because someone redrew the org chart.

Turning a Reorg Into an Opportunity

Here’s the part most people miss: reorgs create openings that don’t exist in stable organizations. The org chart is fluid. New roles are being created. Old hierarchies are dissolving. This is one of the few moments where you can make a lateral or upward move without going through a formal application process.

Volunteer for High-Visibility Projects

The new leadership team will have priorities they want to execute quickly. If you can identify what those priorities are and position yourself to help deliver them, you jump to the front of the line for recognition, raises, and promotions.

This is especially true if you’re willing to work on something outside your normal scope. The sysadmin who volunteers to help the security team with a compliance audit during a reorg is showing adaptability, which is the single most valued trait during organizational transitions.

Pitch the Role You Want

During a reorg, there’s often a gap between what leadership needs and what the existing team structure provides. If you can identify that gap and propose a role that fills it, you might create your own promotion.

This takes confidence, but it works more often than you’d think. Draft a one-page proposal: here’s the gap, here’s how I can fill it, here’s the business impact. Present it to your new manager or skip-level if appropriate. The worst they can say is no. If you’ve been stuck at a career plateau, a reorg might be the disruption you needed to break through.

Expand Your Skill Set Intentionally

Reorgs often combine teams that were previously separate. A network team might merge with a security team. A help desk might absorb desktop support. Instead of resenting the expanded scope, use it to build skills you wouldn’t otherwise get exposure to.

If your team just absorbed cybersecurity responsibilities, lean into it. Start with fundamentals on platforms like TryHackMe or OverTheWire. Build hands-on skills with Shell Samurai for interactive terminal and security challenges. Pick up a Security+ certification if it makes sense for the new direction.

If the reorg is pushing your team toward infrastructure-as-code and automation, start learning Terraform or Ansible. Build a home lab project that demonstrates these skills.

The people who thrive through reorgs are the ones who see organizational change as a forcing function for personal growth.

Common Mistakes That Get People Cut

Reorgs expose certain behaviors that leadership notices and penalizes. Avoid these:

Openly resisting the change. Saying things like “the old way was better” or “this will never work” marks you as someone who will slow the transition down. Even if you’re right, the timing is wrong.

Going invisible. Some people respond to uncertainty by keeping their heads down and hoping nobody notices them. During a reorg, the people who aren’t noticed are the first to go. Visibility is survival.

Clinging to your old role definition. If your job description just changed, clinging to what you used to do signals inflexibility. The fastest way to get cut in a reorg is to be the person who says “that’s not my job” when the org chart is literally being rewritten.

Badmouthing departed colleagues. If people got laid off as part of the reorg, speaking negatively about them or distancing yourself from them is a bad look. It doesn’t make you look better by comparison. It makes you look untrustworthy.

Ignoring your professional network outside the company. Even if your position is secure today, a reorg is a reminder that organizational stability is an illusion. Maintaining external relationships isn’t disloyal. It’s smart career management.

Refusing to learn new tools or processes. The reorg might come with new ticketing systems, new monitoring platforms, new processes. The people who adopt quickly get ahead. The people who drag their feet get labeled as problems.

When the Dust Settles: Your 30-60-90 Day Plan

Once the initial chaos of the reorg subsides, you need a plan for establishing yourself in the new structure. Think of it like starting a new job, except you already know where the bathrooms are.

Days 1-30: Learn. Understand the new reporting structure, the new priorities, and the new team dynamics. Meet with your new manager and peers. Ask questions. Listen more than you talk. Figure out what “good” looks like in the new world.

Days 31-60: Deliver. Pick one or two projects that align with the new priorities and execute them well. This is where you prove that you belong in the new structure. Make your work visible through updates, demos, or documentation.

Days 61-90: Shape. By now you should understand the new setup well enough to start influencing it. Propose improvements. Identify gaps. Mentor newer team members who are still finding their footing. Be the person who’s driving things forward, not just the person who survived.

If you’re eyeing a management track, reorgs are often when new IT manager positions open up. The leadership behaviors you demonstrate during the transition period are your audition tape.

The Hard Truth: Sometimes You Should Leave

Not every reorg is survivable, and not every reorg is worth surviving. If the new structure puts you in a role you hate, under a manager you can’t work with, or in a direction that doesn’t align with your career goals, staying out of inertia is worse than leaving on your terms.

Ask yourself these questions 90 days after the reorg:

  • Do I understand my role and feel valued in it?
  • Is my new manager invested in my growth?
  • Does the company’s new direction give me opportunities to develop skills I care about?
  • Am I doing more interesting work, less interesting work, or the same?
  • Has my compensation been adjusted to reflect any expanded responsibilities?

If you’re answering “no” to most of these, it might be time to start exploring. Check out our guide on when to leave your IT job for a more detailed framework.

Leaving after a reorg isn’t giving up. It’s recognizing that the organization changed, and you’re choosing to find one that fits better.

FAQ

How long does a typical IT reorg take to stabilize?

Most reorgs take three to six months to fully settle. The announcement and initial changes happen fast, but the cultural and operational adjustments take much longer. Expect at least one round of “adjustments to the adjustments” as leadership realizes their initial plan had gaps. Budget for a full quarter of reduced productivity across the team as people figure out new processes and relationships.

Should I start job searching immediately after a reorg announcement?

Not necessarily, but you should get prepared. Update your resume, refresh your LinkedIn profile, and reconnect with your professional network. Think of it as putting on your seatbelt, not jumping out of the car. If the reorg turns out to be positive for your career, great. If it doesn’t, you’ve already done the groundwork to move quickly.

My new manager has no technical background. How do I handle this?

This is increasingly common after reorgs, especially when IT gets folded under operations or finance. Focus on translating your work into business impact. Instead of saying “I migrated our DNS infrastructure,” say “I reduced outage risk by modernizing a system that affects every employee’s ability to access company resources.” Our guide on working with a non-technical boss covers this in depth.

I survived the reorg but lost my best team members. How do I cope?

Survivor’s guilt is real. Acknowledge it rather than pretending everything’s fine. Professionally, focus on what you can control: doing good work, supporting the team that remains, and maintaining relationships with departed colleagues (they might be your referral into a future role). If you’re now doing the work of three people, raise this with your manager early. Don’t wait until you’re burned out to flag that the workload is unsustainable.

Can a reorg actually be good for my career?

Absolutely. Reorgs create chaos, and chaos creates opportunity. Some of the biggest career jumps happen during organizational transitions because normal gatekeeping mechanisms break down. If you’re strategic about positioning yourself, a reorg can accelerate your career by years. The key is being proactive rather than passive during the transition.