How to Run 1:1s That Your Direct Reports Actually Look Forward To

Q: How often should I have 1:1s?

Weekly is the standard for direct reports, and the data backs it up — Gallup finds weekly meaningful conversations correlate most strongly with engagement. Biweekly is acceptable for senior ICs who need less oversight, but beyond two weeks you lose the ability to catch problems early. Never go monthly with a direct report unless you want to be surprised when they resign.

Q: How long should each 1:1 be?

30 minutes weekly is the sweet spot for most direct reports. 45-60 minutes biweekly also works. Shorter than 25 minutes and you don't get past status; longer than an hour weekly and both of you start treating it as a burden. Always end on time — running over teaches your report that you don't respect the container, which means they'll stop respecting it too.

Q: Who sets the agenda — manager or report?

The report should own 70-80% of the agenda. They bring 2-3 topics they want to discuss; you add your items at the end. This inversion is the single biggest differentiator between 1:1s people value and 1:1s people tolerate. Managers who run the agenda end up with status meetings; managers who let reports drive end up with trust.

Q: What if my report says 'nothing to talk about'?

That's almost always a signal that either (a) they don't yet trust the format, (b) they're new and don't know what belongs in a 1:1, or (c) your prior 1:1s have trained them to say this. Try a specific prompt instead: "Tell me about the hardest decision you made this week" or "What's one thing that's slowed you down?" Silence is also fine — 3-4 seconds of pause often produces the most honest answers. Don't fill the void with your own agenda.

Q: Should I take notes during the 1:1?

Yes, but in a shared doc both of you can see — not in your private notebook. Shared notes create accountability on action items, let the report see their own progress over time, and mean you don't waste the first five minutes reconstructing last week. Type lightly or jot afterward; eye contact still matters more than complete transcripts.

Q: Is skipping a 1:1 ever OK?

Rescheduling within the same week is fine and sometimes necessary. Canceling outright is rarely OK. Research consistently finds that unreliable 1:1 time is among the top signals employees cite when they describe disengagement. The rule: if you can't do 30 minutes, do 15. If you can't do 15, walk through it on a call while you commute. Skipping entirely tells your report they're not a priority — and they will believe you.

Q: How do I run 1:1s with remote or hybrid reports?

Keep cameras on, keep the shared doc open on a second tab, and protect the time more zealously than you would in person — the casual hallway contact that compensates for bad 1:1s in an office simply does not exist remotely. See [productive one-on-ones in distributed teams](/guides/team-productivity/productive-one-on-ones) for the full playbook.

Q: When should a 1:1 become a formal performance conversation?

It shouldn't. If you're delivering corrective feedback or doing a performance review, that's a separate meeting with its own agenda. Mixing them poisons the regular 1:1 — your report learns to approach the weekly conversation defensively. Keep the 1:1 for development, blockers, and trust; use dedicated sessions for performance calibration.

Key Facts: The State of 1:1s

Only about 2 in 10 employees strongly agree their manager gives them meaningful feedback weekly, per Gallup's State of the American Workplace — yet those who do are nearly 4x more likely to be engaged.

Harvard Business Review reports that employees whose managers hold regular 1:1s are 3x more engaged than those who don't, and their managers are rated significantly higher on trust and effectiveness.

The ideal cadence most research converges on: weekly, 30 minutes for direct reports — biweekly at 45-60 minutes is acceptable for senior ICs, but gaps longer than two weeks correlate with sharp drops in psychological safety.

In a well-run 1:1, the direct report talks 70-80% of the time. Gallup's manager effectiveness data shows "manager does most of the talking" is one of the top three signals employees cite when describing bad 1:1s.

67% of managers admit they find giving feedback uncomfortable (Harris Poll / Interact), which is why most default 1:1s degrade into status reports — it's the path of least resistance.

Your first 1:1 with a direct report probably went something like this. You asked how things were going. They said fine. You asked about the project. They gave a status update. You had nothing else prepared, so you wrapped up early and spent the rest of the 30 minutes feeling like you'd wasted everyone's time.

Or maybe you filled the silence by talking about your own thoughts on the team's direction. They nodded. You left feeling like it went okay. They left still not sure what you needed from them.

Both of these are common. And both of them are fixable, but only once you understand what a 1:1 is actually supposed to do.

What a 1:1 Is Actually For

The 1:1 is not a status meeting. You can get project updates in Slack or a shared doc. A 1:1 is a trust-building conversation between you and a direct report. It's where they tell you about problems before they become crises. It's where they tell you they're considering leaving before they've already decided. It's where you find out the work is harder than it looks from the outside, or that someone's collaboration issue is affecting the whole team. Gallup's State of the Workplace research finds that employees who have regular meaningful conversations with their manager are significantly more engaged and far less likely to be actively looking for other jobs.

None of that happens if the 1:1 is a status report.

For new managers, 1:1s carry extra weight. You don't have the informal relationship-building that comes from years on the same team. You probably don't bump into your reports at the coffee machine and catch up naturally. The weekly 1:1 is often the only real conversation you have with each person in a given week. That means its quality matters more, not less. If your team is mostly remote or async-first, productive one-on-ones in distributed teams covers the extra structure these conversations need.

The goal is a conversation where your report leaves feeling like you understand them, you're invested in them, and you're useful to them. When that happens consistently, they start showing up prepared and engaged. When it doesn't, they start treating it as a calendar event they can't skip.

The Single Shift That Changes Everything

The Employee-Led 1:1 Agenda

The Employee-Led 1:1 Agenda inverts the default structure where the manager arrives with a checklist of items to cover and the report answers questions. Instead, the direct report comes prepared with 2-3 topics they want to discuss — blockers, decisions, development, team dynamics — and the manager adds their items at the end. The shift matters because ownership of the agenda determines ownership of the conversation, and conversations people own are conversations they invest in.

Let your direct report own the agenda.

This is the single most impactful change you can make. Most managers come into 1:1s with their own list of things to cover. Status check on Project A. Question about the upcoming deadline. Thought about the team meeting. The result is a conversation that feels like a manager's meeting, not a report's meeting.

When your report owns the agenda, they decide what matters. They show up having thought about it in advance. And they feel like the conversation is for them, which is the whole point.

Here's how to set this up. Before the first 1:1, send a note like this:

"I want our weekly 1:1s to actually be useful for you, not just a status check for me. My plan is for you to own the agenda. Each week, I'll ask you to share two or three things you want to cover — updates on what you're working on, things blocking you, anything you need from me, or anything on your mind about the team or your own development. I'll always have a few items I want to add, but your topics come first. Does that work for you?"

Most people will say yes and feel relief. Some will feel surprised. They're used to managers who run the meeting. Give them a week or two to adjust.

The 1:1 Agenda Template

Here's a simple template you can share with your team. Ask them to fill it in before each meeting:

Weekly 1:1 Prep

Updates (2-3 bullets on what you're working on, optional):

Blockers or decisions I need help with:

Something I want to discuss (work, team, development):

One thing that went well this week:

The "one thing that went well" is optional but valuable. It trains people to notice their own wins, which matters for their confidence and for your calibration on the team's health.

You add your own items at the end:

Manager items:

Feedback I want to share
Context from leadership that's relevant to you
Anything I need to know or decide together

Your Opening Question

The first question you ask in a 1:1 matters more than you think. It sets the tone for whether this is a safe conversation or a performance conversation.

Don't open with: "Where are you on the X project?"

Do open with: "What do you need from me this week?"

The first question puts them in report mode. The second puts them in ownership mode. The answers are often completely different.

Other good openers:

"What's on your mind?"
"What's been the hardest part of this week?"
"What's one thing that's going better than you expected?"

None of these are magic. What they do is signal that you're not there to extract status. You're there to help.

Rotate in a Growth Question

Every third or fourth 1:1, add one question about the person's development or career. Not a formal review moment, just a genuine check-in. According to Harvard Business School research on coaching conversations, managers who ask growth-oriented questions in regular check-ins are more than twice as likely to retain high performers beyond two years.

Here are 10 questions you can rotate through over time:

"What kind of work have you been doing lately that you find energizing?"
"Is there a skill you want to build this quarter? How can I help?"
"What's one thing you wish you had more time to work on?"
"What's a stretch project you'd want to take on if the opportunity came up?"
"What's something you'd like to learn about how our team or business works?"
"Is there someone at the company you'd find it useful to spend time with?"
"Where do you feel like you're growing fastest right now?"
"What's a challenge you've faced this month that's taught you something?"
"How do you feel about your workload: too much, too little, or about right?"
"What would make your work feel more meaningful?"

You don't have to remember these. Keep a note in your 1:1 doc and add one whenever it feels right. The goal isn't to have a formal career conversation every week. It's to show that you think about your report's growth in the 51 other weeks of the year too.

For deeper development conversations, read Career Conversations That Don't Feel Scripted.

Keep a Shared Running Doc

Use a shared doc, not just your own notes. Something both you and your report can see and edit.

Why? Because when you have a shared record, it means:

Your report can see their own progress over time
You don't spend the first three minutes recapping last week
Action items from the previous week are visible, which creates accountability
Context carries from week to week, even when things get busy

The format doesn't matter. A Google Doc, a Notion page, a Rework task, whatever your team uses. What matters is that it's shared.

At the bottom of each session's notes, write: "Agreed actions this week." Both of you name what you're doing before the next 1:1. This turns the conversation into commitments.

How Rework Work Ops Handles 1:1 Continuity

The practical problem with 1:1 notes isn't writing them — it's finding them again three weeks later when the same concern resurfaces and you can't remember whether you already promised to fix it. Rework Work Ops (from $6/user/mo) solves this by treating each 1:1 as a recurring workspace per direct report: a shared doc that threads week over week, with action items that auto-carry forward until checked off and a "recurring topics" view that flags when the same blocker has come up three weeks running. Managers can tag discussion items as "development," "blocker," "feedback," or "personal" and filter the history by tag before quarterly reviews — which means the career conversation you have in December is informed by the 40 hours of notes from the year, not by what you can remember in the last two weeks. Action items sync to the report's own task list, so commitments made in the 1:1 don't disappear into a doc nobody re-opens.

Protect the Slot

One of the easiest ways to damage trust as a manager is to repeatedly cancel 1:1s.

I know how it goes. You get pulled into a back-to-back day. The 1:1 is at 4pm and you've run over on everything else. You cancel with a "let's reschedule" that never gets rescheduled. Research on meeting-heavy teams and attrition consistently shows that unreliable 1:1 time is one of the first signals people cite when they disengage. The Center for Creative Leadership's research on manager trust identifies consistency and reliability as the two most foundational trust behaviors, and skipping 1:1s directly undermines both.

Your direct report notices. They conclude that the 1:1, their meeting, isn't actually a priority for you. And then they stop investing in it.

The rule: never cancel. Reschedule if you must, but before the day of the meeting, and to a slot within the same week. If you can't do that, do a shorter version. 15 minutes is better than nothing.

The inverse also applies: show up even when you're not sure you have anything to say. Some of the best 1:1 conversations I've had started with "I don't have much on my list today, so let's just talk. How are you really doing?"

Your First 1:1 Script

If you've never managed anyone before, the first 1:1 can feel awkward. Here's a simple opening:

"Thanks for making the time. I've been in listening mode this week, trying to understand how things work here before I start forming too many opinions. I want to use this first conversation to get to know you and what you're working on. I've got a few questions prepared, but before that — what would be most useful for you to cover today?"

Then listen. Ask follow-ups. Take notes.

If there's silence after a question, don't fill it immediately. Give them 3-4 seconds. A lot of the most honest answers come after the first pause.

At the end of the first 1:1:

"This was really helpful, thank you. My plan is for us to have a regular weekly 1:1. I'll send you a template to fill in before each one so you're driving the agenda. Is there anything you need from me before we talk again?"

Common Mistakes to Avoid

Turning it into a status meeting. If the whole conversation is about project timelines and delivery, your report learns that 1:1 is a place to be inspected, not helped. Keep status to a few minutes. Use the rest for them.

Doing all the talking. New managers sometimes fill 1:1s with context-setting and updates because it feels productive. The 80/20 rule applies here: your report should be talking 80% of the time. If you're talking more, stop and ask a question.

Never asking about career. If the only growth conversations you have happen at performance review time, your team will tell you about their plans when they've already decided. Read Career Conversations That Don't Feel Scripted for how to make these feel natural year-round.

Skipping when things are busy. The weeks when you're most likely to skip 1:1s are the weeks your team most needs to talk to you. Deadlines, reorgs, unclear priorities: these are when 1:1s matter most. Don't trade them for more meetings that don't have names on them.

Making it feel like a performance check. If every 1:1 starts with "how are you tracking against your goals," your report learns to come prepared with a defense. Not a conversation. Lead with curiosity and care, not evaluation. The giving feedback without defensiveness guide covers how to separate performance observations from the regular conversational check-in.

What Good Looks Like

After three months of well-run 1:1s, here's what you should see:

Your reports prepare agendas without you reminding them
Blockers surface before they become crises
You find out about problems in the 1:1, not in a team meeting or via Slack
People bring you things they're uncertain about, not just things they've already figured out
At least some people tell you things that have nothing to do with work, context about their lives that helps you understand why they're having a tough week

None of that happens overnight. It happens because you show up consistently, you listen more than you talk, and you make clear that the meeting is genuinely theirs.

The team meetings are for everyone. The 1:1 is for the individual. Don't confuse them, and don't underestimate how much the individual one matters.

First-Time Manager Playbook