How to have an effective 1 on 1 with your employees
An effective one-on-one is a short, regular meeting that belongs to your employee: same time every week or two, their topics first, yours second, and two minutes at the end to agree what each of you will do before next time. Keep status updates out of it. Spend most of it listening.
That is the whole idea, and it's easy to agree with. The hard part is week three, when they say "nothing much, all good" and the meeting dies in eight minutes, or week six, when you cancel twice for a deadline. Below: a 30-minute shape that holds up, the script for your very first one, questions that get real answers, how to take notes, what to do when it goes quiet or turns into a hard talk, and the mistakes that quietly kill them.
What a one-on-one is for (and what it isn't)
Andy Grove, who ran Intel and wrote High Output Management, called the one-on-one "the subordinate's meeting": the employee sets the agenda and the manager's job is to learn and to help. Kim Scott makes the same point in Radical Candor. That framing answers most questions about what belongs in it.
| Belongs in a 1:1 | Belongs somewhere else |
|---|---|
| What's getting in their way and what they need from you | A line-by-line status update (a shared tracker, standup or a two-line message) |
| How they feel about their work, workload and the team | Decisions that affect the whole team (the team meeting) |
| Small feedback both ways, while it's fresh | Formal discipline or a final warning (a planned meeting, often with HR) |
| Where they want to grow, and the next step toward it | Pay or promotion decisions you can't make yet (say when you'll know) |
| Questions they wouldn't ask in front of others | Anything they'd hear better in writing first, like a policy change |
When a 1:1 turns into a status report, both of you learn what you already knew. The point is the thing you'd never hear otherwise: the colleague who's struggling, the tool that wastes an hour a day, the job offer they're thinking about.
How often and how long?
Google's re:Work guide suggests every week or two, for 30 to 60 minutes, at a consistent time. For a first-time manager with 3 to 12 people, the table below is a workable start. Adjust after a month.
| Team size | How often | How long | Your time a week |
|---|---|---|---|
| 3–5 people | Weekly | 30 minutes | 1.5–2.5 hours |
| 6–8 people | Weekly | 25–30 minutes | 2.5–4 hours |
| 9–12 people | Every two weeks (weekly for anyone new or struggling) | 30–45 minutes | 2.5–4.5 hours |
| Shift teams (retail, nursing) | Every two weeks, booked inside their shift | 15–20 minutes | Varies |
Two rules beat any number. First, pick a rhythm you can keep: a 20-minute meeting that always happens beats a 60-minute one that gets moved three times. Second, meet more often with people who are new, just changed roles or are having a hard time. Grove argued the same: the less experienced someone is at the task in front of them, the more often you should meet.
If your team works shifts, book the 1:1 as paid time inside the shift, not before or after it. Asking someone to stay late to talk to you sends the opposite message from the one you want.
A 30-minute shape that works every week
Manager Tools, a long-running management podcast, popularized a simple split: about 10 minutes for them, 10 for you, 10 for the future. We use a slightly different version for first-time managers, because the first two minutes and the last three are where most 1:1s go wrong.
| Minutes | What happens | What you say |
|---|---|---|
| 0–2 | Arrive on time, put your phone away, a human check-in | "How's your week actually been?" |
| 2–15 | Their topics, in their order | "What's on your list today?" |
| 15–23 | Your topics: one or two at most | "I've got two things. First…" |
| 23–27 | Growth or feedback, rotating each week | "Anything I could do differently that would help you?" |
| 27–30 | Agree actions out loud and write them down | "So you'll send the draft Thursday, I'll ask finance about the budget. Anything else?" |
If they have nothing on their list, don't fill their 13 minutes with yours. Use one of the questions in the next-but-one section. If they run long on something that matters, let your own topics slip to next week or a message. Their part is the part that earns the meeting.
Your first 1:1 with each person: what to say
The first one sets the pattern for every one after it, so it's worth a little script. Book it within your first two weeks as a manager (or their first two weeks on the team), and tell them in the invite what it's for, so it doesn't read as trouble: "Getting to know how you work and what you need. No prep needed."
Open by saying what this meeting is and isn't:
"I want to meet with you every week, same time, for about half an hour. It's your time more than mine. Bring whatever's on your mind: what's in your way, ideas, worries. Status updates can go in the tracker, so we don't spend this on them."
Then ask five questions and mostly listen:
- "What do you like most about your job right now? What would you drop if you could?"
- "What's one thing about how this team works that you'd change?"
- "How do you like to get feedback: in the moment, in here, in writing?"
- "What did a past manager do that really helped you? What drove you up the wall?"
- "Where do you want to be in a year or two? It's fine if you don't know."
Close by naming what happens next and one thing you'll do with what you heard:
"Thanks. I wrote down the bit about the rota changes. I'll look into it and tell you what I find out next week. Same time Tuesday?"
If you used to be their peer, add one honest line near the start, once: "It's a bit strange that I'm now the one booking these. I'd like us to keep talking as straight as we used to." Our guide to first time manager tips covers the rest of that change, week by week. And our sample lesson on your first 1:1 has a full, ready script you can read before you walk in.
Questions that get real answers
"How's it going?" gets "Fine." Specific, slightly unusual questions get more. Rotate through these; don't read them as a list.
About their work
- "What took longer than it should have this week?"
- "What are you waiting on from someone else?"
- "If you had an extra day this week, what would you spend it on?"
- "What's one decision you'd like to make yourself that you currently run past me?"
About how they feel
- "On a scale of 1 to 10, how was your week? What would have made it one point higher?"
- "Is your workload too much, too little or about right? What would you move?"
- "Is there anything on the team that's bothering you that you haven't said?"
About you (asking for feedback)
- "What's one thing I could do differently that would make your job easier?" (Google's re:Work guide suggests a version of this: "Is there anything I should be doing for you that I am not doing?")
- "Was there a moment this week where I made something harder?"
- "What should I stop doing?"
About growth
- "What's a skill you'd like to be known for a year from now?"
- "Which part of my job would you like to try?"
- "What's one small step toward that we could set up this month?"
When you ask for feedback about yourself, the answer the first few times will usually be "No, all good." Keep asking, and when you do get something, thank them and change it visibly. People tell you more once they see it's safe and that it makes a difference.
When they say "nothing to discuss"
Every manager hits this. It usually means one of four things, and each has a different fix.
| What it often means | Sign | Try this |
|---|---|---|
| Things really are fine | Work is on track, they seem relaxed | Go to growth: "Then let's use the time on you. What would you like to get better at?" |
| They don't know what a 1:1 is for | They list tasks, or wait for you to lead | Re-explain once, then give them a shared doc to add topics to during the week |
| They don't trust it yet | New to you, a former peer, or had a bad manager | Go first: share something small you're working on fixing, then ask about one specific thing ("How did the Henley handover feel?") |
| Something's wrong they won't say | Shorter answers than usual, quieter in team meetings | Name what you noticed, without a conclusion: "You seemed quieter this week. Anything going on?" Then wait. |
It's fine to end a 1:1 early now and then. It's not fine for it to end early every week. If it keeps happening, change the format before you cancel the habit: a walk, a coffee, a different time of day.
Notes, a shared doc and following through
Kim Scott recommends a shared 1:1 document; Google's guide suggests both of you add to the agenda in one. A simple version works:
- One doc per person, newest meeting at the top. Both of you can add topics any time during the week.
- Three headings per meeting: Their topics. My topics. Actions (who, what, by when).
- Private notes stay private. If you note something sensitive (a health matter, a complaint about a colleague), keep it out of the shared doc and handle it under your company's rules.
Before each 1:1, spend three minutes rereading last week's actions. The fastest way to make 1:1s feel pointless is to promise to "look into it" and never mention it again. Start each meeting with your actions from last time, done or not: "I said I'd ask about the rota. Finance says not before January. I'll keep pushing."
Giving feedback in a 1:1
Some coaches, Kim Scott among them, say feedback should come in the moment and the 1:1 is for getting feedback, not giving it. In practice, for most new managers the regular 1:1 is the safest place for small corrections: it's private, expected, and doesn't need a scary "can we talk?" message.
Keep it small and specific. One behavior, when it happened, what it caused, what you'd like instead:
"One thing from Monday's handover: you skipped the allergy note for bed 4. The night nurse found it later. Can you read the notes out in full, even when we're rushed?"
Then ask for their side and listen. If the reply is "That's not fair" or a list of reasons, our guide on how to give feedback to an employee who gets defensive has the exact replies to the six most common pushbacks.
Give praise in the 1:1 too, just as specifically: "The way you handled the angry customer on Saturday, staying calm and offering the exchange first, is exactly what I want the new starters to see." Praise that names the action gets repeated. "Great job" doesn't teach anything.
When a 1:1 turns into a hard conversation
Sometimes a routine 1:1 goes somewhere you didn't plan: tears, a resignation, a complaint about a colleague, something about health or home. You don't have to solve it in the room.
- Slow down and listen. Let them finish. Don't jump to fixing or reassuring.
- Say what you heard. "So the schedule changes are making childcare really hard, and you're wondering if you can stay." Getting it back right is often more useful than advice.
- Don't promise what you can't give. "I want to help. I don't know yet what I can change. I'll find out by Friday."
- Know when it's not yours alone. Harassment, discrimination, safety, a medical condition or a request for accommodation usually need HR involved. Tell the person you'll need to bring HR in, rather than promising to keep it secret.
- Follow up on the date you said. Even if the answer is no.
If it's a performance problem that has gone on for weeks, don't try to cover it in the last five minutes of a regular 1:1. Book a separate, planned conversation; our guide to difficult conversations with employees walks through how to prepare and what to say.
Remote and video one-on-ones
- Cameras on if they're comfortable, and yours always on. You lose a lot of the signal without faces.
- Close everything else. They can tell when you're reading email.
- Ask about the work setup: "Is anything about working from home getting in the way?"
- Allow more silence. Video lag makes people talk over each other; pause a beat longer before you speak.
- Use the phone for a walk-and-talk now and then. Some people say more when they aren't looking at a screen.
Mistakes that quietly kill one-on-ones
| Mistake | What it tells them | Instead |
|---|---|---|
| Cancelling for "something urgent" | They're the first thing you drop | Move it, never skip it: offer a new time in the same message |
| Arriving late or looking at your phone | Your time matters more than theirs | Arrive a minute early, phone face down or away |
| Talking more than half the time | It's your meeting, not theirs | Aim for them talking about two-thirds of the time |
| Only booking one when there's a problem | A 1:1 means trouble | Keep the rhythm even in good weeks |
| Running it as a status report | You care about the tasks, not them | Move status to a tracker; ask what's in the way instead |
| Saying "I'll look into it" and never coming back | Raising things is pointless | Open each 1:1 with your actions from last time |
| Saving all feedback for the review | Surprises once a year | Small notes every week or two |
A one-on-one template you can copy
1:1 with [name], [date]
Last time's actions: [me: …, done / not yet] [them: …, done / not yet]
Their topics: (they add during the week)
My topics (max 2):
This week's growth or feedback question:
Actions: who, what, by when
That's it. Anything longer stops getting filled in.
Curious which part of running 1:1s will come easiest to you? The free leadership style quiz takes about 2 minutes and names the conversations your style tends to put off.
Questions about one-on-ones
Who should set the agenda for a 1 on 1?
Mostly the employee. Ask them to bring their topics and cover those first. You add one or two of your own after. Google, Kim Scott and Andy Grove all describe it as the employee's meeting.
Should I cancel a 1 on 1 if we have nothing to talk about?
Not as a habit. Shorten it instead, and use the time on growth or on feedback about you. If they keep having nothing to say, try a different format or ask what would make the meeting more useful to them.
Can I do 1 on 1s every two weeks instead of weekly?
Yes, especially with 9 or more people or with experienced staff. Go weekly with anyone new, newly promoted or having a hard time.
Should 1 on 1s be in person?
In person or on video with cameras on is best, in a private place. Avoid a chat thread: tone gets lost and people say less.
What if my employee cries or gets upset in a 1 on 1?
Pause the topic, not the meeting. Offer a few minutes or to continue tomorrow. Listen first, and bring in HR if it's about harassment, safety, health or an accommodation.
How do I start 1 on 1s with a team that never had them?
Tell the whole team at once, in a team meeting, so nobody thinks they've been singled out: "I'm starting a regular half hour with each of you. It's your time, not a check-up." Then book them all in the same week.
Next: take the free leadership style quiz to see which 1:1 habits fit your style and which will take practice, or browse all our guides for new managers.
Sources
- Google re:Work, "Hold effective 1:1 meetings": https://rework.withgoogle.com/intl/en/guides/hold-effective-one-on-one-meetings
- Andrew S. Grove, High Output Management, Random House, 1983 (Vintage edition 1995), chapter on one-on-ones.
- Kim Scott, Radical Candor, St. Martin's Press, 2017; and Radical Candor, "How to Have Effective 1-on-1 Meetings With Your Direct Reports": https://www.radicalcandor.com/effective-one-on-ones/
- Manager Tools, "One on Ones" (the 10/10/10 format): https://www.manager-tools.com/