The 1:1 That Actually Works

I used to run terrible 1:1s. Not because I didn't care. I did. But I had no structure for them. I'd open the meeting, ask how things were going, get a summary of whatever was on my report's plate that week, nod along, maybe flag one thing I needed from them, and we'd both leave 25 minutes later feeling vaguely okay about the interaction. But nothing had actually happened. No trust built. No growth conversation. No real honesty.

I was running what I now call a "check-in disguised as a 1:1." It happened every week, took up 30 minutes on both our calendars, and produced almost nothing that couldn't have been handled in a two-sentence Slack message.

The moment I understood this clearly came from a direct report named Keisha. About four months into our working relationship, she said something I've thought about ever since: "I like our check-ins, but I don't know what they're for." She wasn't being critical. She was being accurate. I didn't know what they were for either. We were both showing up to a container with no purpose, and we'd both made peace with it.

I tried fixing it by adding more agenda items. That made it worse. The 1:1 became a longer status meeting. I tried doing fewer of them, biweekly, to make each one feel more "special." That just meant problems sat longer. It took me another two months to understand that the issue wasn't the frequency or the agenda length. It was that I'd made the 1:1 about information transfer instead of relationship.

Here's what I've learned since then: a 1:1 either has a purpose and a structure, or it slowly becomes a status meeting. There's no neutral ground. And once it becomes a status meeting, you've lost the only dedicated time you have to build a real relationship with each person on your team.

What a 1:1 is actually for

The purpose of a 1:1 is not status. Status has a hundred other channels: project boards, Slack threads, team standups. If you're using your 1:1 to get project updates, you're wasting both people's time and quietly signaling that your meetings are about what you need, not what your report needs.

The real purpose of a 1:1 is to have a conversation that can't happen anywhere else. It's where someone can tell you they're overwhelmed without announcing it to the team. It's where you can give targeted feedback without making it a performance. It's where growth happens, slowly over dozens of conversations, because someone feels safe enough to say what's actually going on. You cannot build that in a group setting. You build it in this 30 minutes, every single week.

Daniel Coyle writes in The Culture Code about "belonging cues," the small signals that tell people they're safe and seen. The 1:1 is the single highest-density belonging cue a manager has access to. Done well, it says: you matter enough for undivided attention, every week, without fail.

The four-part agenda that works

I run every 1:1 with the same four sections. Not because I'm rigid, but because consistency creates safety. When someone knows what to expect from a meeting, they can prepare for it. They come in with things on their mind instead of having to improvise on the spot.

Here's the structure I use:

1. Personal check-in (5 minutes). Not "how are you" in passing. An actual pause. "How are you doing this week, genuinely?" Some people need this. Some will wave it off. But the fact that you ask, every week without skipping, tells them you see them as a person, not just a function. Over time, this is where you learn that someone's going through something hard, or burned out, or more energized than usual. You can't manage well without that information.

2. Their agenda (15 minutes). This is the most important section, and it should come second, not last. Ask: "What's on your mind? What do you want to make sure we cover today?" Then stop talking. The instinct to fill silence is strong. Resist it. What surfaces in this space, after a few seconds of quiet, is almost always more important than whatever you were planning to bring up. This is where you hear about the thing that's been frustrating them for two weeks, the decision they're not sure about, the dynamic with a colleague that's been sitting unresolved.

3. Your agenda (5 minutes). Now it's your turn. Keep it focused. One or two things you genuinely need from them. Not a status check, but a real ask, a piece of feedback, or context you want to share. If you've been doing this right, most of what you needed to cover probably got covered in their agenda. That's a good sign.

4. Growth (5 minutes). Not every week needs a deep career conversation. But every few weeks, I ask something forward-looking: "What do you want to be getting better at?" or "Is there something you're not learning right now that you wish you were?" or "How do you want your role to look different in six months?" These conversations compound. One of them, every month or so, is how you stop people from quietly disengaging while appearing fine.

"The best question I ever added to my 1:1 agenda: 'What's one thing I could do differently as your manager?' The first time I asked it, three people had an answer ready. They'd been waiting for permission to say it."

The questions that actually open things up

Most managers ask questions that invite short answers. "How's the project going?" gives you a status update. "Anything blocking you?" gets a yes or no. These questions feel efficient. They produce very little of value.

The questions that surface real information are the ones that require reflection. I rotate through these depending on what feels relevant:

• "What's the most frustrating part of your work right now?"
• "Is there anything you feel like you're not getting enough support on?"
• "What's something you wish I knew about but might not?"
• "If you could change one thing about how we work as a team, what would it be?"
• "What's one thing I could do differently as your manager?"

You don't ask all of these every week. You pick one, ask it, and then give it real space. The goal isn't to collect answers. It's to have the kind of conversation where someone actually says something honest. When that happens, resist the urge to immediately fix or explain. Just say: "Thanks for telling me that. I want to think about it before I respond." That single sentence does more for psychological safety than most managers realize.

Try this week: At the start of your next 1:1, ask each person: "What do you actually want to get out of our 1:1s? What would make them more useful for you?" You might be surprised how many people have never been asked. Some have had a clear answer for months.

Why consistency beats perfection

I've had great 1:1s and I've had flat ones. Some weeks there's not much to say. Sometimes the conversation goes somewhere unexpected and runs long. Sometimes you ask a growth question and get a shrug. That's all fine.

Gallup's research on employee engagement consistently finds that the manager accounts for at least 70% of the variance in team engagement scores. Not company culture, not comp, not the work itself. The manager. And the single most consistent behavior of high-engagement managers isn't some sophisticated technique. It's showing up. The same meeting, same time, every week.

What matters far more than any individual 1:1 is whether they happen. Consistently. When your team knows the meeting will happen, not sometimes or only when things are calm, but every week regardless, they start treating it differently. They save things for it. They think about what they want to bring up. The 1:1 becomes a container, and they start to trust it.

"Frequency matters more than perfection. A flat 1:1 that happened is worth more than a brilliant one you keep postponing."

Common mistake: Skipping 1:1s when things get busy. I understand the impulse. You're underwater, the meeting feels optional, you can catch up later. But the weeks when you're most overwhelmed are exactly the weeks your team most needs the check-in. They're probably just as underwater, and the cancelled 1:1 is the signal that says "we don't have time for each other right now." That signal compounds.

Actually use your notes

The single easiest way to make your 1:1s feel meaningful is to reference the last one. Open the meeting and say: "Last week you mentioned you were worried about the rollout timeline. How did that land?" or "You said you wanted to take a bigger role in client calls. Did you get a chance to do that?"

This tells people something simple and powerful: I was paying attention. You matter enough that I wrote it down and came back to it. Most managers don't do this. The ones who do build a different kind of loyalty. Not because they're particularly brilliant, but because they consistently treat conversations as something worth remembering.

You don't need a perfect notes system. A Google Doc per person, a Notion page, a section in Cadence. Whatever you'll actually open before the next meeting. The tool is not the point. The habit is.

"The manager who shows up every week, listens well, and remembers what was said, that's the manager people don't leave. Not because the job is great, but because they feel genuinely seen."

I built Cadence partly because I kept losing this. My 1:1 notes were scattered across five different places, I had no easy way to see patterns across conversations, and prep before each meeting took longer than it should. I wanted a system where the rhythm was easy enough to sustain without thinking about it. If you're managing a team right now, start there: pick a system, any system, and commit to it for 90 days. See what changes.

Want 1:1s that actually work?

Cadence gives you structured 1:1 templates, a place to track notes and follow-ups, and the weekly rhythm to make it stick. 14-day free trial.