Meeting notes · One-on-ones · Management
One-on-one meeting questions: what to ask, with a 30-minute agenda
By T. Krause
Questions for your one-on-ones, sorted by what you want to find out: how someone is doing, what is blocking them, feedback in both directions, growth and workload. Plus a 30-minute agenda and a way to keep notes from one meeting to the next.
Your one-on-one starts in ten minutes and you have nothing written down. You'll probably open with "So, how's it going?" and get "Fine, busy" back. Then you'll talk about the project for half an hour, which you could have done in the team channel.
A list of good questions helps, but only if you pick from it with a purpose. This guide groups questions by what you are trying to find out, gives you a simple agenda for a 30-minute meeting and shows how to keep notes so each one-on-one picks up where the last one stopped. If you want a page that is already set up for that, the one-on-one template has the layout ready.
What a one-on-one is for
A one-on-one is a regular, private meeting between a manager and one person on their team. It belongs to the team member more than to the manager. It is the place for things that don't fit into a stand-up or a project meeting: what is getting in their way, how they feel about their work, what they want to learn, and feedback that shouldn't be given in front of others.
It is a poor place for status updates. If most of your one-on-one is "where are we on X?", move that question to a written status update or a team meeting and use the time for what only a private conversation can do.
One-on-one meeting questions, grouped by purpose
Don't work through a list. Pick two or three questions before each meeting, based on what you want to learn this time, and leave room for whatever the other person brings. Open questions work better than yes-or-no ones. "Any problems?" gets "No." "What took longer than you expected this week?" gets an answer.
Check-in questions
Use one of these to open.
- What's on your mind this week?
- What went well since we last talked?
- What do you want to make sure we cover today?
- On a scale of one to ten, how was your week, and what would have made it a point higher?
Priorities and blockers
These find the work that is stuck before it shows up as a missed deadline.
- What are you working on that matters most right now?
- What is slowing you down?
- Is there a decision you're waiting on from me or someone else?
- What took longer than you expected, and why?
- If you could drop one thing from your list, what would it be?
Feedback both ways
Give feedback in the one-on-one while it is still fresh, rather than saving it for the review. Then ask for some back. Asking for feedback about yourself only works if you take the answer without arguing, so listen and write it down.
Feedback for them:
- Can I share something I noticed in the client call on Tuesday?
- What do you think went well in that presentation, and what would you change?
Feedback for you:
- What could I do differently to help you more?
- Is there something I do that gets in your way?
- What's one thing about how this team works that you'd change?
- Was there a decision recently that you didn't understand or didn't agree with?
Growth and career
Not every week. Once a month or so, set aside a meeting mostly for these.
- What part of your work do you enjoy most right now?
- What would you like to be doing more of in a year?
- Which skill would you like to get better at, and how can I help?
- Is there a project coming up you'd like to be part of?
- How do you feel about where your role is heading?
Wellbeing and workload
Ask these without pressure, and accept a short answer. People share more once they trust that it won't be held against them.
- How is your workload at the moment, too much, too little or about right?
- Are you able to switch off in the evenings?
- Is anything outside work making this week harder that I should know about?
- What drains your energy at work, and what gives you energy?
Questions for a first one-on-one
The first meeting with a new team member, or with someone you have just started managing, sets the tone. Spend it learning how they like to work.
- How do you like to receive feedback, in the moment or saved for our one-on-ones?
- What did a good manager do for you in the past?
- How do you prefer to communicate, written messages or a quick call?
- What are you hoping to get out of these meetings?
- How often would you like to meet?
A 30-minute one-on-one agenda
Thirty minutes is enough for most weekly one-on-ones. Their topics go first. If you start with your list, theirs gets whatever time is left, and the meeting starts to feel like a status check.
- Check-in, 5 minutes. One check-in question and a look at last meeting's follow-ups.
- Their topics, 15 minutes. Whatever they added to the page during the week. If they added nothing, use a question about blockers or growth.
- Your topics and feedback, 5 minutes. News they should hear from you, and feedback while it's still current.
- Follow-ups, 5 minutes. Agree who does what before the next meeting and write it down with a name in front.
Here is how that can look on the page. The people and topics are invented.
14 November, Sam and Priya
Topics from Priya: the support backlog after the release, a course on writing documentation.
Topics from Sam: feedback on last week's customer email (clear and calm, keep doing that), the hiring plan for next quarter.
Follow-ups: Priya to send two course options by Friday. Sam to ask finance about the training budget.
How often to hold one-on-ones
Weekly or every two weeks suits most teams. Weekly helps with someone new to the team or the role, or anyone in the middle of a difficult project. Every two weeks can work for an experienced person who already talks to you often. Mentoring sessions and skip-level meetings, with the people who report to your managers, can be monthly.
Pick a rhythm and keep to it. If you have to, move a one-on-one rather than cancel it. A meeting that keeps getting cancelled tells the other person it comes last on your list.
How to keep running notes between meetings
The questions are half the work. The other half is memory. Without notes, every one-on-one starts from zero and the follow-ups from last time get lost.
A setup that works for most managers:
- One shared page per person. Not a new document per meeting. Put the newest meeting on top, so you both open the page and see this week first.
- Topics added during the week. Each of you has a heading for your own topics. When something comes up on a Wednesday, add it there and stop trying to remember it.
- Follow-ups with a name. Every action gets an owner, written at the start of the line. Start the next meeting by checking them.
- Old meetings folded away. After a month or so, collapse earlier meetings so the page stays short. At review time you can read back through six months in order instead of trying to recall them.
- Private notes kept elsewhere. Notes you would not want the other person to read don't belong on a shared page. Keep them on a separate page that only you can open, and keep them factual.
If your team runs other recurring meetings as well, the guide on how to write meeting minutes covers the format for group meetings, where the record has to work for people who weren't there.
Doing this in Prompt Notebook
Prompt Notebook is the notes app we make, and its one-on-one template follows the setup above. It is one page with the newest meeting on top, a heading for each person's topics, a follow-ups list of to-dos and an Earlier meetings toggle for older notes. Share gives the other person edit access, and nobody else sees the page unless you add them. Search with ⌘K still finds meetings inside the toggle.
Two AI features help once the page has some history. Select a few months of meetings and pick Summarise in Ask AI to get a short overview before a review, then check it against the notes. Ask your workspace answers a question like "what did we agree about the training budget?" with numbered links to the pages it used, and it only searches pages you are allowed to open. Clear follow-up lines make those answers better, for the reasons explained in how AI answers from your notes work.
Open the one-on-one template and fill in your first meeting.
Common mistakes
Turning it into a status update. If you could have asked the question in the team channel, ask it there.
Doing most of the talking. As a rough check, the other person should talk for more than half the meeting. Ask a question, then wait.
Cancelling when things get busy. Busy weeks are often when people most need the meeting.
Saving feedback for the annual review. Nothing in a review should come as a surprise. If it does, the feedback was held back for too long.
Forgetting the follow-ups. A follow-up that nobody checks teaches both of you that agreements in one-on-ones don't count.
Frequently asked questions
How long should a one-on-one meeting be?
Thirty minutes works for most weekly one-on-ones. If you meet every two weeks, or if a meeting is set aside for career topics, plan 45 to 60 minutes. End early when you're done rather than filling the time.
Who sets the agenda for a one-on-one?
Both of you, with the team member's topics first. A shared page where each person adds topics during the week means the agenda is already there when the meeting starts.
Should one-on-one notes be shared with the employee?
The running notes, yes. Topics, agreements and follow-ups should be visible to both people, so you remember the same things. Keep personal notes you wouldn't show them on a separate private page.
What if my employee has nothing to talk about?
Bring two prepared questions from different groups, for example one about blockers and one about growth. If that happens every week, ask them directly whether the meeting is useful in its current form and what they would change.