Good Leadership Questions to Ask
Questions to ask a leader about how they actually work: where their week goes, how they give hard feedback, what they delegate, who tells them they are wrong, and how they handle a crisis.
The questions
Open any question for the note
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 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.
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 a decision you made with bad information, and how did it turn out?
Why ask it
Bad information is the normal condition, so this avoids the tidy case study. Watch whether they own the call or blame the circumstances.
How do you tell someone their work is not good enough?
Why ask it
Feedback is where most managers are weakest and most confident. Ask for the words they use, not the framework they follow.
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.
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.
What do you delegate that you would rather keep?
Why ask it
The reluctant handover is where delegation becomes real. A leader who kept everything they enjoy has a team with no room to grow.
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.
What happens on your team when two people cannot resolve something?
Why ask it
Asks about the mechanism rather than the philosophy: whether they step in, at what point, and what happens if it still does not settle.
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.
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 handle it when you have to let someone go?
Why ask it
Keep this plain. What matters is whether they talk about the process and the person, or only about the business need.
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 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.
Who have you promoted, and what did you see before anyone else did?
Why ask it
Specific and checkable. Naming a person and the early signal is very different from describing a talent framework.
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.
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 work do you still enjoy?
Why ask it
Worth asking late, when the answer is less polished. Enthusiasm about the work itself is a good sign; enthusiasm only about outcomes is worth noting.
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.
Using these in interviews and one-to-ones
Practical guidance for the conversation itself
Where each question fits
- In an interview, the questions about the week, about what the team does not do, about unresolved conflict and about protecting time tell you what working for this person would be like.
- Hold the ones about hard conversations and letting people go for a later round, or for a mentor rather than a hiring panel.
- If you already report to the person, pressure and enjoyment come out better on a walk than in a scheduled review.
Getting past the rehearsed answer
- Ask for the instance, then the words used, then the outcome. Most polished answers dissolve at the second step.
- Follow every abstraction with 'what did that look like'. Trust, alignment and empowerment mean nothing until somebody gives an example.
- Leave the silence after an answer. The more honest second half often arrives in it.
What to watch for
- A leader with no failures to describe has either not been tested or is managing you. Neither is a good sign.
- Be suspicious of stories where the leader is the only actor. Good answers name colleagues who pushed back or fixed something.
- Notice whether they describe people by role or by name. It is a small tell about how close they are to the work.