How to Run One-on-Ones That Actually Change Outcomes

The Resignation That Shouldn’t Have Been a Surprise

Marcus had been running one-on-ones with his team of six for over a year. Every other week, thirty minutes each, always the same opening: “So, how’s it going?”

The conversations were pleasant. People shared updates. Marcus nodded, offered encouragement, and moved on to his next meeting. He considered himself an approachable manager.

Then his strongest contributor, Priya, resigned. In the exit interview she said something that stuck: “I never felt like Marcus knew what I was working toward. Our one-on-ones were fine. They just never went anywhere.”

Marcus wasn’t a bad manager. He was a busy one running a meeting with no system behind it. And that is one of the most common, most fixable problems in management today.

Why Most One-on-Ones Fail

One-on-ones fail for three reasons, and none of them are about frequency or calendar discipline.

1. They default to status updates. If the only question is “What are you working on?”, you’ve built a reporting meeting, not a development conversation. Status belongs in standups, project tools, or async updates.

2. There is no follow-through between sessions. A one-on-one without notes or next steps is a conversation that evaporates. When nothing carries forward, people stop bringing up things that matter.

3. Managers avoid the hard part. Development means naming gaps, setting expectations, and revisiting commitments. Most managers skip this, not out of laziness, but because they want to be fair and they fear being harsh. The irony is that avoiding clarity is rarely fair. Clarity gives someone a chance to succeed.

The 3-Part One-on-One

A one-on-one that changes outcomes has three segments, run in order, every session. The time split is flexible, but the structure is not.

Part 1: Progress Check (5-10 minutes)

This is not “What are you working on?” This is “What moved forward, and what didn’t?”

The goal is to surface momentum and stalls, not to collect a task list.

Dialogue script (standard):

“Last time we talked, you were focused on [X]. What progress have you made, and where did things slow down?”

Dialogue script (soft, for a newer or less confident report):

“Walk me through where things stand on [X]. I want to understand what’s working and where you might need support.”

Dialogue script (firm, when a commitment was missed):

“We agreed you’d have [X] completed by this week. It’s not there yet. Help me understand what happened, and let’s figure out a realistic next step.”

The key: reference the previous session. If you cannot, your one-on-ones have no connective tissue.

Part 2: Blocker Clearing (5-10 minutes)

This is where you earn your role as a manager. Your job is to remove obstacles your report cannot remove alone.

Dialogue script (standard):

“What’s in your way right now that you need my help with?”

Dialogue script (soft):

“If you could change one thing about how this week is going, what would it be?”

Dialogue script (firm, when you suspect someone is stuck but not saying so):

“I’ve noticed [specific observation]. Is there something blocking you that we haven’t talked about?”

Do not solve every problem in the room. Sometimes the answer is “Let me look into that and get back to you by Thursday.” That is a better answer than improvising a solution that doesn’t hold.

Part 3: Development Thread (10-15 minutes)

This is the part most managers skip entirely, and it is the part that retains people.

A development thread is a recurring conversation about growth: what skills are being built, what the next level looks like, and where the gap is between current performance and that next level.

Here’s what good looks like: every direct report should be able to answer two questions at any time: “What am I being developed toward?” and “What does my manager think I need to work on?”

If your people cannot answer those questions, your one-on-ones are missing their most important function.

Dialogue script (standard):

“Last month you said you wanted to get stronger at [skill]. How has that been going? Where are you noticing growth, and where are you still feeling stuck?”

Dialogue script (firm, when performance needs to shift):

“I want to be direct with you because I think it’s the most respectful thing I can do. Right now, [specific gap]. Here’s what good looks like in this area: [concrete description]. Let’s talk about what support you need to close that gap, and I’d like to check back on this in two weeks.”

Notice the pattern: name the gap, define the standard, agree on a next step, set a date to review. The system is simple. The discipline is in doing it consistently.

Manager Mistakes to Watch For

These are not character flaws. They are habits that form when no one teaches you how to run this meeting.

Doing all the talking. If you are speaking more than 40% of the time, you are running a broadcast, not a conversation. Ask a question, then wait. Silence is not a problem to fill.

Avoiding hard topics. If you have feedback and you save it for a quarterly review instead of raising it in a one-on-one, you have delayed someone’s ability to improve by months. Small, timely, specific feedback is kinder than a delayed performance summary.

Canceling too often. Every cancellation sends a message: this meeting is not important enough to protect. If you need to reschedule, reschedule within the same week. If you cancel more than twice in a row, expect trust to erode. Research on employee engagement consistently shows that the manager relationship is one of the strongest predictors of retention. Canceling the one meeting dedicated to that relationship has real cost.

Using the meeting to assign work. A one-on-one is not a tasking session. If you regularly use this time to hand out assignments, your report will start to dread it. Keep task delegation in other channels.

Skipping notes. If you don’t write down commitments and revisit them next session, nothing compounds. A two-line summary after each meeting (“discussed X, next steps Y, revisit by Z”) is enough.

Reflection Prompt

Before your next one-on-one, ask yourself:

Could each of my direct reports tell me, right now, what I think they should be working on to grow? If not, what have I been using this meeting for?

One-on-One Operating Template

Use this as a repeatable structure. Print it, paste it into your notes app, or build it into whatever tool you already use.

Before the meeting (2 minutes of prep):
– Review notes from the last session. What commitments were made?
– Identify one thing you want to acknowledge (progress, effort, a win).
– Identify one development topic to revisit or introduce.

During the meeting:

Segment	Time	Core Question
Progress Check	5-10 min	“What moved forward since last time, and what stalled?”
Blocker Clearing	5-10 min	“What’s in your way that you need my help with?”
Development Thread	10-15 min	“How is your growth area progressing, and where do you need support?”

After the meeting (2 minutes of follow-up):
– Write 2-3 lines: key discussion points, commitments made, and a date for any follow-up.
– Send a brief recap to your report if commitments were specific (“Just to confirm, you’ll have the draft by Friday and I’ll review over the weekend”).
– Add any action items on your side to your own task list. Do not rely on memory.

Cadence: Weekly is ideal for anyone in their first year on your team or in a new role. Biweekly works for experienced, autonomous contributors, but only if the structure stays intact.

---

Kinetiq’s LEAD module helps managers build systems like this into their weekly rhythm, with guided one-on-one frameworks, follow-through tracking, and development planning tools. If running better one-on-ones is a priority for your management team, it may be worth a look.