The 7 Ways Your 1:1s Are Failing (And What Your Team Won't Tell You)

You have 1:1s on your calendar. They happen most weeks. You talk about projects, deadlines, maybe ask "how's everything going?" at the end.

You think you're doing 1:1s. You're not.

You're having check-in meetings and calling them 1:1s. The distinction matters enormously. A real 1:1 builds trust, surfaces problems before they become crises, and makes your direct reports feel like actual humans instead of task-completion engines. A fake 1:1 burns your employee's time and signals that you don't really care.

After managing hundreds of people and coaching dozens of managers, I've seen the same failure modes over and over again. Here are the seven most common ones, and what to do about each.

Failure Mode 1: The Status Update Trap

This is the big one. The failure mode so common it's practically the default.

It sounds like this: "So where are we on the Q3 launch?" and "Can you walk me through the sprint backlog?" and "What's the status on the client deliverable?"

That's not a 1:1. That's a status meeting for an audience of one. You already have tools for this. Slack, Jira, your project management software, standups, team meetings. If you're using your 1:1 to gather information you could get from a dashboard, you've turned your most valuable management time into the least efficient reporting mechanism imaginable.

Here's the test: if you could replace your 1:1 with an email or a Slack message and lose nothing of value, it's a status update.

The fix: Ban project status from the first 20 minutes. Start with the person, not the work. "What's on your mind?" is a better opening than "What's the update?" every single time.

Failure Mode 2: The Cancellation Pattern

Things get busy. A fire breaks out. An exec needs something. Your calendar is packed. So you cancel the 1:1. It's the easiest meeting to drop because there's no external stakeholder, no deliverable attached to it, no one who will complain.

Except someone will notice. Your direct report notices every single time.

Every canceled 1:1 sends the same message: something else matters more than you do. Cancel it twice in a row and you've told them their career development, their concerns, their relationship with their manager are all less important than whatever landed on your plate that day.

I've seen managers cancel 1:1s three weeks running and then act surprised when the employee puts in their two weeks. They had no idea there was a problem. Of course they didn't. They'd canceled every opportunity to find out.

The fix: Reschedule, don't cancel. Even a 15-minute version is better than nothing. And if you absolutely have to cancel, acknowledge it. Say "I'm sorry I had to move this, it matters to me, let's lock in tomorrow." Those words cost you nothing and they mean everything.

Failure Mode 3: The Manager Monologue

You walk in with your agenda. You have things to cover. You talk for 25 of the 30 minutes. You ask "any questions?" at the end. Your report says "nope, all good." You both leave.

You just held a one-directional broadcast and called it a 1:1.

The 1:1 is the employee's meeting. Not yours. If you're doing most of the talking, you're doing it wrong. Your direct report has context you don't have, problems you can't see, frustrations that are building. But none of that surfaces if you're filling every minute with your own agenda.

The fix: Let the employee set the agenda. Send a simple prompt beforehand: "What do you want to make sure we cover?" Then shut up and listen. Your job in a 1:1 is to ask good questions and actually hear the answers.

Failure Mode 4: The Zero Follow-Through Loop

Your report tells you about a blocker. You say "I'll look into that." Next week arrives. You didn't look into it. They mention it again. You say "right, let me follow up on that." Another week passes. Nothing happens.

After two or three rounds of this, they stop bringing things up. Why would they? The 1:1 has become a place where problems go to die.

This is one of the fastest ways to destroy trust. When someone raises an issue and you commit to action, that's a promise. Breaking it once is forgivable. Breaking it repeatedly tells your team that speaking up is pointless.

The fix: Keep a shared running doc. Write down every action item, who owns it, and when it's due. Start every 1:1 by reviewing last week's items. If you dropped something, own it immediately. "I said I'd do X and I didn't. Here's what happened and here's when I'll have it done."

Failure Mode 5: The "How's Everything Going?" Trap

"How's everything going?"

"Good."

"Great. Anything else?"

"Nope."

"Cool. See you next week."

Congratulations, you just had the most useless meeting of the week. Generic questions get generic answers. If you're not asking specific, thoughtful questions, you're going to get surface-level responses every time.

Your employees aren't going to volunteer that they're frustrated, burning out, or thinking about leaving in response to "how's everything going?" That requires a level of trust and specificity that vague questions will never create.

The fix: Ask specific questions. "What's the most frustrating part of your week right now?" or "Is there anything slowing you down that I could help remove?" or "If you could change one thing about how our team works, what would it be?" Questions with edges get answers with substance.

Failure Mode 6: No Structure At All

Some managers treat the 1:1 like an unstructured hang. No agenda, no notes, no consistent format. Just vibes. "Let's chat" is not a management strategy.

Without structure, 1:1s drift. They become social catch-ups one week, crisis management the next, and awkward silences the week after that. Both people leave feeling like the time wasn't well spent, so eventually one or both of them start finding reasons to skip it.

Structure doesn't mean rigidity. It means having a framework that makes sure important things actually get discussed instead of hoping they come up organically.

The fix: Use a simple repeatable format. Something like: (1) Review action items from last time. (2) Employee's topics. (3) Manager's topics. (4) Career development check-in. (5) Agree on next steps. You don't need to hit every section every week, but having the skeleton ensures nothing important falls through the cracks.

Failure Mode 7: Treating It as Optional

This is the meta-failure, the one that enables all the others. When a manager treats the 1:1 as a nice-to-have instead of a fundamental management practice, everything downstream breaks.

I've heard every version of this. "My team knows my door is always open." "We talk all the time in Slack." "We sit right next to each other, we don't need a formal meeting."

None of that replaces a dedicated, protected, consistent space for real conversation. The hallway chat isn't where someone tells you they're struggling. The Slack thread isn't where they share that they feel passed over for a promotion. Those conversations need a container, and the 1:1 is that container.

The fix: Put 1:1s in the same category as team meetings and sprint reviews: non-negotiable. They happen every week, at the same time, and they are the last meeting you cancel when things get busy. Because if you're too busy for your people, you're too busy to be a manager.

The Compounding Cost

Here's what most managers miss: these failures don't just waste 30 minutes a week. They compound.

A manager running bad 1:1s for a year with a team of six has wasted roughly 300 hours of combined time. But the real cost is what didn't happen in those hours. The problems that didn't surface until they were crises. The feedback that was never given. The career conversations that never happened. The trust that was never built.

And eventually, the resignation letter that blindsided you. The one that, if you'd been running real 1:1s, you would have seen coming months ago.

Good 1:1s are the highest-leverage activity a manager has. Thirty minutes a week, done right, can be the difference between a thriving team and a crumbling one.

Stop checking the box. Start doing the work.