Reorgs are one of the most reliably destabilizing events in an engineer’s career — not because they are usually catastrophic, but because the uncertainty they create is difficult to think clearly through. You don’t know who your manager will be. You don’t know whether your team will stay together. You don’t know whether the project you’ve been leading for six months still matters.
Most engineers respond to that uncertainty by waiting for clarity. The engineers who come out of reorgs in better shape are the ones who move toward clarity rather than waiting for it to arrive.
This guide is about how to do that: how to read an announcement, what to do in the first two weeks, how to rebuild your position in a new structure, and how to recognize when a reorg is actually a signal that you should be looking outward.
What a Reorg Actually Means
Reorgs happen for a handful of reasons: new leadership wants to restructure around their priorities, the company is responding to growth or contraction, a strategic shift changes which teams are core, or someone noticed that the org structure had become misaligned with how work actually flows.
Most of those reasons have nothing to do with your performance. A reorg announcement is not usually a verdict on your work. The mistake is interpreting it as one — either catastrophizing about what it means for you specifically, or dismissing it as noise that won’t affect your day-to-day.
The accurate read is: this changes something about the structure around you, and you need to figure out what. The impact can range from “manager changed, everything else stays” to “your team dissolved and your role doesn’t exist in the new structure.” Most reorgs fall somewhere in the first half of that range, but you need to determine where yours lands before you can respond appropriately.
Reading the Announcement
Reorg announcements are written to minimize panic. They emphasize continuity and strategic intent, and they omit the parts that create anxiety: what actually changes for individual teams, who is affected, what happens to in-flight work, what the timeline is.
Read the announcement twice. The first time, read it for what it says. The second time, read it for what is absent.
Questions the announcement often doesn’t answer:
- Which specific teams are changing, and which are not?
- Who is reporting to whom, and at what level of specificity?
- What happens to in-flight projects that span the old structure?
- Is headcount changing, or just reporting lines and team boundaries?
- When does this take effect, and is there a transition period?
The gaps in the announcement tell you what to investigate. Your goal in the first 48 hours is to understand the actual structure change — not the strategic narrative around it — so you can reason about what it means for your specific situation.
The First Two Weeks
How you behave in the first two weeks of a reorg sets expectations that are difficult to correct later. The two failure modes to avoid:
Waiting passively. Waiting for your manager to tell you what’s happening, for the new org chart to be published, for the dust to settle. This is comfortable but positions you as a recipient of decisions rather than a participant in shaping them. Other people fill the vacuum; you get told what was decided.
Reacting visibly. Voicing concerns in broad forums before you have full information, treating the reorg as evidence of bad leadership or bad faith, flagging anxiety in ways that become the first data point your new manager has about you.
What to do instead:
Talk to your manager before the announcement settles. Get their read on what changes and doesn’t. Managers often know more than is in the announcement, and a direct conversation surfaces information you won’t get from the announcement or the rumor mill.
Map the new structure immediately. Identify who owns what in the new org, who the key decision-makers are, and where your team sits relative to the work that matters most. If you’ve been maintaining a shadow org chart, update it. If you haven’t, now is the time to build one. The informal power structure matters just as much after a reorg as before — it just looks different.
Introduce yourself to new stakeholders. If the reorg creates new reporting relationships or new cross-functional dependencies, initiate introductions rather than waiting for them to find you. A brief message — “I heard we’ll be working more closely; I’d love to find 30 minutes to connect” — is low-cost and establishes you as proactive.
Protect your in-flight work. Reorgs create the opportunity for projects to slip through the cracks when the people who were accountable to them are now reporting to different managers. Explicitly surface your in-flight work to your new or continuing manager early, so it doesn’t become orphaned.
If Your Role Changed Substantially
Sometimes a reorg isn’t neutral — it moves you to a team where your existing work is less central, changes your scope in ways that don’t align with your strengths, or reorganizes around priorities that exclude what you do best.
This is worth taking seriously but not catastrophizing. The right response depends on the specific change:
If your scope shrank: find out whether this is permanent or temporary (reorgs often produce transitional states that normalize over time), and have an explicit conversation with your manager about what operating at your level looks like in the new structure. The conversation should be curious, not adversarial — you’re trying to understand, not to negotiate immediately.
If your team moved away from a domain you care about: this is worth sitting with before acting on. Some engineers prefer staying on a team they know with a changed mandate over moving to a team with a mandate they prefer but where they have no standing. Others find the opposite. Your answer depends on what matters more to you at this point in your career.
If the reorg effectively eliminates your role: this is a different category. If your responsibilities genuinely don’t exist in the new structure, and no equivalent role is being offered, that’s a signal worth taking seriously. Have a direct conversation with your manager about what your path forward looks like. If the answer is unclear or unsatisfying, start updating your options externally — not as a final move, but because having options changes your ability to negotiate.
Rebuilding Relationships in the New Structure
The most durable impact of a reorg is often not the org chart change itself, but the relationship disruption. The manager who understood your work, the peer who was your most reliable collaborator, the skip-level who was familiar with your contributions — these relationships may have been moved outside your reporting chain. The visibility they created doesn’t transfer automatically to new relationships.
Rebuilding takes time and deliberate effort. The principle is simple: you are starting from scratch with anyone new in your chain, regardless of your history or reputation elsewhere. Your new manager has no direct evidence of your work yet. The promo committee feedback you got from your old skip-level isn’t in your new skip-level’s head.
This is frustrating, but it’s also an opportunity. You can control the narrative about your work and your ambitions from the beginning of a relationship in ways that aren’t possible when a relationship is already established with its own history.
Invest in 1:1s with new stakeholders early. Come with a clear, concise picture of what you’re working on and what outcomes you’re targeting. Ask questions about their priorities. The goal is to be on their radar as a valuable, low-maintenance contributor before they form impressions based on secondhand information.
When a Reorg Is a Signal
Most reorgs are manageable. Some are not. The signals that a reorg is more than an org chart shuffle:
- Your team’s work is being absorbed into another team’s mandate, with no clear role for yours going forward
- Key leaders you trusted are leaving, and the pattern suggests they see something you don’t
- The reorg puts you in a structure you tried to get out of previously and found limiting
- Your manager is being moved to a less influential role, and your visibility is likely to drop with them
None of these automatically means you should leave. But they are signals that you should update your read of your situation. “Update your options externally” is not the same as “start interviewing aggressively” — it means making sure your external network is warm, that your resume is current, that you’re not making long-term commitments based on a structure that may be less stable than it appears.
Maintaining Your Career Trajectory Through Change
The engineers who maintain steady career trajectories through reorgs are rarely the ones who are unaffected — they are the ones who adapt quickly. They map the new structure before most people have processed the announcement. They initiate relationships before new managers have fully formed their views. They surface their work proactively rather than assuming visibility follows effort.
That discipline is easier to maintain when you have a clear record of your own trajectory — what you’ve accomplished, what you’ve been working toward, and what skills and relationships matter for where you want to go. A reorg doesn’t reset that record. It does reset some of the context that was providing evidence for it, and that’s worth rebuilding intentionally.
VividMap helps you map your org structure, track the relationships that matter for your career, and maintain a record of your progress — so that when things change around you, your picture of your own trajectory stays clear. See how it works.