The New-Manager Reset

When your manager changes, everything they knew about you does not transfer. The promo case they were building evaporates. Re-onboard the new manager yourself, or start over from zero.

Your manager leaves, gets re-orged away, or you move teams. You had two years of goodwill: a track record of shipped projects, a trajectory they'd articulated in calibration meetings, maybe an explicit "you're on track for senior next cycle." A week later you have a new manager who knows one thing about you: your name, and possibly the phrase "solid engineer" from a fifteen-minute handoff call.

That phrase — "solid engineer" — is frequently the complete transfer of two years of your work. Not because anyone was negligent, but because that's what handoffs are: brief, lossy, and compressed to a sentence per report.

What evaporates

A promo case lives in two places: artifacts (design docs, review packets, written feedback) and a narrative in your manager's head — the story of your trajectory, the context on why a project was hard, the judgment calls you got right, the sponsors they'd been lining up. The artifact half survives the transition. The head half is where most of the value was, and it walks out the door with them.

Verbal commitments are the first casualty. "You're on track for senior next cycle" is not a contract; it's a statement of one person's intent, and that person is now gone. The new manager did not make that promise, has no record of it, and — critically — has no obligation to honor it. Unless it exists in writing somewhere they can find, it functionally never happened.

What replaces the old narrative is whatever the new manager observes in their first few months. Reputation forms early and updates slowly (Reputation Forms Early and Updates Slowly), so this observation window becomes your new baseline — for years, potentially. That makes a reset dangerous, but note the symmetry: it's also an opportunity. If you'd been typecast — "the maintenance person," "junior energy" — that label dies with the old manager too. A reset is a rare chance to be re-evaluated from scratch. The question is only whether you shape the re-evaluation or leave it to chance.

Mechanics: why the new manager won't just inherit your standing

Three forces work against a clean transfer, and none of them are malice.

Handoffs are structurally lossy. An outgoing manager doing handoffs for eight reports, while also transitioning their own projects, spends minutes per person. Compression to "solid, no concerns" is the norm, not the failure case.

The new manager is incentivized to re-evaluate. Their credibility with their new boss rides on their own calibration judgments. Sponsoring a promo case they inherited but can't personally vouch for is a career risk for them. Rationally, they discount inherited judgments and rebuild their own — which means your clock partially restarts no matter what the old manager said.

They're drowning. A new manager is absorbing a new team, new systems, new stakeholders, and new politics simultaneously. They have no spare attention to reconstruct your history from artifacts. But this is also the opening: they will gratefully anchor on whoever makes their onboarding easy. The person who orients them becomes, by default, the person they trust.

The re-onboarding project

Treat the transition as a project you run, with a before phase and an after phase.

Before the old manager leaves:

• Get the narrative into writing. Ask them directly to document your standing and trajectory — in a handoff note, or better, in the official review record where it's durable and discoverable. Most managers will do this if asked; almost none do it unprompted.
• Extract verbal commitments into email. "Just to confirm my understanding before your transition: we'd discussed that I'm on track for senior in the next cycle, pending X and Y." A reply of "yes, that's right" converts a worthless verbal promise into an artifact the new manager can't easily dismiss (Write Things Down).

After the new manager arrives:

• Prepare a re-onboarding packet: your brag doc — the work doesn't speak for itself, and it certainly doesn't speak across a manager transition (The Work Doesn't Speak for Itself) — plus current projects, your trajectory, and what the old manager had committed to (with the written evidence). Book an early 1:1 to walk through it. Frame matters enormously: this is helping them onboard, not lobbying. "I figured context on my work would be useful as you ramp up" lands; "here's why I deserve promotion" does not.
• Make their first months easy. Be the person who explains the team's systems, the deploy process, the tribal knowledge. First impressions with a fresh evaluator compound, and the guide role builds the relationship on their terms — the same move that works in a reorg works here (Reorg Survival).
• Restate your goals explicitly: "I was working toward X; I'd like to keep that on track — what evidence do you need to see?" This enlists them in the goal instead of presenting them with a demand, and it surfaces mismatched expectations in month one instead of at review time.
• Keep skip-level continuity as the hedge. Your skip-level manager often survives the churn that takes your direct manager, and a skip who knows your work holds your narrative across transitions (Skip-Level Relationships). Build that relationship before you need it.

Failure modes

Grievance as strategy. "It's not fair — my old manager promised me" is true and useless. Fairness does not obligate the new manager to honor commitments they never made and can't verify. The engineers who lose the most in transitions are the ones who spend the first quarter being owed something instead of rebuilding.

Lobbying too hard, too fast. If your first three interactions with the new manager are all about your promotion, you read as someone managing them before you've helped them. The sequence matters: be useful first, establish the record second, ask for the commitment third.

Diagnostic test

If your manager gave notice tomorrow, could the promo case for you be reconstructed entirely from written artifacts — or does it live in their head?