New Boss After A Reorg? Treat It Like A New Job

Last updated: September 2026

A Director of Product I coach was two years into his role, confident in it, good at it. Then his company acquired another one. In January he sat down to write his annual goals and this is what came out:

“I started putting together OKRs for this year. I’m like, I don’t even know what we’re doing. I don’t know what company we are. I don’t know how this is going to work.”

He had not changed employers. He had not applied for anything, interviewed anywhere, or negotiated a start date. And he was starting a new job.

That is the part most reorg advice skips. You are not adjusting to a change. You are onboarding, without any of the things that normally come with onboarding: no ramp-up period, no welcome meeting, no one whose job it is to explain the place to you. If you treat it as a disruption to get through, you will wait for clarity that nobody is coming to give you. If you treat it as a first week, you know exactly what to do, because you have done a first week before.

Why does a reorg feel like starting over when you didn’t go anywhere?
What does it mean to treat a reorg like a new job?
What changes when your manager stays the same and everything else moves?
How do you read a signal nobody explains?
What do you say to a new manager who is also drowning?
What do you owe your team while you’re still figuring out your own job?
What happens if you get this right?
FAQ

Why does a reorg feel like starting over when you didn’t go anywhere?

Because you did start over. You kept the badge and lost almost everything else it stood for.

The person who knew what you were worth is gone, or is now three levels away, or is suddenly your peer. The scope you spent a year defending is on someone’s slide as a box that might move. The people who used to route decisions through you have a new org chart on their desk and are quietly working out whether you are still on it. Sometimes you also lose the desk, which sounds trivial until your team is scattered across a different floor and the hallway conversations that used to do half your coordinating just stop happening.

Everything you built that was not written down has to be rebuilt. Relationships, credibility, the sense people had of what you are good at. None of it transferred, because the thing it was attached to no longer exists in the same shape.

There is a 2026 version of this that makes it worse. Companies are flattening, and they are doing it through reorgs rather than through design. Gartner projects that through 2026, one in five organizations will use AI to flatten their structure, cutting more than half of their middle management roles. Amazon raised its ratio of individual contributors to managers by 15% in a single quarter. The practical consequence for you is specific: the person above you may not know the answer either. You are not being kept in the dark. There may not be a light on anywhere.

What does it mean to treat a reorg like a new job?

It means running the same play you would run in your first ninety days somewhere new, on purpose, starting now.

I use The First 90 Days by Michael D. Watkins with clients who are stepping into a new role, and I have started using it with clients who have not gone anywhere at all. It is written for people joining a new company, but almost none of it depends on that being literally true. The moves are the same:

You are rebuilding trust with people who did not choose you. Your new manager did not hire you. Your new peers did not interview you. Whatever reputation you had was earned in a structure that no longer exists, and you cannot assume it survived the reorganization intact.

You are learning expectations nobody wrote down. The old definition of good work in your role came from a manager who may be gone and a strategy that may be retired. Somebody now has a picture in their head of what your job is. It is probably not identical to yours, and nobody is going to volunteer the difference.

You are establishing a working relationship from scratch. How this person likes to be briefed, what they do with bad news, how much detail they want, whether they would rather read something before the meeting or talk it through in the room. You learned all of this about your last manager over months. You are back at zero and pretending otherwise costs you.

Here is why the frame matters more than any individual tactic. A reorg is volatile. It is a turmoil-filled time when people question motivations and reset expectations, and plenty of them go into it in a bad state of mind, waiting to find out what is being done to them. Deciding it is a new job is what moves you from being someone things are happening to, into someone with a first week to run. Same facts, completely different set of available actions.

The clients who do well in a reorg are not the ones who read the politics best. They are the ones who start onboarding before anyone tells them to.

What changes when your manager stays the same and everything else moves?

You can keep your manager and still be in an entirely new job. This is the version nobody writes about, and it is extremely common for people who manage people.

The Director above kept his direct manager through the whole acquisition. Everything underneath him changed. The reporting structure beneath him was rebuilt, he ended up with four direct reports, the engineering organization he worked with went from around thirty people to about a hundred, and in the middle of all of it his team had to move offices.

Nothing in the standard advice covers this. The standard advice assumes the change came to you through your reporting line, and that your task is to get your new boss up to speed on your value. His boss already knew his value. His problem was that he was now running a function inside a company twice the size, with people he had not hired, at a scale he had not operated at, and there was no version of “build trust with your new manager” that touched any of it.

If this is your situation, the new-job frame still holds, but you are the new hire and the hiring manager at the same time. You are onboarding yourself into a larger job while onboarding a team into a structure none of you have worked in before. Both are real. The mistake is treating only the first one as your actual work, because the second one is where your people are watching.

How do you read a signal nobody explains?

You read it against the pattern, and then you go ask.

Reorgs and acquisitions run on signals that arrive without explanation. You get added to a distribution list. You are asked for headcount numbers with no stated reason. You get access to the acquired company’s systems and nobody says why.

A client of mine, a senior product leader, was one of a handful of people given access to the acquired company’s systems. No explanation came with it. His read was, roughly, I assume this means I’ll be involved in something, I’m just not sure what.

That signal almost always means something specific. You have been identified as someone who will evaluate the other company’s products or systems, or you are being considered to take responsibility for some of them. I have been through acquisitions where it played out exactly that way. Access is rarely administrative. Somebody put your name on a list on purpose.

Most people sit with a signal like that and quietly decide what it means. That is the expensive move, because you will usually decide something smaller than the truth, and then act accordingly.

The better move is boring and almost free. Go to whoever sent it, thank them, and ask how the decision was made. Ask what they expect you to do with the access, and what mindset you should have when you are using it. You are not fishing for reassurance. You are getting a read on where you sit, from someone who actually knows.

What that conversation is really for is not the information. It is the doubt. Most senior people in a reorg are privately unsure whether they are still considered central, and that uncertainty leaks into how they show up in rooms where it matters. Asking a direct question and getting a direct answer settles something internally that no amount of interpreting the org chart will settle. You stop performing confidence you do not have, and start acting on something you actually know.

What do you say to a new manager who is also drowning?

First of all, start with empathy. Say something like: “I know you’re in a tough situation. We’re all in a tough situation. How can I help you be successful?”

That is not softness and it is not patience. It is the fastest way to find out what your new manager is actually being measured on, which is the thing you most need to know and the thing nobody will tell you unprompted.

Think about what the person on the other side of that conversation is dealing with. They are drinking from a firehose. They likely have a new boss of their own and pressure coming down from above. They have more direct reports than they have ever had, possibly more than anyone should reasonably have. And here is the part that rarely gets said: in tech especially, a lot of these managers are not experienced people managers. They have never run a team this size. They have never watched anyone else do it well at this scale. They do not have a model to follow, and they are unlikely to admit that to someone who reports to them.

If you walk in assuming the relationship is adversarial, you will read every ambiguous thing they do as a threat, and you will be wrong often enough to do real damage to a relationship you need. Assume good intentions, do not take the disruption personally, and put yourself in their seat long enough to work out what winning looks like for them.

Then use it. Once you know what they are being measured on, you know how to frame everything you want, which is the practical reason to do any of this.

What do you owe your team while you’re still figuring out your own job?

A standing meeting, before you have answers.

The instinct is to wait until you can tell them something definite. Do not. In a reorg, your people are generating explanations for the silence, and the explanations are worse than the truth. Put a recurring team meeting on the calendar so all of your direct reports are in the same room on a known cadence, and protect your one-on-ones even when it feels like there is nothing to report. Especially then. The cadence itself is the message: this is still a team, somebody is still paying attention to you, and you will hear things from me rather than from a rumor.

You do not need the final org chart to do this. That is the point. Steadying a team is available to you immediately and requires no information you do not already have.

What is harder, and what the meeting cannot do for you, is the deciding. At some point you will have to choose what to defend for your people and what to let go, which projects to fight for, which scope to argue you should keep, whose role you go to the mat for. Each of those spends credibility you are still rebuilding, in a structure that is still moving, with a manager whose priorities you are still learning. Get that sequence wrong and you spend everything you have on the thing that was never going to survive anyway.

That judgment is the actual work of a reorg, and it is the part that does not come with a framework.

What happens if you get this right?

Often, you come out of it with more than you went in with.

The client I have been describing went into the acquisition as a Director of Product. He came out of it a Senior Director, with a larger team and a bigger remit.

Nobody handed him a clean explanation of why. That happens more than it should, and it leaves people guessing about their own promotion. But both of us read it the same way: it had to do with how he showed up while everything was unsettled. He was in the rooms. He asked the questions. He kept his team steady while he was still working out what his own job had become.

This is the part worth knowing if you are in one right now. A reorg is one of the few stretches where senior people are being evaluated closely and informally at the same time. Somebody is deciding who is indispensable in the new structure, and they are doing it based on what they watch you do over a few uncertain months, not on your last performance review. Treating it as a new job and running it properly is not only how you get through it. It is frequently how people come out the other side with a bigger one.

FAQ

How long should I wait before pushing back on a new boss after a reorg?
Push back early on small things, and hold the significant disagreements until you understand what they are being measured on. The first weeks are for finding out what they care about, not for winning arguments. But going completely quiet for months trains them to see you as someone who does not have a point of view, and that is a harder impression to reverse than an early disagreement.

Should I ask directly whether my role or my headcount is at risk?
Ask what the plan is for your area and how decisions are being made, rather than asking for a guarantee about yourself. Nobody can promise you an outcome in the middle of a restructuring, so a direct question about risk usually produces a non-answer that leaves you more anxious than before. A question about process gets you something real, and it tells you where in the sequence the decision sits.

What if my new manager is less experienced than I am?
Fairly common in a flattening org, and it does not change your job. Do not compete with them on experience. Work out what they are accountable for, be the person who makes that easier, and be honest with yourself about whether the thing bothering you is their judgment or the fact that you wanted the seat. Those require different responses.

How do I write goals when I don’t know what the org will look like?
Write them against what will be true in any version of the outcome. Customer commitments, revenue-critical work, and the things that will still matter whoever ends up running the function. Mark the rest as provisional and say so out loud when you present it. A plan with its assumptions stated is more credible in a reorg than a confident plan everyone knows is fiction.

What if my manager didn’t change but everything below me did?
You are still in a new job. Your scope, your team, and the scale you are operating at all changed, even though your reporting line did not. Onboard yourself into the larger role deliberately, and onboard your team into the new structure at the same time. Do not assume that keeping your manager means you kept your job description.

One more thing

If you are in the middle of one of these right now, the part you are stuck on is probably not information. It is the call about what to spend your credibility on while the ground is still moving, and there is no template for that.

That is the kind of call I work on with product leaders. Book a call if you want to think one through. Thirty minutes, no pitch.

Related reading:

This post contains an affiliate link to a book I use with clients. If you buy through it I earn a small commission, at no extra cost to you.