Questions to Ask Company Leadership
Questions for the moment you have the executive team in one room: a town hall, a leadership panel, a departmental Q&A, a round of introductory meetings after you join. The focus is on how decisions actually get made across functions, who owns what, and what leadership has chosen to stop doing.
The questions
Open any question for the note
What did this group debate hardest before landing on the current plan?
Why ask it
The disagreement is where the real tradeoffs are, and naming it tells you which parts of the plan are settled and which are still contested. A group that claims it agreed easily is either unusually aligned or telling you the debate happened somewhere you cannot see.
Which goals did we miss last year, and what did you conclude from that?
Why ask it
Every leadership team knows what it missed. Whether they will say it out loud tells you how honest the internal reporting is, and the conclusion matters more than the miss: a changed approach is useful, blaming market conditions twice in a row is not.
What is the one number this team looks at every week?
Why ask it
Weekly attention is the truest signal of what the company optimizes for, and it is often narrower than the stated strategy. If different leaders name different numbers, you have just learned why cross-team priorities keep colliding.
How much of next quarter's roadmap is already committed to customers?
Why ask it
Committed work cannot be reprioritized without a conversation someone will avoid having. The share tells you how much slack exists for anything new, and it explains why good ideas keep getting deferred to a later quarter.
When two of you disagree, how does the decision actually get made?
Why ask it
Listen for whether there is a named decider or whether things escalate until someone gives up. Teams that resolve by attrition produce reversals weeks later, which is what turns into rework further down the organization.
Who owns the outcome when a project spans two of your teams?
Why ask it
Shared ownership usually means no ownership. A clear single name, with the others explicitly supporting, is the answer that predicts the project finishing. If the answer is that both teams own it together, expect the escalation to land on the people doing the work.
What decisions can someone at my level make without approval, and where is the line?
Why ask it
Vague autonomy is worse than a narrow mandate, because you find the boundary by crossing it. A leadership team that can state the line clearly has thought about delegation. One that says to use good judgment has left you to guess and be corrected later.
When every request arrives marked urgent, how does anything get sequenced?
Why ask it
You are asking whether a real prioritization mechanism exists. A named forum, an owner, or a written intake process is a working answer. Hearing that they trust teams to figure it out means the queue is being managed by whoever pushes hardest.
How do you keep two teams from building the same thing twice?
Why ask it
Duplication is a symptom of how information moves between leaders, not of careless staff. Concrete answers involve shared planning reviews or a visible roadmap. If nobody can name a mechanism, duplication has probably already happened and gone unnoticed.
What is the process for stopping a project, and when was it last used?
Why ask it
The second half is the test. Many companies have a documented stage gate that has never killed anything. A recent, specific example tells you that saying no is survivable here, which affects how honestly people report bad news.
Which of last year's initiatives are still running mainly because nobody wants to cancel them?
Why ask it
Direct, and it works better than it sounds, because leaders usually know exactly which projects those are. An honest answer signals a team willing to be self-critical in public; deflection tells you sunk cost is a live problem here.
How is headcount divided between teams, and when does that get revisited?
Why ask it
Allocation is often inherited from a plan two years old, which is why some teams feel permanently short. Knowing the cadence tells you when arguing for more people is even possible, and whether the answer this quarter is already fixed.
What information do you wish reached you faster than it does?
Why ask it
This invites a specific request rather than a platitude, and it often reveals a gap you personally can close. If the answer is that they get everything they need, the more likely truth is that filtered updates have made the gap invisible.
When did you last change a decision because of something someone below director level said?
Why ask it
Asking for a concrete instance separates practiced openness from actual influence. No example available is itself the answer, and it tells you that raising concerns upward here works better through your manager than through a forum like this one.
What happens to the engagement survey results after you read them?
Why ask it
Everyone runs the survey; the useful question is what followed the last one. Look for a specific change with a date. A summary presentation followed by nothing is the most common outcome, and it is why response rates fall the following year.
What gets someone promoted here that is not written in the criteria?
Why ask it
There is always an unwritten part: visibility, willingness to take on unowned work, proximity to whatever leadership is anxious about. Leaders who can name it are being genuinely useful. Insisting the rubric is the whole story is not credible to anyone who has been through a cycle.
Which recurring complaint have you decided not to act on, and why?
Why ask it
Some complaints are legitimate and still not going to be fixed, and saying so plainly is more respectful than another promise to look into it. The reasoning also shows you what constraints leadership is working under that staff cannot see.
Where is the company carrying risk that most of us cannot see?
Why ask it
Concentration in a few customers, a dependency on one vendor, a regulatory exposure, key-person risk. Leaders can usually share the shape of it even when the details are confidential, and knowing it makes their otherwise puzzling decisions legible.
What are you not going to do this year, even though people keep asking for it?
Why ask it
This gets you the no list, which saves everyone from relitigating settled questions. If nothing is on it, then no decision has actually been made and the requests will simply be absorbed quietly until the work runs out of room.
If the plan changes mid-year, how will we hear about it?
Why ask it
Plans change; the failure mode is finding out through a reorganization. A named channel and cadence is a commitment you can hold them to later, and it also reveals whether they expect changes they have not yet mentioned.
What should we stop bringing to this group?
Why ask it
A good closer, because it hands back decision rights rather than asking for more work. The answer tells you which decisions are being escalated out of habit, and it often gives your team explicit permission to move faster on them.
Getting real answers from a leadership group
Practical guidance for the conversation itself
How to ask a group
Address one person, not the panel
Questions thrown at a whole leadership team get answered by whoever is most comfortable, which is rarely the person who knows. Name the leader whose area it touches, then let others add. You will get a specific answer instead of a general one.
Ask about mechanisms, not intentions
Intentions are easy to state and impossible to check. Mechanisms leave traces: who decides, at what meeting, on what cadence, with what evidence. When you ask how something happens rather than whether it matters, you can verify the answer later.
Ask for one example
The most useful follow-up in these sessions is a request for the last time it happened. A described process with no recent instance behind it usually is not running, and asking for the instance is polite while still being difficult to dodge.
Submit written questions early where that is an option
Many town halls collect questions in advance and answer the ones with the most votes. A question submitted early and clearly worded stands a much better chance than one raised from the floor at minute fifty.
Reading the room
- When two leaders answer the same question differently, that gap is the most valuable thing you will hear all session. Note it rather than pointing it out publicly.
- Watch who defers to whom. It maps actual decision authority more accurately than the organization chart does.
- An answer that arrives as a process description with no owner named is usually a way of saying nobody owns it yet.
- If a leader says they will follow up, note the date. Whether the follow-up arrives tells you more about the company than the original answer did.
- Questions about people and pay get careful answers in public for legal reasons as much as political ones. Do not read caution there as evasion.
What goes wrong
Asking a question that is really an accusation
There is a version of every hard question that gets a real answer and a version that puts a leader on the defensive in front of their staff. Ask about the mechanism and the tradeoff rather than the failure, and you can raise difficult topics without the room closing up.
Avoiding hard topics entirely
The opposite error is a session of vision questions that could have been answered by the careers page. Cost pressure, missed goals, cancelled projects, and decision rights are legitimate subjects and leaders are usually prepared for them.
Treating the answer as a commitment
A leader speaking off the cuff in a large meeting is not signing a contract. If something matters to your work, follow up in writing and confirm what you heard, rather than repeating it to your team as settled policy.
Asking about your own project in a company forum
It burns shared time on something specific to you, and the answer will be to take it offline. Bring the pattern to the town hall and the instance to your manager or to a one-on-one.
Not writing anything down
These sessions produce a handful of usable facts: a number, a cadence, a decision boundary, a commitment. Without notes, all of it becomes a vague impression by the following week.
By setting
Town hall or panel
- 1Submit your question in advance if the format allows it, worded in one sentence.
- 2Address it to the specific leader whose area it touches.
- 3Ask for a measure, a date, or a recent example, then let the session move on.
Introductory meetings as a new joiner
- 1Ask each leader what their team is judged on, and note where the answers overlap or conflict.
- 2Ask what decisions your level can make without approval, so you learn the boundary before you cross it.
- 3Ask what they wish reached them faster, then follow up in a month with something that does.