How Great Engineering Leaders Run 1:1s

1. Why most 1:1s are a waste

The default 1:1 goes like this. Manager asks, "so, what are you working on?" Engineer runs through their in-flight tickets. Manager nods, offers a suggestion or two, mentions a thing they need. Thirty minutes later both parties leave feeling vaguely productive and nothing has changed.

That meeting is not a 1:1. It is a status meeting for one person. And it is a criminally expensive way to move information that Slack, Jira, or your standup could have moved for free.

2. What a 1:1 is actually for

The 1:1 is the only recurring surface in your week where an engineer has your undivided attention with no audience. That makes it the wrong place for status and the right place for four things Slack cannot do:

• Surface friction they wouldn't raise in a group setting.
• Coach on something specific and hard — a stuck design, a difficult peer, a habit that's holding them back.
• Design their career, in slow motion, six months at a time.
• Build the trust that means when something actually breaks, they'll tell you early.

3. The four-quadrant agenda

A repeatable structure beats a good mood. Every 1:1, in this order:

• Status (5 min max). Anything blocked I need to know about? Anything about to be blocked? That's it. If it takes longer than five minutes, it belonged in writing.
• Growth (10 min). What are you working on that's stretching you? What would you want more of? What's one skill you'd want to be visibly better at in six months?
• Friction (10 min). What's frustrating? What's slower than it should be? Who or what is quietly costing you energy? Ask, then wait — silence is a feature.
• Signal (5 min). Anything I need to hear that I'm not hearing? Anything you'd change about how I'm running the team?

The quadrants are a scaffold, not a script. Some weeks growth eats the whole hour because a real conversation is happening. That's fine. What you're avoiding is the drift into pure status by default.

4. Ask questions that can't be answered in one sentence

The quality of a 1:1 is the quality of your questions. "How's it going?" is answered "fine" and buys you nothing. Try instead:

• What's the most annoying part of your week right now?
• If you could delete one meeting from your calendar, which would it be?
• Where are you spending energy that doesn't feel worth it?
• What's a piece of feedback you've been sitting on for me?
• Who on the team do you learn the most from? What would it take to make that more available?

Then — and this is the harder skill — shut up. Most managers under-tolerate silence by about eight seconds. The best answers arrive on the other side of the pause you were tempted to fill.

5. Write things down

A shared doc, one per engineer, appended to every week. Your notes on one side, theirs on the other. This is not bureaucracy — it is the difference between a conversation and a system. You will forget what they told you in April. The doc will not. And when it's time to write a promotion case, a growth plan, or, painful but necessary, a performance conversation, you'll have receipts instead of impressions.

6. When to cancel

Cancel a 1:1 only when the relationship is stronger than the calendar. Early in a working relationship — the first six months, a new hire, a shaky quarter — treat it as sacred. Later, with an experienced engineer you have deep trust with, a two-week cadence is often better than a weekly meeting neither of you needs.

7. Final takeaway

Thirty minutes a week per engineer is a small budget for the highest-leverage coaching surface you have. Spend it on the conversations only you can have with them — not on the ones a dashboard could have on your behalf.