I still remember the moment I realised what I was doing. I’d delegated a client presentation to one of my team members. Someone experienced, someone who’d done dozens of these before. The presentation wasn’t due for another week.
And I’d already asked her three times how it was going.
- “How’s the deck coming along?” on Monday.
- “Making good progress on the presentation?” on Wednesday.
- “Just checking in on the client presentation” on Friday morning.
Each time, she responded professionally. “It’s going well, thanks.” “On track.” “All good, I’ll have it ready.”
But that Friday, there was a pause before she answered. Just a second. And in that pause, I heard what she wasn’t saying: “Why do you keep asking me this? Do you think I’ve forgotten about it?”
I thought I was being engaged and showing I cared about an important client deliverable. What I actually communicated was: I don’t trust you to manage this without me breathing down your neck. Yep, I was micromanaging.
Here’s what makes this particularly uncomfortable: these checking questions feel supportive when you ask them. You’re staying informed. You’re being involved. You’re showing interest in your team’s work. I genuinely thought that I was doing the right thing and being a good manager.
But to your team, especially your experienced team members, they sound completely different. They sound like supervision. Like doubt. Like you don’t actually believe they can do their job without constant monitoring.
Today, I want to talk about the specific questions that create this problem, why they land so differently than you intend and what to ask instead when you genuinely need information.
The engagement trap
Let’s start with why this happens in the first place, because understanding the gap helps you fix it.
When you ask these “checking in” questions, you’re coming from a good place. You care about the work. You want to stay informed about important projects. You’re trying to be an engaged manager, not an absent one.
The problem is the gap between your intention and their interpretation.
You think you’re showing interest. They hear “I’m checking because I assume you’re not on top of this.” Especially when you do it over and over again.
You think you’re being supportive. They hear “I don’t think you’re capable of managing this alone.”
You think you’re staying informed. They hear “I’m monitoring you.”
Context changes everything.
These same questions can work fine in certain situations. A casual hallway chat. A team meeting where you’re checking in on multiple projects. A broader conversation about workload and priorities.
They become trust killers in one on ones, in standalone messages, or when you repeat them. It’s the pattern and the setting that creates the problem, not necessarily the question itself.
I’ve also learned that high performers often react most strongly to these questions. Your best people are thinking three steps ahead. They’ve already considered the timeline, the dependencies, the potential issues. When you ask “Have you thought about X?” they hear “I don’t think you’re thorough enough to have considered X.”
Yes, occasionally you’ll make them aware of something that they hadn’t considered before. But it’s the exception, not the rule.
Six questions that sound helpful but undermine confidence
Right, let’s get specific. Here are the questions that consistently create this problem, even when you don’t mean them to.
1. “Have you started on [project] yet?” when there’s still plenty of time before the deadline
What you mean: I want to understand your workload and make sure you have capacity.
What they hear: I don’t trust you to manage your own time.
This becomes a real problem when you ask it more than a week before a deadline, or when you ask it at all for someone with a solid track record of delivering on time.
If someone has never missed a deadline, asking if they’ve started a week early sends a message: despite your perfect record, I still doubt you.
2. “Did you remember to [basic task]?” for someone experienced in the work
What you mean: I’m being thorough and making sure nothing falls through the cracks.
What they hear: I think you’re careless or forgetful.
This is asking an experienced account manager “Did you send the meeting invite?” or a developer “Did you test this before deploying?”
These are foundational parts of their role. Asking if they remembered suggests you think they might forget the basics of their job.
3. “Are you sure about [their recommendation]?” without specific concerns
What you mean: I want you to feel confident in your decision.
What they hear: I think your judgment is questionable.
There’s a crucial difference between “Are you sure?” and “Walk me through your thinking on this.”
One questions their conclusion. The other explores their process. Same information needed, completely different message about whether you trust their capability. Again, all in their head, not yours.
4. “How’s [project] going?” asked repeatedly in a short timeframe
What you mean: I care about this important project.
What they hear: I’m anxious you’re not handling it properly.
Once in a one on one is a reasonable check in. Three times in three days is surveillance.
The frequency is what kills trust here. It signals that despite their reassurance the first time, you didn’t actually believe them.
5. “Do you need any help?” after every single task assignment
What you mean: I’m here to support you.
What they hear: I don’t think you can handle this alone.
Offering help on genuinely new or challenging work is supportive management. Offering help on routine tasks they’ve done dozens of times suggests you doubt their capability.
I made this mistake constantly early in my management career. I thought I was being supportive. My team heard “I don’t think you’ve got this.”
6. “Just wanted to check…” [anything] in a standalone message
What you mean: This is casual and low pressure.
What they hear: I’m monitoring you.
There’s something about these questions arriving alone, outside of any other conversation, that makes them feel heavier. They become the subject of the interaction, rather than one question among several.
A checking question in a broader conversation feels different than a checking question that arrives on its own at 9:47am on a Tuesday.
The information you need without the trust damage
Right, so if these questions create problems, how do you actually get the information you need? Because you do need to stay informed. You do need to understand project status and identify risks.
The difference is asking about their process, planning and thinking rather than whether they’ve done the basics you hired them to do.
When you need a status update:
Instead of “How’s the project going?” try “What’s the current status on [project]? Anything blocking progress?”
Even better, establish regular update rhythms so you’re not asking at all. Build status updates into your one on ones or use a shared project tracking system. Then you’re getting the information through a predictable channel rather than through questions that feel like spot checks. If they expect it, it doesn’t feel like you’re checking in on them because you’ve spotted a problem.
When you’re concerned about timing:
Instead of “Have you started yet?” try “Talk me through your timeline for [project]” or “I want to make sure you have enough time for this. How are you thinking about fitting it in?”
This addresses your actual concern, which is probably about capacity and prioritisation, without questioning their ability to manage their own time.
When you want to understand their approach:
Instead of “Are you sure?” try “I want to understand your thinking here. What factors did you weigh?” or “What alternatives did you consider?”
This gets you the same information while demonstrating you trust they’ve thought it through. You’re exploring their reasoning, not doubting their conclusion.
When you’re genuinely worried something’s been missed:
Instead of “Did you remember to X?” try “What’s your checklist looking like for this?”
Or for truly critical items where missing them would be disastrous: “I know this is obvious and you’ve probably already planned for this, but the one thing that would completely derail this is [X]. How are we covering that?”
The acknowledgment that it’s obvious changes everything. You’re naming the importance without suggesting they wouldn’t have thought of it.
The pattern here is consistent: ask about process, planning and thinking. Not about whether they’ve done their job.
You’re being far clearer with your communication, getting to the heart of what you’re really asking.
The mindset shift that matters most
Your job isn’t to verify they’re doing the work. That’s not management, that’s supervision.
Your job is to remove obstacles, provide context, make decisions they can’t make and ensure they have what they need to do great work.
These are completely different orientations. One assumes they need monitoring. The other assumes they’re capable and need support.
This week, I want you to notice the questions you ask your team. Specifically:
- Are you asking about completion of basic tasks they’ve done many times before?
- Are you asking the same question multiple times in a short period?
- Are you asking checking questions rather than questions about their thinking or process?
When you catch yourself, pause. Ask yourself: what information do I actually need here? What am I worried about?
Then reframe the question to get that information in a way that demonstrates trust rather than doubt.
This is harder than it sounds because these questions come from genuine care. You care about the work getting done well. You want to stay informed. You’re trying to be engaged.
But engagement and checking up are different things.
Your team knows the difference, even when you don’t think about it.
Trust them to do what you hired them to do. Ask questions that reflect that trust and get to the heart of what you actually care about.
