More Than a Status Update: How to Run 1:1s That Develop Your Team

When clients describe their 1:1s to me, I tend to hear a version of the same thing: they're fine, but I'm not really sure what they're for. Most of the time, they are spent on status updates and running through a to-do list. Rarely are they spent talking about career development, blockers or what could be going differently. Nothing actually moved, not the work in a meaningful way and definitely not the person.

That's the problem with status-only 1:1s. When the whole meeting is "here's where things stand," there's no feedback going in either direction. You're not learning what it's actually like to work on your team, and your report isn't getting anything they couldn't have put in a Slack or Teams message. Over time, the hours you spend with your report don't result in growth or development.

There's probably no need to completely revamp how 1:1s are run, but rather make some small shifts to make better use of the time in an effort to develop your team, free up some of your time, and enable the team to move forward in a way that means you can focus on higher level, more strategic initiatives.

It's their meeting, not yours

Here's the shift I highlight the most with my clients: the report should drive the agenda.

That tends to land as a surprise, because the instinct for a lot of managers is to come in with their own list: the things they need an update on, the things they want chased down. While sometimes this is necessary, it's not always the best use of face-to-face time. When the manager owns the agenda, the meeting becomes about their priorities, and your report learns to show up and wait to be asked rather than taking ownership.

When it's their meeting, something different happens. They have to think about what they actually need from you. They bring the thing they're stuck on, the decision they're sitting on, the bit of feedback they've been wanting. They start treating the time as theirs to use well, which is exactly the muscle you want them building.

This doesn't mean you go quiet. It means your job changes.

Your job is accountability, not rescue

If the report drives, what's left for the manager? Two things, mostly.

The first is accountability. It's your job to hold your report to the progress they've committed to — on their projects and on their own development — and to keep returning to it. Not to hover, and not to do it for them. Just to make sure the things that were meant to move are actually moving, and to name it clearly when they're not.

The second is support, but on their terms. You're there when they're stuck. The caveat is that it's their job to ask. If you jump in and rescue every time you sense there's a problem, you've taught your report that getting stuck is your cue to take the work back. That's the opposite of what you want. The more useful posture is: I'm here, I'm paying attention, and I trust you to flag it when you need me.

This is one of the harder shifts in moving from doing the work to leading it, staying close enough to hold the standard without pulling the work back onto your own desk. It's exactly the tension I dig into in The Doer to Leader Identity Shift workbook, because for most people it's the difference between a team that grows and a team that just keeps handing things back to you.

Who owns the follow-up

The same logic decides the follow-up.

If anything needs writing down after the meeting, the recap, the takeaways, the who's-doing-what, that's the report's to send. Not because you're offloading admin, but because the act of capturing it is part of the ownership. They were the one paying attention. They know what they committed to. Writing it down is how it becomes real.

Your part is to hold them to it. Next time, you pick up the thread: last time you said you'd do X, where does that stand? That single habit does more for accountability than any tool, and it tells your report that what gets said in these meetings actually counts.

Make room for development

Here's the practical bit. Even with the agenda in the right hands, if every 1:1 is focused on tasks and projects, development is always the thing that gets deprioritised.

So protect it. If your regular 1:1s tend to default to status, set aside at least one a month that's only about development — growth, skills, where they want to go next, the feedback you've both been meaning to give. Some people do this quarterly. The right cadence depends on how often you meet and how the rest of your 1:1s are being used. The point isn't the exact number. It's that development gets its own dedicated space instead of being an afterthought at the end of a status call.

When they show up empty-handed

"Drive your own agenda" is easy to say. Plenty of reports, especially earlier in their careers, will show up with nothing, or with a thin list of updates, and look to you to fill the silence.

Don't fill it with more status questions. Here are ways to drive the conversation instead:

What's going well? What's not going well? What would you want done differently?

These questions are meant to be open-ended and left for interpretation. That's a default agenda you can hand someone until they build the habit of bringing their own. It opens room for feedback in both directions, it surfaces the things that never show up in a project tracker, and it makes clear that this meeting is for more than reporting progress.

A quick caveat, though. None of this is permission to check out as a manager. "It's their meeting" isn't a way to do less, it's a way to do the harder, more useful thing. You still prepare. You still follow through. You still say the direct thing when progress has stalled. Handing over the agenda raises the bar on you; it doesn't lower it.

Because a good 1:1 was never really about the update, it's the most regular, most personal hour you get with the people you're responsible for growing. The managers who use it well aren't the ones with the best templates, they're the ones who treat it as their report's time to get better and then hold them to actually doing it.

Working with Base Pace Coaching

Running 1:1s like this — handing over the agenda, holding the line on accountability, resisting the urge to rescue — is simpler to describe than it is to do, especially when you're busy and it feels faster to just take the work back yourself or go through the status update. If you're in the middle of that shift from doing the work to leading it, The Doer to Leader Identity Shift workbook walks through the three practices that tend to be the hardest: delegating, holding people accountable without hovering, and getting out of the weeds. And if you'd rather work through it with someone alongside you, that's exactly what coaching at Base Pace is for. Book a free consultation and let's talk about the leader you're growing into.