Questions to Ask a Senior Manager
Questions for a skip-level, a first meeting with a new leader, or twenty minutes with someone two levels above you: what they are measured on, how decisions really get made, what good looks like from where they sit, and how to be useful to them.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
How did you end up in this role?
An easy opener that is not wasted, because the path explains the lens. Someone promoted from inside the function reads your work differently from someone brought in from another industry, and the answer usually surfaces which parts of the business they know cold and which they take on trust.
- 2
What does a normal week look like for you?
Most people two levels down have no accurate picture of this. Learning that six of their hours go to one governance forum, or that most of Tuesday is spent with finance, tells you when to reach them and why some decisions take three weeks that feel like they should take a day.
- 3
What are you being measured on this year?
This is the single most useful question in the list. Their targets are the frame every request you make will be judged against, and they are often narrower than the stated strategy. Ask for the actual metrics, not the theme.
- 4
What are the top priorities for this group over the next two quarters?
Ask for the order, not the list. Everything is a priority in an all-hands deck, and the ranking is where the information is. If they cannot rank them, that itself explains why your team keeps getting conflicting direction.
- 5
What is the thing about this area that worries you most?
Senior managers rarely get asked what worries them, and often answer honestly one-to-one. The worry is usually something you can help with and did not know about, and it is a better guide to where to spend effort than any published objective.
- 6
What decisions come to you that people assume are made lower down?
This maps the real authority structure, which is never the org chart. Knowing that headcount, tooling spend or a particular customer commitment lands on their desk saves you weeks of pushing a proposal through the wrong door.
- 7
Where do you think we are slowest, and why?
Asking about speed rather than problems gets you a more concrete answer, since delay is measurable and blame is not. Their answer also tells you whether they see the bottleneck as process, people, or a dependency outside the group.
- 8
What do you wish people brought to you earlier?
Every senior manager has been surprised by something a team knew about for weeks. Asking this gives you explicit permission to escalate, and it tells you their tolerance for unfinished information, which varies enormously between leaders.
- 9
How do you prefer to receive bad news?
Ask this before you have any. Some want a note the moment something wobbles, some want it in the weekly with an option attached, and some want to hear it from your manager first. Getting this wrong once costs more trust than months of good work builds.
- 10
From where you sit, what does good look like in my role?
Your own manager tells you what good looks like on your team. Two levels up, the definition is usually different and broader, and the gap between the two answers is the most actionable thing you will get from the meeting.
- 11
What is one thing my team does that you would stop?
Direct and slightly uncomfortable, which is why it works. Senior managers see duplicated effort and legacy commitments that are invisible from inside a team, and being the person who asks to stop something rather than start something is rare enough to be memorable.
- 12
How do promotion decisions actually get made here?
Ask about mechanics rather than criteria: who is in the room, how often it happens, what evidence is presented and by whom. The published framework describes the bar, and this question describes the process that applies it, which is what determines outcomes.
- 13
What separates the people who progress here from the people who stall?
Answers tend to be specific and unflattering, which is what makes them useful: taking on unglamorous work, being reliable in writing, managing across rather than upward, or simply being visible in the right forums. Expect at least one answer you did not want to hear.
- 14
What is your read on how my work is landing?
Ask this plainly and then stop talking. It is uncomfortable and it is the reason to have the meeting. If the honest answer is that they have not seen your work, that is not a rejection, it is a finding, and it tells you exactly what to fix.
- 15
What have you had to explain upward recently that was hard to explain?
This shows you what leadership above them cares about and where the story about your area is weakest. It frequently produces a request you can act on, since the thing that is hard to explain is usually the thing nobody has good data for.
- 16
How much runway does this initiative have before someone asks whether it is working?
Every project has an unstated evaluation date and a threshold. Asking for both lets you plan what to show and when, and it stops you optimising for a milestone nobody senior is actually watching.
- 17
What have you changed your mind about in the last year?
A question about judgment rather than information. Leaders who can name something specific tend to be arguable with, which matters a great deal if you ever need to change their mind. Leaders who cannot usually require a different approach.
- 18
Who else should I be talking to?
Ends the conversation with an introduction rather than a summary. Ask for names and what to ask each of them, then follow up within a week, because an unclaimed referral from a senior manager expires quietly.
- 19
What is the most useful way to keep you informed without adding to your load?
Senior managers are drowning in updates and most of what they receive is unread. Agreeing a format and a cadence, a short monthly note or a line in an existing forum, makes you the person whose information arrives in the shape they can use.
- 20
If you were in my position for the next year, what would you do?
A closing question that invites them to be generous rather than evaluative. The answer usually reveals what they think matters, what they think is undervalued, and occasionally something concrete about where the organisation is heading that they would not state directly.
Getting value from time with a senior manager
Practical guidance for the conversation itself.
Before the meeting
Before the meeting
Tell your own manager you are meeting
Skip-levels are normal in most organisations and being surprised by one is not. A short heads-up removes the only real political risk, and it gives your manager a chance to tell you what is already being handled, which stops you raising something that has been resolved.
Pick three questions and cut the rest
Twenty minutes holds three questions with follow-ups, or ten questions with nothing underneath them. Choose one about their priorities, one about how things get decided, and one about your own work, then let the conversation go where it wants.
Do not bring a complaint you have not raised elsewhere
Escalating around your manager in a skip-level is the fastest way to make the meeting expensive. If something genuinely needs escalating, say that you have raised it, what happened, and what you are asking for. Framing matters more than content here.
Read what they have said publicly
Their last presentation, the objectives they published, the thing they posted internally. Referencing it specifically shows you pay attention to the level above yours, and it lets you ask a follow-on question rather than making them repeat the summary.
In the room
In the room
- Open by saying what you want from the meeting in one sentence. Senior managers appreciate the frame and will often reorganise the time around it.
- Ask for examples when an answer is abstract. What happened last time a project missed a date is worth more than a description of the governance process.
- Take one page of notes, visibly. It signals that you intend to act on this rather than just meet.
- Leave silence after a hard question rather than filling it. The second sentence of an answer is usually the honest one.
- If they ask you a question, answer it in under a minute and stop. Concise answers under pressure are themselves a form of evidence.
- Do not use the time to list accomplishments. Ask what they have seen, and let them tell you what is missing.
Afterwards
Afterwards
- Send a short note within a day, naming what you took away and what you will do. Three lines is enough and it is what makes the meeting memorable.
- Act on one thing quickly and visibly. A single completed follow-up is worth more than a good conversation.
- Share the useful parts with your own manager. It keeps the relationship straight and often turns their priorities into your team's context.
- Chase the introductions they offered within a week. Referrals go cold and re-asking is awkward.
- Note what they asked you about. Their questions reveal what they are being pressed on, which is often more useful than their answers.
- Ask for another conversation in a quarter rather than a standing meeting. It is easier to say yes to, and easier to renew if it goes well.