Questions to Ask When Taking Over a New Department
Questions for a new department head in the first weeks, to ask your boss, the team you inherited, and the groups that depend on you, covering why the seat opened, what is already committed, who is holding the place together, and what everyone expects you to change.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
Why is this seat open now?
Ask your boss and then ask two people on the team, and compare. A promotion, a resignation, and a removal produce very different rooms, and the version told upward is often shorter than the version told sideways.
- 2
Who has been running things since the seat emptied?
There is almost always a person who absorbed the decisions, whether or not they were asked to. They know where everything is, they may have wanted the job, and how you treat them in week one sets the tone for the year.
- 3
What does this department do that no other group here could do?
If your boss struggles to answer, you are running a department whose existence is up for debate, and your first job is defining it rather than improving it. Ask the same question of the team and watch how far apart the answers are.
- 4
When people in other departments complain about us, what do they say?
Every group has a reputation it cannot hear from the inside: too slow, too precious, impossible to get a straight answer from. The complaint is usually exaggerated and usually has a real cause underneath it.
- 5
What commitments have already been made on my behalf?
Dates, budgets, headcount, and favors promised to other teams do not leave with your predecessor. Finding them in month one lets you renegotiate. Finding them in month four makes you the person who broke a promise.
- 6
What is the budget, and how much of it is already spent or committed?
The number you are given is the annual figure. The number that matters is what is uncommitted, after contracts, licenses, and salaries. Ask when renewals land, because those dates are the only real decision points you have.
- 7
Which roles are open, and how long have they been open?
A role open for eight months is either impossible to fill at the offered pay or quietly being used to make the budget look better. Either explanation changes how you plan the year.
- 8
Who here would be hardest to replace, and what happens if they leave?
Ask this of your boss and of the team separately. The names people outside give are usually the loudest ones. The names insiders give are usually the person holding some system together with no documentation.
- 9
Who is overdue for a promotion or being paid below what they should be?
Inherited pay problems are the fastest resignations a new leader faces, and they are almost never raised voluntarily in your first month. Ask before someone else makes them your emergency.
- 10
What did my predecessor do well that I should not undo?
New leaders reliably overcorrect against whatever they were hired to fix and take good practices out with the bad. Asking this in the open also signals that you are not planning to erase everyone's last three years.
- 11
What did people expect from the last leader and never get?
This surfaces the standing disappointment you will be measured against without being told. It might be career conversations, decisions that never came back, or air cover in meetings with other departments.
- 12
What is the thing everyone knows is broken that nobody has managed to fix?
Every department has one, and the interesting part is why previous attempts failed. If three people have tried, the obstacle is probably political rather than technical, and your fresh plan will hit the same wall.
- 13
What should I be careful not to break in my first ninety days?
Ask each person individually. You get the fragile dependencies, the informal arrangements, and the one process that looks pointless and is holding up something important.
- 14
Which meetings would you drop if you could?
Meeting load is the cheapest early change you can make and the one people notice most. It also tells you where coordination has been substituted for a decision nobody wants to make.
- 15
Which numbers do you actually look at when you think about this group?
Ask your boss, and expect the answer to differ from the dashboard you inherited. You will be assessed on the two or three they name, not on the twenty your predecessor reported.
- 16
Where do we depend on another team, and how well does that work?
Cross-team dependencies are where deadlines quietly die. Ask who the counterpart is, whether there is a history, and whether anything is currently stuck waiting on someone you have not met.
- 17
What was the last significant change here, and how did it land?
The team's response to your plans is largely set by what happened the last time someone reorganized them. If the last change was announced and then abandoned, expect polite agreement and no movement.
- 18
What is one thing you want me to say to the whole department in my first week?
Asking a few people this before you speak keeps you from opening with a message that answers a question nobody is asking. Usually the request is about job security, direction, or whether the pending decision is finally being made.
- 19
What would you change if you had my job?
Ask everyone, including the quietest people. Repeated answers point at a real problem. Answers only one person gives tell you a great deal about that person, which is also useful.
- 20
Six months from now, what would make you say this went well?
Ask your boss last, once you know enough to hear whether the answer is achievable. If it depends on a hire you cannot make or a team you do not control, negotiate that now rather than reporting on it later.
Your first weeks running a department you did not build
Practical guidance for the conversation itself.
How to run the first round of conversations
How to run the first round of conversations
Talk to everyone before you change anything
Thirty minutes each, same handful of questions, no promises. The point is not only what people say. It is that by the time you announce something, nobody can say you never asked them.
Ask the same question up, down and sideways
Why is this seat open, what does this group do well, what is broken. The gaps between the three versions are the most reliable map of the department you will get, and the gaps close quickly once people adjust to you.
Write down names, not just problems
Who owns the flaky system, who other teams call directly, who people check with before sending something. Informal authority is invisible on the org chart and it decides whether your changes take.
Say clearly what you are not going to do yet
Silence in the first weeks gets read as a reorganization being drafted. Telling people you are not making structural changes before a certain date buys you a calmer set of conversations.
Reading the department before you rearrange it
Reading the department before you rearrange it
- Look at where the money goes before you look at the strategy deck. Contracts and headcount describe the real priorities better than any plan does.
- Find the work that generates the loudest complaints from outside and sit through it once yourself, end to end.
- Read the last two years of the group's status reports in one sitting. The pattern of what keeps being described as almost done is the pattern you inherited.
- Check which open roles have been open longest, and ask what the offered pay was compared with the last accepted offer.
- Notice who answers on behalf of others in group meetings, and check whether the quiet people agree in private.
- Ask a peer in another department what they wish this group would stop doing. They will tell you things your own team has stopped noticing.
Things worth chasing down early
Things worth chasing down early
- A promotion or raise your predecessor promised verbally and never processed.
- A contract or license renewing in the next quarter that nobody has reviewed.
- Two people who both believe they own the same area.
- A commitment made to another department with a date attached that your team has not started.
- A key system that only one person understands and that has no written documentation.
- Any answer that begins with the previous head just handled that personally.