One-on-One Meeting Questions That Get Honest Answers

"How's everything going?" Priya asks, and Sam says what he has said for nine Tuesdays running: "Fine, all good." She glances at the running doc. His section is empty again. There are 27 minutes left, and she has nothing to fill them with except his status update.

You've had that meeting. Most managers reach for the same fix: a longer list of one-on-one meeting questions. That doesn't help, because the problem isn't the number of questions. It's that "how's it going?" can be answered with one word, it's asked cold, and it's asked by the person who writes the review.

This is the question bank for that problem: 56 one-on-one meeting questions grouped by purpose, with a line on why each group works, which questions to skip, and what to write down afterwards. It ends with a six-week rotation so the same questions don't come round every week.

It's a question bank, not a template. The structure of the meeting, a running document per report with six sections, is in our one-on-one meeting template. And if you'd rather listen during the meeting than type, try ParrotNotes free before your next one.

Why most one-on-one meeting questions get "fine"

Three things turn a one-on-one into a status update. The question is closed, so "fine" is a complete answer. It's asked with no history, so the report has to decide in two seconds whether this is a safe place to say the real thing. And the person asking controls their pay and their next project.

The report's side of that meeting is easy to find online. In one anonymous post on Blind titled "Weekly 1:1 are waste of time", the writer describes it exactly: "He talks about random stuff for a few minutes and then asks me to provide an update on what I did last week."

The numbers back him up. Gallup's August 2025 report on U.S. engagement found that only 28% of employees strongly agree their opinions count at work, and only 31% strongly agree someone at work encourages their development. If a report doesn't believe their opinion counts, "fine" is the rational answer.

Managers aren't faring better. Gallup's State of the Global Workplace 2026 puts global manager engagement at 22% in 2025, down from 31% in 2022. A tired manager asks the easy question, and a question bank makes the good question the easy one.

So what makes a one-on-one meeting question work? It's open, so one word can't answer it. It's specific to a moment ("this week", "the last release", "the Thursday meeting"), and it asks for a judgment about their own work, not a rating of their own happiness. Every question below passes those three tests.

How to use this one-on-one meeting question bank

Don't ask all 56. Don't ask eight. Three rules keep the bank useful:

1. One purpose, three questions, per meeting. Pick the group that fits what's going on, choose three questions from it, and spend the rest of the time listening. Two of the three will usually be enough.
2. Their items still go first. In a good one-on-one the report sets the agenda. These questions fill the silence when their section is empty; they don't replace it.
3. Wait through the pause. The honest answer usually comes after the first one. Count to five, then ask "what else?" or "say more about that."

Each group below ends with a write down after line. That's the part every list of one-on-one meeting questions leaves out: an answer only matters if it changes what you do next, and it only does that if it's recorded somewhere. The last section covers how to capture it in three minutes without typing during the conversation.

56 one-on-one meeting questions, grouped by purpose

Gallup's research on meaningful manager conversations (updated February 2026) names four topics that make them land: recognition, collaboration, goals and priorities, and strengths. It also reports that only 16% of employees say their last conversation with their manager was extremely meaningful. The seven groups below cover those four topics, plus the three situations managers ask about most: skip-levels, remote and field staff, and the hard conversation.

Check-in questions

Why they work: a check-in question replaces "how are you?" with something that asks about a specific week and gives the report a low-stakes way to say what kind of week it was.

1. What's been taking up most of your head space this week?
2. What's one thing that went better than you expected since we last met?
3. What's been more annoying than it should be?
4. If this week had a title, what would it be?
5. What did you do this week that nobody saw?
6. Who helped you this week, and how?
7. On a scale of one to ten, how was the week, and what would have made it one point higher?
8. What are you looking forward to, and what are you dreading?

Skip these: "How are you?" and "Everything okay?" invite "fine." "Are you happy here?" asks the report to rate their loyalty to their boss's face, and nobody answers that honestly in week nine.

Write down after: the score if you asked for one, the one thing they named as annoying, and anyone they credited. Three scores under six in a row is a pattern, and credit given is recognition you can pass on publicly.

Workload and blocker questions

Why they work: a report will rarely say "I'm overloaded," because it sounds like a complaint. They will answer a question about a specific task, a specific wait, or a specific decision.

9. What's taking more of your time than it deserves?
10. What are you waiting on from me, or from anyone else, right now?
11. If you could hand one task to someone else this month, which one?
12. What's the one decision that, if it were made today, would unblock you?
13. Which meeting on your calendar could you drop without anyone noticing?
14. Where did you spend time this week on something that got thrown away?
15. What's the deadline you're most worried about, and why?
16. Is there anything you've said yes to that you wish you'd said no to?

Skip these: "Do you have too much on?" (a yes-or-no with an obvious safe answer) and "Can you handle it?" (which asks them to admit weakness to get help).

Write down after: each blocker with an owner, especially the ones that are yours. "Waiting on Priya for the vendor approval" is an action with your name on it and a date. That line belongs in the shared actions, not in your memory.

Career and growth questions

Why they work: development conversations are where trust is earned fastest, because you control the projects, the introductions, and the training budget. A good career question asks about direction, not titles.

17. What do you want to be doing in a year that you're not doing now?
18. Which part of your job would you do for free, and which part do you tolerate?
19. What skill would make the biggest difference to your work in the next six months?
20. Who in the company does something you'd like to learn?
21. What's a project you'd want to be pulled into if it came up?
22. When did you last feel stretched, and was it a good stretch or a bad one?
23. What have I not noticed that you're good at?
24. If a role opened up above you tomorrow, what would you want me to say about you?

Skip these: "Where do you see yourself in five years?" (an interview question, and it gets an interview answer) and "Do you want to be a manager?" as an opener, because it forces a binary before you know what they actually want.

Write down after: the goal in their words, the skill they named, and what you agreed to do about it. Career promises are the ones that cost the most when they're forgotten, and the most when they're kept.

Feedback on you as a manager

Why they work: asking for feedback on yourself is the most direct way to show that opinions count in this meeting. The trick is to ask about a behavior you can change, not for a verdict on you as a person.

25. What's one thing I do that makes your work harder?
26. When did I last give you feedback that was useful, and what made it useful?
27. What do you wish I'd stop doing in team meetings?
28. Is there a decision I made recently that you'd have made differently?
29. How do you prefer to hear it when I think something's off: in the moment, in writing, or in this meeting?
30. What's something I should know that I probably don't?
31. How much of my time do you get, and is it the right amount?
32. If you were me, what would you change about how this team works?

Skip these: "Do you have any feedback for me?" (too broad, and the polite answer is no) and "Am I a good manager?" (unanswerable by anyone who reports to you).

Write down after: the exact words, one thing you'll do differently, and a date to check back. Nothing kills this group faster than asking, getting a real answer, and changing nothing.

Skip-level meeting questions

Why they work: in a skip-level you're two steps from the work, so the report is your best source on how the team really runs. The purpose is to learn, not to audit their manager, and the questions should make that obvious.

33. What does a good week on your team look like, and how often does it happen?
34. What's the team spending time on that you're not sure matters?
35. What's one thing you'd want me to understand about your day that I probably don't?
36. Which decision from above landed badly, and what would have made it land better?
37. What does your manager do that the rest of the company should copy?
38. Where does the team need something from me, or from leadership, that it isn't getting?
39. What rumour is going round that I should know is going round?
40. If you had ten minutes with the whole leadership team, what would you tell them?

Skip these: "How's your manager doing?" and "Any concerns about your manager?" turn the meeting into an investigation. A real concern will come up without being fished for, and it then needs a separate, proper process.

Write down after: themes, not names. Three people mentioning the same slow approval is a finding. One person's opinion of their manager is a note you keep to yourself and follow up on carefully.

Questions for remote and field staff

Why they work: when you see someone once a month, or only on a screen, you lose the hallway signals that tell you when something's off. These questions ask for the signals directly.

Dev manages six field reps and sees each of them for a one-on-one on the first Monday of the month, usually from a car park. Marcus's answer every month was "all good, pipeline's solid." In March, Dev asked question 44 instead.

Marcus said he'd been driving 90 minutes each way to a plant nobody else had heard of, twice a week, for a deal he hadn't logged because he didn't believe it would close. It closed in June. Dev is invented; the question is real.

41. Where did you spend the most windshield time or screen time this month, and was it worth it?
42. What do you know about a customer, a site, or a problem that nobody else on the team knows?
43. When you need a quick answer, who do you ask, and how long does it take?
44. What have you been working on that isn't visible to me?
45. When did you last feel out of the loop, and what was the loop?
46. What would make the monthly visit, or the video call, more useful to you?
47. Which tool or process is slower on the road, or from home, than it is in the office?
48. Who on the team do you talk to least, and does that matter?

Skip these: "Are you staying on top of things out there?" (it's a check, not a question) and "How's the pipeline looking?" (that's a report, and it's the answer Marcus gave for three months).

Write down after: the customer, site, or problem they named in question 42, because that's knowledge that leaves with them. For sales reps, this is also where coaching starts; if you coach reps from their own call notes, our guide to AI sales coaching covers what that looks like without a bot on the call.

Questions for a hard conversation

Why they work: when performance has slipped, when there's a conflict, or when you suspect someone is looking, the wrong question makes it worse. These questions open the door without pushing anyone through it.

49. What's changed in the last month, from where you sit?
50. How do you think the last project went, before I say what I think?
51. What's getting in the way that I might not be able to see?
52. What would need to be true for you to be doing your best work here?
53. If you could reset one thing about your role, what would it be?
54. What's the feedback you're expecting to hear from me, and how close am I?
55. What do you need from me in the next two weeks, specifically?
56. What haven't I asked that you were hoping I would?

Skip these: "Are you looking for another job?" (it forces a lie or a resignation), "Is everything okay at home?" (you're their manager, not their counselor), and "Why did this go wrong?" as an opener, which gets a defense instead of an answer.

Write down after: the change they named, what you each committed to, and the date you'll revisit it. Keep it factual and short. If the conversation becomes a formal performance or HR matter, your notes follow your company's process, not this article.

A rotation plan so the same six questions don't repeat

A question loses its power the third time it's asked; the report has an answer ready, and the answer is "fine." The fix is a rotation of one-on-one meeting questions: one purpose per week, in an order that matches how a month of work goes. Pick two or three questions from the week's group, and let their items run first.

For fortnightly one-on-ones, run three purposes per cycle: check-in and blockers in meeting one, career in meeting two, feedback on you in meeting three, then repeat. Skip-level questions sit outside the rotation because skip-levels happen quarterly for most directors; run them from the skip-level group and keep the notes separate.

Two things override the rotation. If their items fill the meeting, the rotation waits; that's the meeting working. And if the check-in score drops or a hard-conversation signal shows up (missed dates, a change in tone, a question about references), switch to that group that week and rejoin the cycle after.

The rotation is for the one-on-one, not for reviews. A quarterly business review with a rep is a different meeting with its own agenda; our sales QBR template covers that one. And if you run a unit that never closes, the nurse manager one-on-one guide shows how the same idea, questions by purpose, works around shifts and certifications.

Priya tried the cycle with Sam. Week one got a seven out of ten and a real reason for the missing point. Week four, question 27, got this: "I wish you'd stop asking for status in the Thursday team meeting. We've all just written it in the doc."

She changed the Thursday meeting. Sam's section stopped being empty.

Write it down after the meeting, not during

Here's the awkward truth about one-on-one meeting questions: a good one produces an answer worth listening to, and you can't listen properly while typing. The manager who types through the meeting gets a record and misses the pause where the real answer was. The manager who doesn't type gets the answer and loses it by 6:00 PM.

The fix is to write it down after, in three minutes, before the next meeting starts. Each group above tells you what to keep; for the note itself, the formats in our meeting notes template guide work here too.

That three-minute note is where ParrotNotes fits. Step out of the room, hit record, and talk through it: who, the questions you asked, the answers in their words, what you each committed to, and one private observation. When you stop, you get a transcript, an AI summary, and the action items pulled out as a list, so the shared actions go into the running doc and the private note stays in your own notes. Recording keeps going with the screen locked, so the phone can sit in your pocket on the walk to the next room.

If your report would find it useful, you can also record the one-on-one itself and let ParrotNotes take the notes while you listen. Consent comes first, every time: ask before the meeting, not as you press record, make "no" an easy answer, and skip recording for the hard-conversation group, where the recap you dictate alone does the job. With their yes, you both get the same summary and action items, and on Pro, AI semantic search finds what Sam said about the Thursday meeting in September when you need it in December.

In the United States, federal law permits recording a conversation you're a party to (18 U.S.C. § 2511(2)(d)), but some states and countries require everyone's consent, and your company may have its own policy. This isn't legal advice. The three-minute recap you dictate alone needs none of it.

Want to try it on this week's one-on-ones? Download ParrotNotes free. The free plan gives you 100 minutes of recording a month, up to 30 minutes per recording, with an AI summary on every recording and AI insights on five recordings a month, which covers a week of three-minute recaps. Pro is $19.99 a month, or $14.99 a month billed annually, with 3,000 minutes a month, recordings up to 3 hours, AI chat on every recording and semantic search across every note you've kept. Your notes about your team stay in your own account; see how we protect your data.

Pick three one-on-one meeting questions for this week

"Fine, all good" isn't a lie. It's the answer to a question that didn't ask for anything else. The 56 one-on-one meeting questions above ask for something else: a specific week, a specific blocker, a specific thing you could stop doing.

The short version:

• Three questions, one purpose, per meeting, after the report's own items
• Wait through the pause, then ask "what else?"
• Skip the closed questions, the loyalty tests, and the interview questions
• Write down after: the score, the blocker with an owner, the career goal in their words, the feedback and what you'll change
• Rotate purposes on a six-week cycle so nobody can answer on autopilot

Think back to Priya at minute three, looking at Sam's empty section. Five weeks later she had a Thursday meeting that ran differently because he told her why. Pick your three questions for this week's one-on-ones, download ParrotNotes free, and dictate the three-minute recap before you open the next calendar invite.