The 1:1 Is Not a Status Meeting

May 17, 2026

The 1:1 Is Not a Status Meeting

If I could go back and give myself one piece of advice when I first became an engineering manager, it would be this: stop running the 1:1. I’ve had managers who turned every 1:1 into a status update — asking where things stood, checking off tickets, moving on. I swore I’d never do that. And I didn’t. But I made a different mistake: I still ran the meeting. I came in with my own agenda, my own questions, my own topics. I thought that was the right move. It wasn’t. My agenda wasn’t project status — it was how are you feeling, what wins have you had, what are your goals this year. The heart was there. But the 1:1 should be driven by your team member first, not by you.

The 1:1 is one of the most powerful tools a manager has — and can easily be misused. Done well, it builds trust, develops your people, and surfaces problems before they become crises. Done poorly, it becomes a boring routine that neither of you looks forward to. Here’s what I’ve learned about doing it well.

Radical Candor

The 1:1 is where you practice being honest. Not performatively honest, not “let me sandwich this feedback between two compliments” honest — actually, genuinely, sometimes-uncomfortably honest. Kim Scott calls this Radical Candor: you care personally about the person while challenging them directly. Both things at once.

You might be tempted to be too nice in 1:1s. We want people to feel good, so we soften feedback until it loses all meaning. The engineer hears “you’re doing great, maybe just be a little more proactive on communication” when what you really meant was “your teammates don’t know what you’re working on and it’s starting to affect the team.” Those are very different messages, and only one of them actually helps.

Being radically candid doesn’t mean being harsh. It means trusting your engineer enough to tell them the truth. If they’re struggling with a skill gap, say so. If a project is at risk because of how they’re handling it, say so. If they’re on a trajectory that’s going to limit their career, they deserve to know — from you, not in a performance review six months later.

The 1:1 is the right place for this because it’s private, recurring, and built on a relationship. Use it.

Relationship, Not Status Update

I cannot stress this enough: do not use your 1:1 to get project status updates. That’s what standups are for. That’s what Tracking Tools are for. That’s what Teams is for. If you’re spending half your 1:1 asking “so where are things at with that API refactor?”, you are wasting the most valuable time you have with that person.

The 1:1 is about the human in front of you, not their tickets. What’s worrying them right now? How are they feeling about the team? Is there something going on outside of work that’s affecting them? Are they bored? Burned out? Excited about something they haven’t had a chance to tell you? Are they thinking about leaving?

I try to ask questions at the start of every 1:1 that have nothing to do with deliverables. “What’s been the best part of your week?” or “Is there anything you’re stuck on that I can help clear?” are great openers. Sometimes the answers are surface-level. But sometimes that’s when someone says “honestly, I’ve been really frustrated with how decisions are being made on this team” — and now you have something real to work with.

Status updates create the illusion of connection without the reality of it. Build the actual relationship.

Coaching, Not Answering

Here’s a trap I still fall into constantly: someone comes to a 1:1 with a problem, and I immediately tell them what to do. It feels productive and helpful. They get an answer, I feel useful, we move on. The problem is that I just trained someone to bring problems to me instead of solving them.

Your job in a 1:1 is not to be the answer machine. It’s to help people become better problem-solvers. That means asking questions instead of giving solutions. “What have you already tried?” “What do you think the right call is here?” “What’s holding you back from making that decision?” These feel slower in the moment. Over time, they are dramatically faster — because your engineers start solving things without you, and that’s exactly the goal.

This is the difference between a manager whose team falls apart when they’re on vacation and one whose team doesn’t even notice. One manager built dependency. The other built capability.

Coaching requires discipline. When someone asks what they should do, your instinct is to tell them. Resist it. Ask what they think first. Nine times out of ten, they already know the answer — they just needed someone to ask the question and listen. Your job is to be that person, not to be a walking FAQ.

The occasional direct answer is fine, especially for genuinely novel situations. But make coaching your default mode, not the exception.

Split-Track and Playback

When your team member starts talking, they’re rarely saying just one thing. There are almost always multiple “tracks” running at once — frustration with a teammate, anxiety about a deadline, uncertainty about their own skills, excitement about something new. Your job as a coach is to hear all of those tracks, not just the loudest one.

Split-tracking means listening to what’s being said and pulling it apart: “I’m hearing that you’re frustrated with the timeline, and also that you’re not sure you have the support you need. Which of those feels most important to dig into?” That second part — reflecting back what you heard, in their words, not yours — is the playback. It tells the person they were actually heard, and it helps them figure out what they most need to work through.

Once you’ve identified a track to focus on, the SOON framework keeps the conversation productive without letting you take over it:

• S – Situation: What’s actually going on? Help them paint the full picture.
• O – Obstacle: What’s getting in the way? What’s making this hard?
• O – Options: What could they do? What have they already tried? What would they do with no constraints?
• N – Next Steps: What are they committing to? By when?

The goal of SOON isn’t to reach your answer — it’s to help them reach their answer. The questions you ask matter more than the advice you give. Most of the time, they already know what to do. They just need someone to create the space for them to get there.

Practice with AI

If you’ve never tried split-tracking and SOON before, AI is a pretty good sparring partner. Try this sequence with ChatGPT or any similar tool:

“Can you provide me a split-track and playback exercise with a statement from a fictional team member?”

“What are the tracks?”

“How should I play them back?”

“Now apply SOON — but I’m the manager asking questions, and the team member should come up with their own solutions.”

Practicing in low-stakes simulations builds the muscle memory you need for the real conversations. You’ll start to hear tracks naturally, and the instinct to just give answers will get quieter.

Tracking Performance — When and How

There’s a version of performance management that treats every mistake as a data point. Someone misses a deadline once, and suddenly that person hears about it seven times as if they have never done anything right. OR they hear nothing about it… until performance review and that one miss among countless success is a smudge on their official record. That’s not management. That’s ambush.

Bring up performance concerns in a 1:1, with Radical Candor, only when you’ve identified a negative trend — not a single stumble, but a pattern. One bad sprint isn’t a trend. One rough week isn’t a trend. Be patient enough to distinguish between noise and signal before you make it a conversation. Personally, I don’t want my team to fear mistakes — they happen. The goal is to not repeat them, not to never make them. Fearing mistakes leads to not trying.

When you do raise a performance issue in a 1:1, get curious before you get critical. Ask what’s going on. Ask how they’re feeling. In my experience, performance dips are caused by something happening in someone’s life — a hard season, a health issue, something at home, stress they haven’t been able to name yet. Odds are your team member needs your support, not a warning. Your high performer doesn’t become a poor performer for no reason. Something must be going on that they haven’t surfaced yet.

That doesn’t mean you avoid the conversation. It means you lead with empathy before you lead with feedback. Something like “I’ve noticed you seem a bit off over the last few weeks — is everything okay? Is there anything you want to talk about?” opens a door that a direct performance comment might close permanently. Today they might not say anything that is material, but that is ok. That little check on them not their work may be the course corrector. If its not, monitor more closely, and be prepared for direct feedback in your following 1:1.

Once you understand the context, work together on busting the slump. Using SOON, what would help them regain momentum? Is there something to take off their plate? Is there a project that would re-energize them? Do they need a win? Sometimes people just need someone to notice they’re struggling and ask. That alone can shift things.

Performance management done well looks a lot like coaching. It’s not a judgment — it’s a conversation.

Put It Into Practice

If you’re a manager, start simple. Block off five minutes before each 1:1 to review your notes from last time. Commit to not asking a single status question in your next three 1:1s. Pick one engineer and practice asking questions instead of giving answers for a full month. See what happens.

The 1:1 is a skill, and like any skill, it takes repetition to get right. But the managers who get this right are the ones whose engineers trust them, grow faster, and stick around. That’s not an accident. It’s a practice.