Questions to Ask New Leader
Questions for your first one to one with a leader who has just taken over your team, covering what they were told before arriving, how they want information and disagreement handled, what they intend to change, what they are measured on, and what they need from you.
The questions
Open any question for the note
What made you take this job?
Why ask it
An easy opener that tells you what they think the opportunity is: fixing something, growing something, or a step toward their next role. Each of those produces a different first year for the people around them.
What were you told about this team before you arrived?
Why ask it
Reveals the brief they are working from, which often contains judgments about the team that nobody has said out loud. It is also your one chance to correct a wrong impression before it hardens.
What are you trying to understand in your first few weeks, and how can I help?
Why ask it
Gets you into their orientation rather than waiting to be assessed by it. If they cannot name what they are trying to learn, expect decisions made on partial information.
How do you like to be kept informed: written updates, a standing meeting, or a message when something changes?
Why ask it
The wrong channel is the most common early friction, and people rarely say so directly. Ask for a preference and then ask how often, because those are separate answers.
How often do you want one to ones, and what do you want them to cover?
Why ask it
Some managers want status, others want only the things that are stuck, others want career and context. Getting this stated saves months of meetings that neither of you finds useful.
When something goes wrong, how do you want to hear it?
Why ask it
Ask whether they want it immediately and raw or with a proposed fix attached, and whether a message at the weekend is welcome or unwelcome. This is the answer that matters most in the first genuine crisis.
Which decisions do you want to be part of, and which would you rather I just make?
Why ask it
Without a line, new reports either escalate everything or surprise their manager. Ask for an example on each side, since abstract answers about autonomy do not survive contact with a real decision.
How do you want me to raise a disagreement?
Why ask it
Some leaders want it in the room, some in private first, some in writing. Someone who says they welcome challenge in any form should be asked when they last changed their mind because someone pushed back.
What does good work look like to you? Tell me about someone you managed who was doing it well.
Why ask it
The example gives you the real standard, where the abstract answer gives you adjectives. Notice whether the person they describe was visible, fast, careful or independent, because that is what will be rewarded.
What do you expect to change in the next few months, and what are you leaving alone for now?
Why ask it
The second half is the reassuring part and the part people forget to ask about. If everything is under review, plan for a slower few months and keep your commitments modest.
What are you being measured on by your own manager?
Why ask it
Their targets become your priorities whether or not anyone says so, and most leaders will answer this if asked plainly. It also tells you which of your work will get their attention and which will not.
What is taking up most of your attention right now?
Why ask it
Tells you when to bring things to them and when not to bother. It also often reveals a problem you could take off their hands, which is the cheapest way to build credit early.
Which of our current commitments worries you most?
Why ask it
Gets a real answer about risk rather than a list of priorities, and shows you where their scrutiny will land first. If nothing worries them a month in, they have not looked closely yet.
How much of the team's existing plan do you intend to keep?
Why ask it
New leaders often want to make a mark, and knowing whether the roadmap is safe changes what you should start. An honest not sure yet is more useful than false reassurance, and worth asking for directly.
What is your working pattern, and what counts as urgent to you?
Why ask it
Covers hours, response times and whether a message at 9pm expects a reply. Mismatched assumptions here cause quiet resentment on both sides.
Is there something you know you are not good at that I should work around?
Why ask it
A candid answer, remembering names, keeping to time, reading long documents, is genuinely useful and rare. How they handle the question tells you how much honesty this relationship will support.
What did people on your last team find hardest about working with you?
Why ask it
Harder to deflect than asking about their leadership style, because it asks for someone else's view. Any specific answer, even a small one, is a good sign about self-awareness.
What do you want to know from me that you have not asked?
Why ask it
Opens the door for the questions they are not sure they are allowed to ask yet, about people, history, or why something is the way it is. This is often where the most useful part of a first meeting happens.
What would you want me to be doing in six months that I am not doing now?
Why ask it
Asks for a direction rather than an assessment, which is fair to request from someone still learning the team. Write the answer down and bring it back to them later.
What can I do to make your first few months easier?
Why ask it
Ends with an offer, and most new leaders will name something concrete: context, an introduction, or one problem taken off their list. Doing it, then not mentioning it again, is what builds trust fastest.
The first one to one with a new leader
Practical guidance for the conversation itself
Before the meeting
- 1Write one page: what you own, what you have delivered recently, what is at risk, and what you need decided. They are meeting many people and reading almost nothing in depth.
- 2Look up what they did before this. It tells you what you will not have to explain and what you will.
- 3Pick your three most important questions. First meetings overrun and get cut, usually before the part about your own role.
- 4Decide in advance what you will not bring up yet. Complaints about your predecessor, pay, and other people's performance all land badly in a first conversation.
- 5Have one concrete thing to offer. Being useful in the first week is worth more than being impressive.
Reading their answers
Notice what they ask you
A leader who asks what is broken, who is good, and what they should not touch is orienting well. One who arrives with conclusions already formed is working to a mandate, and you should find out what it is.
Specific beats fluent
Answers about style, culture and empowerment are easy to give and mean little. Answers with a name, a date or an example in them are the ones you can plan around.
Watch how they handle what they do not know
A month in, they should be saying I do not know yet fairly often. Someone who has an answer for everything is either exceptionally well briefed or not being straight, and you will find out which within a quarter.
The following weeks
- Send a short note after the meeting with what you understood and what you will do. It costs five minutes and prevents most early misunderstandings.
- Do the small thing you offered, and do it before they ask again.
- Give them a way to look good early. New leaders remember who helped them land, and it is rarely the person who waited to be impressed.
- Adjust once, then check. Send your first update in the format they asked for and ask directly whether it was what they wanted.
- Give it a quarter before concluding anything. First impressions of new managers are frequently wrong in both directions.
What goes wrong
- Using the first meeting to unload. Everything you say about the old regime is information about you, not about them.
- Waiting to be told how they work. The people who ask early get a working relationship; the rest get a review.
- Promising more than usual to make an impression, then missing it. The first commitment you break is the one they will remember.
- Assuming continuity. Plans, goals and priorities set by a previous manager are not automatically inherited, so get confirmation in writing.