Better 1 on 1s for engineering managers

The default 1:1 degrades quickly.

It becomes a status ritual, then a calendar obligation, then a subtle source of frustration for both people involved.

Good 1:1s work because they are designed around a job. Their job is not to catch up. Their job is to produce clarity that would not appear otherwise.

The real purpose of a manager 1:1

Many teams treat 1:1s as if their purpose were self-evident. They are not.

The strongest framing is this: a 1:1 is the most reliable place for a manager and an engineer to exchange nuanced information that may not surface well in group settings.

That makes it an unusually high-leverage conversation. It is where ambiguity appears early, motivation becomes legible, and coaching can be tailored instead of generalized.

For engineering managers, that usually means using 1:1s for four things:

• uncovering ambiguity before it becomes risk
• coaching on judgment, not just execution
• understanding energy, confidence, and motivation
• making sure important context does not get trapped inside formal process

Why so many 1:1s become unhelpful

Status should be the smallest part of the conversation. If a dashboard or ticket board can answer something, the 1:1 should spend very little time there.

Useful prompts tend to be specific:

• What feels more complicated than it should right now?
• Where are you making assumptions that we should verify?
• What kind of support would actually move this forward?
• What are you not saying in the larger group setting?

1:1s often decline because neither side is designing them actively. The manager arrives with whatever is top of mind. The engineer arrives with a few updates and a vague sense that they should bring “something.” The conversation becomes reactive.

That pattern wastes one of the few recurring moments built for depth.

What better 1:1 design looks like

Useful 1:1s usually include a mix of:

• forward-looking discussion about upcoming work
• reflective discussion about patterns and friction
• coaching on how decisions are being made
• space for non-obvious concerns, including team or organizational context

Managers do not need to script every minute. But they should own the design. That means adjusting cadence, structure, and prompts based on the person and the season of work.

For example:

• a newer engineer may need more support on prioritization and confidence
• a senior engineer may need more discussion around influence, tradeoffs, and technical strategy
• a staff engineer may benefit from more time on cross-team systems and leverage

The point is not equality of format. It is consistency of value.

Signals that a 1:1 is working

The strongest 1:1s are not always comfortable. They are honest, directional, and concrete. They produce better next moves.

That is the bar.

Good signs include:

• new information shows up regularly
• issues surface before they become escalations
• both people leave with more clarity than they had before
• the conversation evolves with the needs of the role

Bad signs include:

• repetition without movement
• over-indexing on task updates
• vague coaching that never lands in behavior
• a feeling that the meeting survives mostly by habit

Managers should periodically redesign their 1:1s the same way they would redesign any other high-value system.