Questions to Ask New Manager
Questions for the first few weeks reporting to someone new, whether you changed jobs or your old manager was replaced. They cover how updates and access work, which decisions are yours, what the team is already struggling with, and what your manager is under pressure to deliver.
The questions
Open any question for the note
How do you prefer to hear from me: quick messages, scheduled check-ins, or written updates?
Why ask it
Mismatched channels cause most early friction. If they read chat once a day and you treat it as instant, you will look unresponsive. A single clear preference is better news than "whatever works for you," which usually means they have not thought about it.
How often would you like us to meet one on one, and who brings the agenda?
Why ask it
The cadence matters less than who sets the agenda. If they run it, expect status reporting. If they want your list, you have room to raise problems while they are still small.
What does a good first ninety days look like to you?
Why ask it
A vague answer like "settle in and meet people" means the job has not really been defined yet, which is worth knowing on day one. A specific answer gives you a standard you both agreed to out loud.
Which parts of my job matter most right now, and which can wait until later in the year?
Why ask it
The second half is the useful half. A manager who cannot name anything as lower priority will treat every later request as urgent, and you will be the one absorbing that.
What is the team working on that I should understand before I start weighing in?
Why ask it
This surfaces history you would otherwise step on: a project someone fought hard for, a vendor already tried and dropped, a decision that is settled and not open again.
How will you judge whether I am doing well, and when will we review it formally?
Why ask it
The formal review date and their private opinion of you are rarely formed at the same time. If the answer is only "the annual cycle," ask what they would notice by week six, because that is what actually shapes the review.
Which decisions do you want to be part of, and which do you expect me to make alone?
Why ask it
The gap between those two lists is your real authority, and it is usually wider or narrower than the job description implied. Wanting in on everything says as much about their bandwidth as about your latitude.
When something goes wrong, do you want to hear it right away or once I have a plan?
Why ask it
This tells you how bad news travels here. Managers who want a plan attached tend to react badly to raw problems. Ones who want it immediately are usually trying to avoid being surprised by their own boss.
What are your working hours, and when is it fair to contact you outside them?
Why ask it
Answers range from "I am offline after six" to "I send mail at midnight and expect no reply." Either is workable once said. What costs you is guessing, and then either interrupting them or waiting on an answer that was never coming.
Who outside the team will I depend on most, and what should I know about them?
Why ask it
The names come easily; the context is what you are after. This is where you find out which relationships are already strained, before your first request to that group lands badly.
How do you decide who gets which project when everyone is already busy?
Why ask it
Listen for whether the answer describes a process or a personality. If work goes to whoever asks loudest or whoever they trust most, that is still an answer, and you now know how to get the projects you want.
What is on the team's plate right now that is not going well?
Why ask it
Someone willing to name a struggling project in your first week will tell you the truth later. "Nothing major" usually means you will find the problem yourself in a month, without the head start.
What does the org chart not tell me about how work actually gets done here?
Why ask it
Most places have someone with informal veto power who does not appear on any diagram. Learning who that is beats discovering it by routing a decision around them by accident.
What tends to frustrate you in how people work?
Why ask it
This is the closest you will get to their unwritten rules: deadlines missed without warning, being copied on everything, meetings with no agenda. Whatever they name, some earlier report did it.
What did the person before me do well, and what would you want handled differently?
Why ask it
The praise tells you the baseline standard. The "differently" half tells you what you were actually hired to fix, which is often nowhere in the job posting.
When two people on the team disagree, do you step in or let them work it out?
Why ask it
A manager who always intervenes makes open disagreement expensive, so people take it offline. One who never intervenes may be leaving stale conflict for the team to carry.
How does good work here get noticed outside the team?
Why ask it
Recognition that never leaves the team caps how far your work can carry you. If they cannot describe any path for visibility, assume you will have to build it yourself.
Where have people on this team gone next, and what got them there?
Why ask it
Actual destinations are stronger evidence than any promise about growth paths. If nobody has moved up or out in several years, the answer is the silence.
What is your own manager pressing you on this quarter?
Why ask it
Their pressure becomes your priorities whether anyone says so or not. Knowing the real target lets you volunteer for work that will register, instead of work that is merely tidy.
What part of your job would you most like to hand off?
Why ask it
Most managers have one task they resent keeping. Offering to take it is a cheap way to become useful, and the answer shows you exactly where they feel stretched.
Using these questions with a new manager
Practical guidance for the conversation itself
Spread them out, do not run a list
First conversation
Logistics only: how they want updates, meeting cadence, working hours, what the first ninety days should look like. These are easy to answer and set up everything else.
Weeks two and three
Priorities, decision rights, who you depend on outside the team, how work gets assigned. By now you have met enough people to ask about specifics rather than in the abstract.
Week four onward
The uncomfortable ones: what is going badly, what frustrates them, what their own boss is pushing. Save these until they have some reason to trust you with the answer.
Getting past the polished answer
- Ask for an example. "Can you think of a time that came up?" turns a stated preference into something you can actually act on.
- Ask about the last instance, not the general rule. "How did the last project get assigned?" beats "how do you assign projects?"
- Let a pause run. New managers often give the official answer first and the honest one four seconds later.
- Do not argue with an answer you dislike in the first month. Note it, watch whether behavior matches, and raise it once you have evidence.
What to do with the answers
- Write down what they said about priorities and read it back in your next meeting. Priorities drift, and a shared record protects you when they do.
- Turn the ninety day answer into three or four things you can show. Vague mandates get judged by feel; specific ones get judged by what you produced.
- If they named something going badly, come back in two weeks with one concrete offer of help rather than a general willingness to help.
- If their stated preferences and their behavior diverge, follow the behavior and adjust quietly. Pointing out the contradiction rarely changes it.
Answers worth taking seriously
- No lower priorities named. Everything will be urgent, and you will be blamed for the sequencing.
- No one has been promoted or moved on from the team in years, and they cannot say why.
- They want to be involved in every decision but are hard to reach. That combination stalls work and the delay lands on you.
- They cannot name anything the previous person did well. Expect the same treatment when you leave.