50 Questions to Ask in Your Next 1-on-1

Why ask this

Career conversations tend to default to the next promotion, but this question is open enough to surface a lateral move, a specialism, or a goal that has nothing to do with title at all. Getting the real answer means you can actually point opportunities their way instead of guessing at what they want. Revisiting this every so often also catches when someone's direction has quietly changed since you last talked about it.

Why ask this

A longer time horizon gets people to think past their current role and the next obvious step, which is where the more interesting answers tend to live. It also gives you a real target to plan development work against, instead of only reacting to whatever comes up that quarter. Coming back to this answer a year later is a useful check on whether the path you've been building toward together still matches what they actually want.

Why ask this

Scoping improvement down to a single week and a single thing makes it something a person can actually act on immediately, instead of a vague resolution that fades by Wednesday. It also gives you a specific, small thing to check back on next time instead of a general 'how's it going' that's easy to answer vaguely. Asked regularly, this turns growth into a habit instead of something that only comes up at review time.

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

Framing it around what they'd want to take with them, rather than what the role requires right now, gets at motivation instead of just job requirements. It also surfaces skills you might be able to build into their actual work, rather than sending them to a course that has nothing to do with what they do day to day. A short, specific answer here is usually more useful than a long list of vague aspirations.

Why ask this

Most people won't volunteer this unless asked directly, either because they assume assignments are decided elsewhere or because they don't want to seem like they're angling for something. Knowing the answer means you can actually put them forward when the opportunity shows up, instead of defaulting to whoever's available. It's a low-cost question that can pay off well after the conversation is over.

Why ask this

This is more direct than asking about promotion readiness in general, because it assumes there's a real reason and asks them to name it instead of leaving room for a vague 'not yet.' Sometimes the answer is a skill gap you can help close, and sometimes it's confidence rather than capability, which needs a completely different response from you. Either way, you can't do anything about a blocker you don't know exists.

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

People hold back feedback for their manager more than almost anyone else, since it's the relationship with the most at stake if it lands badly. Naming that you know feedback might be sitting there unsaid makes it easier for them to actually say it instead of waiting for a safer moment that may never come. Whatever they raise is worth taking seriously, since it likely took some nerve to bring up.

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 are often harder on their own work than anyone else, and if something's been bothering them without ever coming up, it's usually because they assumed it wasn't worth mentioning or didn't want to look like they were making excuses. Asking directly gives them permission to raise it before it turns into a bigger issue at review time. It's also a chance to catch a real quality problem before a customer or another team does.

Why ask this

This surfaces a mismatch in perception before it becomes a surprise, since most people carry some assumption about how their manager sees them that's rarely checked directly. A big gap in either direction is worth a real conversation, whether that means correcting an inflated self-view or reassuring someone who's underrating their own work. It's a faster way to get at calibration than waiting for a formal review to reveal the gap.

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

Leaving the question open, instead of asking about workload specifically, lets whatever is actually weighing on them surface, whether that's a deadline, a person, or something outside work entirely. Naming it as the top concern also forces prioritisation, so you're not stuck reacting to a list of minor things while missing the one that actually matters. This is a good question to open with, since it sets the agenda for the rest of the conversation instead of you guessing at it.

Why ask this

A simple, regular check-in like this is what makes the more specific questions in a 1-on-1 land better, since it gives the conversation a natural starting point instead of jumping straight into a deep topic cold. It's also a good early signal, since how someone answers this, not just what they say, often tells you whether the week was actually fine or just being described that way. Skipping this and going straight to business tends to make the whole session feel more like an interrogation than a conversation.

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

Sleep is one of the first things to slip when work gets overwhelming, and it tends to show up here before it shows up in someone's actual output. Asking about it directly, rather than a general wellbeing question, gets a more honest answer since it's specific and doesn't feel like it's testing them. It's also an early warning sign worth taking seriously rather than waiting for it to turn into a bigger problem.

Why ask this

This is a faster way to find low-value work than asking someone to justify everything they're doing, since it reframes the question around what they'd keep rather than what they'd defend. The answer often reveals a task that's been running on autopilot long after it stopped being useful. It's a good one to actually act on, since asking and then doing nothing about the answer undermines the question next time you ask it.

Why ask this

This separates two very different reasons work gets avoided, since a task that's draining needs a different response than one that's actually difficult. If it keeps getting pushed to the bottom of the list, that avoidance is a signal on its own, regardless of how important the task actually is. Knowing which kind of avoidance you're dealing with means you can actually help, whether that's redistributing the task or just acknowledging that it's a grind.

Why ask this

Asking what would need to change gets past the polite 'I'm doing fine' that a plain mood check usually gets, since it assumes there's room for things to be better and invites them to say what that looks like. The answer is often something small and fixable, like a schedule change or clearer priorities, rather than anything dramatic. It's a useful question precisely because it doesn't wait for something to be visibly wrong before asking.

Why ask this

This is a more direct question than asking about engagement or satisfaction in the abstract, since it's about the actual day-to-day work rather than the job as a whole. Someone can be committed to the team and the company while quietly disliking most of what they're doing, and that distinction matters for what you do next. A flat or hesitant answer here is worth a follow-up rather than moving straight on.

Why ask this

Small, chronic annoyances rarely get raised on their own, since none of them feel big enough to justify bringing up, but they add up and quietly wear down engagement over time. Asking about it directly gives permission to name something minor without it feeling like a formal complaint. Catching these early is a lot cheaper than waiting until they've built into genuine disengagement.

Why ask this

Recognition almost always looks fine from the manager's seat and thin from everyone else's, since the manager sees every decision behind a result and the team mostly sees the outcome. A quick scale answer catches that gap before someone quietly decides their work doesn't matter here. Watching the score over several sessions also tells you whether a change you made actually landed.

Why ask this

Framing it around tomorrow specifically, rather than the job in general, gets a more concrete answer than a broad question about engagement usually does. It might be a particular task, a person they get to work with, or just finishing something they've been stuck on, and any of those are things you can actually act on. Asking this regularly also gives you an early read on motivation drifting, well before it shows up as a drop in output.

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.

Why ask this

Team conflict rarely gets raised proactively, since most people would rather work around a difficult dynamic than name it directly to their manager. Tying the question to productivity, rather than just asking about team harmony, gives it a practical framing that makes it feel less like gossip and more like a legitimate work topic. Catching this early is a lot easier than untangling it once it's affected a delivery date.

Why ask this

New eyes and fresh frustration both tend to notice process oddities that everyone else has stopped questioning, and this question gives permission to say it out loud instead of quietly going along with it. Sometimes the answer is a genuine reason nobody explained, and sometimes it's a leftover habit that's outlived its purpose. Either way, you learn something about how the team actually operates versus how it's supposed to operate on paper.

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

Organisational change is exactly the kind of thing people speculate about privately instead of raising directly, since it can feel like there's no safe way to ask without sounding like they're resisting it. Giving them a direct opening to name a concern means you find out what's actually worrying people before it turns into rumour or disengagement. It also gives you a chance to correct a misunderstanding while it's still small.

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

Peer feedback tends to be the hardest kind to give, since there's no formal structure forcing it the way a review cycle does with manager feedback. A low score here is worth digging into, since it usually points at either a trust issue on the team or just a lack of practice having those conversations. Tracking this over time also shows whether team-building or process changes are actually making peer feedback easier to give.

Why ask this

Managers often assume they already know what kind of help someone needs, when the honest answer might be something small like protecting their calendar or something bigger like advocating for them in a room they're not in. Asking directly instead of guessing means the support you offer actually matches what they need instead of what you assume they need. It also signals that helping them succeed is something you're actively thinking about, not just a line you say once a quarter.

Why ask this

Managers who jump straight to solving a problem often step on someone who just wanted to think out loud, and managers who hold back advice sometimes leave a report stuck when they actually wanted help. Asking which one they want up front removes the guesswork and stops you giving the wrong kind of support at the wrong moment. It's a small question that prevents a surprising amount of frustration on both sides.

Why ask this

Most people won't volunteer this kind of feedback unprompted, even when it's costing them real time or energy, because it can feel risky to criticize the person who reviews them. Asking directly, and naming that you might not realise it, removes some of that risk and makes clear you actually want the answer. Whatever comes up is also usually fixable once you know about it, which is the whole point of asking.

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

Limiting it to one thing makes the question feel manageable instead of an invitation to list every complaint, which makes people more likely to actually answer honestly. It also forces them to prioritise, so whatever they say first is usually the thing that matters most to them. Softer versions of this question are easy to deflect with a vague answer, but this phrasing is direct enough that a non-answer stands out.

Why ask this

It's easy for a 1-on-1 to quietly turn into a status update that only serves the manager, and this question checks for that directly instead of assuming the format is working. A flat yes is worth pushing on with a follow-up, since most people won't volunteer that a recurring meeting has stopped being useful to them. Asking this every few months also gives you permission to actually change the format if the answer is lukewarm.

Why ask this

This is a more targeted version of a general support question, since asking for one area forces a real answer instead of a polite 'I'm fine.' It also puts the responsibility on you to act on what comes back, which is part of what makes the question worth asking in the first place. Coming back to this a few months later is a good way to check whether the support you added actually helped.

Why ask this

Asking someone to imagine being in your seat gets past the usual politeness of a direct 'what should I be doing differently' and gets you their actual priorities instead. The top-3 format keeps the answer focused instead of turning into a wish list, and it often reveals what they think is actually broken versus what's just mildly annoying. It's also a good gut check on whether your own priorities match theirs.

Why ask this

Remote isolation tends to build up slowly enough that it's easy to miss until it's already affecting how connected someone feels to the team. Asking specifically about the days they're not in the office isolates the variable, rather than asking a general connection question that could be about anything. Catching this early is easier than repairing team cohesion after someone's already checked out.

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

A bad chair, unreliable internet, or a noisy environment can quietly drag down someone's work for months without ever getting mentioned, since it can feel like a personal problem rather than a work one. Asking directly makes it clear that it's a legitimate thing to raise, and often the fix is simple once you know about it. This is worth asking again after any change in living situation, not just once when someone starts working remotely.

Why ask this

Meeting schedules often get set once and never revisited, even as someone's personal schedule, energy patterns, or time zone situation changes. A meeting that lands at a bad part of someone's day tends to get less useful input from them, which affects the whole team even if nobody names why. This is a quick, easy thing to fix once you actually ask, instead of assuming the current schedule still works for everyone.

Why ask this

Decisions made in a hallway conversation or an impromptu desk chat rarely get written down, which puts remote team members at a real disadvantage even when nobody intends it. Asking this directly surfaces a structural gap rather than a personal complaint, since the fix is usually about how decisions get documented rather than about any one person. If the answer is yes, it's worth treating as a process problem rather than something to just apologise for.

Why ask this

New hires notice confusing parts of onboarding and process that everyone else has stopped seeing, since familiarity erases the rough edges over time. Asking early catches this while the confusion is still fresh, since after a few months people either figure it out or just stop mentioning it. Whatever they name is also useful for the next person who joins, since it's usually not unique to them.

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.

Why ask this

The gap between what's said in an interview and what the day-to-day is actually like is one of the biggest predictors of early attrition, and it rarely gets checked directly after someone starts. Asking this early gives you a chance to address a mismatch while someone is still deciding whether to fully commit, rather than after they've already started looking elsewhere. It's also useful information about what your own hiring pitch is over-promising.

Why ask this

Asking this after the fact, once the first week is behind them, tends to get more honest and specific answers than asking someone mid-onboarding how it's going. Whatever they name is usually fixable for the next new hire, whether that's clearer documentation, an earlier introduction to someone on another team, or just a slower first few days. Treating onboarding as something to keep improving, rather than a fixed process, is what this question is really for.