HRBP Questions to Ask Leaders
Written for HR business partners preparing to sit down with a line leader. The questions ask about their priorities for the quarter, which talent gaps are blocking their goals, how they read their team's culture, and what recognition and development already exist.
The questions
Open any question for the note
What are your top three priorities this quarter, and which of them has a people problem attached?
Why ask it
Leaders name business priorities easily and rarely connect them to people work. If none of the three has a people angle, you have learned they do not yet see you as relevant.
What is the thing about your team you find yourself thinking about at night?
Why ask it
Phrased this way you usually get one named person or one unresolved conflict. An abstract answer about engagement means they have not looked closely, or do not trust you with it yet.
How would you describe your team's culture to someone joining next week?
Why ask it
Explaining it to a newcomer forces concrete detail: who speaks in meetings, what gets escalated, what gets forgiven. Values-poster language means the leader is not close to the daily reality.
Which roles or skills are you missing that are holding up your goals?
Why ask it
Listen for whether they ask for headcount or for capability. A leader who only wants more people often has a work design problem that hiring will not solve.
How do you decide who your strongest performers are?
Why ask it
The method matters more than the names. If the answer comes down to visibility or hours rather than outcomes, your calibration data is already unreliable.
Who on your team is ready for more, and what is stopping them getting it?
Why ask it
This surfaces blocked promotions before they become resignations. A leader who cannot name anyone is either not developing people or not watching.
Walk me through the last difficult performance conversation you had.
Why ask it
A real example shows their practice rather than their theory. If the most recent one was months ago on a struggling team, the issue is avoidance, not skill.
What part of managing people do you still find uncomfortable?
Why ask it
Most leaders will answer honestly if you ask about discomfort rather than weakness, and the answer tells you which coaching would actually get used.
Who tends to get the visible work on your team, and how does that get decided?
Why ask it
Task allocation is where inclusion either happens or does not, and it leaves a trail you can check against who gets promoted a year later.
What is the most recent piece of feedback you got from your team, and what did you do with it?
Why ask it
The second half is the test. A leader who can quote the feedback but not name a change has run a survey, not a conversation.
When someone on your team does good work, what actually happens?
Why ask it
You want a mechanism, not an intention. Recognition that depends entirely on the leader remembering will lapse in the first busy month.
What is coming in the business over the next two quarters that your team does not know about yet?
Why ask it
This buys you lead time on restructures, freezes and workload spikes, and shows how much the leader is carrying without help.
If your two most senior people left next month, what would happen?
Why ask it
Deliberately uncomfortable. Vague reassurance here is how single points of failure survive right up until they fail.
Which HR process wastes the most of your time?
Why ask it
Leaders will name the worst one if you ask for the worst one. Fixing a single named irritation buys more credibility than any new initiative.
How do you protect development time when delivery is behind?
Why ask it
Everyone says they value growth. This asks what happens under pressure, which is exactly when development time gets cut first.
What would make your job easier that is within my control?
Why ask it
Narrowing it to your control avoids a wish list about pay bands and produces something you can act on this month.
How did the last disagreement on your team get resolved?
Why ask it
A specific case shows whether conflict surfaces or goes underground. 'We do not really have conflict' on a team of any size means it is not being said in front of the manager.
What is changing in your market that will change who you need to hire?
Why ask it
Connects workforce planning to something the leader already thinks about, and gives you the argument you will need when you ask finance for those roles.
What does your team believe about the company that is not true?
Why ask it
Surfaces the misunderstandings you can fix with communication rather than policy, and shows what the leader is picking up informally.
What has HR got wrong with you in the past?
Why ask it
Asking for a specific failure rather than general feedback gets a real answer, and dealing with it plainly does more for the relationship than any relaunch.
Making These Conversations Worth the Leader's Time
Practical guidance for the conversation itself
How to run the conversation
Book a standing slot, not an ad hoc meeting
Leaders share the useful things in the fourth or fifth conversation, not the first. A recurring slot also means you are not only in the room when something has gone wrong.
Ask about one case, not one policy
'How is the team doing' produces nothing usable. 'Tell me about the last time you had to move work around' produces the actual state of the team.
Bring one number they do not have
Attrition in their function, time to fill on their open roles, or how their promotion rate compares to the next team over. It turns a check-in into something they want on the calendar.
Leave with one thing you will do
Small and specific beats a plan. Vague commitments are the main reason these partnerships stall after a few months.
Reading what the answers tell you
- A leader who names individuals is close to the team. One who speaks only in categories is managing through their own reports, which changes what advice can land.
- Watch the gap between who they praise and who they promote. That gap is where your calibration work actually is.
- If every problem is described as a hiring problem, look at how the work is divided before you open a requisition.
- Repeated 'we are fine' from a team with rising attrition means the leader either does not have the information or is not ready to hand it over.
- Note which questions they answer with process and which with people. It tells you whether they see managing as administration or as judgment.
What to do between meetings
- Close the loop in writing on anything you promised, including the answers that turned out to be no.
- Check one figure they quoted against the system, and raise it next time whether or not it supported their case.
- Disagree with them out loud at least once, plainly. Partners who only ever agree get consulted last.
- Warn them before their team hears anything from HR centrally. Being surprised in front of their own people is what ends the trust.
- Keep a short private list of what each leader is worried about, and reread it before the next meeting rather than starting fresh.
What derails these conversations
Opening with the HR calendar
Starting on the review cycle or a compliance deadline tells the leader the meeting is for your benefit. Put process items last, and cut them if you run out of time.
Taking notes that could be read back to them
If a leader suspects their honesty about a person will end up in a file, they stop being honest. Say what you will write down and what you will not.
Solving a problem they have not named
Advice on something they did not raise reads as criticism. Ask, wait through the pause, then offer.
Being the only place they ever reflect
If your questions are the only time a leader thinks about how they manage, nothing changes between meetings. Push them toward peers doing the same job.