How to Prepare for a One-on-One Meeting

A one-on-one is a standing appointment, not a favour you ask for. Baylor University's HR guidance describes the common pattern as thirty minutes once a week, stretched to forty-five or sixty minutes when the role is complex or the person manages others. The US Office of Personnel Management tells federal supervisors to hold check-ins monthly at the very least. Put the slot in the calendar as a recurring event and treat illness or a genuine emergency as the only reasons to drop it.

Format changes how honest the conversation feels. Harvard Business School's Working Knowledge advises managers to settle the cadence and the setting with each person: a desk, a small meeting room, a coffee, or a walk around the block. The same piece warns against turning the meeting into after-work drinks, because the signal is that the discussion is not serious. If you work remotely, use video rather than audio, and try to get one or two in-person meetings a year.

Scattered notes are the same as no notes. Pick one place for every one-on-one you have with this manager, in date order, and never split it across a notebook, a phone app and three email drafts. A paper notebook, a single document or one long note all work. What matters is that you can scan back through six months in a minute and find the commitment you are about to ask about again.

Preparation starts with the previous meeting, not with this one. Baylor's guidance for managers is to review the earlier notes before arriving, and the advice is just as useful on the other side of the table. Go through the last page and mark three categories: what you finished, what slipped and why, and what you are still waiting on from your manager. That third category is the part most people quietly drop.

Nobody can reconstruct a fortnight of work the night before a meeting. Keep a slow-growing list instead. When something goes unusually well, when a decision gets stuck, when a piece of feedback lands, add one line on the spot. By the time you sit down to prepare, the raw material is already there and you are choosing between items rather than straining to remember any.

Half an hour holds three topics if you want any of them discussed properly. Lay out everything you could raise, then cut until two or three remain, and leave a few minutes at the end for whatever your manager wants to bring. The cut items are not lost. They either go in the written update, wait for the next meeting, or turn out not to matter, which is its own answer.

A heading like "the migration" gives your manager nothing to prepare. A line that asks which of two options to run first, or who owns the sign-off, tells them exactly what you need from the next ten minutes. Phrase every item so that the meeting can end with an answer. If you cannot find the question inside a topic, you are probably about to deliver a status report.

Baylor's tips are explicit: keep status updates out of the meeting when an email would do. Status is low-bandwidth information, and reading it aloud spends your most valuable half hour on the thing a document does better. Send the update separately in writing, keep it short, and bring to the meeting only the parts where progress depends on a judgement, a trade-off or a decision that is not yours to make.

The OPM roadmap asks supervisors to run development conversations regularly rather than saving them for the annual rating, and to make goals specific, measurable, achievable, relevant and time-bound. Its own example replaces "improve reporting accuracy" with "reduce reporting errors by 25% over the next six months". Put one development line on every second or third agenda: a skill you want, a project you want near, or feedback on something you are deliberately practising.

Working Knowledge recommends sending the list roughly twenty-four hours before the meeting, and saying plainly if the other person needs to read or bring something. Keep it to a handful of bullet points in the body of a message, not an attachment. Close by asking what they would like to add. That single question turns your list into a shared agenda and gives your manager room for the topics they were saving.

Walk in with the notebook, the agenda and nothing else running. Close the other tabs, silence the notifications on both your phone and your laptop, and leave the unrelated work where it is. If the meeting is remote, open the call early enough to check that the camera, the microphone and the light are all behaving, and sit where the window is to the side of you rather than behind.

The first two minutes are not filler. Working Knowledge treats personal connection as a legitimate part of the agenda and suggests bookending hard topics with easier ones, so nobody leaves the room deflated. Start with a short human check-in, then one thing that went well since you last spoke, then move into the list. A single concrete win also quietly answers the question managers rarely ask directly.

Take each item in turn, give the context in a couple of sentences, ask your question and then leave the silence alone. Both HR guidance and management writing describe the same failure mode: one person filling the whole half hour. If there is feedback you want, ask for it by name. "How did the client call come across to you?" gets a real answer far more often than "any feedback for me?"

Spend the last three minutes repeating what you both agreed: who does what, and by when. Saying it aloud catches the mismatch while you can still fix it, which is the whole point. Include your manager's actions as well as yours. Then ask the one question that is easy to forget in your own meeting: is there anything they need from you before the next one?

Working Knowledge recommends following every one-on-one with brief notes covering what was discussed, what was decided and any feedback given. Keep it to a few lines and send it the same day. A recap keeps you both on one version of the conversation, and it builds a record you will be grateful for later. Paste the same lines into your running notebook so the next preparation session starts with a finished page.