Good Questions to Ask a New Boss
Questions for the first weeks with a new boss, whether you are new or they are: what they want done this quarter, what good looks like in your role, how they want updates and bad news, which decisions they want in on, and how to disagree with them well.
The questions
Open any question for the note
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.
What is your own boss judged on, and how does our work show up in that?
Why ask it
Understanding what lands on their performance review tells you which of your work will get attention and which will be quietly deprioritised, however worthy it is.
What does good look like in my role ninety days from now?
Why ask it
You want observable outcomes, not adjectives. If the answer is that they will know it when they see it, propose two or three concrete markers yourself and ask them to correct the list.
What is currently on my plate that you would drop if it were up to you?
Why ask it
New bosses often see redundant work faster than the people doing it. This question also gives you permission to stop something, which is usually harder to obtain than permission to start something.
How do you want updates: written before we meet, or live in the meeting?
Why ask it
The mismatch here causes a surprising share of early friction. Some managers read nothing in advance and some resent being talked through a document they have already read.
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.
Which decisions do you want to be in on, and which should I just make and tell you about?
Why ask it
Getting this explicit early prevents both bottlenecks and unpleasant surprises. Ask for an example on each side, since most people describe themselves as hands-off and then define a wide set of exceptions.
When something goes wrong, how soon do you want to hear about it and in what form?
Why ask it
Some bosses want an immediate heads up with no analysis, others want you to have a plan before you speak. Both are workable, but guessing wrong on your first bad week is expensive.
Do you prefer to give critical feedback in the moment or save it for a one-on-one?
Why ask it
Asking gives you the standing to request the version you can act on. It also surfaces the boss who does not give critical feedback at all, which is information you need much earlier than your review.
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 did the person in this role before me do well, and what would you like done differently?
Why ask it
This is the fastest route to the unwritten expectations of the job. Be careful with what you hear about a predecessor who left unhappily, but do note what is being asked of you by implication.
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.
Which relationships outside the team should I be building first?
Why ask it
You get a map of where influence actually sits, which rarely matches the org chart. Ask for an introduction to the first one or two, since a referred introduction moves much faster than a cold one.
What is a habit of mine that will annoy you before I notice it?
Why ask it
Asked lightly, this gets past the polite phase to something concrete: long emails, being late, escalating too fast, agreeing in meetings and doing something else. Small frictions do most of the damage in a new reporting line.
Which of your commitments am I in a position to make easier?
Why ask it
The answer identifies work that will be noticed, which is not always the work you were hired to do. It also reveals what they are worried about, which is worth knowing on its own.
What do you think this team currently gets wrong?
Why ask it
A new boss has an outsider's read that will disappear within a few months as they acclimatise. Ask early and write it down, because it is the most valuable thing they know right now.
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 constraints on budget, headcount, or tools should I know before I propose things?
Why ask it
Proposals that ignore a hiring freeze or a locked platform decision make you look naive. Ask what has already been decided above you and is not up for discussion.
Six months from now, what would make you say this went well?
Why ask it
It asks for their picture of a good outcome for the relationship rather than for your task list, and the answer often includes something about trust or bad news travelling fast that no other question surfaces.
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.
The First Weeks with a New Boss
Practical guidance for the conversation itself
Pace the questions
Three or four in the first meeting, not twenty
A full list delivered at once reads as an audit rather than an introduction. Take priorities, communication preferences, and what good looks like first, then spread the rest over the following month as situations make them relevant.
Ask the operating questions before the career ones
How they want updates and which decisions they want in on will pay off in week one. Progression, title, and development land much better once they have seen you finish something.
Write the answers back to them
- 1After the meeting, send a short note: here is what I heard your priorities are, here is what I am picking up, here is what I plan to stop.
- 2Keep it under a screen and ask them to correct anything you got wrong.
- 3Save their reply. When priorities shift in two months, you will have a record of what was agreed rather than a disagreement about memory.
- 4Revisit the note at the ninety day mark and ask which parts changed.
Watch behaviour, not stated preference
- Managers describe themselves as hands-off and then rewrite your slides. Test cheaply: send one update in the format they asked for and see what comes back.
- Note which meetings they cancel and which they never move. That ranking is their real priority list.
- Notice whether the feedback they promised ever arrives. If it does not, ask directly for one thing to improve rather than waiting.
- Watch what happens to the first piece of bad news you bring. That reaction, not their stated policy, is your guide for the next year.
What to avoid early
- Do not compare them to the previous boss out loud, favourably or otherwise.
- Do not raise promotion or title in the first weeks unless it was already in progress before they arrived.
- Do not ask questions the handbook answers. Spend the access on judgement calls only they can make.
- Do not arrive with a list of the team's grievances. Bring one problem, framed with options, and see how it is received first.