Best Questions to Ask Leaders
Questions for a skip-level, a panel, or an interview with someone running a team or a company. They cover the metrics they actually manage by, the trade-offs behind the plan, how they make calls, and how they spot failure early.
The questions
Open any question for the note
Which few numbers do you watch most closely right now, and why those?
Why ask it
The 'why those' is the test. A leader who can explain what each number is a proxy for is managing by cause. One who lists a dashboard is reporting.
When did you last change your mind about something significant?
Why ask it
Look for what the evidence was. Leaders who cannot recall changing their mind either do not revisit decisions or do not notice when they were wrong.
What trade-offs are you making deliberately this quarter?
Why ask it
Every plan has costs. Naming them means the strategy was chosen rather than assembled from everything anyone asked for.
Where is the biggest bottleneck in getting work out the door?
Why ask it
Pins the conversation to operational reality. If the bottleneck named is another department, ask what they have done about it, not just when they noticed.
What behavior do you celebrate here that an outsider would miss?
Why ask it
Gets at what actually earns credit, which is often something small like flagging problems early rather than anything printed on a values page.
How do you prefer people to disagree with you?
Why ask it
Answers range from a specific forum to a vague statement about open doors. The specific answer is the one you can actually use next week.
Which risks do you accept, which do you watch, and which would make you act?
Why ask it
Turns a general statement about risk appetite into something usable, and reveals whether anyone has agreed what would trigger a change of plan.
If you had to cut a fifth of the team's effort, what would you stop?
Why ask it
Forces prioritization out loud and exposes the work nobody is willing to defend but everyone keeps doing.
What does good look like for this team six months from now?
Why ask it
Ask for something observable. Answers built on adjectives rather than outcomes usually mean the goals have not been agreed with anyone above them.
What piece of feedback most changed how you lead?
Why ask it
Specific and slightly uncomfortable answers indicate a leader who takes feedback. Rehearsed answers about being too much of a perfectionist do not.
Where do you want bad news faster than you currently get it?
Why ask it
Invites them to name a blind spot, and their answer tells you what you should escalate rather than handle quietly.
How would we know early that this strategy is not working?
Why ask it
A plan with no failure condition cannot be abandoned. Listen for a signal and a date rather than an intention to keep an eye on things.
Which decisions do you want to make yourself, and which should be made lower down?
Why ask it
Draws the real line on decision rights, which is the thing people most often guess at and get wrong in both directions.
What does your calendar say about your priorities that your goals do not?
Why ask it
Compares stated strategy against where attention actually goes. Most leaders find this uncomfortable, and the discomfort is where the honest answer is.
Who has grown most on the team this year, and what did you do differently with them?
Why ask it
Shows whether developing people is deliberate practice or something they attribute to the person. The second half of the question is the one that matters.
What information reaches you too late or too filtered?
Why ask it
Identifies the reporting paths that hide problems until they are expensive, and often explains why a team feels unheard.
How do you decide when to kill a project rather than rescue it?
Why ask it
Reveals whether there is a stopping rule or just sunk-cost momentum. Ask for the last thing they canceled and how long it took.
What part of the plan depends on something outside your control?
Why ask it
Exposes external dependencies and whether they are hedged. A leader who says nothing does has either a very unusual plan or an incomplete one.
What do new people most often get wrong in their first month here?
Why ask it
Practical onboarding guidance, and it usually surfaces an unwritten norm that nobody would think to document.
If this year goes well, what will be different for the people you serve?
Why ask it
Ties internal targets to something a customer or user would notice. If the answer never leaves the org chart, the goals may only matter inside the building.
Getting Real Answers From Leaders
Practical guidance for the conversation itself
Approach
Anchor to a time and a number
'This quarter' and 'which metric' turn a question that invites a platitude into one that requires a fact. Vague questions get vague answers from busy people.
Ask what they will not do
Constraints describe strategy better than ambitions do. Anyone can list priorities; only someone who has decided can list what they dropped.
Ask one question, then stop
Leaders answer in the space you leave. Stacking three questions together lets them pick the easiest one and move on.
Follow-ups Worth Having Ready
- What evidence would change your view on that?
- When did that last come up, and what happened?
- Who owns it, and by when?
- What would the first small test look like?
- What would have to be true for that to work?
Common Pitfalls
Asking for their philosophy
Questions about leadership style or philosophy get a prepared answer. Questions about last Tuesday get information.
Using a skip-level to complain
If the meeting is a skip-level, questions land better than grievances. A question about decision rights or bottlenecks raises the issue without putting anyone on trial.
Not writing down what they said
Answers about priorities and trade-offs are worth quoting back a quarter later. That is only possible if you noted the words at the time.