Imagine this conversation. Your team is preparing to move to a new system. Someone asks whether the existing customer records will transfer across.
You’ve been told the migration is being handled. You haven’t seen confirmation about those particular records. “It should all be fine,” you say.
Maybe it will. But you’ve just given a more confident answer than your information supports. What could you say instead?
“I don’t know yet” is a reasonable start. The useful part is what comes after it: what you’ll check, what people should do in the meantime and when they’ll hear from you again. You don’t need to have every answer to make the next step clear.
Name the gap, rather than making everything uncertain
There’s a difference between “We don’t know what’s happening” and “We haven’t confirmed whether the archived records are included.”
The second sentence gives people a specific question to work with. It also leaves room to explain what is known. In our hypothetical example, you might know that the new system has been selected and training is scheduled. The unanswered question concerns one part of the migration.
Try separating the conversation into what has been confirmed, what remains unconfirmed and what that uncertainty affects.
For example: “The system change is confirmed, and the training date hasn’t changed. I haven’t confirmed whether the archived records are included in the migration. Until I have that answer, I can’t tell you whether we’ll need a separate retrieval process.”
That’s more useful than blanket reassurance. It’s also more precise than presenting the entire change as a mystery.
Check the assumption behind your urge to reassure
You might be thinking: if I don’t have an answer, they’ll lose confidence in me. That’s worth examining rather than accepting automatically.
A 2020 study by Anne Marthe van der Bles and colleagues tested how communicating uncertainty about facts and numbers affected trust. Across five experiments, including a BBC website experiment, the researchers found only small reductions in trust overall, mostly when uncertainty was expressed verbally rather than numerically. The paper is linked in the sources below.
There’s an important limit here. These were studies of factual communication, not trials of managers answering their teams. They don’t prove that saying “I don’t know” always builds workplace trust. They do challenge the blanket assumption that acknowledging uncertainty must destroy credibility.
The practical approach below is a communication exercise, not an intervention tested by that research. Use it to make your answer more accurate and useful, rather than to guarantee a particular reaction.
Give the unanswered question an owner
“I’ll find out” sounds helpful. But what will you actually do? Be specific enough that there’s a real next action.
“I’ll ask the migration lead to confirm whether archived records are included, and whether there’s an exception list.”
Sometimes you’re not the right person to investigate. You can still clarify who is. “The implementation lead owns that question. I’ll raise it with them and bring the answer back to this team.”
Avoid volunteering someone else for a commitment they haven’t accepted. If you still need to establish ownership, say that. “I need to confirm who can authorise that decision. I’ll start there.”
You haven’t solved the problem yet. You have made responsibility clearer.
Explain what people should do while you check
An unanswered question can leave someone unsure whether to continue, pause or improvise. Ask what work depends on the answer.
In the migration example, training might be able to continue while the archive question is checked. Deleting the old records would be a different matter.
A practical response might be: “Continue with the scheduled training. Don’t delete or alter the archived records while we confirm the migration arrangements.”
That example is hypothetical, not technical guidance for an actual migration. In your situation, follow the relevant operational, security and approval requirements.
The wider point is to distinguish work that can proceed from work that needs an answer first. Don’t let “we’re checking” become an instruction for everyone to guess.
Promise an update you can control
There’s a tempting shortcut here: promise the answer by Friday, even though someone else controls it. Instead, commit to the update you can provide.
“I’ll update you by Friday afternoon. If the answer is still outstanding, I’ll tell you what we’ve checked, what’s missing and what we’re doing next.”
Then follow through, including when there’s no final answer. An update could be brief: “The migration lead has confirmed active records are included. Archived records are still being checked. We’ll keep the existing archive unchanged, and I’m escalating the remaining question to the project owner.”
That is progress someone can act on. “Still waiting” gives them much less.
Don’t confuse “unknown” with “not mine to disclose”
Some questions involve information you’re not authorised to share. Others concern decisions that haven’t been made. Those are different from not knowing the answer.
Where appropriate, use accurate language: “That decision hasn’t been made.” “I don’t have confirmed information about that.” “I can’t share those details.” “That sits outside my authority, so I need to refer it to the decision-maker.”
Don’t disguise a confidentiality boundary as a lack of knowledge. Equally, don’t imply that you’re withholding a decision when no decision exists.
For sensitive staffing, legal or safety matters, use the appropriate organisational process. A better sentence isn’t a substitute for it.
Try this before your next team update
Choose one question you haven’t been able to answer. Write four sentences:
1. Here’s what I can confirm.
2. Here’s the specific part I can’t confirm.
3. Here’s who is checking it and what we’ll do meanwhile.
4. Here’s when I’ll update you.
Read them back. Have you slipped in an assumption? Promised an answer you don’t control? Left the team unclear about what to do?
You can be honest about what’s missing and still take responsibility for the next step. That’s a useful place to lead from.
A practical takeaway
Take one unanswered question into your next team update with a clear account of what you know, what you’re checking and when you’ll report back.
Andy Nunn’s signature keynote, The Human Advantage, explores leadership, assumptions and decision-making through change and uncertainty. For teams wanting to apply that thinking to their own situations, explore the Leadership Mindset Workshop. Both are linked below.
Explore further
- The Human Advantage keynote — Explore Andy’s keynote on assumptions and leadership through uncertainty.
- Leadership Mindset Workshop — Practise questioning assumptions and everyday leadership conversations with your team.



