The 1:1 That's Worth Having

Most 1:1s are status updates with better eye contact.

The manager asks what their direct report is working on. Their direct report summarizes the week. Maybe there's a blocker or two that gets flagged. Then both parties walk away feeling like they've done the thing. The box is checked. The relationship is maintained. Progress is being made.

Except it actually isn't.

The status update style 1:1 is one of the most common and least examined habits in engineering management. And the cost isn't obvious until you realize, usually too late, that a key person on your team has been quietly disengaging, operating below their potential, or sitting on a frustration that a single honest conversation could have raised months ago.

Status belongs somewhere else

Here's my rule of thumb: if something could be communicated in a Slack message, it shouldn't consume 1:1 time. Project updates, sprint progress, blockers that need routing - these are important, but they have appropriate homes: stand-ups, team syncs, async check-ins. When status becomes the default content of a 1:1, it's usually because the harder conversations aren't happening.

The most valuable thing about a 1:1 is that it's private, it's recurring, and it belongs entirely to the two people in the room. That's a rare and expensive resource, with a clear opportunity for building trust. Spending it on information that could flow through a dozen other channels is a waste of the format.

What the time is actually for

I think of a good 1:1 as fundamentally about two things: growth and friction.

Growth means actively working to understand where someone wants to go, what's in their way, and what they need from you to get there. It means knowing, and not in a vague, impressionistic way, but specifically - the top three to five strengths this person brings, and the top three to five areas where they have real room to develop. And it means regularly asking yourself: what have you done lately to capitalize on the former and work on the latter?

Friction means surfacing the things that aren't working before they get worse. A process that's slowing someone down. A team dynamic that's creating drag. A concern about the direction of a project. These are the conversations that make a team healthier over time, and they almost never happen organically. Instead, they require a manager who is willing to ask direct questions and sit with uncomfortable answers.

The case for near-real-time feedback

The annual performance review is a useful forcing function for documentation. It is nearly useless as a feedback mechanism.

People don't improve from feedback they receive once a year, decoupled from the specific moments when the behavior in question was actually happening. By the time a review cycle arrives, the context has blurred, the emotional resonance is gone, and the feedback lands more like a verdict than a coaching moment.

What actually moves people is near-real-time feedback, delivered close to the moment where it's relevant, specific enough to be actionable, and given within a relationship with enough trust that it can be received honestly. A 1:1 is the natural home for this kind of conversation, but only if the manager has built the habit of bringing real observations to the table rather than waiting for the formal process to do the work.

If someone is genuinely surprised by critical feedback in a performance review, that's not a data point about the employee. It's a signal that the ongoing communication has failed.

Making it "awkward" on purpose

The best word I've found for what I'm describing is awkward. Meaning, deliberately going somewhere neither party was necessarily expecting. Asking the question that doesn't have an easy answer. Naming the dynamic that's been sitting unspoken in the room. Giving the piece of feedback that the employee probably needs to hear but might not love in the moment.

This isn't about manufacturing discomfort. It's about taking the time seriously enough to use it for something that actually requires it.

A 1:1 that never gets uncomfortable is probably a 1:1 where real things aren't being said. The relationship may feel smooth, but smooth isn't the same thing as healthy. The test I like to apply: if I walked out of a 1:1 and couldn't point to something meaningful that was surfaced, learned, or advanced - something that couldn't have happened in a Slack thread - I probably wasted both of our time.

The manager's job in the room

High-touch management doesn't mean being in everyone's business. It means being genuinely invested in each person's development. A foundation built on genuine trust and human connection, knowing them well enough to have the right conversation at the right time, and doing it consistently enough that the feedback loop is tight rather than episodic.

That requires showing up to 1:1s well prepared. It requires setting goals collaboratively and checking in on them regularly. It requires being willing to have the hard conversation now rather than the harder conversation later.

The 1:1 is one of the most powerful tools a manager has. Most of us are using it for something a Slack message could do just as well.