Questions to Ask New Boss After Reorganization
Questions for the first conversations with the person you now report to after a reorganization, covering what changed in your role, who holds which decisions, how your work will be judged this cycle, and which parts of the new structure are still unsettled.
The questions
Open any question for the note
How would you describe what our group is responsible for now, and what it is not?
Why ask it
Reorganizations redraw boundaries, and the second half of the question is the part that prevents months of duplicated work. If your new boss cannot yet say what sits outside the group, the structure is still being negotiated above them.
What has changed about my role, and what has stayed the same?
Why ask it
Most people are told the new reporting line and nothing else, then guess at the rest. Asking for both halves stops you quietly dropping work that is still yours or picking up work that is not.
Who do I go to now for the things I used to take to my previous manager?
Why ask it
Approvals, budget sign-off and technical review often move to different people at different times, and requests sent to the old owner simply sit. Ask for names, not functions.
Which decisions are mine, which are yours, and which go higher than you?
Why ask it
This is the single most useful thing to establish early, because getting it wrong looks either like overstepping or like being unable to act. A boss who answers only in principles has not yet been given clear authority themselves.
What were you told about our team when you took this on?
Why ask it
Reveals the brief they are working from, which may include assumptions about performance or headcount that you can correct now. It also tells you whether they arrived with a mandate to change things or to steady them.
What do you already know about what I work on, and what would be useful for me to fill in?
Why ask it
New bosses inherit a summary, not the detail, and the gaps are where credit and context get lost. Offer one page rather than a meeting: they are reading a great deal at the moment.
What are the two or three things you need to see happen in the next quarter?
Why ask it
Forces a short list rather than a survey of priorities, and gives you something to hold your work against. If everything is urgent, that is information about how the group will be run.
How will my work be judged this cycle, and by whom? Did the criteria change?
Why ask it
After a reorganization, goals set under a previous manager often no longer count, and nobody says so out loud. Ask whether your existing goals still stand and who will write your review.
Does the reorganization change my level, title or compensation?
Why ask it
Uncomfortable to ask, and much worse to discover in a payslip or an org chart. A straight answer, including nothing has changed, is what you need before you accept new scope.
Are any of the projects I am on being stopped, moved, or absorbed somewhere else?
Why ask it
People keep working on cancelled projects for months because nobody told them. Ask specifically about anything you are more than halfway through, and ask who would tell you if that changed.
Is there work that came out of this change that nobody owns yet?
Why ask it
Reorganizations create orphaned responsibilities, and these are the most straightforward openings available to you. Volunteering for one is also how people end up quietly carrying two jobs, so ask what would come off your plate.
Who else has moved into this group, and how are overlapping responsibilities being sorted out?
Why ask it
Two people arriving with claims on the same work is the most common friction after a merge of teams. Better to raise it as a structural question now than as a personal dispute in three months.
How often do you want to meet one to one, and what do you want those meetings to cover?
Why ask it
Sets the rhythm before it is set by default, which after a reorganization tends to mean not at all. Ask whether they want status in the meeting or in writing beforehand.
How do you prefer bad news to reach you?
Why ask it
The answer tells you what they will actually do when something slips: some want it immediately and unpolished, others want a proposed fix attached. Getting this wrong once is what damages new working relationships fastest.
What does a useful written update look like to you?
Why ask it
Length, frequency and format vary enormously between managers, and guessing wastes your time and theirs. Ask for an example of an update they thought was good.
Where do you want me to push back, and where would you rather I just get on with it?
Why ask it
Gives you permission to disagree in the places it is welcome, which is much harder to judge with someone new. Someone who says they always want challenge should be asked for a recent example of changing their mind.
What is still unsettled about the new structure?
Why ask it
Reorganizations are announced as finished long before they are, and knowing which parts are provisional stops you building on sand. An honest answer here is a good sign about how much you will be told in future.
Is more change expected in the next few months, and would you tell me if you knew?
Why ask it
The second half is the real question, and the way they handle it tells you what kind of manager you now have. Watch for whether they distinguish between what they cannot say and what they do not know.
What have you seen go wrong in reorganizations before that you want to avoid here?
Why ask it
Invites a candid answer without asking them to criticize the company. It usually surfaces their real worry, whether that is losing people, losing momentum, or a service quietly failing during the handover.
Six months from now, what would make you say this worked?
Why ask it
Ends on their definition of success, which is often more concrete than any official rationale for the change. Compare it with what you were told publicly, since the difference is where the actual priorities sit.
Finding your footing after a reorganization
Practical guidance for the conversation itself
Before the first conversation
- 1Write one page on what you own, what you have delivered in the last six months, and who depends on you. Your new boss inherited a headcount line, not this.
- 2Find out what they did before this role. It tells you which parts of your work they will understand without explanation and which you will have to translate.
- 3Decide your two most important questions. First meetings get cut short, and the ones about your own role are the ones nobody else will raise for you.
- 4Do not lead with grievances about the old structure. It is the fastest way to be filed as part of the problem being solved.
Reading the answers
Vagueness about decision rights means more change
If nobody can say who approves what, the structure above your boss is still moving. Expect another adjustment, and keep decisions documented in writing until it settles.
Silence about your goals is not agreement
Objectives written under a previous manager are frequently ignored at review time. Get confirmation in writing that they still count, or get new ones.
Watch what they ask you
A new boss who asks what is broken, who is good, and what they should not touch is orienting properly. One who arrives with the answers already decided is telling you their mandate came with instructions.
The first weeks
- Send a short written summary after each early conversation, listing what you understood and what you will do. It creates a record while everything is fluid.
- Meet your new peers before you need something from them. After a reorganization, most delays are caused by unclear handovers between people who have not spoken.
- Keep delivering something visible. Attention is scarce during a transition, and finished work is the most reliable way to be counted.
- Keep your own notes on who now owns what. The official chart will lag reality by weeks.
What goes wrong
- Waiting to be told. Nobody has a complete picture in the first month, so the people who ask early are the ones who get clarity.
- Accepting new scope without asking what comes off your plate. Reorganizations are how quiet workload increases become permanent.
- Comparing everything to how the last manager did it, out loud. Say it once if it matters, then stop.
- Treating the announcement as the plan. What is written in the announcement and what happens in practice diverge within weeks.