Re-org Survival

Engineers experience re-orgs as weather. Operators recognize them as the one window when the org's scope map is unlocked for editing — and whoever writes first, keeps.

What a re-org really is

The org chart is a map of who owns what. Most of the time that map is frozen: charters are settled, ownership is defended, and moving scope between teams requires expensive political negotiation. A re-org melts the map. Charters get rewritten from scratch, reporting lines snap to new anchors, and — critically — a lot of scope ends up ambiguous. Projects lose sponsors. Systems lose owners. Responsibilities that used to sit cleanly inside one team now straddle two, or none.

Engineers tend to process this as disruption: new manager, new standups, wait for the dust to settle, get back to work. That framing quietly cedes the most valuable weeks of the cycle. Operators read the same event differently: the dust is the opportunity. While ownership is ambiguous, claims are cheap. Once the new charters harden — usually within a quarter — the map refreezes and moving scope becomes expensive again.

This connects directly to Scope Is Taken, Not Granted: scope is almost never handed out by a planning process; it's claimed by whoever shows up with a coherent story and the ability to deliver. A re-org is simply the moment when the maximum amount of scope is claimable at once.

Mechanics of the window

Two things are briefly true after a re-org, and both work in your favor.

Formal authority is out of sync with reality. The new leader has the title but not the terrain. They don't know which systems are load-bearing, which projects are theater, or which people actually make things move. They are actively — sometimes desperately — looking for two things: someone who can explain the landscape, and something they can announce as an early win to justify the re-org to their boss. The person who shows up with "here's the map, here's what's broken, here's what I can own by this date" satisfies both needs simultaneously. You become the guide, and guides get to draw the map in their own favor. This is not manipulation; it's supply meeting demand. The leader genuinely needs orientation, and you genuinely have it.

Relationships persist even when structures don't. Every reporting line you had can be severed overnight; none of the trust you've built is. The people who know your work, owe you favors, and vouch for you in rooms you're not in — that network survives every re-org intact, which is exactly why the The Shadow Org Chart matters more than the formal one. Structures are the org's short-term memory. Relationships are its long-term memory. Invest accordingly.

The plays

Brief the incoming leader early — offer the map. Ask for 30 minutes in their first two weeks. Bring one page: what the team owns, what's broken, what the top three risks are, and one concrete thing you can deliver. You're volunteering to be their eyes. Nobody else will move this fast; most people are waiting to be summoned.
Restate your wins to the new manager immediately. Your promo narrative does not transfer automatically. The evaluator who watched you carry last year's launch may now be three orgs away, and per Reputation Forms Early and Updates Slowly, a new evaluator is a label reset — their first impression of you will harden fast and update slowly. Write the summary of your last 12 months of impact and get it in front of them in week one, framed as context, not as bragging: "so you know what the team's been shipping."
Identify orphaned scope and claim a piece — with a date. Every re-org strands work: the cross-team initiative whose sponsor left, the service whose owning team was dissolved, the migration nobody's charter mentions anymore. Pick one that's genuinely valuable, announce that you're taking it, and attach a delivery date. The date is what separates an honest claim from cookie-licking (see Cookie Licking: Claiming Work Without Doing It) — a claim with a deadline is a commitment; a claim without one is just spit on a cookie.
Audit your projects for dead sponsors. If your project's executive sponsor got shuffled out, the project may be politically dead even though the Jira board looks alive. Grinding loyally on an orphaned project is one of the most common post-re-org career mistakes. Ask directly: who above me still wants this to exist? If you can't name them, redirect your effort before the next planning cycle formalizes the death.

Emotional discipline

New leaders are pattern-matching hard in their first weeks, and one of the strongest signals they read is adaptation speed. Visible nostalgia — "the old structure made more sense," "we used to do it this way" — reads as junior, regardless of your level, because it signals attachment to a world that no longer exists. You can privately think the re-org is idiotic. Many are. But grief is a private activity. In public, be the person who has already metabolized the change and is operating in the new reality. Leaders promote people who look like they belong in the future org, not the past one.

Failure modes

Land-grabbing beyond delivery capacity. Claiming three orphaned areas and delivering none is public cookie-licking at scale. Your first missed date in front of a new leader becomes your label. Claim what you can actually ship; claim once, deliver, then claim again.
Backing the old order out of comfort. Staying loyal to the displaced manager, the dead project, or the dissolved team structure because it's familiar. Loyalty to people is an asset; loyalty to defunct structures is a liability. The old order cannot reward you — it no longer controls anything.

Diagnostic test

When the re-org email lands, does your calendar for the next two weeks fill with waiting — or with briefings you requested?