IAnswerable

Running One-on-Ones That Aren't Status Updates

18 Jun 2026

Status belongs in a written update, not a 1:1. If your 1:1 is “what did you work on this week,” you’re spending relationship time on something Slack already does better, and you’ll never hear the thing that actually needed to be said.

What a 1:1 is actually for

The one recurring slot where someone can say something that’s uncomfortable, half-formed, or not yet a real problem. It only works if they trust it won’t be used against them and won’t just be forgotten.

Questions that get past “fine, all good”

Swap the generic “how’s it going” for something specific enough to require a real answer:

That last one is uncomfortable to ask and uncomfortable to answer. Ask it anyway, occasionally — it’s the one most likely to surface a resignation-in-progress before it’s final.

Let them set the agenda

Send a shared doc or note before the call and let them add items first. If you fill the agenda before they get to it, you’ve signaled this is your meeting, not a shared one, and the real topic, theirs, quietly doesn’t make the list.

Follow up on what they said last time

Nothing kills trust in a 1:1 faster than raising a concern and having it never come up again. Start the next 1:1 with “last time you mentioned X, where’s that at?” even if the answer is “still stuck.” Being asked again, even without a fix, tells someone it was heard.

Silence is data

If someone has nothing to say for three 1:1s in a row, that’s not a good sign, it’s usually disengagement, not contentment. Ask directly: “You’ve been quiet in these lately, is that because things are genuinely fine, or because it doesn’t feel worth bringing things up here?”

What ruins a 1:1

The actual payoff

A good 1:1 habit means you hear about a problem, a teammate conflict, a burnout signal, a disagreement with the roadmap, weeks before it would otherwise surface, usually as a resignation letter. That’s the entire value of the meeting. Everything else is a bonus.