How to Run a One-on-One That Actually Works
Most one-on-ones are status meetings in disguise. Thirty minutes on projects, five minutes on "anything else?" and then everyone rushes back to work having exchanged updates and grown nothing. The meeting fills the calendar. It does not move the person.
A one-on-one that works has a shape. It runs on time, holds a rhythm, and creates space for the two things a status meeting cannot. Coaching, and being seen. Here is how to run one.
The short answer
A weekly one-on-one that works has a simple shape. Their agenda first, your agenda second, five minutes on development last. Keep it thirty to forty-five minutes. Do not turn it into a status meeting, do not skip it when you are busy, and do not treat the last five minutes as optional. That is where the development happens.
Want a fast read on your team's accountability? Take the free 3-minute Team Accountability Check for a personalized Accountability Blueprint.
Key takeaways
The one-on-one is their meeting first, yours second.
The agenda is a shape, not a checklist. Same shape, different content, every week.
Save the last five minutes for development. Not the last five if there is time. The last five.
Do not use the one-on-one to deliver hard feedback for the first time. Feedback is delivered close to the event, not stored for the weekly.
Skipping it costs more than most managers think. Cancel other things first.
Why most one-on-ones fail
The failure mode is remarkably consistent. The manager walks in with a mental list of things they need from the direct. They cover their list. Time runs out. The direct's actual questions and the development conversation both get lost. Over a quarter, that pattern teaches the team that the one-on-one is a status meeting, and everyone stops bringing the real stuff to it.
The reframe. The weekly one-on-one is not a status meeting. Status updates should live in async messages, project trackers, or team meetings. The weekly is for the things that need a real conversation. Blocking work, coaching, feedback, and development. When you shove status into it, you push out the actual value.
The shape
Same shape, every week. Same agenda template. Different content.
Their agenda (roughly 15 to 20 minutes). What is on their mind. Projects they need to talk through, decisions they are wrestling with, obstacles they cannot get past on their own. This is the biggest block of time and the first block, on purpose.
Your agenda (roughly 10 to 15 minutes). What is on your mind for them. Not status. Things you want to coach through, questions about their team, longer-term priorities, feedback that requires a conversation.
The last 5 minutes. Development. Not "if there is time." Reliably. This is where you deliver the mirror, name what you see, or ask what they are trying to get better at this month.
The order matters. If you lead with your agenda, you will run out of time before theirs, and eventually they stop bringing it. If you skip the development block, the meeting stays a task meeting.
Their agenda first. What to ask
The first three minutes set the tone for the meeting. A few openers that reliably surface the real stuff.
"What is on your mind this week?"
"What are you stuck on?"
"What is the one conversation you are avoiding?"
"What would you not bring to me if we were not here right now?"
The last one is the sharpest. It gives permission for the thing the direct half-wanted to raise and half-wanted to sit on.
When they bring you something, resist the urge to fix it in the same breath. Run the 3-question coaching sequence. "What have you tried? What are you thinking? What do you need from me?" That sequence turns a status update into a coaching moment without lengthening the meeting.
Your agenda second. What belongs here
The manager's block is where a lot of one-on-ones go sideways. Two rules that keep it from turning into a status audit.
Status is not your agenda. If you want an update, ask for it in the async channel or a project tracker. Status has no place in a one-on-one that only happens weekly.
Feedback close to the event does not wait for the weekly. If something needed feedback on Tuesday, do not save it for Thursday's one-on-one. That is one of the most common failures of the weekly. It becomes a graveyard of delayed feedback.
What does belong in your block.
Longer, thinking-required conversations. Coaching questions. Direction on longer-arc priorities. Pattern-level feedback that needs sit-down time.
Alignment on shared priorities. Are we still working on the same things? Where are the tradeoffs this week?
Concerns that need context. "I have been noticing X across projects. What is your read on it?"
The last five minutes. Development
The single most-skipped section of the weekly one-on-one, and the one that carries the most weight over a year.
Rotate the move.
This week. Deliver the Development Mirror. One sentence. Strength or growth edge. Specific.
Next week. Ask what they are trying to get better at. Then ask what one Rep this week could move them toward it.
Sometimes. Read a specific moment together. "That conversation with the client. Talk me through what you noticed about yourself in it."
The reason this block is protected is that it is the only place in most work relationships where development gets a real airing outside a review cycle. If you save it for reviews, you get reviews. If you save five minutes a week for it, you get developed leaders.
For the full framing on why, see tell them what you see in their development.
What does not belong in a one-on-one
First-time hard feedback. Redirecting feedback is delivered close to the event, in its own moment, not stored for the weekly. See redirecting feedback.
A status update either way. Status is async.
A performance review. Reviews are their own conversation, on their own cadence.
Solving for them. If you catch yourself doing more than half the talking, you are running a fixing meeting, not a one-on-one. See are you coaching or fixing.
Cadence and length
Thirty to forty-five minutes. Weekly is right for most working relationships. Every other week is right for a few senior directs who genuinely do not need weekly time. Monthly is a signal that the person has effectively been removed from active management, whether intentionally or not.
Do not cancel it. If the calendar is tight, shorten it. A twenty-minute one-on-one is more useful than a canceled one, because cancellation reads as unimportance, and it does not take many cancels before the team learns that the weekly is not real.
What to do when your person does not bring anything
Some directs default to "everything is fine" and struggle to fill the first block. Two moves.
Ask a smaller question. "What is one thing that has been on your mind at work that we have not talked about?" Smaller than "how are you," bigger than "any updates."
Ask about a specific project. Not the status. The thinking. "How are you feeling about the Acme scope? What is worrying you about the timeline?" That surfaces the real question underneath the fine.
If that keeps happening for weeks, the meta-move is to name it. "I notice we tend to run through things fast in these. What would make this more useful for you?" Directly asking is often the unlock. See everyday courage.
What to do when your person brings too much
The other failure mode. They arrive with a fifteen-item list and want to grind through all of it. You lose the coaching and development blocks to task triage.
Rank the list. "Which two of these need me to weigh in? Let's start with those."
Batch the small stuff. "Let's park these five for a Slack thread tomorrow."
Protect the last five minutes. Even in a full one-on-one. That block is not negotiable.
Once your direct sees you consistently protect the development block, they start pre-ranking on their own.
Notes and follow-through
The rule of thumb is not to over-tool this. Two lightweight moves.
A shared doc with a running list of topics. Both of you can add to it during the week. Reduces the cost of remembering to raise something.
Two lines at the end. What was decided, and what is next. That is the whole notes practice most one-on-ones need.
The important part is not the tool. It is following through on what you said you would follow through on. See do what you said and close the gap. The trust in the one-on-one is built between the meetings, in whether the manager does what they said they would.
Common mistakes
Turning it into a status meeting. Status is async.
Skipping the last five minutes because time ran out. Protect that block.
Storing feedback for the weekly. Feedback close to the event is stronger.
Canceling when you are busy. Shorten it instead.
Doing more than half the talking. That is a fixing meeting, not a one-on-one.
Same script every week. The shape is stable. The content should not be.
Start with one rep this week
Pick one direct.
Start with their agenda. Not yours. First ten minutes minimum.
Protect the last five minutes for development. Deliver one mirror. Or ask what they are trying to get better at.
Do one thing they asked you to do, before next week. The follow-through is what makes the meeting real.
Frequently asked questions
What is the ideal agenda for a weekly one-on-one?
Their agenda first (about 15 to 20 minutes), your agenda second (10 to 15 minutes), development in the last five minutes. Same shape every week, different content. The order matters. Lead with theirs or you will run out of time for it.
How long should a one-on-one meeting be?
Thirty to forty-five minutes. Longer usually turns into a project meeting. Shorter can work when the calendar is tight, but a twenty-minute one-on-one is more useful than a canceled one.
Should status updates happen in the one-on-one?
No. Status is async. If you use the weekly for updates, you push out the coaching, feedback, and development that only work in a real conversation. Status has other channels. The one-on-one is not one of them.
What questions should I ask in a one-on-one?
"What is on your mind this week?" "What are you stuck on?" "What is the one conversation you are avoiding?" "What would you not bring to me if we were not here?" Any of those is stronger than "how are things going?"
Can I skip a one-on-one if the week is really busy?
Shorten it instead. Skipping teaches the team the meeting is not real. Twenty minutes with the same shape (their agenda, your agenda, development) is better than a cancellation.
For the coaching pillar, see how to coach your team as a manager. For the move that lives in the last five minutes, see the Development Mirror.