I wrote the first version of this post in 2022. A lot has changed since then: more remote and hybrid teams, more engineering dashboards, and AI that can take your meeting notes. What hasn't changed is that the 1-on-1 is still the most important meeting a tech manager has.
It's also the meeting that goes wrong most quietly. Gallup asked nearly 15,000 employees about their last conversation with their manager, and only 16% called it extremely meaningful. Research by Humu, published in MIT Sloan Management Review, found that 1 in 4 people don't have regular 1-on-1s at all.
Here are the five things I'd focus on if I were setting up 1-on-1s with an engineering team today.

Download full 1-on-1 cheat sheet (PDF)
1. Don't turn it into a status update
Your team already reports status all day. Jira shows where every ticket is. Standups cover yesterday and today. Sprint reviews and demos show what shipped. If your 1-on-1 starts with "So, where are we with the migration?", you're spending 30 minutes of someone's focus time on information you could have read in two.
Use the time for what no tool shows you:
- Growth: what do they want to learn, and where do they want to be in a year?
- Blockers: what is slowing them down that they haven't said out loud in standup?
- Feedback, both ways: what's going well, what should change, and what you could do better as their manager.
- How they're doing: workload, energy, and anything outside work they want to share.
If a status question really can't wait, ask it in Slack before the meeting. That keeps the 1-on-1 free for the conversation.
2. Let your report own the agenda
A 1-on-1 is their meeting, not yours. They bring the topics. You listen and ask questions. Your own points go at the end, if there's time left.
The easiest way to make that work is a shared agenda you both add to during the week. Google's re:Work guide on 1-on-1s recommends exactly that. Nobody walks in cold, and the topics that matter most to your report come first, not whatever you happened to think of on the way in.
During the meeting, talk less than you think you should. Open questions help:
- "What's on your mind this week?"
- "What's the most frustrating part of your work right now?"
- "What would make the next two weeks easier for you?"
- "What should I do more of, or less of?"
- "What else?" Google's guide recommends this one, because the important topic often comes up last.
For a brand-new report, Lara Hogan's "Questions for our first 1:1" is still the best starting list I know. It asks how they like to get feedback, whether they prefer recognition in public or in private, and how you'll know when they're having a bad week.
3. Fixed rhythm, don't cancel
Same slot, weekly or every two weeks. Short on time? Shorten it: 5 minutes still counts.
When a release is on fire, the 1-on-1 is the easiest meeting to drop. "Things are fine, let's skip this week." Do that twice and your report learns that they come second.
The research here is pretty clear:
- Google's Project Oxygen found that its higher-scoring managers were more likely to hold frequent 1-on-1s.
- In the Humu survey, people who met their manager at least weekly felt 20% less anxious about their 1-on-1s, dreaded them 17% less, and felt 12% more successful at their jobs than people who met less often.
- Gallup found that when managers have a meaningful conversation with each direct report every week, employees are four times as likely to be highly engaged. Gallup also says 15 to 30 minutes is enough, as long as it happens often.
So put the 1-on-1 in the calendar as a recurring meeting at the same time every week or every two weeks, and protect that slot. When the week is packed, shorten it instead of cancelling it. Even 5 minutes is worth it as a check-in: it keeps the rhythm, and it tells your report the meeting still matters. If you really have to move it, set the new time right away.
Consistency is what builds psychological safety. People raise the hard things, like a conflict in the team or thinking about leaving, only when they trust the meeting will be there next week too. That's also why it's worth meeting when everything is going well: it's when you get to talk about growth instead of firefighting.
One tip for engineering teams: put the 1-on-1 at the edge of a focus block, for example right after standup or just before lunch, so it doesn't cut someone's afternoon in half.
4. Use metrics to start a conversation, not to judge
Engineering teams have more data than ever: cycle time, PR review time, deployment frequency, shipped work. It's tempting to bring the dashboard into the 1-on-1. Done right, that's useful. Done wrong, it turns the meeting into a performance review.
Treat a number as a question, not an answer. Instead of "Your cycle time went up 40%", try "I noticed your PRs have been open longer lately. What's going on there?" Often the answer has nothing to do with the person. Reviews are slow because two seniors are on vacation. The tickets got bigger. The test suite now takes twenty minutes.
The DORA research team at Google puts it well: software delivery performance is not an individual measure. An engineer's commit pace can be held back by slow code reviews rather than a lack of skill, so managers should look for causes in the system first. That's exactly what a 1-on-1 is good for. It's where you hear about the systemic blockers that never come up in standup.
A few rules I'd stick to:
- Look at trends over several weeks, not one bad sprint.
- Share the data before the meeting, so nobody feels ambushed.
- Pair the numbers with shipped work and PR feedback, so you also talk about what went well.
- Never compare one engineer's numbers with a teammate's.
5. Follow up, every time
Nothing kills trust in 1-on-1s faster than a manager who says "I'll look into it" and never does. If your report raises the same blocker three meetings in a row, they'll stop raising blockers.
So close the loop:
- Take notes during or right after the meeting, somewhere you can both see them.
- Write down action items with an owner, and a due date when it needs one.
- Use the last few minutes to recap what each of you will do before next time.
- Start the next 1-on-1 by going through the open items from the last one.
This isn't bureaucracy. It's the difference between a nice chat and a meeting where things actually change. Atlassian reports that 54% of workers often leave meetings without a clear idea of the next steps. Your 1-on-1 shouldn't be one of them.
Over time, your notes also become a record. When review season or a promotion case comes around, you'll have months of goals, wins and feedback written down, instead of trying to remember what happened in March.
A simple 30-minute agenda

If you want a starting point, this is the structure I'd use:
- Check-in (5 min): how are you doing, really?
- Their topics (15 min): whatever they put on the agenda.
- Open action items (5 min): what got done since last time, and what's stuck.
- Your topics and next steps (5 min): your feedback, then a short recap of who does what.
Want all of this on one page? Download the 1-on-1 cheat sheet for engineering managers (PDF). It has the agenda, the five rules, what to do before, during and after each 1-on-1, and the questions that get people talking.
Wrapping up
Good 1-on-1s aren't complicated. Skip the status update, let your report drive, keep a fixed rhythm, use data to ask better questions, and do what you said you would. Keep that up for a few months and you'll notice the difference: people tell you about problems earlier, and you spend less time guessing what your team needs.
If your team works in Confluence, Meetical creates a private 1-on-1 page from your Google or Outlook calendar event, one for every occurrence, carries open action items over to the next session, and can even write the notes with Meetical AI. Here's how I'd organize those notes in Confluence.
Thanks for reading, and stay meetical!
Sources
- Susan Jacobs, 5 Ways Engineering Leaders Can Hold Impactful One-on-One Meetings, Jellyfish, March 2025
- Harsha Bhat, 9 easy tips for engineering managers to make 1:1s effective, Engg Mgmt! on Medium, January 2023
- Jessica Wisdom, Five Ways to Make Your One-on-One Meetings More Effective, MIT Sloan Management Review, January 2023
- MIT Sloan Management Review, Five Tips for Better One-on-One Meetings (video), January 2024
- Kat Boogaard, 7 tips for better 1-on-1 meetings, Inside Atlassian, July 2025
- Gallup, A Great Manager's Most Important Habit, updated February 2026
- Corey Tatel and Ben Wigert, 42% of Employee Turnover Is Preventable but Often Ignored, Gallup, updated February 2026
- Google re:Work, Hold effective 1:1 meetings, updated March 2026
- Lara Hogan, Questions for our first 1:1, 2016
- DORA, How to empower software delivery teams as a business leader, April 2024


