Questions to Ask a New Boss
Questions to ask a new boss in a first meeting and in the early one-to-ones that follow it. As a new hire, the smart questions to ask your boss are the plain operating ones: what they will judge you on, how they want to hear bad news, what you can decide alone, the pressure they are under, and the habits that annoy them. Written for anyone just hired into a new job or inheriting a new manager.
The questions
Each question, and why to ask it
What would you like me to focus on in my first month?
Why ask it
Gives them an easy, concrete opening and gives you something to be measured against. A manager who cannot name anything specific is telling you the role is undefined, which is worth knowing in week one rather than month six.
Three months from now, what would make you say this was going well?
Why ask it
Forces the answer into observable outcomes rather than adjectives like proactive or reliable. Whatever they name here is what your first review will actually be about, whether or not it appears in the job description.
What does your week look like, and when is the worst time to bring you something?
Why ask it
Practical and rarely asked. Knowing which days are consumed by their own reporting cycle saves you from raising an important decision at the moment they have the least capacity for it.
How do you want to hear about problems: straight away, or in our one-to-one?
Why ask it
The single most useful thing to establish, because the mismatch causes most early friction. Some managers want a message the moment something slips; others treat that as panic, and you cannot guess which.
What kind of update do you find useful, and how often?
Why ask it
Ask for an example of a good one from someone else. Managers differ enormously in appetite for detail, and the ones who say keep it brief often mean weekly rather than never.
What was it in the interviews that made you decide to hire me?
Why ask it
Whatever tipped the decision is the first thing they expect to see from you. If they name something you treated as a side note in the interview, that is the strength to show early.
Has anything about the role or the team changed since I accepted the offer?
Why ask it
Weeks pass between an offer and a start date, and budgets, projects and reporting lines move in that time. The first meeting is the cheap moment to learn that the work you were hired for has been paused or handed to someone else.
How did you come to be running this team?
Why ask it
Few people ask a boss about their own route in, and it makes the first meeting less of a briefing. Listen for whether they built the team, inherited it, or were brought in to fix it, because each of those bosses wants something different from a newcomer.
What should I read or sit in on before we next talk?
Why ask it
A first meeting is short and you leave it knowing very little. Asking for homework gets you the two documents or the one standing call that explain the team, rather than a link to the whole shared drive.
What can I decide on my own, and what should come to you first?
Why ask it
Explicit decision rights prevent both the overstep and the bottleneck. If the boundary is fuzzy, ask about a specific decision you expect to face this month rather than in general.
What are you being measured on this year?
Why ask it
Their targets are the reason some of your work gets attention and some does not. Understanding the pressure above them explains behaviour that otherwise looks arbitrary, and it lets you offer help that actually counts.
What is the team known for, and what is it known for getting wrong?
Why ask it
The second half is where the information is. A manager willing to name the team's reputation problem is inviting you to help fix it, and one who insists there isn't one may not hear criticism at all.
Who outside the team do I most need a good relationship with?
Why ask it
Names and reasons, not an org chart. This surfaces the people whose cooperation you will need and any history you would otherwise walk into unaware.
How does work usually reach me: through you, or directly from others?
Why ask it
Determines whether you can be pulled in several directions and who resolves it. If requests come in directly, ask what you should do when two of them conflict.
What did my predecessor do well, and what would you like done differently?
Why ask it
The most efficient way to learn the unwritten expectations of the role. It also reveals whether the person left of their own accord, which changes how you read the rest of the answers.
What do you find frustrating in how people work with you?
Why ask it
Asked directly, most managers will answer honestly, and the answer is usually specific: long emails, meetings without an agenda, being copied on everything. These are cheap habits to change if you know them early.
How do you prefer to give feedback, and can I ask for it directly?
Why ask it
Establishes whether feedback arrives in the moment, in one-to-ones, or only at review time. Managers who default to the last of these will still give it if asked, but you have to ask.
How much of my job is fixed, and where is there room to change things?
Why ask it
Distinguishes the parts of the role you are expected to maintain from the parts you are expected to improve. Getting this wrong is why new hires either look passive or look like they are trampling on things.
What is the norm here for hours and for being reachable in the evening?
Why ask it
Ask what they do and what they expect, since those often differ. A manager who says they email late but does not expect a reply should be asked to confirm that plainly, because the team copies behaviour rather than policy.
How do meetings work here, and which ones should I be in?
Why ask it
Also worth asking which you can leave. New starters get added to standing meetings by default and spend months in rooms where their presence changes nothing.
When people disagree in this team, how does it usually get resolved?
Why ask it
Look for whether disagreement is aired in the room or handled privately afterwards. Getting this wrong in your first weeks is the most common way a new person acquires a reputation they did not intend.
What is the constraint on the team right now: people, budget, or something else?
Why ask it
The answer tells you which suggestions have any chance of being adopted. Proposing solutions that require the missing resource is how new hires get labelled unrealistic.
What growth is realistically available in this role over the next couple of years?
Why ask it
Ask for the actual mechanism: promotion cycles, the criteria, who decides. A vague answer about opportunity for those who perform usually means there is no defined path, and it is better to know now.
What do people take a while to work out about working with you?
Why ask it
A softer way of asking about their blind spots, and most managers enjoy answering it. What they volunteer, that they go quiet when thinking, or push back hard and then agree, saves you weeks of misreading them.
What are the two or three things you most want this team to get done this quarter?
Why ask it
Forcing a short list is the point. A boss who lists nine priorities has not chosen yet, which means the choosing will happen later by accident and you will be the one who guessed wrong.
Of the things I am responsible for, which matters most to you, and which could slip without much cost?
Why ask it
Asking what could slip is the part that produces honest prioritization, because it forces a ranking rather than a list. If the answer is that everything is critical, that is a signal about the manager as much as about the work.
What do you need from me in the first two weeks that would make your life easier?
Why ask it
It offers help rather than requesting onboarding, which tends to get a specific and immediately useful answer. Whatever they name, do it visibly, because the first thing you deliver sets the assumption about everything after.
What is on fire right now that I should stay away from for the moment?
Why ask it
New people often wade into a live political problem because nobody warned them. The answer also tells you which battles are already lost or already assigned, which saves you weeks of misdirected effort.
How often do you want one-on-ones, and what do you want them used for?
Why ask it
Status reporting, problem solving, and career conversation are three different meetings. Agreeing which one this is prevents the slow drift into a weekly recital of your task list.
What should never be a surprise to you?
Why ask it
Most managers have one or two specific things: a slipped deadline, a customer complaint, a conversation with someone senior. These are the tripwires in the relationship, and they are much easier to hear about now than after you cross one.
How would you like me to disagree with you, especially in front of other people?
Why ask it
The answer sets the rules for the most consequential interaction you will have with them. A boss who wants disagreement raised privately first is telling you something useful about how meetings here work.
What is something you would like me to push back on?
Why ask it
The answer tells you whether disagreement is genuinely welcome and, if so, in what setting: privately, in writing, or in the room. A manager who cannot name anything is telling you to be careful, whatever their stated policy on candor.
What are you still working out about this team?
Why ask it
Admitting an open question is a good sign, and the gap they name is often where you can be most useful. If they claim to have the whole picture in week two, calibrate accordingly.
Is the team hoping anything changes now that I am here?
Why ask it
New arrivals are usually loaded with expectations nobody has stated, and hearing them early prevents a slow disappointment. Compare what your manager says to what the team tells you, because the two lists often differ in revealing ways.
Is there history on this team or this project I should know before I put my foot in it?
Why ask it
There is almost always a failed initiative, a departure, or a reorganization that still shapes how people react. Not knowing about it means eventually proposing something that sounds sensible to you and lands badly for reasons nobody explains.
How is my performance reviewed here, and who else has a say besides you?
Why ask it
Review processes often involve peer input, calibration meetings, or a skip level, and the mechanics change who you need to keep informed. Asking now is routine; asking a week before review season looks anxious.
How do you judge whether someone is ready for more responsibility?
Why ask it
You are asking for criteria, not a promise. Vagueness here is common and is itself worth knowing, since it means progression will be decided by visibility rather than by any stated standard.
What would you like me to bring you in three months that you do not have today?
Why ask it
It turns a vague expectation of impact into a deliverable you can both name, which is exactly what you want on record. If they cannot answer, suggest something concrete and ask whether it would be worth having.
What do you think I am likely to get wrong in this role?
Why ask it
Uncomfortable to ask and unusually informative, because managers form a prediction early and rarely share it unprompted. Do not defend yourself against the answer; write it down and check yourself against it in a month.
Is there anything you would rather I heard from you than from someone else?
Why ask it
A reorganisation, a departure, a struggling project, or their own doubts about a plan. Asking plainly gives them a clean opening, and a pause before the answer is worth paying attention to.
Early one-to-ones with a new manager
Practical guidance for the conversation itself
How to use these
Three at a time, not twenty
Bringing a list to a first meeting turns it into an interrogation and the answers get shorter. Pick three, spread the rest across your first six weeks, and open each one-to-one with one of them.
What to ask a new boss in the first meeting
The first meeting is usually short, and they will do half the talking. Ask what they want from your first month, how they like to hear about problems, and what you should read before the next one. Decision rights and career can wait for the second or third conversation.
Ask the operating questions first
How they want bad news, what you can decide alone, and what they are measured on are the three that prevent early mistakes. Career and growth questions land better once you have delivered something.
Write down the answers and repeat them back
Send a short note after the conversation summarising what you understood. It catches misreadings while they are cheap and shows you treat their time as worth acting on.
Check the answers against what happens
Managers describe how they want to work, not always how they do. If someone says they want problems early and then reacts badly, believe the reaction and adjust.
If the manager is new to the team
Expect not to get answers yet
A manager in their own first month cannot tell you the team's priorities because they are still working them out. Offer context instead: what has been tried, what failed, and who knows what.
Do not lobby in the first fortnight
New managers are flooded with people making cases. Waiting a few weeks, then raising one well-prepared issue, gets a far better hearing than being early and indistinguishable from the queue.
Say plainly what you want to be doing
A new manager reassigns work in their first months and will use whatever information they have. If you never state a preference, you will be allocated according to the previous manager's assumptions.
Common mistakes
Asking only about yourself
A first conversation entirely about your objectives and progression reads as self-interest. Asking what pressure they are under changes the tone and usually produces more useful information anyway.
Taking the org chart at face value
Influence rarely matches reporting lines. Ask who actually needs to agree before something happens, because that is the answer that determines whether your work goes anywhere.
Treating an answer as permanent
Priorities move when the pressure above your manager moves. Re-ask what matters most every quarter rather than working from what you were told in week one.
Never asking about their frustrations
Most of the habits that damage a working relationship are small and easily fixed. If you never ask, you find out about them at a review instead.