Running a one-on-one that actually helps

Meetings · 8 min read

Most one-on-ones fail quietly. They drift into a recital of what happened this week, end without a decision, and get cancelled the first time the calendar gets crowded — until the meeting exists on paper and nowhere else. That is a waste of an unusually valuable half hour. Gallup's analytics have long found that managers account for about 70% of the variance in team engagement, and the one-on-one is the recurring conversation where much of that influence is actually delivered. The good news: a helpful one-on-one does not need a charismatic manager or a complicated system. It needs four things — a clear owner, status moved out of the room, a light structure, and a running document that remembers what was agreed.

Whose meeting is it, actually?

Meeting researcher Steven Rogelberg, author of Glad We Met, makes a distinction that rearranges everything else: the manager facilitates the one-on-one, but the meeting belongs to the employee. His research found that a lightweight agenda was associated with more effective one-on-ones — and that the employee driving the plan mattered even more than the agenda itself. A lockstep script is not the goal. Two approaches worked well in his research: a small set of broad core questions that rotate over time (so the conversation does not go stale), and a listing approach, where the employee brings a list of topics — big and small, short-term and long-term — and the manager's own list comes second, only if time allows.

This framing matters for both chairs. If you manage people, your job in the meeting is infrastructure: hold the cadence, protect the time, and make it safe for the other person to set the agenda. If you report to someone, the meeting is yours to use — which means arriving with topics is not being pushy; it is the meeting working as designed.

Move status out of the room

The fastest way to waste a one-on-one is to spend it reporting progress the other person could have read in two minutes. Status is information transfer, and information transfer is what documents are for. The fix is a rule both sides can adopt without permission from anyone: before the meeting, the employee sends a short written update — what was finished, what is in progress, anything already blocked. Five bullets is plenty, and it can be the same update used for a weekly team summary.

That single change converts the meeting's purpose. Instead of "here is what I did," the conversation becomes "here is where I need a decision, a resource, or your judgment" — the three things that genuinely require two people in a room together. Status still gets communicated, earlier and more reliably than before; it just stops consuming the only half hour reserved for discussion.

Pick a structure: three agenda models compared

A light structure beats both a rigid script and no plan at all. Three published models are worth knowing, because they suit different situations:

None of these is the "right" one. The decision rule is diagnostic: if meetings feel one-sided, choose 10-10-10; if action items vanish between meetings, choose the five-part split with its built-in review; if the conversation never rises above this week's tasks, choose the balanced agenda and defend the growth item. Kim Scott of Radical Candor offers a lighter alternative still — framing the employee's agenda around four recurring questions, including what is on their mind this week and what feedback they have for their manager. Whichever model is chosen, hold it loosely: Rogelberg's finding was that lightweight beats lockstep.

The running doc does the remembering

One shared document, appended every week, is the entire technology requirement. Radical Candor points out why it earns its keep: it captures action items, decisions, and due dates so nothing falls through the cracks; it lets the other person read the agenda in advance and arrive prepared rather than surprised; and over months it builds a running archive that becomes genuinely useful at performance-review and career conversations, when memories are otherwise unreliable.

Keep the format boring on purpose. Each week gets a dated heading, the agenda items as bullets, and a short "agreed" list at the end with an owner and a date for each item. The next meeting opens by scanning last week's "agreed" list — thirty seconds that quietly create accountability without any formality. If a topic matters but there is no time, it stays in the doc as a parked item instead of evaporating.

A decision framework: what belongs in the room

When a topic could go either way, run it through three questions:

• Does it need a decision or a judgment call? If a choice has to be made and the other person's authority or perspective changes the answer, it belongs in the room. If it only needs to be known, it belongs in the written update.
• Is something blocked on the other person? Blockers belong in the room, framed with options: what is stuck, what has been tried, and what specifically is being asked for — a decision, a resource, an introduction, or air cover.
• Is it about direction, growth, or the working relationship itself? Career topics, feedback in either direction, and frustrations with how the work is going almost never survive being put in writing alone. These are the highest-value uses of the half hour, and the first to be crowded out when status takes over.

Everything else — progress reports, FYI items, scheduling — goes in the pre-written update or a quick message during the week. The framework's point is not bureaucracy; it is protecting scarce synchronous time for the small set of things that only work synchronously.

Repairing a stale or cancelled cadence

Pathwise and Radical Candor agree on the diagnosis: cancelling occasionally, when both people genuinely agree there is nothing pressing, is fine — but cancelling regularly sends a clear message that the other person's time is not a priority, and it damages trust. If a one-on-one has decayed into that pattern, do not just rebook it and hope. Run a short reset:

1. Name it directly. Open with the pattern, not a complaint: "Our last three meetings were cancelled, so the cadence is not working. Can we fix the setup rather than let it fade?"
2. Shrink before you cancel. Offer a shorter meeting — 20 minutes, same slot — for a trial of four weeks. A shorter meeting that happens beats a full one that does not.
3. Reschedule, never delete. Agree that a conflict moves the meeting within the same week instead of removing it. The slot is movable; the cadence is not optional.
4. Restate the purpose in one sentence. For example: "This half hour is for blockers, decisions, and your development — status goes in the written update." A shared purpose gives both people something to defend when the calendar gets crowded.
5. Review after four meetings. Ask explicitly what would make the meeting more useful, and change one thing. A meeting that gets reviewed gets kept.

What success looks like: four consecutive meetings held (rescheduled counts, cancelled does not), each one opening with last week's agreed items, and at least one decision, unblocked problem, or longer-term topic covered per meeting. If the written update is doing its job, nobody in the room should be hearing routine status for the first time.

Next: Managing up without more meetings →