Your 1-on-1s show The Goldfish patterns — here's where to start

Why ask this

Development goals set at the start of a quarter are easy to lose track of once day-to-day work takes over, and this question forces an honest look back instead of letting the goal quietly expire. Naming the gap between what was planned and what actually happened is more useful than the goal itself, since it usually points at what got in the way. It also gives you a natural moment to reset the goal if it's no longer the right one.

Why ask this

Most solid work never makes it into a status update, so asking directly closes the gap between what actually happened and what you as the manager actually saw. It also gives you something concrete to reinforce, rather than a generic compliment that doesn't reference anything real. Tracking these over time builds a record you can actually use at review time instead of trying to remember months of work from scratch.

Why ask this

Opening with this instead of a generic 'how's it going' makes the conversation build on the last one instead of starting from zero every time. It also surfaces whatever's actually moved, whether that's a blocker clearing up or a new problem showing up, without you having to guess what to ask about. Skipping this step is usually why 1-on-1s start to feel repetitive.

Why ask this

This catches the specific gap between effort and visibility, which is different from just asking about recent wins in general. People often assume their manager has more visibility than they actually do, so this question corrects that assumption directly instead of leaving it as a quiet source of resentment. It also gives you a concrete example to reference the next time you're advocating for them.

Why ask this

Asking for their number before giving yours tells you whether you're both looking at the same picture, and a gap between the two ratings is usually more useful than either number on its own. If they rate themselves lower than you would, that's often a confidence problem worth addressing directly rather than a performance one. If they rate themselves higher, you've just found a blind spot before it turns into a surprise at review time.

Why ask this

People hold back honest opinions about how work actually gets done day to day, especially anything that reflects on you or the team. Framing it as advice for someone else, rather than a direct complaint, makes it much easier to say the parts they'd normally soften. It also surfaces process gaps and workarounds that never come up in a normal status update.