A supervisor sits down with a team member for a scheduled one-on-one. They jump right in. Where are we on the project? Did the customer ever respond? What’s holding up the report? Can we get this finished by Friday?

Twenty minutes later, they’ve covered a lot of ground. The supervisor knows what’s happening, and the team member knows what needs to happen next. It may have been a perfectly good status meeting. But it wasn’t much of a one-on-one.

There are plenty of opportunities to talk about the work. Project meetings, emails, Teams messages, production reports, hallway conversations, and dozens of small interactions fill a normal week. A one-on-one creates something rarer: dedicated space to understand the team member’s experience of the work.

Where are they getting stuck? What are they seeing that you’re not? What’s creating unnecessary friction? Where are expectations unclear? What are they learning? What decision are they hesitant to make? What could they handle themselves if you resisted the temptation to solve it for them?

That distinction changes the conversation. A status meeting focuses on the work. A one-on-one focuses on the conditions under which the work gets done.

No one knows more about how the system really works than the people who work inside it every day. Leaders see the system from a different vantage point. Team members live inside it every day. They know where it supports good work and where it gets in the way. They know which handoffs create confusion, where an approval slows everything down, which process adds unnecessary work, and where people have quietly created workarounds just to get the job done.

That knowledge matters because improving the system is leadership work. Leaders are responsible for understanding what helps the team perform, what gets in its way, and what needs to change.

One-on-ones give supervisors a recurring opportunity to learn what the people closest to the work know about the system. They surface friction, weak points, and workarounds that may never appear in a report but can affect the entire team.

The team member knows where the friction lives. The supervisor is responsible for making sure that knowledge leads somewhere.

That makes the exchange bigger than a project update. The supervisor learns what needs attention. The team member gets an opportunity to think, gain clarity, exercise judgment, and take greater ownership.

The deadline and the current project still matter. They are part of the conversation, but they are not its purpose.

Urgent work will always find its way into the room. The longer-term work of developing people and improving the system rarely arrives with the same urgency. A good one-on-one protects space for it.

A Different Conversation

The most useful one-on-ones begin with what matters to the team member, not with the supervisor’s need for updates. The supervisor becomes a partner in understanding what’s happening, thinking through what matters, and helping the team member move forward.

The supervisor’s role is simple: Listen. Ask. Clarify. Coach. Remove friction. Align.

Listen for more than an update. Listen for what might otherwise remain buried beneath the day’s tasks: uncertainty, hesitation, an idea that hasn’t quite surfaced. Ask open-ended questions that help the team member think. “What’s getting in your way?” “What are you seeing that I may be missing?” “Where do you feel least clear right now?”

Clarify what matters. Work gets harder when two people leave the same conversation with different understandings of what was decided. Use the one-on-one to make expectations, decisions, and next steps clear.

Coach without taking over. This is where a supervisor’s instinct to help can easily become an obstacle to development. Someone brings you a problem, and you know the answer. Giving it to them would be faster, but speed isn’t always development. Sometimes the better question is, “What do you think we should do?” When the supervisor routinely takes the thinking back, the team member loses opportunities to exercise judgment and build confidence in their own decisions.

Remove friction when the obstacle is outside the team member’s control. Sometimes the supervisor has access, authority, or influence the team member doesn’t. Use it to improve the conditions around the work without taking the work away from the person responsible for it.

Finally, align around what comes next. Make sure you both understand what was decided and who owns the next step. The goal isn’t to leave with a longer task list. It’s to leave with greater clarity about the work ahead and greater ownership of it.

What Does This Team Member Need From This Conversation?

There’s a simple question a supervisor can carry into every one-on-one: “What does this team member need from this conversation?” It is not a question to ask aloud. It is a frame for the supervisor to hold in mind as the conversation unfolds.

They may need clarity. They may need to think through a difficult decision or get past an obstacle. They may need you to listen long enough for them to discover that they already know what to do. They may see something in the system that you need to understand. Sometimes they simply need twenty uninterrupted minutes with a supervisor who’s genuinely paying attention.

The work will still get discussed. It should. But the work gives you something to learn from, not merely something to check on. Through it, the supervisor learns more about the system, and the team member develops greater clarity, judgment, and ownership.

A good one-on-one educates the leader and develops the team member.

By Frank Bennett, Executive Director of The Leadership Center, a 501(c)(3) nonprofit organization that provides professional development and training solutions in West Kentucky. Learn more at www.LeadershipCenter.training