“So… what do you want to talk about?” If a 1:1 opens with those words, the meeting was lost before anyone sat down. No one-on-one meeting agenda means no purpose, and no purpose means the loudest problem in the room wins the half hour.
I ran 1:1s for two decades as a CEO, most recently at Arcules as we scaled from 3 people to 150 across three countries. Every single one had an agenda, the same agenda, and I owned it. Not HR. Not the employee. Me.
This post gives you that structure, a filled-in sample, and the two rules that keep it working: one problem per meeting, and delegated things stay delegated.
Quick answer: A working one-on-one meeting agenda has three timed blocks in a 30-minute slot: up to 5 minutes confirming status sent earlier by email, about 15 minutes of coaching built around a single new growth question, then roughly 15 more driving exactly one problem down to an owner and a date. The manager owns the agenda, always.
Who Owns the One-on-One Meeting Agenda? You Do.
The internet mostly disagrees with me here. The fashionable advice says the 1:1 is “the employee’s meeting,” so the employee should set the topics. I’ve watched what that produces inside real companies: drift, venting, and a manager taking dictation.
The manager always owns the one-on-one meeting agenda and the reporting structure around it. There always is an agenda. Your report feeds it, by sending status in writing beforehand and nominating problems, but you decide what the 30 minutes are for.
That’s not control for its own sake. It’s what makes the meeting safe to go deep in. When both people know exactly what happens in which minutes, the strange, valuable conversations, the ones about shadow sides and standards, finally have room to happen.
Ownership cuts the other way too: if the meeting is a waste, that’s on you. Nobody gets to blame their calendar.
The Structure: 5/15/15 Inside 30 Minutes
Here’s the run order I teach, the same one inside my one-on-one meeting template. Three blocks, hard boundaries.
| Minutes | Block | What happens |
|---|---|---|
| 0 to 5 | Status confirmation | Exceptions to the pre-sent email only. Five minutes is a ceiling. |
| 5 to 20 | Coaching | One new growth question opens it. The person, not the projects. |
| 20 to 35 | One problem | A single problem, solved to an outcome, an owner, and a date. |
Yes, the blocks add to 35 against a 30-minute slot. That’s deliberate slack: status almost never earns its full five, and most meetings a clean email hands the coaching block extra time.
Two structural notes that matter more than they look:
Status never happens live. Your report emails it at least 24 hours ahead: done, on track, stuck, one line each. Reading is faster than listening, and everything the typical 1:1 wastes on recitation, this agenda spends on growth. The five live minutes exist only for what changed overnight.
Coaching sits in the middle on purpose. Front-load status and people linger in it; the comfortable block eats the valuable one. Put coaching second and give it the biggest share, because growing the person is the point. I open it with one growth question, a new one every meeting, and I published five of my best openers with instructions.
A One-on-One Meeting Agenda Sample, Filled In
Templates are abstract until you see a real one. Here’s a one-on-one meeting agenda sample from a plausible Tuesday, manager and a senior product lead, 30 minutes booked.
Received Monday, 9:14 am (status email):
Six commitments: four done, one on track, one stuck (legal review blocking the pricing page). Nominated problem: the stuck item. One heads-up: a designer is interviewing elsewhere.
Agenda as run:
- 0:00 to 0:03, status. Two questions about the on-track item’s date. The stuck item is parked for the problem block. Done in three minutes.
- 0:03 to 0:19, coaching. Opener: “What do you tolerate and thereby invite to get more of?” The answer turns out to be missed design deadlines, which connects straight to the interviewing designer. Sixteen minutes on standards, and one commitment: reset expectations with the design team this week.
- 0:19 to 0:33, one problem. The legal review. Outcome delegated: “pricing page cleared or a documented workaround by Friday the 19th.” The lead owns the conversation with legal. The manager offers one door-opening intro, nothing more.
- 0:33, close. Commitments read back in one breath. Next meeting already on the calendar.
Notice the designer news did not hijack the meeting. It informed the coaching block, and if it needs its own session, it gets booked separately. The agenda held.
Want this as a printable one-on-one meeting agenda template? It ships inside the free 1:1 pack with the meeting template and my full question bank, gated behind name, email, and phone, linked from the template post above.
The One-Problem Rule
The last block solves exactly one problem. Not the top three. Not “whatever comes up.” One.
Here’s the reasoning. A 1:1 that tries to clear a problem list becomes triage, and triage crowds out coaching, and suddenly you’re running the meeting everyone else runs: an hour of you dispensing solutions to a queue. If the week produced five real problems, that’s a working session, booked separately, with the right people in the room.
One problem, treated properly, means you go deep enough to delegate the outcome instead of prescribing steps. What does done look like? Who owns it? By when?
That takes ten to fifteen real minutes. Five problems in fifteen minutes produces five pieces of advice nobody owns.
The discipline also trains your team’s judgment. When your report knows only one problem makes the agenda, they arrive having ranked their problems. That ranking is management skill, practiced weekly, and it’s a skill most managers accidentally do for their people forever.
Delegated Stays Delegated: The Accountability Half of the Agenda
The agenda above only works if the things it delegates stay delegated. This is where most 1:1s spring their leak.
Watch what happens in the follow-up thread. “We should probably check with legal” sounds harmless; it’s a handback. “Where did you land with legal?” asked BY you two days later teaches everyone the outcome quietly returned to your desk.
The words people choose broadcast ownership before any deadline slips. Learning to hear them is a skill I drill relentlessly, because I watched vague language quietly re-staff my own to-do list as a young CEO.
So the close of every one-on-one meeting agenda is a read-back: each commitment, its owner, its date, said out loud in ten seconds. Corny? Maybe. But the read-back is a contract, and contracts survive busy weeks better than vibes.
If work keeps boomeranging back to you no matter how cleanly you delegate it, that’s a system problem, not a willpower problem, and it’s exactly what my delegation training exists to fix.
What This Agenda Leaves Out, on Purpose
Compare this structure to the usual advice and you’ll notice missing sections. That’s not an oversight.
No “personal check-in” block. Not because people don’t matter, but because a scheduled five minutes of forced warmth is neither warm nor useful. Care shows up as attention inside the coaching block and availability between meetings. When I ran my companies I was genuinely reachable same-day for my direct reports, and that did more for the relationship than any icebreaker ever could.
No “career development” section. Career growth isn’t a quarterly agenda item; it’s the entire fifteen-minute coaching block, every meeting. Teams that quarantine development into a twice-a-year conversation are admitting the other fifty meetings don’t build anyone.
No open “manager topics” grab bag. If you have feedback, it goes in the coaching block, tied to the thread you’re building. If you have a directive, send it in writing; announcements don’t need a meeting.
No performance-review talk. Compensation and formal reviews get their own meetings with their own preparation. Let one anxiety-loaded topic into the weekly agenda and every meeting inherits the anxiety.
Every one of these cuts buys minutes back for the two things a 1:1 does that no other meeting can: grow the person, and solve one problem properly.
One-on-One Meeting Format Variations That Keep the Skeleton
The 5/15/15 skeleton flexes. Here’s how the one-on-one meeting format changes without losing its spine:
- The 20-minute biweekly. Status 3, coaching 10, one problem 7. Works once the status email habit is bulletproof. This is the format I coached a drowning leader into, and it’s the one I’d pick for any team above ten reports.
- The weekly first-90-days. New hire or new role: run it weekly at 30 minutes, keep the same blocks, and spend the coaching slot setting expectations early. Your first one-on-one with a new employee sets that pattern in meeting one.
- The C-level 30. With executives I ran biweekly 30s, because our weekly EOS L10 meeting caught tactical issues as a team. If you run EOS or any weekly leadership meeting, your 1:1 agenda gets to stay almost entirely growth.
- The skip-level. Same skeleton, softer coaching block, and the one problem is usually a standards or communication issue their manager can’t see. Keep it quarterly.
What never changes: the manager owns it, status lives in email, coaching gets the biggest block, one problem, read-back at the close.
Run It Twice Before You Judge It
The first meeting on this one-on-one meeting agenda feels abrupt to a team raised on status theater. The second one doesn’t. By the third, your report arrives with a ranked problem and a real answer to a hard question, and you’ll wonder what you used to do with those hours.
Print the structure, book the next 1:1 at 30 minutes, and hold the blocks. The rest of the doctrine, cadence, availability between meetings, what to do with 17 direct reports, is all in my one-on-one meetings guide.
The Agenda Is One Protocol of Four
An agenda controls one meeting. It can’t stop delegated work from crawling back Monday, and it can’t keep execution steady when your quarter catches fire. Those failures live between the meetings.
That’s the job of The 5-Minute Leader: four protocols, each about five minutes to run. The 1:1 Protocol is the agenda you just read. The Delegation Protocol makes handoffs permanent. The Rhythm Protocol keeps the operating cadence alive when everything is on fire.
And the deflection-language checklist this post touched on comes from a bundled tool I’m deliberately not naming. Buyers tell me it permanently changed how they hear their own team.
It costs $47, which is less than the loaded cost of one badly run 1:1, and you’ll run your first protocol the same afternoon.
Get The 5-Minute Leader for $47
Frequently Asked: the One-on-One Meeting Agenda
Who should set the agenda for a one-on-one meeting?
The manager, every time. The report feeds the one-on-one meeting agenda by sending a status email beforehand and nominating a problem, but the manager decides the growth opener, picks the one problem, and holds the timeboxes. Employee-led agendas sound enlightened and reliably drift into venting or status recitation.
What is a good one-on-one meeting agenda for 30 minutes?
Three blocks: up to 5 minutes confirming status that was already emailed, about 15 minutes of coaching opened with one new growth prompt, and about 15 minutes solving exactly one problem to an outcome, an owner, and a date. Close with a ten-second read-back of every commitment made.
Should you cancel the 1:1 if there is nothing to discuss?
No. Nothing to discuss means nothing tactical, and the meeting’s core is coaching, which never runs out of material. Run the growth block and skip the rest if you must, or shorten to 20 minutes. Canceling teaches your report where they rank, and rebuilding that trust costs more than the half hour you saved.
How do you stop a one-on-one turning into a status meeting?
Move status out of the room entirely: your report emails it at least 24 hours ahead, one line per commitment. In the meeting, cap status talk at five minutes for exceptions only, then open coaching with a growth prompt before anyone can drift back to projects. The one-on-one meeting agenda enforces this only if you hold the timeboxes out loud.
What belongs in the pre-meeting email?
Three things: a one-line status for each open commitment (done, on track, or stuck), anything the manager should read before the meeting, and the problem the report would nominate for the problem block. Sent at least 24 hours ahead, on working days, so the manager can actually prepare rather than skim it in the hallway.
Does the same agenda work for a 20-minute one-on-one?
Yes, compressed: roughly 3 minutes of status exceptions, 10 of coaching, and 7 on one problem. The 20-minute biweekly format works once the status email habit is solid, and it scales better than hour-long meetings for managers with large teams. Keep the read-back close even when time is tight.
