How to Run Effective One-on-One Meetings That Your Team Doesn’t Want to Cancel
The one-on-one is the only meeting most employees have that exists for them, and it is the first meeting most managers cancel when the week gets busy. That combination is why so many of them decay into status updates, get rescheduled into oblivion, or persist as a fifteen-minute formality that neither side would miss. This guide covers how to run one-on-ones that hold their slot and earn it: the cadence, who owns the agenda, what a manager should bring, and what should never come into the room.
What a One-on-One Is For
A one-on-one is not a status update; status belongs in the tools and in team meetings. It is not a performance review; those are periodic and documented, and our guide on conducting a performance review covers them separately. And it is not a project meeting with one attendee.
It is the employee’s time: the one scheduled hour in the fortnight where the agenda is theirs, the manager listens more than talks, and the subjects are the ones that never fit anywhere else. Blockers the person is embarrassed to raise in a group. Career direction. Whether the workload is sustainable. Feedback in both directions. The meeting exists to surface what the manager would otherwise find out three months late, usually in a resignation conversation.
Managers who treat it that way find it is the highest-leverage hour in their calendar. Managers who treat it as a status update find their reports stop preparing for it, and then stop turning up.
Cadence and Length
Weekly for new hires, people in difficulty, and anyone whose work changes fast. Fortnightly for most established employees. Monthly is too infrequent for anything but very senior reports, because a month is long enough for a problem to become a decision.
Thirty minutes is the practical default. Less becomes a check-in; more becomes a meeting people dread. The important property is not the length but the reliability: a thirty-minute slot that happens on the same day every fortnight is worth more than an hour that floats. Rescheduling occasionally is fine. Rescheduling more than one in four tells the employee where they rank, and they will hear it.
Protect the slot the way you would protect an external meeting. If the manager’s calendar shows one-on-ones as the first thing to move, that is the first thing to fix.
The Employee Owns the Agenda
The single change that improves most one-on-ones: the employee sets the agenda, and the manager adds to it, not the other way round. A shared document that both can edit, with the employee’s items on top, does the job. If the employee arrives with nothing three times running, that is itself the topic, because it usually means they have concluded the meeting is not for them.
The manager’s standing items are few. Anything the employee needs to hear before they hear it elsewhere. One piece of specific feedback. One question about workload or wellbeing that is asked every time, so that answering it honestly becomes normal.
A useful opening question for the employee’s section is “what is getting in your way?” rather than “how is it going?”. The first invites a blocker; the second invites “fine”.
What to Bring From the Data, and What to Leave Out
Managers with access to working-time and productivity data face a choice about whether it belongs in the one-on-one. The answer is: some of it, carefully, and only in the employee’s interest.
Bring: a hours trend that suggests overload. “Your weeks have been over 50 hours for a month; is that sustainable, and what can we take off?” is exactly the conversation the meeting exists for, and the data lets it happen before the person breaks rather than after. Bring meeting load if it is crowding out the work the person is measured on. Bring a focus pattern if the person has said they cannot get anything done, because it turns a complaint into a specific problem with a specific fix.
Leave out: anything that reads as surveillance. Which sites were visited, minute-level activity, comparison with peers. The moment the one-on-one becomes the place where monitoring data is used against the employee, it stops being their meeting and they stop bringing anything to it. Our guide to using monitoring data in performance reviews covers the legal side; the management side is simpler: if you would not show the employee the dashboard you are reading from, do not read from it.
The best practice is for the employee to have the same view you do. When both people can see the hours trend, the conversation is about the trend, not about the fact that the manager was looking.
One-on-One Meeting Health, This Quarter
One-on-ones held on schedule, by week
Where the time goes
▲ Workload flags rose once the hours-trend question became a standing item; two reports had work reassigned in W4.
Illustrative eMonitor dashboard.
A Structure That Works in 30 Minutes
Minutes 0–3: how are you, genuinely. Not a formality. If the answer is off, the rest of the agenda can wait.
Minutes 3–18: the employee’s items. Blockers, decisions they need, things they want to raise. The manager’s job is to listen, ask, and commit to specific follow-ups.
Minutes 18–25: the manager’s items. One piece of feedback, anything they need to know, the standing workload question.
Minutes 25–30: career and growth, every third meeting; otherwise, confirm the follow-ups and who owns each. Write them in the shared document while both are present.
The follow-ups are where trust is built or lost. A manager who commits to three things and does none has taught the employee that the meeting is theatre. Fewer commitments, all kept, is the rule.
Common Failure Modes
The status update. The manager asks “where are we on X?” and the meeting becomes a project review. Fix: status goes in the tool; if the manager needs it, they read it beforehand.
The monologue. The manager talks for twenty-five of the thirty minutes. Fix: the employee’s items go first and get the majority of the time, by structure rather than intention.
The cancel cascade. One reschedule becomes two, then the slot quietly disappears. Fix: treat the slot as an external commitment; if it must move, move it within the same week.
The surprise. Difficult feedback lands in a one-on-one that the employee thought was routine. Fix: signal in advance that there is something to discuss. The meeting should never be the first the person hears of a serious concern.
The data ambush. The manager opens a dashboard the employee has never seen. Fix: covered above. Shared data or no data.
Shared Data Makes Better One-on-Ones
eMonitor gives employees the same view of their hours, meeting load and focus time that managers see, so the conversation is about the trend, not about who was watching.
One-on-Ones for Remote Teams
Remote one-on-ones matter more and are easier to skip. The informal correction that happens in an office, the corridor conversation and the noticed bad day, does not happen remotely, so the one-on-one carries all of it. Cameras on, if the team norm allows, because a great deal of the “how are you” answer is on the face rather than in the words.
The hours-trend question is also more important remotely, because remote working days lengthen invisibly. Our guide to the signs of employee burnout lists what to listen for, and the guide to tracking time for remote employees covers how to have the data available without it becoming surveillance.
Skip-Levels and Group Meetings Are Not Substitutes
Skip-level meetings, where a manager’s manager meets the team, are valuable and different: they check on the manager, not the employee. Team meetings are for coordination. Neither replaces the one-on-one, and organisations that try to consolidate them into a single “check-in” lose the one hour that belonged to the employee. Our guide to reducing meeting overload is explicit about this: cut everything else first.