One-on-ones That Matter

A one-on-one is a recurring private conversation between you and one person who reports to you. In a small team it usually happens every week or every other wee

Level: First-time lead
Setting: Small team
Core skill: A useful private check-in
Common pitfall: A status-report meeting
Practice to try: A simple 3-question format

What this looks like in real work

A one-on-one is a recurring private conversation between you and one person who reports to you. In a small team it usually happens every week or every other week, for twenty to thirty minutes, in a quiet room or over a call. The purpose is not to review tasks. The purpose is to understand how the work is going for that person, what is getting in their way, and what they need from you. When it works, the conversation feels calm and unhurried. The person talks more than you do. You leave with a clearer picture of the work and the person, and they leave feeling heard and pointed in a useful direction.

In real work, this looks like a short conversation that drifts between the practical and the personal without becoming either a task list or a therapy session. Someone might mention that a handover keeps slipping, then explain that they are unsure who owns the final check. You might hear that a project is fine but the pace is wearing them down. You listen, ask a follow-up or two, and agree on one small thing to try before you next meet. The meeting is not the only place these topics come up, but it is the reliable place where they get air.

For a first-time lead, the shape matters less than the habit. A regular slot that belongs to the person, not to the project, signals that you are paying attention to them as a colleague and not only as a producer of output. That signal is what makes the conversation useful over time.

Why it trips people up

New leads often inherit a calendar full of meetings and assume a one-on-one should look like the others. They open with a project update, walk through tasks, and close with next steps. It feels efficient. It also turns the meeting into a status report, which is the most common way this conversation loses its value. The person learns that the meeting is about the work, not about them, and they start preparing a list instead of bringing a problem.

Another trap is treating the one-on-one as a place to deliver feedback that could have been given sooner. If the only time someone hears something difficult is in this meeting, they begin to dread it. The meeting becomes a courtroom rather than a check-in. Trust erodes, and the person stops volunteering anything that might invite scrutiny.

A third trip is silence. Some new leads worry that if they stop talking, the conversation will stall. So they fill the space with their own updates and opinions. The other person waits for a pause, finds none, and leaves without saying what mattered. The meeting looks fine on the calendar and changes nothing in the work. Over a few weeks, both people quietly decide the time is not worth protecting, and it becomes the first thing cancelled when the week gets busy.

The mistake that quietly hurts

The quiet mistake is letting the one-on-one become a status-report meeting. It does not announce itself. Nobody complains. The meeting happens on time, notes get taken, and tasks move forward. But the information that flows is the same information that already exists in a tracker or a team channel. The conversation adds no new understanding, and the person has no reason to bring anything that is not already resolved.

What gets lost is the early signal. A worry about a deadline, a confusion about who decides, a growing frustration with a process, a quiet wish to try something new. These things rarely appear in a status update because they are not status. They appear when someone feels there is room to say them. If the meeting is only about tasks, that room never opens. By the time the issue surfaces elsewhere, it is usually larger and more expensive to address.

The hurt is also personal. A person who is only ever asked about their tasks begins to feel like a resource rather than a colleague. That feeling is hard to measure and easy to dismiss, but it shapes how much care they bring to the work and how long they stay. The fix is not dramatic. It is a shift in what the meeting is for, and it starts with the questions you ask.

A practice you can repeat

Try a simple three-question format, used in the same order each time. First: what is going well for you right now? Second: what is getting in your way? Third: what would help most from me before we next meet? These three questions cover progress, friction, and support. They are broad enough to fit almost any week and specific enough to produce a real answer.

Use the format as a starting frame, not a script. Ask the first question and wait. If the answer is thin, ask for one example. Move to the second question and listen for the thing behind the thing. A complaint about a tool is often a complaint about unclear ownership. A comment about being busy may hide a worry about priorities. Then ask the third question and take the answer seriously. If the person asks for something you cannot give, say so plainly and offer what you can.

Keep a short note after each conversation: one thing you heard, one thing you agreed to do. Bring that note to the next meeting and open by following up. This closes the loop and shows that the conversation has weight. Over a month, the format becomes familiar, and the person starts arriving with answers already in mind. That is the sign it is working. The questions stay the same; the depth of the answers changes.

What to say and do

Open the meeting by naming its purpose, so nobody has to guess. You might say, "This time is for you, not for the project list. What is on your mind?" That single sentence changes the tone and gives the person permission to bring something that is not a task. If they start with a status update, let them finish, then gently redirect: "Thanks, that is useful. What is the part of that which is hardest for you right now?"

When you hear a problem, resist the urge to solve it immediately. Ask one more question before you offer anything. "What have you already tried?" or "What would good look like here?" These questions keep the ownership with the person and often surface a solution you would not have chosen. When you do commit to something, make it small and specific. "I will check with the other team by Thursday and tell you what I hear." Then do it.

Close by confirming what each of you will do next. "So you will try the new handover note this week, and I will follow up on the access question. Does that match what you need?" This ending turns a good conversation into a shared plan. It also gives you a natural way to open the next meeting, which builds the sense that these conversations accumulate rather than repeat. Keep your own talking short, and let the silence do some of the work.

When the stakes get higher

The same format holds when the work gets harder, but the pace changes. If a project is under pressure, the one-on-one may need to be shorter and more frequent. Do not drop it. A ten-minute check-in during a hard week is worth more than a cancelled thirty-minute meeting. The person needs to know you are still paying attention when everything feels urgent. Keep the three questions, and accept briefer answers.

When something has gone wrong, resist the temptation to turn the meeting into a review of the failure. Separate the two. Deal with the incident in the place where the work lives, and keep the one-on-one as the place where the person can think out loud. You might say, "We will handle the details separately. Right now I want to know how you are seeing it." That distinction protects the meeting and gives the person room to be honest without feeling judged.

If the person is struggling over several weeks, the conversation may need to move from questions to clarity. Be direct about what you are observing and what you need, without turning it into a verdict on their character. "I have noticed the last two handovers were late. What is making that hard?" Then listen. High stakes do not require a different meeting. They require the same meeting, held with more care and more honesty, and with follow-through that the person can count on.

Questions new leaders ask

How often should we meet? For a small team, weekly or every other week works for most people. Choose a rhythm you can keep for months, not a perfect rhythm you will abandon in three weeks. Consistency matters more than frequency. If someone needs more contact for a season, add a short check-in rather than stretching the main one.

What if the person has nothing to say? Silence is information. Wait a little, then ask a narrower question, such as what felt hardest this week. If the pattern continues, ask directly whether the meeting is useful and what would make it better. Sometimes the format needs to change; sometimes the person needs time to trust it. Do not fill the space with your own updates.

Should I take notes? A few lines are enough: one thing you heard, one thing you agreed to do. Notes help you follow up and show the conversation has weight. Avoid turning them into a formal record that makes the person cautious. The point is memory, not documentation. Keep them private and use them to open the next meeting.