One-on-one meetings are the single most important management practice available to you. They are where trust is built, problems are surfaced early, feedback is delivered, and development happens. Yet most managers either skip them, run them as status updates, or let them drift into unstructured conversations that produce nothing.
The structure that works
First 5 minutes: Personal check-in
"How are you doing?" asked with genuine interest. This builds the relationship that makes everything else possible.
Next 15 minutes: Their agenda
The one-on-one belongs to the team member. They bring topics: obstacles, ideas, frustrations, requests. Your job is to listen, ask questions, and remove barriers. This is not your meeting — it is theirs.
Next 5 minutes: Your input
Share feedback, context, or information they need. Keep it brief. If you dominate the one-on-one, you are doing it wrong.
Last 5 minutes: Development
"What do you want to learn next?" or "Where do you want to be in a year?" Every one-on-one should include at least one development-focused question.
Common mistakes
Canceling one-on-ones signals your team member is not a priority. Making them status updates wastes everyone's time. Doing all the talking means you learn nothing. Having no follow-up means nothing changes.
Whose meeting it is
The single change that improves most one-on-ones is deciding that the meeting belongs to the person being managed. If it is your meeting, it becomes a status update, and status updates can be handled asynchronously by anyone with a shared document.
That means they set the agenda, they bring what they want to discuss, and you resist the urge to fill the time with your own list. It will feel inefficient at first, particularly if the early ones are quiet. Quiet early one-on-ones usually mean the person has not yet believed that the format is real.
Cadence and length
Weekly for thirty minutes generally beats fortnightly for an hour, because the value comes from things being raised close to when they happen rather than from having a long conversation.
Cancelling is the most damaging thing you can do to the format, and it is the easiest thing to do when the week is compressed. A repeatedly cancelled one-on-one communicates a priority ranking more clearly than anything you say about valuing your team. Moving it is fine; dropping it is not.
What actually belongs in the conversation
Useful territory includes obstacles you can remove, decisions they are weighing, feedback in both directions, and career direction — not every week, but often enough that it is not a strange topic when it arises.
What does not belong is a walk through the project list. If that is consuming the meeting, the underlying issue is usually that project status is not visible anywhere else, which is a systems problem being solved with a person's time.
Questions that produce more than “fine”
“How's it going?” reliably produces nothing, because it asks for a summary and summaries are safe. More specific questions work better: what took longer than it should have this week, what decision are you sitting on, what would you do differently if it were entirely your call, what am I doing that makes your job harder.
That last one takes several attempts before it gets an honest answer, and the answer is usually worth the wait. Related: difficult conversations and creating accountability.