How often should you have 1:1 meetings?

Weekly for new hires, people in transition, or new managers. Bi-weekly for senior engineers who are self-directed and on stable teams. Never monthly: too much drift between sessions causes small issues to become big ones before the next meeting.

What should a 1:1 meeting agenda include?

Four sections: a brief personal check-in (5 min), the report's agenda with their topics and blockers (15 min), the manager's agenda with feedback and context (5 min), and explicit action items with owners and deadlines (5 min). The report's section comes first and is the largest.

What questions should managers ask in 1:1s?

Rotate 2-3 questions per session across five categories: career growth, work satisfaction, blockers and support, team dynamics, and feedback for the manager. The most valuable questions are the uncomfortable ones, like "What is one thing I should stop doing?" and "Is there anything you have wanted to tell me but haven't?"

1 on 1 Meeting Template for Engineering Managers

Key Takeaways

✓Most 1:1s fail because they turn into status updates or have no structure at all. A lightweight template fixes both.
✓The report owns the agenda. If you run out of time, cut your section, not theirs.
✓Pick 2-3 questions per session from a rotating list. Asking all 25 in one sitting is an interrogation, not a 1:1.
✓Weekly 1:1s for new hires and people in transition. Bi-weekly for senior engineers who are self-directed. Never monthly.

Every engineering manager runs 1:1s. Most run them badly. Not because they don't care, but because nobody taught them how. You get promoted, you inherit a calendar full of one on one meetings, and you wing it for years.

The result is predictable: half your 1:1s become awkward status updates where your report reads their Jira board out loud, and the other half are unstructured conversations that drift nowhere. Both waste time. Both miss the point.

A one on one meeting template won't make you a great manager. But it will stop you from being a bad one. Here's the only template you need.

Why most 1 on 1 meetings fail

There are two failure modes for 1:1s, and most engineering managers hit one of them.

Failure mode 1: the status update. The manager asks "What are you working on?" and the report recites their task list. This is a waste of 30 minutes. You can read a Jira board. You can check the PR queue. Status is available async, so you don't need a synchronous meeting for it. If your 1:1 feels like a standup for two people, something is wrong.

Failure mode 2: the blank page. No agenda, no structure, no preparation. The meeting starts with "So... how's it going?" and ends 25 minutes later with neither person sure what was accomplished. These meetings feel nice but produce nothing. Over time, both sides start canceling them because they feel optional.

The fix is the same for both: a lightweight template that creates space for what actually matters. Blockers, growth, feedback, and the things your report won't bring up unless you ask.

Managers account for 70% of the variance in employee engagement scores. The 1:1 is where that engagement is built or broken.

— Gallup, State of the Global Workplace 2023

The best 1:1s are not about the manager. They're about the report. That one shift, making the 1:1 their meeting instead of yours, changes everything. It's the difference between a meeting that drains people and one they actually want to keep.

Employees want to decline 31% of the meetings they attend but only actually decline 14%. The 1:1 should never be one of those meetings. If it is, the format needs fixing.

— Otter.ai, 2023

The 1 on 1 meeting template

This template works for a 30-minute 1:1. Adjust the time blocks if yours is 25 or 45 minutes, but keep the order the same.

1:1 / [Manager] & [Report] / [Date]

Check-in (5 min)

How are you doing? Anything on your mind outside of work stuff?

Their agenda (15 min)

Report's topics (they fill this section before the meeting)

Blockers, questions, things they need from you

Your agenda (5 min)

Feedback, context on org changes, decisions that affect them

Action items (5 min)

Who does what, by when

Carry forward anything unresolved from last time

Three principles make this template work:

The report's agenda comes first. Their 15 minutes are protected. Your 5 minutes are secondary. If the meeting runs long, you cut your section, not theirs. This signals that the 1:1 exists for them. Most managers get this backwards.

The report fills their section before the meeting. Not during, not "let me think..." Before. Even three bullet points written the night before changes the quality of the conversation. If you use a shared doc, both sides can see topics in advance.

Action items are explicit. "Let's follow up on that" is not an action item. "You'll draft the RFC by Friday, I'll review by Monday" is. Write them down. Review them at the start of next week's 1:1. This is the accountability loop that makes 1:1s actually useful. Use meeting minutes if you want a lightweight format for capturing these.

Start a shared Google Doc for each report. Both of you add topics before the meeting. Over time, this doc becomes a living record of discussions, decisions, and growth, far more valuable than any performance review.

25 questions for engineering manager 1 on 1 meetings

The template gives you structure. These questions give you depth. Don't use all 25 in one sitting. That's an interrogation. Pick 2-3 per session and rotate.

Career growth

Where do you want to be in a year? What about two years?
What skills do you want to develop this quarter?
Is there a project or area of the codebase you'd like to own?
Do you feel like you're learning at the pace you want?
What would make you excited to come to work on Monday?

Work satisfaction

What's energizing you right now?
What's draining you?
Are you spending your time on the right things?
Is there anything you used to enjoy at work that you've lost?
On a scale of 1-10, how would you rate your work-life balance this month?

Blockers and support

What's slowing you down that I could help unblock?
Is there a decision that's been stuck for too long?
Do you have what you need to do your best work? Tools, access, context?
Is any process getting in your way?
What's one thing I could do differently to help you more?

Team and collaboration

How's the team dynamic right now?
Is there any friction with anyone you'd like to talk through?
Do you feel like your contributions are visible to the team?
Is there someone on the team you'd like to work more closely with?
Are our meetings helping or hurting the team's productivity?

Feedback for the manager

These are the hardest questions to ask and the most valuable answers to get. Most reports won't give honest feedback unless you make it safe.

What's one thing I should stop doing?
What's one thing I should start doing?
Do you feel like I give you enough context on what's happening in the org?
Am I giving you enough feedback? Too much? The right kind?
Is there anything you've wanted to tell me but haven't?

Question 25 will get silence the first few times you ask it. That's normal. Keep asking. The day someone actually answers it is the day your 1:1 starts working.

The goal is not to get through the list. It's to find the one question that opens a real conversation. Some weeks that's question 6. Some weeks it's question 11. Some weeks you throw the list away because your report walks in and says "I need to talk about something."

Good. That's the 1:1 working.

Get the 1:1 template + all 25 questions as a Google Doc

Copy it to your Drive and start using it with your team this week.

1 on 1 meeting cadence: weekly vs. bi-weekly

The right cadence depends on the person, not a blanket rule.

Weekly works best for:

New hires in their first 6 months. They have more questions, more uncertainty, and need faster feedback loops.
People going through a difficult stretch: performance issues, team conflicts, burnout. More frequent check-ins catch problems before they spiral.
New managers who are still building the habit. Weekly forces consistency.

Bi-weekly works best for:

Senior engineers who are self-directed and don't need frequent unblocking.
Stable teams where the work is predictable and the relationship is strong.
When both sides feel like the weekly 1:1 has become a 15-minute "everything's fine" with nothing substantive to discuss.

Never monthly. Too much drift between meetings. By the time you sit down, small issues have become big ones, and the report has stopped expecting the 1:1 to be useful.

One more thing: if you're moving from weekly to bi-weekly, tell your report why. "I'm switching to bi-weekly because I trust you and you don't need me checking in every week" lands very differently than "I'm cutting our 1:1s because I'm too busy." Same action, opposite message. For more on finding the right meeting cadence across all your recurring meetings, not just 1:1s, see our full guide.

Common 1 on 1 meeting mistakes

Canceling when you're busy. This is the number one mistake. When a manager cancels 1:1s because "this week is crazy," it signals that the 1:1 is low priority. Do this three times and your report stops preparing, stops bringing up issues, and starts updating their LinkedIn. Reschedule if you must. Never cancel. Consistent canceling is one of the fastest paths to meeting fatigue and burnout for your reports, because it adds uncertainty to their week.

Doing all the talking. If you're talking more than 30% of the time, you're using the 1:1 as a broadcast channel, not a conversation. Ask a question. Then shut up. Count to five silently if you have to. The uncomfortable silence is where honest answers live.

Only discussing tasks. 1:1s that are 100% about work deliverables miss the point. Career growth, team dynamics, personal motivation: these are the topics that retain engineers. A good meeting agenda has space for both tactical and personal items.

Not taking notes. If you don't write down action items and review them next session, your report will notice. It tells them their concerns don't matter enough to remember. Keep a shared doc. Revisit it at the start of every 1:1.

Not following up. You said you'd talk to the VP about the promotion timeline. You said you'd look into the on-call rotation. Did you? The fastest way to kill trust in a 1:1 is to agree to something and then forget about it. If you can't do it, say so. Don't promise and ghost.

The 1:1 is one of the few meetings that's almost always worth keeping. It's where trust gets built, problems get caught early, and engineers decide whether they want to stay.

But what about the rest of your calendar? Most teams have 10-15 recurring meetings, and the 1:1 is probably one of the only ones everyone actually wants. The others? Kill One Meeting collects anonymous ratings from your team on every recurring meeting, so you know which ones to protect and which ones to fix. Free for 30 days.

Frequently asked questions

How often should you have 1:1 meetings?: Weekly for new hires, people in transition, or new managers. Bi-weekly for senior engineers who are self-directed and on stable teams. Never monthly: too much drift between sessions causes small issues to become big ones before the next meeting.
What should a 1:1 meeting agenda include?: Four sections: a brief personal check-in (5 min), the report's agenda with their topics and blockers (15 min), the manager's agenda with feedback and context (5 min), and explicit action items with owners and deadlines (5 min). The report's section comes first and is the largest.
What questions should managers ask in 1:1s?: Rotate 2-3 questions per session across five categories: career growth, work satisfaction, blockers and support, team dynamics, and feedback for the manager. The most valuable questions are the uncomfortable ones, like "What is one thing I should stop doing?" and "Is there anything you have wanted to tell me but haven't?"