Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo partial listsCopy or print any set and take it with you

Leadership Questions to Ask

40 questions to put to someone who leads people, in a mentoring chat, a panel or a skip-level. For anyone new to the role or heading for it, these are questions to ask a manager about management as it is practised: deciding without enough information, conflict between colleagues, telling someone their work is not good enough, delegation, announcing unpopular changes, and who develops the leader.

40 questions

Want questions from the whole vault instead? Try the random question generator.

The questions

Each question, and why to ask it

When you strip the title away, what is the job actually?

Why ask it

A good opener because it cannot be answered from a template. Some describe removing obstacles, some describe deciding, some describe recruiting. Whatever they name is what they will be judged on internally, and it frames every later answer.

How do you decide when to decide? What tells you that waiting for more information has stopped paying?

Why ask it

Look for a trigger they can state: a date, a cost of delay, a point where the team stalls. Leaders without one tend to decide when the pressure becomes unbearable, which their teams experience as lurching.

Tell me about a decision you made with less than half the facts.

Why ask it

Forces a story instead of a philosophy of decision-making. The useful detail is what they did to limit the downside: a pilot, a reversible step, a date to revisit. If the story ends at 'it worked out', ask what they would have done if it had not.

How do you get people to say what they actually think while you are in the room?

Why ask it

Specific mechanisms beat statements about openness: asking the most junior person first, writing before discussing, leaving the meeting. If the answer is that their door is always open, ask when someone last disagreed with them out loud.

What do you do first when two of your people are in conflict?

Why ask it

The first move tells you their model. Separate conversations, a joint meeting, or waiting to see if it resolves each carry a different cost. Ask how long they let it run before intervening, since that is where most managers get it wrong.

How do you tell someone their work is not good enough without losing them?

Why ask it

Ask for the actual wording. Leaders who have done this well can usually quote themselves. Vague answers about being direct but kind often mean the message was softened until the person never understood there was a problem.

What does accountability look like on your team when something is missed?

Why ask it

You are listening for whether it lands on a person or on a process, and whether the leader takes any of it publicly. A team where mistakes are only ever systemic has no accountability, and one where they are only ever personal has no learning.

What do you do when someone is a strong performer and a poor colleague?

Why ask it

This is the case that reveals what a leader really rewards. Watch for whether they have ever acted on it, and how long the behavior ran before they did. Most people have a story here and most stories involve waiting too long.

How do you know when it is time to let someone go, and when have you given up too early?

Why ask it

The second half is the part that gets an honest answer, because almost every experienced manager has one they wish they had backed for longer. What they say they were missing at the time is the transferable lesson.

How do you decide what to delegate and what stays with you?

Why ask it

Look for a rule rather than a case-by-case instinct: anything reversible, anything they have done twice, anything not requiring their authority. Leaders who keep whatever they enjoy tend to have teams who feel underused.

What do you do when delegated work is going wrong but has not failed yet?

Why ask it

The hardest moment in delegation, and the answer separates coaching from taking over. Ask what they said, whether they set a checkpoint, and what they would have let happen if the person had not course-corrected.

How do you build trust with someone who wanted the job you were given?

Why ask it

A concrete situation rather than a general question about trust. Good answers involve naming it early and giving the person real scope. If they say they simply focused on the work, ask where that person is now.

What do you do with a team that did not trust the manager before you?

Why ask it

You learn how they handle inherited damage: what they promised, how small they started, how long it took. Leaders who describe arriving with a plan and a new structure usually made it worse first, and it is worth asking whether they did.

How do you announce a change people will not like?

Why ask it

Listen for sequence and honesty: who is told first, whether the reasoning is given, whether they admit the parts they disagree with. A leader who claims everyone came round quickly is either fortunate or not being told what people think.

What do you do when your team is right and your own manager is not?

Why ask it

Tests whether they carry disagreement upward. Ask what they took up, in what form, and what happened. Leaders who only ever relay decisions downward lose the team's belief in everything else they say.

How do you handle knowing something you cannot yet share?

Why ask it

Reorganizations, departures and deals all create this. The workable answer is saying that there is something they cannot discuss and when they expect to be able to. Leaders who bluff instead get caught, and then nothing they say is trusted.

The last time something failed, what did you say to the team?

Why ask it

The words at that moment set whether people bring the next problem early or hide it. Look for whether they took responsibility in front of the group, and whether anyone was named. Compare their answer with how quickly bad news reaches them now.

Who is worth developing, how do you spot them, and what do you actually invest?

Why ask it

The third part is where claims about growing people meet reality: hours, projects handed over, introductions made. If the investment is all encouragement and no scope, the development is not happening.

How do you keep long-term work alive under short-term pressure?

Why ask it

Look for a mechanism: protected capacity, a named owner, a proportion of each cycle. Intentions do not survive a bad quarter, so ask what they gave up last time the pressure came, since something always gives.

How do you avoid becoming the bottleneck, and who tells you when you are?

Why ask it

Ends the conversation on their own limits. The interesting answers name a specific person or signal, such as decisions queuing while they are on holiday. If nothing comes to mind, they are probably the bottleneck now.

What does your week actually look like, hour by hour?

Why ask it

Cuts past philosophy. Where the hours go, into meetings, review or one-to-ones, is the most accurate description of how somebody leads.

What surprised you most about managing people, compared with what you expected?

Why ask it

An easy opener that usually gets a real answer, because almost every manager has one specific thing they misjudged: how much of it is repetition, how little authority the title carries, how long a bad hire takes to resolve.

What did you have to stop doing when you started leading people?

Why ask it

Every move into leadership costs a skill somebody was good at. The answer shows whether they made the shift or are still quietly doing both jobs.

What does leadership done well look like to you, and how do you know when you are doing it?

Why ask it

The second half is the test. Anyone can describe good leadership; what matters is whether they have any signal beyond their own sense of it, such as retention, whether people bring problems early, or what happens when they are away.

How do you decide what your team does not do?

Why ask it

Prioritization is a subtraction problem. The answer shows whether they make choices or pass all the pressure downward.

How do you protect your team's time when demands come from above?

Why ask it

Shielding a team costs a leader something upward. If they cannot name one instance, the shield is theoretical.

How do you explain a strategy you did not choose and do not fully agree with?

Why ask it

Managers in the middle do this constantly. Listen for whether they hide behind the decision, disown it, or explain it honestly.

How do you know someone on your team is struggling before they say so?

Why ask it

Asks about noticing, not fixing. A vague answer here usually means the team is expected to raise problems entirely on its own.

What's the hardest conversation you have had at work, and what would you do differently?

Why ask it

Hindsight is where the honesty is. If the only regret is about timing, they probably have not looked at it hard.

How do you take feedback from someone who reports to you?

Why ask it

The structural problem is that people below you have every reason not to tell you. Managers with a real answer describe a mechanism, not an open-door claim.

What's the last thing you changed your mind about after being pushed back on?

Why ask it

Tests whether disagreement reaches them and changes anything. 'I cannot think of one' is itself an answer.

Who tells you when you are wrong, and how did you set that up?

Why ask it

This names an actual person or it does not exist. How they built that relationship is the practical half of the answer.

How do you decide who to promote when two people are close?

Why ask it

Reveals what the organisation genuinely rewards, which is often visibility or tenure rather than the criteria on the framework. Ask what they told the person who was not promoted.

How do you keep a team going through a stretch where the news is bad?

Why ask it

Watch for whether the answer involves telling people the truth. Motivation strategies that depend on withholding context tend to work once and then cost the manager their credibility.

What do you do in the first hour of a crisis?

Why ask it

The first hour is habit rather than strategy: who gets called, what gets stopped, what gets said publicly. That is what a crisis actually exposes.

What did you get wrong about leadership in your first year?

Why ask it

First-year mistakes are safe to admit and still revealing. Most involve either avoiding conflict or trying to stay everyone's peer.

How has your approach changed in the last five years, and what caused the change?

Why ask it

Asking what caused it separates lessons that stuck from ones that were only read about. The trigger is usually a specific failure, a difficult hire, or working for someone who did it differently.

Where does the pressure of the job show up for you?

Why ask it

Everyone in the role pays something for it. A leader who claims to pay nothing is either new or not being straight with you.

What part of the job do you find lonely?

Why ask it

Rarely asked and often answered candidly: holding information you cannot share, losing the peer group you used to complain with, having no one to check your judgement against. Worth knowing before you take the role.

What would you tell someone about to manage people for the first time?

Why ask it

Advice for a first-time manager is where real priorities surface, and it is usually more concrete than anything they say about their own approach.

Adapting these to the setting

Practical guidance for the conversation itself

Where you are asking

A panel or all-hands

Public settings reward questions about craft rather than about people. Ask about deciding without full information, or announcing unpopular changes. Anything about firing, conflict or their own manager will get a careful non-answer with an audience present.

A mentoring conversation

Here you can ask for the cases: the person they let go too late, the delegation that went wrong. Bring a live situation of your own so their answer can be aimed at something real.

A one-to-one with your own manager

Asking the person you report to about management works best when the question is about craft: what they delegate, how they decide what the team does not do, what they had to stop doing when they took the job. Leave out letting people go and the strong performer who is a poor colleague, because your manager will hear those as questions about your teammates.

A skip-level with your manager's manager

Stick to how decisions are made, how they hear bad news, and what they expect from teams like yours. Avoid anything that reads as a complaint about your own manager, since you will not control where the answer travels.

Getting past the polished version

  1. 1Ask for one instance, not a pattern. 'The last time' and 'tell me about a case' cut through practised answers.
  2. 2Request the words. 'What did you actually say?' is the single most useful follow-up in this list.
  3. 3Ask about the counterfactual. 'What would you have done if it had not worked?' finds out whether it was judgment or luck.
  4. 4Ask who disagreed. Every real decision had an objector, and how they describe that person tells you a great deal.
  5. 5Accept the discretion. If they decline to discuss a named person, that is the correct answer and you should move on.

Turning the answers into something you use

  • Collect wording, not principles. Phrasings for hard conversations transfer between organizations. Values statements do not.
  • Ask several leaders the same two questions. Where their answers diverge is where the real choices in leadership sit.
  • Watch for advice that only works with their authority. Some approaches need seniority you do not have yet, and applying them early reads as arrogance.
  • Test one thing within a fortnight, while you still remember why it sounded right, then write down what happened.
  • Notice the advice you resist. It is usually pointing at the part of the job you have been avoiding.

Common mistakes

Asking what their public talks answer

If it is in a conference session or an internal blog post, read that first and ask what has changed since. Repeating a question they have answered publicly wastes your slot.

Turning it into a debate

Challenging their approach in the first conversation gets you a defence rather than an explanation. Ask what conditions their approach depends on instead.

Collecting advice you never apply

Notes from six leaders and no change in your own practice is the usual outcome. Leave every conversation with one concrete thing to try.

Taking every answer at face value

Self-reports about openness, trust and feedback are the least reliable part of any leader's account. Where you can, compare with how their team describes the same thing.

More on this topic