One-on-one meeting questions: 60 questions by situation — the first meeting, a stalled quarter, a hard week — and how to keep the answers between meetings (2026)

A one-on-one meeting question is a question the manager asks so that the report talks about the thing that matters this week, in their own words, rather than reporting status. The good ones are chosen for the situation — a first meeting, a quarter that has stalled, a week that went badly — and they come in pairs: the first question opens the subject, the second one ("what makes you say that?") is where the meeting earns its slot.

This guide is the sixty questions, grouped by ten situations, with the second question written out where it is not obvious. It is also the half that lists of questions skip: what you do with the answer. An answer that is heard and not written is gone by the next session, and the report has to start the subject again. So the second half is where the answers live between meetings in the tools your team already uses, and one way to keep the running history readable by both of you.

The structure of the meeting itself — the four items, the 30-minute template, the cadence — is in the one-on-one meeting template; this guide assumes it and fills in the questions.

What a good one-on-one question does

Three tests, and a question that fails one of them is a status question in disguise:

1. It opens the report's item, not the manager's. "How is the migration going?" is the manager's question; the report answers it in the channel every day. "What took more of your time this week than it should have?" is the report's: only they know, and the answer is news to the manager.
2. It cannot be answered with "fine". A question that accepts "fine" will get "fine". Ask for a specific — a decision, a person, a day, a thing — and the answer has to contain one.
3. It has a second question behind it. The first answer is the headline; the second question — "what makes you say that?", "what would change that?", "who else knows?" — gets the paragraph. Three first questions per meeting is plenty, because each one is really two.

One more rule, which is not about asking: when the answer produces anything to do, say it back aloud as a sentence with a name and a date — "so we're recording: I get you twenty minutes with Dana before the 20th." That sentence is the record. The questions below are sorted so that you pick the group for the week, take three, and leave the rest for another session.

Sixty questions, by situation

Pick the group that fits the week. Three per meeting; the second question matters more than the first.

The first meeting with a new report

The only one-on-one with an agenda the manager sets, because the report does not yet know what to bring.

1. How do you like to work — hours, focus time, where you do your best thinking?
2. How do you prefer to get feedback: in the moment, in writing, or in this meeting?
3. What does a good week look like for you, and what does a bad one look like?
4. What did your last manager do that you'd like me to keep doing — and to stop?
5. What is the one thing you'd like to understand about this team by the end of the month?
6. What are your first three questions for me?

The second question behind each: "what would I see if that were going well?" The answers go into the shared note as the working agreement for the pair — they are the baseline every later session refers back to.

A weekly check-in when the list is short

A short list is not a quiet week; it is a week the report has not had time to think about yet.

7. What took more of your time this week than it should have?
8. What are you putting off, and what would make it easier to start?
9. What did you decide this week without asking anyone — and should you have asked?
10. Who on the team would you like to work with more, and who less?
11. What is one thing you learned this week that the rest of the team should know?
12. If this week repeated itself for a month, what would you change first?

A stalled quarter

The goal was set in week one, it is week eight, and the number has not moved. The questions here are about what is waiting, not about trying harder.

13. What decision is this quarter waiting on, and from whom?
14. Which part of the goal still makes sense, and which part was wrong when we set it?
15. What have you tried that didn't work, and what did it tell you?
16. If we dropped one thing from your plate today, which one would move the goal most?
17. Who outside the team has to do something for this to land — and do they know?
18. What would you need to see by the end of next week to believe this quarter is recoverable?

The second question behind 13 is "what have you done to get that decision?", and the honest answer is often "waited". Write the decision, its owner and the date it is needed by into the note; the stall is usually that sentence.

A hard week

Something went wrong — a release, a client, an argument. The first question is not about the thing; it is about the person.

19. How are you doing after this week — honestly, not the version for the team meeting?
20. What part of what happened was in your control, and what part wasn't?
21. What did you need from me this week that you didn't get?
22. What would make tomorrow easier?
23. Who else was affected, and has anyone talked to them?
24. What do you want the team to take from this — and what do you want me to say about it?

No second question on 19: let the answer be as long as it needs to be. On 22, take the answer literally and do it; a hard week is the one meeting where "I'll look into it" is the wrong sentence.

Growth and career

Once a month, in the longer session. These are the questions that disappear first when the meeting becomes a status update, and the ones people leave over when they have been missing for a year.

25. What would you like to be doing more of a year from now, and less of?
26. What is one skill you'd like to be known for?
27. Which piece of recent work are you proudest of, and why that one?
28. What is the next role you can imagine for yourself, here or elsewhere?
29. What would you need from me in the next quarter to take one step towards it?
30. Who in the company is doing the thing you want to learn, and have you talked to them?

The output is fixed: one development step per quarter, with a date, written in the report's words. Question 29 produces it.

Feedback for the manager

Asked every few weeks, and answered honestly only when the earlier answers changed something.

31. What is one thing I could do differently that would help you?
32. When did I last get in your way?
33. Is there a decision I made recently that you'd have made differently?
34. What do I ask about too much, and what do I not ask about enough?
35. When was the last time you felt I didn't have the full picture?
36. Is there something you've told me twice that I still haven't done?

Write the answer to 31 down with a date, and open with it next time: "you said X three weeks ago; here is what I did." A manager's feedback question is only credible after the first answer visibly changed something.

A remote report, or one in another time zone

The weekly session is the only hour the two of you are in the same room, so part of it is about the other hours.

37. Which meeting this week did you leave less sure than you came in?
38. What happened in the office that reached you late, or not at all?
39. Where do you wait longest for an answer, and from whom?
40. What do you do in your first hour when the rest of the team is asleep?
41. Which decision this month did you first learn about after it was made?
42. Is there anything about where or when you work that you've been managing around rather than raising?

Question 41 is the one with a record attached: when the answer names a decision, the next question is where that decision was written, and whether the report could read it.

A report who manages others

The questions shift from their work to their team's, and the manager's job is to ask about the people the report never brings up.

43. Who on your team haven't we talked about in a month?
44. Which of your one-on-ones is the hardest right now, and why?
45. What decision are you holding that your team is waiting for?
46. Who on your team is ready for more, and what is in the way?
47. What are you doing yourself that someone on your team should be doing?
48. What did your team learn this quarter that mine should?

Before a review, or after a change

The weeks before a performance review, after a reorg, or when the scope of the role has moved.

49. What would you expect to read in your review, and is any of it a surprise?
50. What have you done this cycle that nobody saw?
51. Since the change, what is clearer, and what is less clear?
52. Which of your responsibilities moved without anyone saying so?
53. What are you measured on now, in your own words?
54. What would you want the next version of this role to include?

A year of these questions is what makes the review contain no surprises; the review is the one meeting where the answer to 49 should already be in the notes.

Questions the report asks the manager

The one-on-one is the report's meeting, and these are the questions a report brings when the manager has not asked anything yet. A manager can also hand this list over in the first session.

55. What are the priorities for the next month, in order?
56. What is the one thing you'd like me to do differently?
57. What decision are you working on that affects my work?
58. How do you see my work from where you sit?
59. What would I need to show you for the next step to be a conversation?
60. Is there something you're hearing about my work that I'm not?

Three of these, asked every month, is a one-on-one in its own right.

How an answer is written down

The question is half the job; the sentence that records the answer is the other half. One session, three questions, recorded as the next session will need them:

Lena / Marco — one-on-one — 14 November
1. What decision is this quarter waiting on, and from whom? — the pricing sign-off, from finance; asked twice by email, no date.
Recorded: Marco asks Dana for a date by Tuesday; Lena escalates if there is none by Thursday.

2. What have you tried that didn't work? — the two-tier offer; two prospects said the tiers were the same thing with different names.
Recorded: drop the second tier from the next three calls; review on the 28th.

3. What do you need from me this week? — twenty minutes with the sales lead before the 20th.
Recorded: Lena books it — by the 18th.

Open from last time: [item] — done · [item] — not done, because [reason] · [item] — dropped on purpose.

Three questions, three sentences with a name and a day, and the open items from last time at the bottom. The next session starts by reading the last block aloud. That is the whole system — if the block survives until the next session, and both of you can read it.

Where the answers live between meetings in the tools you already use

A one-on-one is the meeting with the longest memory: the answer from March is the one that matters in September. Where the written answers go is therefore a design decision. Documented behaviour only, from the vendors' own pages, with the month each page was checked:

Read across the row for your tool and the shape is the same in each: one document per pair or per meeting, written by hand or generated once, in one language, with last session's open items carried to this session by whoever remembers to open the previous document. Where that is fine, any of the four will do and the table is the whole answer. Where the one-on-one runs in Teams or Meet and you want to hold on to what the call produced, where Teams and Meet store your transcript, recording and summary lists what each keeps and for how long; what their captions do inside the call when the two of you do not share a first language is documented in Microsoft Teams live translation and Google Meet live translation.

A running record both of you can read

InterMIND is a communication space where a meeting lives in a channel, so a one-on-one is a channel with two members and one permanent meeting link. The three questions for Thursday go into the channel the day before as a note — the report's items first, the manager's below; during the call either of you puts the note on both screens with Share to conference, edits it live while the other watches, and each of you reads it in your own language, with the original one toggle away — as you read the channel's chat around it, typed by each of you in your own language. When the session ends, the recap is written from the meeting itself: a summary, the points marked agreed, open or disputed, the next steps with owners, each line keeping its timestamp — so the three recorded sentences are edited from a draft rather than typed from memory. Either of you can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session, not only the latest, so the answer from March is a switch between sessions in September. The recap is members-only: forwarding the link grants nobody access. An ad-hoc meeting by link keeps only its latest recap and its chat is wiped when the call ends; a one-on-one belongs in a channel.

In an organization with team status pages on, the open items of earlier sessions are judged when the next recap is written — an item someone reported finished is marked done, an item discussed but not finished is marked not done with the reason in the words of the meeting, an item nobody brought up stays open — with the verdicts on the organization's status page rather than in the recap, and at the start of the next session Mia names the open items and their owners, so question 36 ("something you've told me twice") has a list behind it. Team status pages are a preview feature: an organization's admin switches them on under Settings → Advanced after accepting the alpha terms (the Preview features page describes each one).

When the one-on-one is with someone outside your organization — a contractor, an agency lead, a candidate in their third interview — the other person joins by link, from a phone if they like, without an account and at no cost, and hears the session live in their own language. There is no record for a guest afterwards — the account is free, and it is what makes the record reachable; a report who belongs in the channel is added by email invitation onto a free account and reads it in their language.

The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia. A report on leave for a month keeps access and costs nothing that month, and the one-on-one they come back to is in the channel, with every session's recap and the open items where they left them.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

The questions survive every tool: somebody still has to choose three for the week, ask the second one, and say the answer back as a sentence. What does not have to survive is the second job — typing that sentence up after the call, in one language, and finding it again in September.

FAQ

What questions should I ask in a one-on-one meeting?

Three, chosen for the situation, each with a second question behind it. On an ordinary week: what took more of your time than it should have; what are you putting off, and what would make it easier to start; what do you need from me this week that you haven't asked for. On a hard week, start with how the person is doing and end with what would make tomorrow easier. For growth, once a month: what would you like to be doing more of a year from now, and what do you need from me this quarter to take one step towards it. The sixty questions above are grouped by ten situations so that the group for the week is a short list.

What are good questions for the first one-on-one with a new employee?

How they like to work — hours, focus time, where they think best; how they prefer to get feedback; what a good week and a bad week look like for them; what their last manager did that they'd like kept, and stopped; what they'd like to understand about the team by the end of the month; and their first three questions for you. The answers are the working agreement for the pair, and they belong in the shared note where both of you will find them in month three.

How many questions should you ask in a one-on-one?

Three first questions in a 30-minute session, because each one is really two: the first opens the subject, the second ("what makes you say that?", "what would change that?") gets the real answer. A one-on-one that gets through ten questions is an interview; one that gets through three and records three sentences with names and dates is a one-on-one.

What questions should I ask my manager in a one-on-one?

What the priorities for the next month are, in order; the one thing they'd like you to do differently; what decision they are working on that affects your work; how they see your work from where they sit; what you would need to show for the next step to be a conversation; and whether there is something they are hearing about your work that you are not. Three of these a month, asked from the report's side, is a one-on-one in its own right even when the manager brings no questions.

What should you not ask in a one-on-one?

Anything the channel already answers — "how is the migration going?" is a status question, and the report has answered it every day this week. Anything that accepts "fine" as an answer, because it will get "fine". And the manager's own update, which is two minutes at the end if it is there at all: the one-on-one is the report's meeting.

How do you keep track of what was said in one-on-ones?

Write each answer that produces anything back as a sentence with a name and a date, keep one place per pair that both people can open, and start every session by reading the last session's open items aloud: done, not done and why, or dropped on purpose. In Teams the place is collaborative notes in a group chat, in Slack a canvas in a private channel per pair, in Google Workspace a Doc per meeting — one hand-typed document in one language, as the table above lists from the vendors' documentation. In InterMIND the pair is a channel that keeps the note, the chat and the recap of every session, each of you reading it in your own language.

What questions do you ask when a one-on-one has gone stale?

Change the group. A stale one-on-one is usually one where the same three questions have been asked for a quarter; take the stalled-quarter group if the work has stopped moving, the feedback-for-the-manager group if the report has stopped bringing items, and the growth group if the last growth conversation was more than a month ago. If none of them fits, ask question 36 — "is there something you've told me twice that I still haven't done?" — and let the answer set the next session's agenda.

Sources: Microsoft — Use collaborative notes in Microsoft Teams chats; Microsoft — Take meeting notes in Microsoft Teams; Slack — One-on-one meeting template; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Zoom — Using Meeting Summary with AI Companion. Microsoft, Slack and Google pages checked October 2026; the Zoom meeting-summary page checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state.