A One-on-One Meeting Template That Does Not Become a Status Update

A 30-minute one-on-one agenda you can copy, why the order matters more than the items, and the two variants: a first meeting, and the one where something is wrong.

· 9 min read · Valor team


"So, what are you working on this week?"

That is how most one-on-ones open, and it decides the next twenty-nine minutes. You have just told your report this is a status check, so you get a status check. It is the safest thing either of you can talk about, and it expands to fill every minute you leave open. A one on one meeting template that opens with status is a status meeting with a nicer name.

At minute twenty-eight you ask whether there was anything else. They say "no, I think that's it," because the thing they wanted to raise needed a running start and fifteen minutes, not two.

Here is the agenda to copy, in the order that matters, plus the two variants worth having ready: a first meeting with a new report, and the one where something is wrong.

Status expands to fill the meeting

Every one-on-one template has roughly the same items. Their topics, your topics, project updates, blockers, career, feedback, next steps. The items are not where these meetings go wrong. The order is.

Whatever comes first tells your report what kind of meeting this is. Put status first and you have run a status meeting, because status has no natural end. There is always another ticket, another client, another thing that slipped. Both of you would rather talk about the sprint than about the fact that the last three reviews came back late. Comfortable material expands into whatever space you give it.

So the fix is not a better list of topics. It is one order, held every week:

  1. Their agenda, first and longest.
  2. Your one thing, second.
  3. Status, last, and only the part that did not fit in writing.
  4. Agreements, named out loud, in the final two minutes.

Status goes in a message the night before: what moved, what is stuck, what you need from me. Ninety seconds to read, and it removes the biggest single consumer of the meeting.

The default 30-minute template

Copy this one. The times are not decoration: you will run over on the first block, and the point of the minutes is knowing which one gets cut.

The open is the part everyone improvises, and it sets everything after it.

The last two minutes

The most common way a good one-on-one still fails is that you each leave with a different memory of what was decided. Keep the agreements small and dated, including the ones you are taking.

Write those lines down while they are in the room. It shows the meeting produced something.

The questions that go in the second block are a separate problem: there is a list of one-on-one questions that get real answers.

Two variants worth having ready

A first one-on-one with a new report

Different meeting, different goal. You are not managing yet, you are collecting the operating manual, and you get one chance to ask for it without sounding like an evaluation. Forty-five minutes.

No status block. Nothing a week-one project update tells you is worth twenty minutes of this.

The one where something is wrong

You have a signal. They went quiet in the last two team meetings, the work is late and the reasons are thinner, or a peer said something in passing. Most managers open with "is everything okay?", get "yeah, fine, just busy," and have spent their opening on a question with a polite answer.

Forty-five minutes, and the shape is unusual: you talk for three of them.

What you write down, and what you never write down

Write down commitments with dates, what they asked you for, decisions and who made them, and facts that repeat.

The repeats matter most. Any single one-on-one is noise. The pattern across six is signal: the same blocker three weeks running, or the fourth time a peer's name comes up in a particular tone.

Never write your diagnosis of the person. Nothing about their health, their family, or whether you suspect they are interviewing. Never a colleague's name attached to a verbatim complaint. Nothing you would not read out loud to them if they asked.

Write every note as if they will read it. In many companies they eventually can, and it makes better notes anyway: a fact with a date beats an adjective six months later.

Vague

Jordan seems checked out and has had an attitude problem for a few weeks now.

Specific

Jordan raised the same design review blocker on Aug 12, Aug 19 and Aug 26. I said I would get a decision by Friday and did not.

Two things have to happen between meetings or the notes do nothing. Your commitments go into the same place as the rest of your work, with the date you said out loud: a run of small promises that quietly do not happen is the fastest way to lose someone. And anything carried over goes to the top of next week's agenda before the meeting starts. Carried three times without moving, either it does not matter or it is blocked on you.

Then send three lines the same day: what you agreed, what you owe, by when. Not to build a file. To make sure you both left the same meeting.

When they bring nothing

"I don't really have anything this week." What you do in the next ten seconds teaches them whether preparing is worth it.

The wrong move is filling the space with your own status questions. It trains them precisely: if I bring nothing, she brings an agenda, so I never need to.

No habit yet. Say what you expect once, plainly: two or three things, sent the day before or carried in their head. Then hold the silence next week instead of rescuing it.

Genuinely nothing wrong. More common than managers assume. Spend the time on something that never feels urgent, then end at minute fifteen. Ending early is a better signal than filling.

Something is wrong and they have not decided to tell you. From the outside this looks identical to the one above. The tell is the pattern: nothing this week, three weeks running, from someone who used to bring things.

In all three, ask something specific rather than general. "How is it going" has a polite answer and everyone knows it. "What was the most frustrating hour of your week?" is small enough to answer honestly. A bank of one-on-one meeting questions that get real answers is worth more than any template, because the template only fixes the order.

This does not work if you keep cancelling. A template survives one skipped week and not three: by the third, the meeting is optional and both of you know it. If the calendar cannot hold thirty minutes every week, cut it to twenty and keep the cadence, because the order only pays off when it repeats.

A template you have read is not a meeting you have run

Copying the blocks into a doc takes five minutes. That is not the part that fails.

What fails is minute nine of the hard variant. You have named the observation, you have stopped talking, the silence has run six seconds, and every instinct says to soften it. "I mean, it is probably nothing, everyone is slammed this time of year." That sentence undoes the meeting. You say it because silence inside your own head is easy and silence across a desk from someone you like is not.

Reading a script does not rehearse that. In your head, the report answers you. You have to have said "That is not like you. What is actually happening?" out loud, to someone who deflects, and then held the pause, enough times that holding it stops feeling like cruelty.

Questions people ask

What should be on a one-on-one meeting agenda?+

Four blocks, in this order: their topics first and longest, your one topic second, status last or sent in writing before the meeting, and the agreements named out loud in the final two minutes. The order matters more than the items. Whatever comes first sets what kind of meeting this is, and status put first expands to fill all thirty minutes, so the thing your report actually wanted to raise never gets a slot.

How long should a one-on-one meeting be?+

Thirty minutes every week is the right default, and it works only if status moves out of the meeting and into writing. Use forty-five minutes for a first one-on-one with a new report, and for any conversation where something is wrong, because the real answer usually arrives after the acceptable one. Ending early is allowed. A short meeting that stops when the topics run out beats a long one padded with project updates.

What do you do in a one-on-one when your report has nothing to say?+

Do not fill the time with your own status questions, because that teaches them that arriving with nothing is fine. Ask one specific question instead of a general one: 'What was the most frustrating hour of your week?' gets a real answer where 'How is everything going?' gets 'fine'. If the honest answer is that nothing is wrong, spend the time on something that never feels urgent, then end the meeting early.

What should a manager write down in a one-on-one?+

Write down commitments with dates, what your report asked you for, decisions and who made them, and facts that repeat across weeks. Never write your diagnosis of the person, anything about their health or family, or a verbatim complaint about a colleague that could be forwarded. The test is to write every note as if they will read it, because in many companies they eventually can, and a fact with a date on it is more useful to you anyway.

What should you cover in a first one-on-one with a new report?+

Skip status entirely and collect their operating manual instead: how they want feedback, the fastest way to lose their trust, what their last manager should have done differently, and what they want to be doing more of in a year. Then tell them the same things about you, including the part you are bad at. End with one small agreement so the second meeting has a thread to pick up.

Practice it before you have it

Run this conversation with Alex tonight.

Your best engineer went quiet three weeks ago. Find out why before they resign. In Valor you say it out loud to Alex, senior engineer, who pushes back like the real thing. Ten minutes, then a score that tells you what actually landed.

A

The Tough 1:1

Alex, Senior Engineer · 3 levels

Download on the App StoreGet it on Google Play

Now on the App Store. Android is on its way.

Read next

All 23 pieces in the library