Most one on ones fail because the manager talks and the report performs. Run them effectively by making the report own the agenda, opening with a two-minute check-in, spending the bulk of the time on blockers and growth rather than status, and closing with one named commitment and a date. Thirty minutes, every week or fortnight, held even when nothing is on fire. The meeting's job is the relationship and the small course corrections that never survive a busy quarter. Status belongs in writing.

Why Status Updates Are the Fastest Way to Waste Thirty Minutes

A status meeting is a report. A one on one is a conversation. When the two get merged, the report always wins, because it's concrete and easy to run through, and the conversation gets whatever time is left. That's usually zero.

Put the numbers in a shared doc before the meeting. Traffic, pipeline, tickets closed, whatever the report tracks. The report reads it first and brings only the parts that need a decision. According to Gallup's State of the Global Workplace reporting, manager conversations that focus on strengths and clear expectations correlate more strongly with engagement than conversations dominated by task review. The Meeting Cost Calculator published by Harvard Business Review puts a 30-minute weekly meeting between two people at roughly 52 hours of combined employee time a year.

That figure is the real budget. Fifty-two hours is enough to fix a stalled project or build a skill. It's not enough to read a dashboard aloud.

Keep one exception: if the report's work has changed shape since the last conversation, that's not status. That's a topic, and it goes on the agenda. The rule of thumb is that the report decides what counts, and the manager only adds items when something would otherwise ambush the report.

The Seven-Part Structure That Fits in Thirty Minutes

Five parts carry the conversation. Two are written and read before anyone speaks. The spoken portion uses the whole slot, and the written portion is the report's own preparation, so the balance stays roughly 70% report talking to 30% manager talking.

Segment Time Who leads What it produces
Written update (read before the meeting) 0 min in-room Report Context the manager already has
Check-in 2 min Report A read on energy and load
Report's agenda 8 min Report The topics they chose
Blockers and decisions 8 min Both A named owner and a date
Growth and feedback 6 min Both One specific observation
Manager's topics 4 min Manager Anything not covered above
Commitments and close 2 min Both One action each, with a date

The table is the skeleton, not a script. If the report arrives with three urgent blockers, the growth segment gets pushed to next time. If the check-in reveals a bad week, the agenda shrinks. The ordering matters more than the timing, because it puts the report's material in front of the manager's material every single time.

Keep the written update to five lines. Anything longer gets skimmed, and anything shorter tells the manager nothing.

How to Make the Report Own the Agenda

The agenda belongs to the person being managed. That's the whole design. When the manager sets the topics, the meeting becomes a performance review with a friendlier name, and the report learns to say "all good" and save the real problem for a resignation letter.

Ask the report to send two or three agenda items before the meeting. Not a form, not a template with seventeen fields. A message that says what's on their mind. If they send nothing, the manager opens with "what would make this week easier?" rather than filling the silence with their own list.

Track how often the report sets the agenda. If the manager is setting it most weeks, something is broken, and it's usually trust or time pressure. A report who never brings a topic after four consecutive meetings isn't disengaged; they're testing whether the meeting is safe. Pushing a topic onto them won't fix that. Waiting, and asking open questions, might.

One practical rule: the report's agenda gets the first ten minutes of discussion, before the manager adds anything. That's the simplest way to enforce the priority without lecturing about it.

Opening Lines That Get Past "I'm Fine"

The check-in is two minutes and it is not small talk. Ask something specific enough that "fine" isn't a satisfying answer. "What's one thing that went well this week?" beats "how are you?" every time, because the second question invites a polite lie and the first invites a real answer.

Listen for the second sentence. The first sentence is usually the safe one. "It's going okay, though the release week was rough" contains the whole story in the clause after the comma. Follow that clause instead of moving to the agenda.

The manager should answer the check-in question too, briefly. Not a monologue about their own week, just enough that the report knows the conversation runs in both directions. Symmetry matters more than depth here.

Body language is part of the data. A report who usually leans forward and now sits back with arms crossed is telling you something before they say a word. Note it, don't diagnose it, and give the conversation room to get there. You can name it gently later in the meeting if the rest of the conversation supports it.

Turning Blockers into Decisions with an Owner and a Date

A blocker is anything the report can't move without help. That's a wide category, and it includes things the manager wouldn't call blockers: missing context, an unclear priority, a colleague who hasn't replied, a tool that doesn't work. If it's slowing the report down, it counts.

For each blocker, name three things before moving on. What the report will do next, who else is involved, and when it will be resolved. "I'll chase the vendor by Thursday" is a decision. "Let's keep an eye on it" is not.

Watch for the manager-shaped blocker. That's the one where the report needs the manager to make a call, and the manager says "let me think about it" and the topic evaporates. If the manager can't decide in the room, they name the decision date in the room. Every time. Otherwise the blocker becomes a recurring agenda item that slowly teaches the report that the meeting doesn't produce outcomes.

Don't let a blocker become a project. If a blocker needs more than five minutes, it gets its own meeting, and the one on one moves on. Protecting the slot is part of the manager's job.

Growth Conversations When Nothing Big Is Happening

Most one on ones don't need a developmental plan. They need a specific observation and a question. "I noticed you handled that escalation well, the customer calmed down quickly" takes ten seconds and lands harder than any generic praise.

Bring one specific observation per meeting, tied to something you actually saw. For the manager's own feedback to the report, that observation should be about behavior, not personality. "You interrupted the client twice" is a fact. "You were dismissive" is a judgment, and it invites a defense instead of a conversation.

Ask about the work the report would rather be doing. The answer changes slowly, which is why the question gets asked regularly. The report who mentions wanting more design work three times over six months is telling you something the manager should act on or explicitly not act on, and either answer is fine as long as it's stated in the room.

For the report's feedback to the manager, make it easy. "What's one thing I could do differently?" is a real question, and the manager should sit with the silence after it rather than filling it with reassurance.

Frequency, Length, and the Meetings You Should Cancel

Weekly for thirty minutes beats monthly for two hours. The shorter, more frequent version keeps problems small enough to be fixable. The monthly version turns every conversation into a catch-up about things that already went wrong.

The exception is an experienced report in a stable role who genuinely prefers fortnightly. If the report asks for a different cadence and gives a reason, take the request seriously. A weekly meeting that both people resent is worse than a fortnightly meeting that both people prepare for.

Cancel when the meeting would be worse than the alternative. Specifically: cancel when the manager is unprepared, when the report is on vacation in everything but calendar, and when the meeting was going to be a status readout with no topics on the agenda. Move it or cancel it with notice, and never quietly skip without saying so. A skipped meeting without explanation reads as "you weren't a priority this week," which is exactly the wrong message.

Don't cancel because nothing urgent is happening. The meetings where nothing is on fire are often the ones where trust gets built, and the urgent weeks are the ones where the report needs the calm slot most.

Notes, Privacy, and What Never Goes in the File

Take notes during the meeting, but keep them short. A few lines on commitments and observations. The notes exist to keep the manager accountable to what was said, not to build a dossier.

Share the commitments with the report after the meeting, in writing, so both people have the same record. The shared record is one of the cheapest ways to build trust, because it proves the manager was listening and will follow through. This is the practical test of whether the manager meant anything they said.

Keep sensitive material out of any system the report can't see. Career doubts, personal issues that surfaced in a check-in, and candid feedback about the manager belong in the meeting, not in a performance file. If the manager needs to act on something, they say so in the room before writing it anywhere.

The notes should also track the manager's own commitments. If the manager said they'd get an answer by Friday, the notes say so, and the next meeting opens by confirming it happened. Unkept manager commitments are the fastest way to lose a one on one culture.

One on Ones When the Report Is Struggling or Leaving

When performance is the issue, the one on one still sits in the same slot, but the agenda changes. The manager names the concern in plain terms, gives two or three specific examples, and asks what the report thinks is happening. The report's answer gets the first full hearing before the manager responds.

Don't turn the one on one into a disciplinary meeting, and don't pretend the concern doesn't exist either. If the conversation needs a formal process, that process gets its own meeting, and the one on one stays the place where the report can talk honestly. Mixing the two teaches the report that candor is a trap.

When a report is leaving, the one on one becomes valuable for a different reason. The exit conversation often surfaces truths the working relationship never did. Ask what would have made them stay, listen without defending, and take notes. That feedback is more useful than most engagement surveys.

Handle the close carefully in both cases. Restate the one thing each person will do next, confirm the next meeting's date, and end on something concrete rather than a vague "let's keep talking."

Common Failure Modes and What to Do Instead

The most common failure is the meeting that becomes a status call in all but name. The fix is the written update, sent ahead of time, and the report's agenda getting the first slot.

Failure mode What it looks like Fix
Status drift Manager reads metrics aloud Written update before the meeting
Manager monologue Report says fewer than 50 words Report opens the agenda
Agenda vacuum "Nothing much this week" Manager asks what would make the week easier
Answer-free blockers Repeated items with no decisions Owner and date named before moving on
Cancellation creep Meeting skipped three weeks running Reschedule instead, with notice
Note hoarding Sensitive material in shared files Commitments shared; sensitive material verbal only

Most of these have the same root cause. The manager is treating the one on one as a tool for themselves. The fix is consistently to hand the tool to the report.

Familiarity is the trap. The better the relationship gets, the easier it is to skip the check-in and get straight to the useful stuff. Do it anyway. The questions that feel unnecessary are usually the ones doing the most work.

FAQ

How long should a one on one be?

Thirty minutes is the standard for weekly meetings, and 45 to 60 minutes suits a monthly cadence or a report with a complex role. According to Harvard Business Review's Meeting Cost Calculator, a 30-minute weekly meeting between two people consumes roughly 52 hours of combined employee time a year, so the length should be justified by what the meeting actually produces rather than defaulted to an hour. If the report leaves most weeks with time to spare, shorten it. If the meeting regularly overruns, split the overflow into a separate topic-specific conversation.

Should the manager or the report set the agenda?

The report sets the agenda, and the manager adds topics only when something would otherwise be a surprise. The report's agenda gets the first slice of discussion time before the manager adds anything, because that's the simplest way to protect the priority without needing a policy. If the manager is setting the agenda most weeks, the meeting is drifting toward performance review. Fixing that usually means a written update sent in advance and a deliberate few minutes of silence if the report has nothing.

Is it okay to cancel a one on one?

Yes, with a rescheduled date and a reason. Skipping without notice is different, because it tells the report they were the least important item on the calendar. A cancelled meeting with notice is a normal part of working life; three skipped weeks in a row without a replacement date is a signal that the meeting has stopped being a priority for the manager. When in doubt, hold the slot and keep it short.

What should I do if my report brings nothing to the one on one?

Wait through the silence once, then ask a specific open question, such as what would make the next week easier or which piece of the work is most frustrating right now. If the pattern continues for four or five meetings, consider that the report may not feel safe raising problems, and address the safety directly rather than demanding agenda items. A report who arrives with a full agenda in week one and an empty one in week six is telling you something about the meeting, not about themselves.

Can the manager give negative feedback in a one on one?

Yes, and it should. The rule is that negative feedback is specific, behavioral, and delivered before the report hears it anywhere else. Two or three examples are usually enough, followed by a real question about what the report thinks happened. If the feedback belongs in a formal performance process, that process gets its own meeting, and the one on one remains the place where the report can speak honestly without feeling that every sentence is being recorded.

How do I keep notes without making the report feel monitored?

Share the commitments with the report after each meeting and keep sensitive material out of any file the report can't see. Notes on commitments, dates, and follow-ups build trust because they prove the manager followed through. Notes on personal disclosures, career doubts, or candid feedback about the manager belong in the conversation only. If the manager ever needs to act on something sensitive in writing, they say so in the room first, which gives the report a chance to weigh in.

Do one on ones replace the annual review?

No. The annual review is a formal record used for pay, promotion, and documentation, and the one on one is the ongoing relationship. A well-run one on one makes the annual review less surprising, because the feedback and the growth conversation have been happening all year. Treating the one on one as a substitute for the formal review tends to produce reports who are blindsided at year-end, which is exactly what the regular meeting was supposed to prevent.