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

Why ask this

This is a narrower, more actionable version of asking how someone is doing, because it's scoped to right now and to something you can actually act on. People are often more willing to name a concrete blocker than to raise a general complaint, especially when the question implies you're ready to go fix it. Asking it every session also builds a habit of surfacing blockers early instead of letting them sit.

Why ask this

Most blockers don't get raised until they've already cost a few days of lost work. People tend to assume you already know, or don't want to bother you with something that feels small. Asking outright puts it on the table while there's still time to actually fix it, instead of finding out in the retro.

Why ask this

This gets at scope creep directly instead of waiting for someone to complain about being busy in general. Naming the specific task that doesn't belong on their plate gives you something concrete to actually reassign or cut, rather than a vague sense that they have too much going on. It's a useful one to ask every few weeks, since low-value work has a way of quietly creeping back in.

Why ask this

A general complaint about 'process' rarely leads anywhere, but naming the specific tool, handoff, or approval step that slowed things down gives you something you can actually go fix. A list format matters here too, since most projects have more than one friction point, and forcing it into a single paragraph tends to bury the smaller ones that are often the easiest wins. Reviewing this across a few projects also shows which bottlenecks are one-offs and which keep coming back.

Why ask this

Splitting the answer into what helped and what hindered gets a more balanced view than a general complaint about meetings, since it forces acknowledgment of what's actually working alongside what isn't. A list format also makes it easy to actually act on afterward, cutting the specific things that hindered without touching what helped. Doing this every sprint builds a real record of what's worth keeping in the process and what's just habit.

Why ask this

This surfaces friction that's specific to being remote rather than a general complaint about process, which matters because the fix is usually different too. A co-located manager might not think to ask about this at all, since the problem is invisible from where they sit. Naming the specific thing that's slower gives you something concrete to actually change, whether that's a tool, a meeting, or just a default to call instead of message.

Why ask this

Missing access, an unset-up tool, or an account that never got created can quietly cost a new hire their first few productive weeks without anyone else noticing, since it's easy to assume someone else is handling it. Asking directly surfaces the specific thing that's stuck rather than a general sense that onboarding feels slow. This is worth asking again in the second and third week too, since new blockers tend to show up as someone gets further into the role.