How to Protect Your Promotion Case During a Reorg

Reorgs have a special talent for making competent adults feel delusional.

On Monday, your manager says your promotion case is moving. By Thursday, leadership unveils a new structure “for speed and clarity,” two teams get merged into a vague abstract concept, and suddenly everyone is speaking in the tone people use around a skittish horse. Your calendar fills with “transition syncs.” Your manager gets oddly tender. The promotion conversation that looked solid ten days ago now looks like it was written on a napkin in rain.

This is not you being dramatic. Reorgs rarely kill promotion cases with one clean, adult sentence. They kill them by dissolving ownership so thoroughly that no one has to admit the case is now wandering around barefoot in traffic.

That is why this feels awful in such a specific way. A direct no hurts, but at least it is real. Ambiguity is a slower, more insulting pain. You leave a meeting thinking, I guess that was fine? Then Sunday night arrives, your chest tightens, and your brain starts doing forensic analysis on phrases like “we should revisit this soon,” which could mean next month or never, lovingly.

The question is not whether people are “still supportive.” The question is whether your promotion case still has an owner, a standard, and a path to review.

TL;DR

• Reorgs usually do not destroy promotion cases outright. They blur responsibility until the case quietly stops existing.
• “My manager supports me” is emotional information, not process information.
• Your job is to find out who decides now, what criteria apply now, and when your case can actually be reviewed.
• After a reorg, your case often needs translation more than reinvention.
• Portable evidence beats reputation, especially when people, teams, and priorities are being shuffled like cards.
• A useful conversation ends with names, dates, standards, and missing proof — not a better mood.

The danger is not the org chart. It is the disappearing decision path.

Companies talk about reorgs as though they are moving boxes on a slide. Cute. That is the executive version.

The employee version is: the person who knew your work may no longer own your future, the criteria may have changed without anybody saying so plainly, and the timeline may now be attached to a review process that exists only in theory.

What changes in a reorg is not just reporting lines. It is the machinery around judgment:

• who has actually seen your work
• who feels obligated to advocate for you
• what kind of impact suddenly counts as “strategic”
• whether your strongest evidence still maps to the new role language
• whether your case is attached to any real approval path at all

This is why vague reassurance becomes dangerous so fast. In a stable org, a soft “yes, let’s keep talking about your growth” can float for a while because the surrounding system still exists. In a reorg, that same sentence is often the last sound your promotion case hears before it sinks into administrative swamp water.

Most in-flight cases end up in one of four buckets:

What you hear	What it usually means	What to ask next
“Reviews are paused, but we still support this.”	Delayed	“What event restarts the process, and who owns my case until then?”
“Your new manager will want to assess first.”	Reset	“What evidence carries over, what needs fresh validation, and when will we revisit?”
“Let’s reconnect once things settle.”	Drifting toward abandonment	“What specifically has to settle, and by what date will we decide whether this is still active?”
“Level expectations are changing.”	Standard changed	“Can you walk me through the updated criteria and how my current evidence maps to it?”

A lot of smart people stop at tone because tone feels safer. They sounded kind. They did not shut me down. Maybe I should just be patient. No. Kindness is lovely. Kindness is not a process.

If someone senior asked you today, “Who approves your promotion now, and what is the path?” could you answer in one sentence without improvising? Sit with that for a minute. If the answer is no, that is the problem to solve this week.

Stop mistaking support for traction

“My manager supports me” is useful the way “your package is somewhere in the system” is useful. Comforting, maybe. Operationally pathetic.

During a reorg, many managers become sincere but foggy. They may genuinely want good things for you while having no idea who signs off now, whether the rubric changed, or whether your case is still attached to a real review cycle. That does not make them evil. It does mean you should stop using warmth as proof of momentum.

Ask questions that force structure back into the room:

• Who is the decision-maker now?
• Is my previous promotion case still active, or is it being reassessed?
• What level criteria apply in the new structure?
• Which evidence from the prior period still counts?
• What timeline is realistic now?
• What would make the case stronger from here?

If you need to script it, script it. You are not less strategic because you prepared complete sentences in advance.

Subject: Clarifying promotion process after the reorg

Hi [Manager],
Given the recent team changes, I want to confirm whether my promotion case is still active, who owns the decision now, and what timeline and criteria apply in the new structure.

Could we use part of our next 1:1 to review:
- whether the case is still in motion
- who the decision-maker is now
- what level criteria apply
- what evidence would matter most from here

I want to make sure I’m working from the current process rather than assumptions.

Thanks,
[Your Name]

Pick one stakeholder and send that email today. Drift hardens fast. “I did not want to seem pushy” is one of the most expensive sentences in corporate life.

What actually decays during a reorg

People often say, “The timing got messed up.” Sometimes that is true.

More often, timing is just the symptom. The real problem is that your case no longer belongs to anyone in a concrete way.

Your old manager may have known your work cold. Your new manager may have inherited you like an unfamiliar houseplant and is trying not to kill you in public. A skip-level sponsor may have moved. A calibration meeting may have changed. The project that made you look indispensable in March may now sound like support for a strategy leadership quietly abandoned in April.

None of this feels dramatic while it is happening. That is exactly why it is so dangerous.

Promotion cases usually die from boring causes:

• the summary never got rewritten for the new org
• the sponsor was never replaced
• the rubric was never shared
• the follow-up was never scheduled
• the assumptions were never corrected

Death by bureaucratic shrug is still death.

Re-validate these four things immediately:

1. Role: What role am I actually being evaluated against now?
2. Reviewer: Who has to approve this?
3. Rubric: What standards define the next level?
4. Review timing: When can this realistically be decided?

If even one of those is muddy, your case is not “on track.” It is floating loose.

And strangely, there can be relief in admitting that. Fog makes people blame themselves. Diagnosis gives you something to do next.

Your work may be fine. The translation layer may be broken.

This is the point where a lot of capable people accidentally turn corporate ambiguity into private shame.

You start thinking: - Maybe I overstated how close this was. - Maybe I misunderstood the original conversation. - Maybe asking again will make me look needy. - Maybe everyone else understands what is happening and I’m the only difficult one.

No. Do not volunteer to carry confusion that belongs to the company.

Sometimes your readiness really has changed. Maybe a major scope area disappeared. Maybe a key proof point is gone. Maybe the job now emphasizes a different kind of influence than the one you were building toward. Fine. Irritating, but real.

But often the issue is not the work. It is the translation.

Maybe your previous manager knew how to frame your impact, and your new one does not. Maybe your old case was written in product language, and you now sit in a revenue org that values different signals. Maybe you were nearly there under one framework, but no one has bothered to map your evidence to the new one.

That distinction matters emotionally because “I am not ready” and “nobody has translated the case” feel completely different in your nervous system. One feels like failure. The other feels like work.

Try This

Write your case in one paragraph from memory: - target level - original owner - strongest evidence - current owner - what might need translation in the new structure

If you cannot summarize it cleanly, nobody above you can advocate for it cleanly either.

A hypothetical example: Priya forces the fog to pick a shape

Hypothetical example: Priya is a Senior Customer Success Manager at a mid-size healthcare SaaS company. She owns major renewals and has become the person Sales, Support, and Product all drag into ugly accounts because she can get a room full of defensive adults to make a decision.

In March, her manager tells her:

“You’re already operating at Lead level in several areas. If this scope continues through Q2, I’m planning to put you forward in the mid-year cycle.”

That is not a guarantee. It is, however, a real case. There is a target level, a timeline, and an owner.

Then the reorg hits. Customer Success moves under Revenue. Priya gets a new Director. In May, she asks where things stand and gets this:

“I’ve heard really good things. I just need a little time to get my arms around the team.”

Reasonable sentence. Completely useless sentence.

So she asks the question most people avoid because they are afraid it sounds too direct:

“Should I think of my promotion case as delayed, reset, or no longer active?”

Now the conversation has bones.

Her new manager says:

“Not gone, but I do need to reassess against what Lead CSM looks like in the Revenue org.”

Good. Not good emotionally, maybe. Good informationally. This is a reset.

Priya follows with the only question that matters now:

“Which parts of the original case carry over, and what specifically do you need to see from me in this structure before we revisit?”

He tells her the renewal performance evidence still counts, but in the new org Lead CSMs are also expected to influence forecast accuracy and partner directly with Sales leadership. He wants six weeks of direct observation and asks her to co-lead the weekly risk review with Sales Ops.

That answer may not produce joy. It does produce traction.

She now knows: - the case is reset, not dead - some evidence transfers - the standard changed - one dimension needs fresh proof - there is a date to revisit

That is miles better than leaving with a nice tone, a stress rash, and no idea what reality she is in.

Your move is not to get the perfect answer. It is to force an answer that can be acted on.

Do not “preserve momentum.” Re-anchor the case.

After a reorg, people usually make one of two bad moves.

The first is passivity. They assume the old momentum will somehow survive on vibes, as if promotion cases are self-propelled luggage.

The second is panic. They dump every accomplishment from the last nine months into a giant recap doc and call it a strategy. It is not a strategy. It is a cry for help with bullet points.

You need neither nostalgia nor an evidence landfill. You need a re-anchored case.

That means making the argument easy to understand inside the new structure, for someone who may not know your history and definitely does not want to excavate it.

A useful sentence sounds like this:

“Given the team changes, I want to align on whether I’m still being considered for the next level, what criteria apply now, and what evidence would matter most in the current structure.”

That is clean. Hard to misunderstand. Harder to evade without visibly evading.

Early-career professionals often worry this sounds political. It does not. It sounds like an adult asking the company to explain its own process after moving the walls overnight.

Before your next 1:1, write your promotion ask in one sentence. Then cut every phrase whose only purpose is to prosecute the old org chart. “As previously discussed” is sometimes necessary, but often it is just resentment wearing office clothes.

Portable evidence wins because memory is fragile and managers are busy

Reorgs are brutal on reputation that lives only in people’s heads.

If your case depends on everyone “just knowing” you stepped up, you are exposed. If it depends on one manager remembering your best moments during talent review, you are exposed. If your best contribution was quietly absorbing chaos so no one else had to feel it, you are very exposed.

What survives handoffs is evidence another person can repeat.

Weak praise vs. portable evidence

Weak praise
“Jordan is a great collaborator and always jumps in.”

Portable evidence
“Jordan ran the weekly decision meeting for the Q2 onboarding launch across Product, Design, and RevOps, resolved approval bottlenecks between teams, and cut sign-off time from 10 days to 4.”

Weak praise
“She’s been showing more leadership.”

Portable evidence
“Since February, she has owned the incident review across Engineering and Support, set the agenda, made tradeoff recommendations, and drove fixes that reduced repeat escalations by 18%.”

Weak praise
“He’s very strategic.”

Portable evidence
“He identified that enterprise churn risk was concentrated in stalled integrations, proposed a cross-functional triage workflow, and helped recover $420K in renewals over two quarters.”

Those examples travel. “Great to work with” dies in transit.

Here is the conversion formula: 1. What did I own? 2. Who had to coordinate because of me? 3. What changed because I acted? 4. Why would a higher-level reviewer care?

Take three accomplishments and run them through those four questions tonight. That exercise is worth more than ten vague compliments and one encouraging emoji from a director.

A fuller hypothetical: same work, two very different promotion stories

Hypothetical example: Maya is a Senior Product Manager at a Series C fintech company. Before the reorg, she reported to the Growth PM lead and owned work on card disputes. After the reorg, she lands in a Platform group led by a VP who mostly hears about teams through compliance noise, launch risk, and whether anything is on fire.

If Maya describes her work like this:

• supported launch planning for dispute redesign
• worked cross-functionally with Engineering, Legal, and Ops
• helped keep project on track

she sounds helpful and immediately forgettable.

If she translates the same work into portable evidence, it becomes:

• led the cross-functional readiness review for the card dispute redesign across Engineering, Legal, Ops, and Compliance
• surfaced a regulator-required disclosure gap ten days before launch, forcing a scope decision before release rather than after customer exposure
• reset the rollout plan, preserved the quarter’s ship date, and avoided an estimated two-week delay tied to compliance rework
• introduced a launch-risk checklist that the new Platform org adopted for other regulated releases

Same work. Different case.

The first version is labor. The second version is judgment, ownership, risk management, and org-level leverage.

When you review your own examples, ask yourself a rude but useful question: if I removed my name from this bullet, would it sound like “competent employee did assigned work,” or would it sound like “this person was operating at a higher level”? If the answer is the first one, the evidence is not ready yet.

A good conversation ends with a path, not a mood

People often judge promotion conversations by emotional weather: - Did it feel supportive? - Did nobody say anything scary? - Did I leave less panicked than I arrived?

Understandable. Ambiguous meetings create a weird physical hangover. Relief, embarrassment, second-guessing, maybe a little self-loathing for saying “totally makes sense” when in fact nothing made sense at all.

But a good conversation feels different. Even disappointing clarity can create a strange, electric relief because your nervous system finally has something solid to stand on.

By the end of the meeting, you want four things:

• the level or criteria that apply now
• the decision-maker or approval chain
• the realistic review timing
• the missing evidence, if any

If you do not have those, the conversation is not done. It was just socially pleasant.

Send a recap that pins the facts to the wall:

“Thanks for talking this through today. My understanding is that my case is currently [delayed/reset/not active], that [name/role] is the decision-maker, that the relevant criteria are [X], and that we plan to revisit on [date]. The main additional evidence you want to see is [Y]. Please let me know if I captured anything incorrectly.”

That note does two useful things. It gives them a chance to correct the record, and it creates documentation that can survive the next shuffle.

If the answer is delayed, reset, or not now, respond accordingly

These are not cosmetic distinctions. They are different realities.

If your case is delayed, get painfully specific about timing and ownership.
“After planning” is not a date. “Once things settle” is not a date. Ask what event restarts the process, who owns your case until then, and whether there is anything you should prepare meanwhile.

If your case is reset, ask for the translation map.
What evidence carries over? What does the new manager need to observe directly? How long is a reasonable assessment period? “I need more time” should come with scope, standards, and a revisit date.

If the answer is effectively not now, let that be information instead of a lifestyle.
That does not automatically mean storming out, updating your LinkedIn headline in a fury, or narrating your pain through passive-aggressive calendar titles. It means you stop feeding yourself fantasy. Maybe you rebuild the case. Maybe you wait a cycle. Maybe you quietly look elsewhere. Any of those is healthier than living in a polite bog and calling it patience.

A concrete question for the week: if your level of clarity did not improve for the next three months, would you still feel good about staying the course? Your answer is data. Use it.

When the org gets messier, your case should get simpler

This is where tools can help — if they solve the actual problem instead of sprinkling motivational glitter over it.

During a reorg, you do not need a chirpy productivity toy telling you to “own your narrative.” You need your evidence turned into something another human can absorb quickly, plus a private prep document that keeps you from freezing in the meeting.

That is the useful role of Promotion Case from Career Compass, available for iPhone in the United States.

It is built for a narrow, practical job: helping you turn scattered proof into a manager-facing Promotion Case PDF and a separate private Conversation Guide PDF. That split matters. One document is for getting another person to understand and carry your case. The other is for helping you walk into the conversation knowing your evidence, your gaps, and the questions that matter.

The process is straightforward: 1. Complete role and pay setup. 2. Approve one Evidence example in each of five Case Check areas: results, teamwork, leadership, bigger responsibilities, and strategic impact. 3. Review the offer, separately authorize optional AI preparation, and complete the one-time US in-app purchase of $24.99 for one case per account. 4. Review both documents, make supported edits, and approve email delivery of the two PDFs.

A few details are worth knowing because they map to the exact anxiety this article is about. You can save Evidence without AI drafting. Optional AI drafting and purchased document preparation use explicit permissions identifying OpenAI. Your employer cannot access your private account through the app; you choose what to share. The app also includes published US national occupation benchmarks, or clearly labeled age-adjusted national earnings context when a reliable occupation match is unavailable. That context is useful for compensation conversations, but it is still context — not a magical valuation machine and not a guarantee of outcome.

The real win is not “winning the conversation.” It is getting out of the fog.

That is the deeper thing reorgs mess with. Not just timelines. Reality.

They make you replay old 1:1s while unloading the dishwasher. They make you wonder whether that encouraging comment from two months ago was substantive or just managerial weather. They make you police your own tone until you are half employee, half hostage negotiator. Outwardly you stay professional. Internally you become a round-the-clock support desk for your own uncertainty.

The way out is not to become louder, more aggrieved, or more “visible.” It is to become clearer. Clarify the decision-maker. Clarify the rubric. Clarify the timeline. Turn praise into evidence. Translate your work into language that survives handoffs. Put the case somewhere sturdier than memory, mood, or office folklore.

There is also a mindset shift here that matters more than any script: support is not the same as sponsorship, and encouragement is not the same as process. Once you see that, a lot of workplace confusion stops feeling personal. You are not asking for special treatment when you ask how the case works now. You are asking the organization to behave like it has a process instead of a weather pattern.

And if the answer you get is disappointing, that is still progress. Bad clarity is better than flattering confusion because clarity lets you choose. It lets you rebuild, wait deliberately, or move on with your dignity intact instead of marinating in polite uncertainty for another quarter.

So if a reorg is unfolding around you, do not spend the next month asking whether people are “still supportive.” Ask what happens now, who owns it, what proof matters, and when a decision can actually be made. Then write the answer down somewhere real. If you want help turning that messy pile of proof into a cleaner, manager-usable case, Career Compass is worth a look. Not because it can guarantee anything — it cannot — but because when the company gets fuzzy, your case does not have to.