I had a team member who had been one of my strongest performers. Good work, reliable, someone the team respected. Then, gradually, things started slipping. Late to meetings. Unprepared for demos. Slow to respond on Slack. The kind of drift that’s easy to explain away the first time, but by the third or fourth instance it’s telling you something.
When we sat down for our next 1-on-1, I noticed it immediately. The body language was off: slumped posture, avoided eye contact, a flatness in their voice that hadn’t been there before. This person was carrying something. I didn’t know what. But I knew enough not to walk in with a list of things I’d observed and start reading it out loud.
That approach (cataloguing the missed meetings, the late responses, the unprepared demos) might feel thorough. What it actually does is put someone on the defensive before they’ve had a chance to say anything. It makes the conversation about your evidence rather than their experience. And it almost always shuts down the very thing you need to hear.
So instead, I said this:
“I’ve noticed that some things have been slipping past you lately. This isn’t a judgment. I just wanted to check in and see if there was anything I could do to help.”
That’s it. No list. No specifics. No accusation framed as concern. Just an observation, a reassurance, and an open door.
They opened up. There was something significant going on in their personal life: the kind of thing that makes showing up to a demo feel impossible. We talked through it. I connected them with what the company had available. The performance conversation could wait, and it did. But it only happened at all because the question didn’t feel like a trap.
Questions that open vs. questions that close
The single most important thing to understand about asking questions in a 1-on-1 is that the framing of a question determines whether someone feels safe to answer it honestly.
Questions that close tend to be narrow, leading, or evaluative. They signal that you’ve already formed a view and you’re looking for confirmation. “Why haven’t you been hitting your deadlines?” isn’t really a question; it’s an accusation with a question mark. “Don’t you think that was the wrong approach?” is the same. These questions put people in a defensive crouch and you stop getting real information.
Questions that open are curious, non-judgmental, and leave genuine room for the person to answer in their own way. They don’t signal what the right answer is. They invite the person to lead. That’s the kind of question that gets you the truth.
The difference isn’t just tone. It’s the structure of the question itself. Here are the specific types worth having in your toolkit:
Four questions worth using
1. “Tell me more about that.”
Technically not a question. Doesn’t matter; it functions as one. When someone says something that sounds like it has more underneath it, this is your default move. It asks for depth without directing where that depth should go. It signals that you’re interested and that you have time. It’s one of the most versatile tools in a 1-on-1 because it works in almost every context: goals, problems, frustrations, ideas.
Use it when someone gives you a short answer to something that deserves a longer one. Use it when you sense there’s more but you’re not sure what direction it’s in. Let them lead.
2. “What’s making that hard?”
This is your go-to when someone surfaces a problem or an obstacle. Not “why haven’t you solved it”; that’s evaluative. Not “have you tried X”; that’s you jumping to solutions before you understand the problem. “What’s making that hard” is different because it asks the person to articulate the obstacle in their own terms. It almost always surfaces something you didn’t know, and it gives you far better information for actually helping.
The other thing this question does is validate that the thing is hard. That matters. A lot of team members have been in environments where admitting difficulty felt risky. This question says: difficulty is expected, let’s understand it.
3. “What would success look like to you?”
Use this for goals, projects, or any situation where the definition of done is fuzzy. It does something simple but important: it asks the person to articulate their own picture of the outcome, not yours. You’ll often discover the gap between what they think success means and what you think it means. And that gap, if you don’t surface it, becomes a problem later.
It also tells you a lot about how someone is thinking. A specific, energized answer means they’re engaged and have ownership. A vague or hesitant answer might mean the goal isn’t clear, they don’t feel ownership of it, or there’s something blocking them they haven’t named yet.
4. The observation-without-accusation opener.
This is the one from the story above, and it deserves its own category because it’s a specific situation: you’ve noticed something is off, and you need to open a conversation about it without triggering defensiveness.
The structure is: name the observation neutrally, explicitly remove judgment, and offer help. “I’ve noticed [thing]. This isn’t a judgment. I just wanted to check in and see if there’s anything I can do.” The key phrase is “this isn’t a judgment.” It directly addresses the fear that’s preventing the person from answering honestly, before they even have to feel it.
One important note: if you’ve noticed it, others have too. That’s worth keeping in mind, not as a threat, but as a reason the conversation matters. You’re doing the person a favor by having it with care rather than letting it become a wider problem.
Knowing when to dig and when to let it go
Not everything in a 1-on-1 needs a follow-up question. Someone mentioning they had a good weekend doesn’t need unpacking. A passing comment about a minor frustration that they’re clearly already past doesn’t need a deep dive.
The moments that warrant digging deeper tend to have a few things in common. There’s a signal: body language, a change in tone, a hesitation before answering. The topic is substantive: a goal, a problem, something that’s clearly affecting their work or their state of mind. Or there’s a gap between what they’re saying and how they’re saying it.
That last one is worth paying attention to. When someone says “it’s fine” but sounds like it isn’t, that’s the gap. When someone answers a question quickly and changes the subject, that’s the gap. When someone who normally has a lot to say suddenly doesn’t, that’s the gap. You don’t have to investigate every one of them. But you should notice them, and you should make a judgment call about whether this is the moment to follow up.
Sometimes the right move is to name it lightly and leave the door open without forcing it: “You seem a bit off today. Happy to get into it if there’s something on your mind, or we can just move on.” That’s enough. It tells the person you see them. They’ll decide whether to go further.
This is still their time
One thing worth keeping front of mind throughout all of this: insightful questions are in service of understanding, not interrogation. The goal is never to extract information, catch someone out, or turn a 1-on-1 into a deposition.
There will be 1-on-1s where the most valuable thing that happens is a genuine conversation about something unrelated to work: how someone is doing, what they’re working toward, what matters to them. That’s not a waste of time. That’s relationship-building, and it pays dividends in trust and loyalty that are hard to put a number on.
These questions are tools for when something needs to go deeper. Use them with judgment. Use them with care. And always remember that the 1-on-1 belongs to the person sitting across from you. Your job is to ask the questions that help them be heard, not the ones that make you feel like a good manager.
Key takeaways
- Questions that open people up are curious and non-judgmental. Questions that close them down are narrow, leading, or evaluative.
- “Tell me more about that” is your default move when something sounds like it has more underneath it.
- “What’s making that hard?” surfaces the real obstacle and validates that difficulty is normal; use it before jumping to solutions.
- “What would success look like to you?” reveals gaps in how you and your team member are defining the outcome.
- The observation-without-accusation opener names what you’ve noticed, removes judgment, and offers help. If you’ve noticed it, others have too.
- Not every thread needs pulling. Read the signals (body language, tone, the gap between what someone says and how they say it) and make a judgment call.
- Insightful questions are in service of understanding, not interrogation. This is still their time.