Most one on one meeting questions fail for a boring reason. They invite an answer the person can give without thinking. This guide covers how to pick five questions per meeting and which ones reliably get you a polite lie. It also covers 1-on-1s with frontline teams, and what to do with the answers afterward.
TL;DR
Ask fewer questions and follow up on more of them. Five per meeting is enough. Use one opener, one on workload, one rotating question about growth or team dynamics, one that invites upward feedback, and one closing commitment. Vague questions produce vague answers, so make yours specific and time-bound. The value is not in the conversation itself. It sits in what happens before you meet again, so you need somewhere to record what was agreed and a real way to act on it.
Why most 1-on-1 questions get you nothing
There is a specific moment every manager recognizes. You ask how things are going. You get “yeah, good, busy.” Then you both look at the agenda.
That exchange is not a rapport problem. It is a question design problem.
Three things go wrong.
The question has an obvious safe answer. “Are you happy here?” has one socially correct response, and almost everyone gives it. So do “any blockers?” and “everything okay?” You have handed the person an exit and they took it.
The question is too big to answer on the spot. “What are your career goals?” is a fair thing to want to know. It is a terrible thing to ask cold, because most people cannot produce a five-year plan in the eleven seconds of silence you have left them.
The answer goes nowhere. This is the one that quietly kills 1-on-1s. Someone tells you they are drowning, or that they want to move toward a technical lead role. Nothing visible happens. Three weeks later you ask again and get a shorter answer. Ask a fourth time and you get “all good.”
That last failure is worth sitting with. Your team is running an experiment on you. They tell you something small and true, then they watch what you do with it. The size of the next thing they tell you depends entirely on what they saw.
Pick five questions, not fifty
You will find lists of 100 and 150 one on one questions online. They are useful as a reference shelf. They are not usable as a meeting plan.
A workable 1-on-1 has room for about five real questions. Anything more and you are conducting an interview, and the person stops volunteering and starts answering.
Here is the slot structure I recommend. Keep the slots fixed and rotate what goes inside them.
| Slot | Purpose | Change it? |
| 1. Opener | Read the person’s state before you read the agenda | Vary the wording, ask every time |
| 2. Workload and capacity | Catch overload and blockers early | Ask every time |
| 3. Rotating deep question | Growth, team dynamics, alignment, or the company | Change every meeting |
| 4. Upward feedback | Give them a route to tell you something hard | Ask every second or third meeting |
| 5. Commitment | Convert talk into two named actions | Ask every time, without exception |
Four of the five stay stable, which is the point. Consistency is what makes slot 3 safe to use. When someone knows the shape of the meeting, an unusual question reads as curiosity rather than as a warning sign.
Questions for managers, sorted by what you need to find out
Pick by the information you are missing, not by the category that sounds nice.
Opening without wasting the slot
The first question sets whether this is a status meeting or a conversation. Ask something with a real answer.
- What has taken up most of your head space this week?
- What is one thing from last week you would do differently?
- Before we start, is there anything on your list that we have to cover today?
- What went better than you expected recently?
The third one matters more than it looks. It hands the agenda over at the beginning rather than in the last two minutes, when there is no time to act on whatever comes out.
Workload, capacity, and early burnout signals
Burnout rarely announces itself. It shows up as flat answers, missed small commitments, and work that gets technically finished but not cared about. Ask about capacity in concrete terms.
- Is your current workload sustainable for the next month, or just for this week?
- Which of your tasks takes far longer than anyone realizes?
- What are you working on right now that you would drop if you could?
- What time of day do you get your actual thinking done? Is that being protected?
- If something slipped this month, what would it be?
The distinction in that first question does a lot of work. Plenty of people can survive a hard week and will say so honestly. Fewer will volunteer that the hard week is now the fourth in a row.
Career growth and skill development
Career questions work when they are narrow and grounded in something recent.
- What part of your job would you like to be doing more of a year from now?
- Which skill, if you had it today, would make your current work easier?
- Who inside the company does something you would like to learn?
- What would need to change for your next step here to feel realistic?
- What training have you started and not finished? What got in the way?
That final question surfaces more than the usual “what do you want to learn.” Unfinished training is a signal. Sometimes it points to time pressure, sometimes to content that missed the mark, occasionally to a development plan that nobody meant seriously.
Goal alignment and hidden blockers
- What is the biggest thing slowing you down that I probably cannot see?
- Do you know how your work this quarter connects to what the team is measured on?
- What decision are you waiting on from someone else?
- Which part of your job feels unnecessary to you?
- What have you had to work around rather than fix?
Workarounds are worth chasing. When a person builds a workaround, they have already diagnosed a problem, decided it will not be fixed, and paid the cost themselves. That is usually a process failure sitting in plain view.
Upward feedback, which is the hardest category to get right
Asking “do you have any feedback for me?” almost never works. It is too open, too exposed, and it asks the person to criticize the individual who writes their review.
Narrow it and lower the stakes.
- What is one thing I could do differently that would save you time?
- Where am I too involved? Where am I not involved enough?
- What did I ask for recently that turned out to be more work than it was worth?
- Is there a decision I made this month that did not make sense from where you sit?
- What did a previous manager do that you wish I did?
The last question is the reliable one. It lets the person offer criticism as a compliment to someone else, which is a much easier thing to say out loud.
Then handle the answer properly. Do not explain, do not contextualize, do not justify. Say thank you, ask one clarifying question, write it down. If you defend yourself once, you have closed the channel for a long time.
Questions employees should ask their managers
If you are the direct report, your 1-on-1 is thirty minutes of your manager’s undivided attention every week. Most people use it to deliver a status report their manager could have read in a document.
Use it better.
About your own work and standing
- What would make the difference between good and excellent on this project?
- Where do you think I am strongest? Where would you want to see me improve?
- Is there anything you are hearing about my work that I have not heard?
- What should I be spending less time on?
About context you do not have
- What are you being asked about most often right now?
- What changed in the leadership conversation this month?
- What is the reasoning behind the priority shift?
- What does your manager care about this quarter?
About your development
- What would I need to demonstrate to be considered for the next level?
- Is there a project coming up where I could take on something unfamiliar?
- Who should I be building a relationship with?
That second group is undervalued. Managers sit on top of context that never travels downward, not because it is secret but because nobody asks and there is no natural moment to volunteer it. Asking gets you a clearer picture of why decisions land the way they do.
Questions that will get you a polite lie
Some questions are worse than silence, because they let both people feel like the topic was covered.
| Weak question | Why it fails | Ask instead |
| Are you happy here? | Only one safe answer exists | What would make you consider a call from a recruiter? |
| Any blockers? | Yes-or-no, and “no” is easier | What is taking longer than it should, and why? |
| Do you have feedback for me? | Too broad, too exposed | What is one thing I could do differently that would save you time? |
| How is everything going? | Invites a summary, not a detail | What has taken most of your head space this week? |
| What are your career goals? | Too large to answer cold | What part of your job do you want more of next year? |
| Do you feel supported? | Sounds like a survey item | What did you need last month that you did not get? |
The pattern across the right-hand column is specificity. A question that names a timeframe, a quantity, or a single instance is far harder to deflect than one that asks for a general verdict.
One on ones with frontline and shift-based teams
Nearly every guide on this topic assumes a salaried desk worker with a sixty-minute calendar slot. That describes a minority of the working population.
If you manage a warehouse floor, a retail store, a production line, a clinic, or a field crew, the constraints are different. You may have fifteen minutes at shift change. You may be managing thirty people rather than seven. Your team may not have company email.
Adjust three things.
Compress to three questions. Opener, capacity, commitment. Drop the rotating slot on most weeks and use it monthly instead.
Anchor questions to the shift, not the quarter. “What slowed you down on Tuesday’s shift?” gets a real answer. “How do you see your development trajectory?” does not, and it can read as corporate noise on a factory floor.
Rotate the deeper conversation. Running a monthly fifteen-minute career conversation with each person beats running a quarterly hour that gets cancelled twice.
A short version that works at shift change:
- What went wrong on your last shift that we could stop from happening again?
- Is there any part of the job you have not been properly shown?
- What do you need from me before your next shift?
That middle question earns its place. On frontline teams a surprising amount of training is informal, passed peer to peer, and uneven in quality. People will admit a gap in a private one-minute conversation that they would never raise in a group briefing.
The follow-through layer
Here is where most 1-on-1 advice stops, and it is the part that determines whether any of it was worth doing.
Every meeting should end with two named commitments: one yours, one theirs. Write both down where both of you can see them. Open the next meeting by reading them out. That is the whole mechanism.
Notes. A shared document is fine. What matters is that it is the same place every week and that the person can see it. Private notes in your own system train people to assume nothing was recorded.
Themes. Look back across a quarter of notes. One person mentioning a broken handoff is an anecdote. Four people mentioning it across six weeks is a process problem you now have evidence for.
Development commitments need somewhere to go. This is the specific gap I see most often. Someone says they want to get better at running client conversations. You agree it is a good idea. Then it lives in a notes doc, and eleven weeks later neither of you can say what happened.
Development discussed in a 1-on-1 has to become something with a date and a completion state. In smaller teams a shared tracker handles that. Once you are past roughly fifty people, or once compliance and role-based training enter the picture, this usually moves into a learning platform: the manager assigns a course or a learning path, the completion is recorded, and the next 1-on-1 opens with evidence rather than recollection.
Some platforms also carry on-the-job checklists and appraisal modules that connect a check-in conversation directly to an assigned activity. Moodle Workplace, iSpring LMS and Docebo all handle this differently, as do combined learning and performance tools like Leapsome. The specific tool matters less than the principle. If a development commitment cannot be assigned, tracked, and reviewed, it will decay quietly, and your team will notice long before you do.
Mistakes I see most often
Cancelling. A rescheduled 1-on-1 is a message about priority, and it is received clearly.
Filling the silence. After you ask something real, wait. The useful answer usually arrives after the uncomfortable pause, not before it.
Asking the same five questions for two years. Rotate slot 3 or the meeting calcifies into a ritual.
Treating it as your status update. If you are talking for most of the meeting, it has become something else.
Asking about wellbeing and then not adjusting anything. Asking creates an expectation. Asking twice with no visible response teaches the person to stop answering.
The right one on one meeting questions are the ones you will actually follow up on. Pick five, keep the structure steady, and put the answers somewhere they can turn into action before you meet again.
FAQ
How often should managers hold one on one meetings?
Weekly is the strongest default for most desk-based teams, with thirty minutes as a reasonable length. Every two weeks works for experienced people in stable roles. Going longer than a month means you are learning about problems after they have grown. Frontline teams often do better with shorter, more frequent check-ins.
How many questions should I bring?
Around five. Enough to cover the ground, few enough to allow follow-up questions when something interesting surfaces.
How do I stop a 1-on-1 becoming a status update?
Move status reporting into writing before the meeting, then use the meeting for anything that needs a conversation. Let the direct report add the first agenda item. If the whole session could have been an email, it was a status meeting.
What questions help identify burnout?
Ask about sustainability over time rather than about feelings in the moment. “Is this workload sustainable for the next month?” and “when did you last take a full day off?” produce more honest answers than “are you doing okay?” Watch for shortening answers and dropped small commitments as well.
What if my direct report gives one-word answers?
Usually one of two causes. Either nothing they raised previously produced a result, or the questions are too broad. Fix the first by visibly closing one small loop. Fix the second by asking about a specific recent event instead of a general state.
