Questions to Ask Organization Leaders
Questions for a sit-down with someone who runs an organization, whether that is an informational meeting, a mentoring conversation, or a scheduled skip-level. Written for people who want specifics about how decisions actually get made rather than a speech.
The questions
Open any question for the note
How would you describe the job you actually do, as opposed to the job description?
Why ask it
Opens easily and gets past the org chart. Most senior leaders spend their time on a handful of things that never appear in the formal description: unblocking, recruiting, managing a board, absorbing bad news. The gap between the two answers tells you what the role rewards.
What did you believe about leading people five years ago that you no longer believe?
Why ask it
Sharper than asking for a philosophy, because it forces a before and after. Leaders who cannot name a single reversal are either early in the job or presenting a rehearsed version of themselves. The reversal itself is usually the most useful thing you will hear.
Walk me through a recent decision where the information was genuinely incomplete.
Why ask it
Asking for a specific decision instead of a framework prevents the textbook answer. Notice whether they name who they consulted, what they were willing to be wrong about, and how long they let the decision sit. Vague answers here often mean decisions get made by default rather than deliberately.
How do you find out when something is going badly, and how long does that usually take?
Why ask it
This is really a question about whether people tell them the truth. Good answers describe deliberate plumbing: standing one-to-ones with people two levels down, reading support tickets, walking the floor. If the answer is that people just bring things forward, ask when that last happened.
Who on your team disagrees with you most, and how does that play out?
Why ask it
The presence of a named person is the signal. Leaders who cannot name one either surround themselves with agreement or have not noticed the silence. Also listen for whether the disagreement changes outcomes or just gets aired politely and then ignored.
What is something the organization keeps doing that you would stop if it were entirely up to you?
Why ask it
Reveals where they feel constrained, which is far more informative than what they feel proud of. The answer often points at a legacy commitment, a customer, or a board expectation, and tells you how much room the top job really has.
When you took over, what surprised you about the state of things?
Why ask it
Draws out how the organization looks from inside versus outside, which is exactly the gap you cannot see from where you sit. Leaders who inherited a mess usually remember the specifics vividly.
How do you decide what to work on this quarter and what to leave alone?
Why ask it
The mechanics matter here: who proposes, who cuts, and what happens to the work that does not make it. Watch for whether things get formally stopped or quietly starved, since the second pattern leaves teams working on projects nobody supports.
What happens here when something fails?
Why ask it
Ask for the last concrete example rather than the stated policy. The gap between "we treat failure as learning" and what happened to the person who ran the failed project is where the real culture lives.
How do you spot someone who could do your job in a few years?
Why ask it
Listen for criteria that are observable rather than personality words. Leaders with a real answer usually describe a test they set: handing over a difficult meeting, a hard hiring decision, a bad quarter. If the answer is that talent rises naturally, promotion here probably depends on visibility.
Where does your organization still look nothing like the people it serves, and what have you tried?
Why ask it
Naming the gap requires them to have looked at the data. Then the second half separates intention from action, since most organizations have run something and can say what did and did not move. Answers that stay entirely at the level of values tell you the work has not started.
Which number do you look at first on a Monday morning, and why that one?
Why ask it
A single number reveals the real priority far better than a list of strategic pillars. It also shows whether they watch a leading indicator or a lagging one, which is the difference between steering and reporting.
How does an idea from someone junior actually reach you?
Why ask it
Ask them to trace a real example end to end. Most organizations have a stated channel that nobody uses and an informal route that works. Knowing which is which is practical information if you work there or are considering it.
Which outside pressure shapes your choices most, and how do you push back on it?
Why ask it
Investors, a board, regulators, a dominant customer, or public attention each bend decisions in a different direction. Leaders who claim no external constraint are either unusually independent or not describing the job honestly.
What hours do you actually keep, and what do you expect from people who work for you?
Why ask it
Asking about both at once matters, because the two often differ and people copy what they observe rather than what they are told. If a leader works weekends and insists nobody else should, ask how that message gets through.
Where do you get information that is not filtered through your own organization?
Why ask it
Answers range from peers in other companies to customer calls they take personally to reading they do outside the industry. Someone whose entire input comes from internal reporting tends to be surprised late.
Tell me about the worst week you have had in this role.
Why ask it
Best asked later in a conversation, once some trust exists. The specifics show what they consider serious and how they behave under real pressure, which no answer about crisis management frameworks will give you.
Which relationship outside the organization has mattered most to your work?
Why ask it
Concrete and often surprising: a former boss, a counterpart at a competitor, a regulator, a supplier. It shows how the work depends on people rather than structures, and it usually explains a decision you were curious about.
If I were stepping into a leadership role next month, what would you tell me to prepare for?
Why ask it
Direct and usually generous, because most leaders remember what nobody warned them about. Push for the specific thing they wish they had known rather than general encouragement.
Where do the organization's stated values and its daily behavior come apart?
Why ask it
A useful closing question because it asks for an honest self-assessment. Leaders willing to name a live gap, and what they are doing about it, are describing a real place. Answers claiming perfect alignment are worth noting for what they leave out.
Making the conversation worth their time and yours
Practical guidance for the conversation itself
Setting it up
Say what you want from the meeting in the first minute
Senior people schedule in blocks and mentally allocate the time as soon as you sit down. "I have three questions about how decisions get made here" gets you a different conversation than "I would love to pick your brain", which invites a generic career talk.
Do the homework that removes the easy questions
Read the annual report, the last few public interviews, and any recent restructuring news. Anything you could have looked up burns time you will not get back, and asking it signals you did not prepare.
Bring fewer questions than you think
Four or five questions with real follow-up beats twenty asked at speed. The value is almost always in the second and third layer of a single answer.
In the room
Ask for the last time, not the general case
"How do you handle conflict" produces a policy. "When did that last happen and what did you do" produces a story with details in it. Convert your abstract questions on the spot when you notice a rehearsed answer coming.
Let silence do some work
After an answer that felt incomplete, wait rather than moving on. Leaders used to being interrupted will often keep going and add the part they hesitated over.
Trade something back
You see parts of the organization or market they do not. Offering one observation, not flattery, changes the conversation from an interview into a discussion and makes a second meeting likely.
Common mistakes
Asking only about the wins
Success stories are polished and rarely instructive. The reversals, the failed hire, and the project that got killed are where the reasoning is visible.
Auditioning instead of listening
If you spend the meeting demonstrating your own competence, you leave with nothing you did not already know. There is time for that at the end, briefly.
Not asking what happens next
If the conversation was useful, ask directly whether you can follow up with a specific question later. Vague warmth on both sides produces no second conversation.
Afterwards
- Write your notes within the hour, while the exact phrasing is still recoverable.
- Mark the one or two answers that contradicted what you expected, and why.
- Send a short note naming the specific thing you are going to act on.
- If they referred you to someone, follow up within a week or not at all.
- Six months later, tell them what happened with the thing they advised on.