Open-Ended Questions to Ask Leaders
Questions for a sit-down with a leader where you want a story rather than a position: an interview, a panel, a podcast, a leadership development session, a long conversation with your own boss. Each one is built around a specific decision or moment, because that is what defeats the rehearsed answer.
The questions
Open any question for the note
What's the hardest call you've made in the last two years?
Why ask it
The time limit is what makes this work, because it rules out the polished story from a decade ago. Listen for whether they name the people affected, since leaders who describe hard calls purely as strategy usually delegated the human part.
Which decision would you make differently now?
Why ask it
A strong answer names one decision and what specifically changed their mind. A weak answer is a general statement about moving faster, which is the leadership equivalent of saying their flaw is caring too much.
What did you believe about managing people ten years ago that you don't believe now?
Why ask it
This gets a genuine reversal rather than a philosophy. Common ones: that talent beats process, that being liked matters, that people leave for money. What they abandoned tells you more than what they profess.
When did you last have to tell your own boss or your board no?
Why ask it
Upward refusal is the clearest test of whether their stated principles cost them anything. If no example comes to mind, that is an answer. Follow up on what it cost and whether they would do it again.
How do you tell the difference between a quiet team that's fine and a quiet team that's afraid?
Why ask it
Good answers are concrete: who stopped disagreeing in meetings, which questions dried up, how long since anyone brought bad news early. Vague answers about open door policies suggest they have not detected the difference yet.
What's the last piece of feedback that stung and turned out to be right?
Why ask it
Two things get revealed: whether anyone still gives them feedback at this level, and whether they can repeat a criticism in someone else's words. If they cannot name who said it, it probably did not happen.
What do you do when you're sure a project should stop and the team isn't?
Why ask it
You are asking how they handle their own conviction against people they trust. Listen for the mechanics: what they told the team, what they said publicly about a cancellation, and what happened to the people on it.
In a week where everything is urgent, how do you decide who gets your time?
Why ask it
The honest answer is usually an ugly hierarchy: the escalating customer, the loudest peer, the executive who follows up. Whether they can describe it plainly tells you how self-aware they are about their own attention as a resource.
Who has told you something you didn't want to hear, and what happened to them afterwards?
Why ask it
The second clause is the question. Whether that person was promoted, ignored, or is no longer there says more about the culture than any statement about candor, and the answer is hard to dress up.
What's the part of this job you're worst at, and how do you cover for it?
Why ask it
The cover is the interesting part: who they hired to compensate, which meetings they avoid, what they have stopped pretending to do. An answer with no mechanism attached is usually a modest-sounding strength in disguise.
If you've had to cut jobs, what did you learn about how it should be done?
Why ask it
Keep this plain and unhurried. Useful answers cover sequence, notice, who told whom, and what they got wrong about timing. Answers that stay in the language of restructuring, with no reference to the people affected, are themselves informative.
What's a decision your team thinks you made for one reason when it was really another?
Why ask it
This surfaces the gap between the announced rationale and the actual one, which every organization has. It also tests whether they are willing to admit that some reasoning could not be shared at the time.
How do you know when you've become the bottleneck?
Why ask it
Look for signals they can name: approvals queuing, decisions waiting for a one-to-one, people stopping until they respond. If the answer is that they delegate well, ask what they approved personally last week.
What do you do about someone who's excellent at the work and bad for the team?
Why ask it
This is the most revealing management question available, because everyone has faced it. The specifics matter: how long they tolerated it, what they said to the person, and what the rest of the team concluded from the delay.
What did your last real failure cost, and how did you describe it publicly?
Why ask it
Asking for the cost prevents a comfortable answer about lessons learned. Compare the internal and external versions they describe, since the gap between them is where you learn how the organization handles bad news.
Where does one of your stated values break down once it costs money?
Why ask it
Every set of values has a price at which it bends. A leader who can name the trade-off, and how they handled it, is more credible than one who insists there has never been a conflict.
How do you find out what's actually happening three levels down?
Why ask it
Listen for specific mechanisms with names attached: skip-levels, exit interviews they read personally, sitting in on support calls, one honest former colleague. Descriptions of an open culture with no method behind them mean the filtering is unchecked.
Who are you developing right now, and what have you done about it that was uncomfortable?
Why ask it
Real development involves risk: giving someone a project you might lose, saying something hard, backing an unpopular promotion. Mentoring answers with no discomfort in them usually describe occasional advice rather than sponsorship.
What are you carrying at the moment that you can't discuss with your team?
Why ask it
Ask this late and let the silence run. Answers tend to be honest and unglamorous: a pending sale, a colleague being managed out, a target they no longer believe in, a health matter. If they deflect, move on without pressing.
What would you want your successor to change on day one?
Why ask it
Framing it through a successor lets them criticize their own organization without disloyalty. What they name is usually the change they have wanted and could not get, which explains a good deal about their remaining constraints.
Running the conversation
Practical guidance for the conversation itself
Getting past the prepared answer
Anchor every question to a time and a case
In the last two years, the most recent instance, the last time it happened. Senior people have a fluent general answer for everything, and a date is what forces them into specifics.
Follow with what did you actually do
Most first answers describe an intention. The second question, what did you say and to whom, produces the substance. Ask it plainly and wait rather than rephrasing.
Let the pause run
Leaders are used to filling silence and will keep going if you do not rescue them. Count to five after what sounds like the end of an answer, and the qualification that follows is often the real one.
Ask about the cost, not the lesson
What it cost, who left, what got cancelled, what it took to fix. Lessons learned is the phrase that lets a story end without any information in it.
Order matters
- Open with a decision, not a philosophy. Asking what leadership means to you first sets a register of abstraction that lasts the whole hour.
- Put the questions about failure, cuts and blind spots in the middle, once there is some rapport but before anyone is tired.
- Save what you cannot discuss with your team, and what a successor should change, for the last ten minutes.
- If an answer is clearly rehearsed, do not fight it. Take the story, then ask what the hardest part of that week was.
- Leave time for them to ask you something. It changes the ending from an interview to a conversation.
What flattens the conversation
- Multi-part questions. Ask two things at once and they will answer the easier half.
- Loaded framing. Anything shaped like do you agree that produces a defence rather than a story.
- Asking for advice too early. It shifts them into speech mode and out of specifics.
- Interrupting a slow answer. The pause before a real admission looks exactly like the pause before nothing.
- Naming other people's failures. If you criticize a named colleague, the candor ends there.
- Nodding through vagueness because the person is senior. One polite follow-up costs nothing: could you give me the actual example.
If you are recording or publishing this
Agree the ground rules before the first question: whether it is on the record, whether they can review quotes, and what happens to anything said about a named individual. Ask permission to record and keep the file somewhere the answer about a pending sale or a departing colleague cannot leak. If they tell you something sensitive mid-conversation, confirm at the end whether it is usable rather than assuming either way. Leaders will go considerably further when they know where the boundary is, so setting it clearly is in your interest as well as theirs.