The Engineering Manager's Complete 1:1 Meeting Guide

2026-06-15 · 8 min read · 1:1 Meetings

The 1:1 meeting is the single highest-leverage tool an Engineering Manager has. Done right, it builds trust, surfaces problems before they become crises, and gives your team members a dedicated space to grow. Done wrong, it becomes a status update — something both of you dread.

This guide covers everything you need to run 1:1s that actually matter.

Why 1:1 Meetings Are Non-Negotiable

Most Engineering Managers are promoted from senior IC roles. The instinct is to stay technical — jump into code reviews, architecture discussions, sprint planning. But the higher-leverage work is people.

A weekly 30-minute 1:1 with each of your 6–8 direct reports gives you:

• Early signal on morale and motivation — before it becomes a resignation
• A channel for feedback that's too sensitive for group settings
• Visibility into blockers that aren't showing up in standups
• A relationship that makes hard feedback land better when you need to give it

Companies with high-quality 1:1 practices see 26% lower attrition according to Gallup's engagement research. The ROI on 30 minutes a week is enormous.

The Big Mistake: Treating It Like a Status Sync

The most common failure mode is turning a 1:1 into a project status update. If your 1:1s sound like "what did you work on this week?" you're missing the point. You can get that from Jira.

A 1:1 is for things that don't fit anywhere else:

• Career growth and promotion path
• Team dynamics and interpersonal friction
• Motivation and engagement levels
• Personal goals and learning
• Feedback — both directions

Keep project status to standups and async updates. Use 1:1 time for the human stuff.

The Weekly 1:1 Template

Here's a structure that works for most teams. Adapt it to your style.

5 min — Their agenda first

Start by asking what's on their mind. This signals that the meeting is for them, not for you. Common openers:

• "What's on your mind this week?"
• "Anything weighing on you I should know about?"
• "What's been the highlight and the lowlight since we last met?"

Do not fill this silence by jumping to your own items. Wait. Let them lead.

10 min — Progress and blockers

This is the closest you get to status — but framed around unblocking, not reporting:

• "Is there anything slowing you down that I could clear?"
• "Any dependencies from other teams you're waiting on?"
• "How are you feeling about the sprint goal?"

Your job here is to be a force multiplier. Find the rocks and move them.

10 min — Growth and development

This is where the long-term investment happens. Even a single question per week compoundsinto meaningful career development:

• "What did you learn this week?"
• "Are you getting enough stretch in what you're working on?"
• "How are you progressing toward [specific promotion goal]?"

Link this to the impact stories they're building for their promo case. Great EMs are always thinking about their team's next level.

5 min — Feedback exchange

This is the hardest part to do consistently. Make it a habit:

• "Is there anything I could be doing better as your manager?"
• "Here's something I noticed this week that I want to share..." (your feedback for them)

Most managers wait until a performance review to give feedback. By then it's too late to act on. Weekly micro-feedback is vastly more effective.

Frequency and Cadence

Never cancel a 1:1. Reschedule if you must, but cancellation sends a signal that the person isn't a priority. The one time you most need to have a 1:1 is exactly when you're busiest.

What to Track Between Meetings

Good 1:1s build on each other. Keep notes on:

• Action items — both yours and theirs — with due dates
• Patterns — if someone mentions feeling blocked three weeks in a row, that's data
• Career goals — so you can connect daily work to longer-term aspirations
• Wins — reference these when you write their performance review

Emtricks was built specifically for this. The 1:1 prep panel surfaces recent impact stories, open action items from prior meetings, and active goals — so you walk in prepared every time, not scrambling to remember where you left off.

Red Flags to Watch For

These signals in 1:1s often precede a resignation or performance issue:

• Short, clipped answers — less engagement than usual
• Stops bringing problems or ideas
• Career growth questions disappear
• Increases focus on compensation relative to work itself
• "Everything's fine" to every question

When you notice these, don't wait. Ask directly: "I've noticed you seem a bit less engaged lately — is everything okay?" Most people will appreciate the observation.

Making 1:1s Sustainable at Scale

At 8+ reports, 30 minutes × 8 people = 4 hours a week just in 1:1 time. Add prep and follow-up and it's closer to 6. This is real — here's how to make it sustainable:

1. Prepare async — review notes before each meeting, not during. 5 min of prep makes the 30 min 3× more valuable.
2. Delegate down — not everything they raise needs to be solved by you in the room. "That sounds like something to raise with the team lead — want me to loop them in?"
3. Use a system — whether it's a shared doc, a Notion page, or a dedicated tool, having all your notes in one place saves 15 min of context-loading per meeting.

The Bottom Line

The quality of your 1:1s is one of the clearest signals of your effectiveness as an Engineering Manager. It's where trust is built, problems are caught early, and careers are shaped.

Start with the template above. Do it consistently for 8 weeks. Then look back at your notes — you'll be surprised how much signal was sitting in those conversations.

Want to track 1:1 notes, action items, and team member goals in one place? Try Emtricks free for 30 days — no credit card required.