The one-on-one that actually helps

Most weekly one-on-ones default to a status update. The engineer reports what they worked on; the manager acknowledges; both leave the meeting no better off. The one-on-ones that build the relationship and surface problems have a different shape.

Written August 2025 from a decade of running and being in one-on-ones.

What doesn't work

• Status update format. The manager already knows the status; the engineer feels like they're reporting to a bureaucracy.
• Manager talking the whole time. The engineer needs the airtime, not the manager.
• No agenda, week after week. The meeting drifts and both participants tune out.

What does

• The engineer sets the agenda. They bring the topics; the manager responds.
• A rolling document. Both add topics between meetings. Anything not resolved in one session carries over.
• Skip the status update. If you need the status, get it in Slack. The meeting is for what Slack can't handle.
• Long-term topics recur. Growth, project preferences, career direction. Not every week, but consistently.
• The manager asks about obstacles, not just tasks. "What's slowing you down?" produces better data than "how's the project going?"

The unspoken rule

The engineer should leave every one-on-one with at least one thing that was useful — a decision made, an obstacle removed, a question answered, a piece of context shared. If they leave without that, the meeting was wasted for them.

The best one-on-ones I've been part of felt more like a conversation between colleagues than a management ritual. That's not accidental. It's the result of the manager being useful to the engineer, not just informed about them.