The One-on-One Agenda

The toolkit overview made the case that a good template is a decision someone already made carefully, so you don’t have to make it badly under pressure. The one-on-one is the first template in the part for a reason: it is the single highest-leverage recurring conversation a manager has, and it is the one most people run badly — or quietly stop running at all.

This page gives you a blank agenda you can reuse every week, a short guide to running it, and a filled-in example from a real conversation. The goal is narrow and important: keep the meeting about the person, not the project. Status belongs elsewhere (see The Weekly Status Report). This half hour is for everything status can’t capture.

What a one-on-one is for

A one-on-one is a recurring, private conversation between you and someone who reports to you. It is not a project checkpoint, not a performance review, and not a place to hand out tasks. Its job is to build a working relationship strong enough that problems surface early — while they are still small, cheap, and fixable.

The core principle: the report owns the agenda. It is their meeting. You are a guest with a standing invitation. When the manager owns the agenda, the conversation drifts inevitably toward what the manager cares about — usually status and deliverables — and the report learns there is no room here for anything else. When the report owns it, you find out what is actually on their mind: the teammate they can’t work with, the decision they’re stuck on, the ambition they haven’t said out loud.

The evidence — small, frequent contact beats big, rare contact

Research on manager effectiveness generally points the same direction: regular, predictable one-on-ones are associated with more engaged, less burned-out teams than infrequent or ad-hoc check-ins. The mechanism is simple — a standing meeting lowers the cost of raising something. If the report knows there’s a slot every week, a worry that isn’t worth interrupting you over still gets aired within days, instead of festering for a month. Cadence, more than any clever question, is what makes the tool work.

The template

Keep it short. A one-on-one is usually 25–50 minutes and four sections is plenty. The order matters: their topics come first, because whatever time you lose at the end, you want to lose it from your topics, not theirs.

ONE-ON-ONE — [name] & [manager]        Date: ____   Cadence: weekly / biweekly

1. THEIR TOPICS  (they lead — this is most of the meeting)
   - Anything on your mind: work, people, decisions, ideas
   -
   -

2. BLOCKERS  (what's in your way that I can clear?)
   - Waiting on / stuck on / need a decision about
   -

3. GROWTH & CAREER  (the long game — not every week, but often)
   - Skills you want to build / work you want more (or less) of
   - Where you want to be in a year
   -

4. FEEDBACK — BOTH DIRECTIONS
   - From me to you:
   - From you to me (how am I helping / getting in the way?):

ACTION ITEMS  (who does what by when — carried forward each week)
   [ ] ____ — owner ____ — by ____
   [ ] ____ — owner ____ — by ____

Carried over from last time:
   [ ] ____

That’s the whole thing. Notice what is not on it: a status update. If you catch yourself asking “so where are we on the launch?”, stop — that question has its own home.

How to use it

Send it before, fill it during. Share the blank template as a living document (a shared doc, a note, whatever you both can edit). The report adds their topics before the meeting; you both take notes in it live. Over time it becomes a shared history of the relationship.

Start by shutting up. Open with “What’s on your mind?” and then wait. The silence will feel long. Let it. The most valuable things people say in a one-on-one come after the first, easy answer — so resist filling the gap.

Protect the cadence like it’s load-bearing. Pick a rhythm — weekly for newer or struggling reports, every two weeks for experienced ones — and put it in the calendar as a recurring event. Then treat it as nearly unmovable. Reschedule if you must; cancel almost never.

Carry action items forward. At the end, you should have a short list of who-does-what-by-when. Copy anything unfinished into a “carried over” section for next time. This one habit is what turns a pleasant chat into something that actually moves. A promise made in a one-on-one and never revisited teaches the report that the meeting is theater.

Growth is the slow section. You won’t touch career every week, and that’s fine. But if a month goes by with zero mention of where the person is heading, the meeting has quietly become pure operations. Every few weeks, deliberately steer into it.

The common trap — the one-on-one that becomes a status meeting or gets cancelled

There are two ways this tool dies, and both are common.

The first is collapse into status: the meeting slowly fills up with “where are we on X?” until it is indistinguishable from a project sync. The person stops bringing real topics because there’s never room. The fix is mechanical — move status to a written report or a separate meeting, and open the one-on-one with their list, not yours.

The second is the cancellation habit: the one-on-one is the first thing to go when your week gets busy. But think about the signal. You are telling the person that when things get hard, they are the least important item on your calendar — which is exactly backwards, because hard weeks are when they most need the channel open. If you must move it, reschedule it; don’t delete it. A protected 20 minutes beats a perfect hour that never happens.

A filled-in example

Here is a real-shaped one-on-one between a manager, Dana, and a report, Sam, who leads a small support team. Notice that status barely appears — and that the most important thing said (Sam is quietly burning out) only surfaced because there was room for it.

ONE-ON-ONE — Sam & Dana              Date: Mar 12   Cadence: weekly

1. THEIR TOPICS
   - The new ticket-routing rules are creating more work, not less. Team is frustrated.
   - I've been covering the evening shift alone for three weeks and I'm fried.
   - Idea: could we trial a shared on-call rotation instead of one person owning nights?

2. BLOCKERS
   - Still waiting on IT access for the two new hires — they start Monday and can't log in.
   - Need a decision from you: do we pause the routing rules or push through?

3. GROWTH & CAREER
   - Sam wants to move toward a team-lead role, not just do more of the same tickets.
   - Would like to shadow Dana in the ops planning meeting next month.

4. FEEDBACK — BOTH DIRECTIONS
   - Dana → Sam: The way you rewrote the escalation guide was excellent — clear and calm.
     One thing: loop me in earlier when the team's frustrated, don't absorb it solo.
   - Sam → Dana: The Slack pings after 6pm make it feel like I can never fully log off.

ACTION ITEMS
   [x] Dana — chase IT for new-hire access today — by end of day
   [ ] Dana — decide on routing rules (pause vs. push) — by Thu
   [ ] Sam — draft a shared on-call rotation proposal — by next 1:1
   [ ] Dana — stop non-urgent evening pings; batch them for morning — starting now

Carried over from last time:
   [ ] Sam to book the ops-meeting shadow with Dana — still pending, move to this week

Two things to see here. First, the routing rules item looks like status, but Sam raised it as a problem affecting the team — so it belongs to them, and it led to a decision and an action, not just an update. Second, “I’m fried” and “the evening pings” are precisely the things a status report would never contain, and precisely the things a manager most needs to hear. The agenda made space for them.

In practice — the action that closed the loop

The single most valuable line in Sam’s meeting isn’t a topic — it’s the last action item: Dana will stop non-urgent evening pings. Sam gave upward feedback; Dana turned it into a concrete change with a start time. Next week, the “carried over” section is where Sam gets to confirm it actually happened. That loop — feedback, action, follow-up — is what teaches a person that speaking up here is safe and worth it. Skip the follow-up and the feedback dries up.

Try this

Before your next one-on-one, do two small things. One: send the person the blank template above and ask them to add their topics before you meet — then open the meeting with their list, not yours, and stay quiet after “what’s on your mind?” for a full ten seconds. Two: at the end, write down exactly one action item with an owner and a date, and copy it somewhere you’ll see it next week. If you already run one-on-ones, audit the last three: how much of each was their agenda versus yours? If it was mostly yours, you’ve found a status meeting wearing a one-on-one’s name tag.

Reflect

1. Whose agenda do your current one-on-ones actually follow — the report’s, or yours? How can you tell?
2. When was the last time someone told you something genuinely hard in a one-on-one? If it’s been a while, what might that silence be telling you?
3. What happens to your one-on-ones when your week gets busy — and what does that pattern signal to your reports?
4. How often does career or growth come up in these meetings, versus pure operations? Which section quietly gets crowded out?
5. Think of a piece of feedback a report gave you upward. Did it turn into a visible change they could see the next week — or did it evaporate?

Show reflections

1. The honest test is the opening minutes: if you tend to start with your questions, the meeting is yours no matter whose name is on it. A report-owned meeting usually feels a little unpredictable — you don’t always know what’s coming — and that unpredictability is the point.
2. Hard truths surfacing is the best evidence the tool is working; a long run of pleasant, frictionless meetings often means the person doesn’t yet feel safe raising the real thing. That’s usually about cadence and follow-through, not about asking cleverer questions.
3. If one-on-ones are the first thing you cancel, you’re training people that they matter least when things are hardest — the opposite of what you want. Rescheduling instead of deleting keeps the channel open and sends the reverse signal.
4. Growth is the section that silently disappears, because operations always feels more urgent. If a month has passed with no career talk, that’s a cue to deliberately steer into section 3 next time — even for five minutes.
5. This is the loop that makes upward feedback survive. A change the report can see teaches them that speaking up moves things; feedback that vanishes teaches them to stop bothering. The “carried over” section exists to make that follow-through visible.