A Question Is Not an Accusation: Why Curiosity Needs Protecting

A question is usually a request for understanding, not an attack on competence or integrity. Questions help the asker learn, force the answerer to test their reasoning, and build shared understanding across the room. Defensiveness comes from confusing ideas with identity, so answer the substance of the question first.

1. The moment the room changes

Most of us have sat in this meeting. Someone has spent weeks on a proposal, working through the options, talking to the people who matter and landing on what they genuinely believe is the right answer, and about ten minutes into the presentation somebody asks a perfectly ordinary question: “Why did we choose this approach?” You can feel the temperature drop. The presenter starts listing how much work went into it, how many people were consulted and how carefully the alternatives were weighed, and their tone makes it fairly clear that they heard something very different from what was actually said.

What was actually said was a question. Nobody accused the presenter of being incompetent, nobody suggested the work was sloppy or dishonest, and nobody questioned their motives or their integrity. Someone simply asked why, and in a surprising number of organisations that is enough to be heard as a challenge to a person’s credibility. I think this is one of the more damaging habits a culture can fall into, because once questions start to feel dangerous people stop asking them, and an organisation that stops asking questions slowly loses its ability to find out what is actually true. The irony is that the person who asked may well have been doing the presenter a favour.

2. Why people ask questions they already know the answer to

We tend to assume a question means the person asking doesn’t know the answer, but that is a narrow view of what questions do in a room full of people. A question helps the asker learn, it forces the person answering to articulate and test their own reasoning, and, most usefully and most often overlooked, it lets everyone else in the room build the same understanding at the same time.

Picture a meeting of ten people where three understand the subject deeply, four have a reasonable grasp of it and three are quietly lost. One of the experts asks what sounds like a basic question: “Can you walk us through why we need this extra layer of security?” The presenter’s instinct might be irritation, because the person asking obviously knows the answer. But the question probably wasn’t for the expert at all. It was for the three people who were too embarrassed to admit they hadn’t followed, and it handed the presenter a clean opportunity to explain the reasoning in a way that actually strengthens confidence in the decision. That isn’t an attack; it is a quiet piece of leadership, and the person answering should recognise it as one.

I do this deliberately, and I’d encourage anyone senior to do the same, because asking the “obvious” question from the front of the room gives everyone else permission not to know things. The distinction that matters is intent. A question designed to expose someone’s ignorance and a question designed to create shared understanding can use exactly the same words, and the difference sits almost entirely in the tone, the motive and the environment the question lands in.

3. Why we get defensive

If questions are this useful, it’s worth being honest about why we react so badly to them, and I think the answer is that we confuse our ideas with our identities. When someone questions a decision we made, it can feel like a verdict on our competence; when someone asks about our reasoning, it can feel like a verdict on our intelligence; and when someone asks whether something was done properly, it is very easy to hear a comment about our integrity. All of this gets worse in public, because now there is an audience of peers and senior leaders, and answering a question stops feeling like explaining something and starts feeling like defending a reputation.

Once that shift happens, we stop engaging with the question and start analysing the person who asked it. Why are they asking this, what are they implying, are they trying to undermine me? The original question, which may have been entirely reasonable, becomes almost irrelevant, and we end up responding to an accusation that may only exist in our own interpretation. To be fair, some questions really are accusations dressed up as curiosity, and people can absolutely use questions sarcastically or as a weapon. Psychological safety doesn’t ask us to pretend otherwise. It asks us to answer the substance of the question before we react to the motives we imagine sit behind it.

4. When the question is about a person

The hardest version of this is when the decision being questioned is about someone’s career. Picture a performance calibration session where a manager tells the room that an engineer everyone rates highly will be marked down this cycle and quietly taken off the list for the next senior role. Nobody says it out loud, but you can watch the same thought cross every face: this isn’t about performance, these two simply don’t get on. Someone asks why, and the manager gives the kind of answer that sounds reasonable and says almost nothing, something like “there are a few areas they still need to grow in”, followed by a reassurance that it really isn’t personal.

That answer doesn’t settle the room; it makes things worse, because a vague explanation for a surprising decision is exactly what people expect to hear when the real reason is one nobody wants to say. So the right move is to push, politely but firmly, and ask which areas, specifically, and what evidence the decision rests on. The manager will very likely feel ambushed, and the follow up will feel like a challenge to their judgement in front of their peers. It isn’t. It is the only route available to protect the manager’s credibility as well as the engineer’s career, because if the reasoning is sound, being specific is the quickest way to prove it, and if it isn’t sound, the room needs to find that out before someone’s trajectory is redirected on the strength of it.

It is worth being careful about what you are asking for. There are genuinely private matters, such as health or personal circumstances, that don’t belong in a group forum, and a good manager can say so plainly (“there’s context I can’t share here, but HR is aware”) without being evasive. “Needs to develop” isn’t that. Development areas are, by definition, things that can be named, evidenced and worked on, and if they can’t be named in a room of senior leaders, it is hard to see how they are being explained to the person whose career they affect.

What happens afterwards matters just as much. If the manager was visibly uncomfortable, the worst outcome is that they leave thinking they were attacked, and the second worst is that the discomfort quietly ends the conversation. A private word afterwards can do both jobs: it makes clear that nobody was questioning their right to make the call, that the room simply didn’t understand the reasoning, and that decisions about people’s careers carry an obligation to give an account of your thinking in the open, where it can be tested and debated. That isn’t a punishment for being challenged; it is the standard every people decision should be held to, and a leader who meets it once usually finds it much easier the next time.

5. What the research actually says about speaking up

None of this is just intuition, and the research on employee voice is worth knowing because it explains why the problem is so stubborn. I’ve tried to describe each study for exactly what it found and no more, because this is a field where findings get stretched a little further with every retelling.

Amy Edmondson’s 1999 paper, Psychological Safety and Learning Behavior in Work Teams, is the foundation most people cite. She defined team psychological safety as a shared belief that the team is safe for interpersonal risk taking, and studied 51 work teams in a manufacturing company. Teams with higher psychological safety showed more learning behaviour, meaning things like seeking feedback, asking for help and talking openly about errors, and that learning behaviour mediated the relationship between psychological safety and team performance. Team efficacy, the team’s belief in its own capability, was not associated with learning behaviour once psychological safety was controlled for. It is a field study, so it shows association rather than proving causation, but the pattern is consistent with the argument here: confidence on its own doesn’t seem to produce learning, whereas feeling safe enough to expose what you don’t know does appear to.

The silence research is, if anything, more uncomfortable reading. In 2003 Frances Milliken, Elizabeth Morrison and Patricia Hewlin interviewed 40 employees about issues they had chosen not to raise, and 85% described at least one situation where they felt unable to raise a concern with a supervisor even though they believed it was important. The reason given most often was fear of being viewed or labelled negatively, and of damaging relationships they valued as a result. It’s a small qualitative study that the authors themselves framed as exploratory, so I wouldn’t treat that 85% as a population statistic, but the reasons people gave map almost perfectly onto the meeting I described at the start.

James Detert and Amy Edmondson pushed this further in 2011 with what they called implicit voice theories, which are taken for granted beliefs about when and why speaking up at work is risky or inappropriate. Across four studies they found these beliefs were widely held, and that measures of five of them added meaningfully to the explanation of workplace silence beyond the factors researchers usually look at. One of those five is, in effect, “don’t embarrass the boss in public”. That tells you a lot of people walk into meetings already believing that a pointed question in front of others carries a career risk, and they may hold that belief before any leader in the room has done anything to earn it. For leaders this matters a great deal, because it suggests a neutral reaction to questions probably isn’t enough to undo assumptions people arrived with; you have to visibly demonstrate that questions are welcome.

There is also some useful evidence on the fear of looking stupid. Alison Wood Brooks, Francesca Gino and Maurice Schweitzer found in 2015 that people often avoid seeking advice because they worry it will make them look incompetent, yet in their experiments the people being asked rated the advice seeker as more competent, not less. That effect showed up when the task was difficult and when people were asked for advice personally, and it disappeared for easy tasks, where asking neither helped nor hurt. Asking for advice isn’t quite the same thing as asking a question in a meeting, so I’d hold this one loosely, but it does suggest the reputational cost we imagine for asking is often larger in our own heads than in anyone else’s.

Finally, Elizabeth Morrison’s reviews of the voice and silence literature, first in 2014 and again a decade later in 2023, pull together a very large body of work on when people speak up and when they hold back. The broad picture is that silence deprives organisations of information they need, and that simply encouraging people to speak isn’t sufficient; the environment has to make speaking up feel both safe and worthwhile. The later review highlights a study by Sherf, Parke and Isaakyan suggesting that voice and silence may not be simple opposites, with speaking up responding most to whether people believe it will make a difference and staying silent responding most to psychological safety. If that holds, it has a practical edge: telling people their questions are welcome addresses one side of the problem, but actually acting on what they raise, and never making them regret raising it, addresses the other.

What this research doesn’t show is that every question is well intentioned, or that difficult questions always lead to better decisions. What it does support is that people routinely hold back information they think matters, that fear of how they’ll be seen is a major reason why, and that teams where people feel safe to expose uncertainty tend to learn more.

6. Silence is not agreement

The practical consequence is that a quiet room is incredibly easy to misread. A meeting where nobody asks anything looks exactly like a meeting where everybody agrees, and leaders who prefer the comfort of the first will often mistake it for the second. Silence isn’t agreement, it isn’t understanding, and it certainly isn’t evidence that a decision is correct. An organisation that discourages questions isn’t creating alignment; it is creating the appearance of alignment, and the gap between those two things tends to surface later, during execution, when it is far more expensive to close.

Anyone who has spent time reading incident reviews will recognise the pattern. Many of the postmortems worth learning from aren’t about a cause nobody could have seen; they are about a signal somebody did see, weeks earlier, and either kept to themselves or raised once and had waved away. Most organisational failures don’t come from a complete absence of intelligence or expertise. They come from information that existed somewhere in the organisation but never surfaced effectively, because nobody asked, or somebody asked and was dismissed, or the person holding the concern decided that raising it simply wasn’t worth the personal cost. In a complex organisation nobody holds the full picture of every system and every decision, so we depend on collective intelligence, and collective intelligence quietly stops working when people are afraid to reveal what they don’t know or to challenge what others claim to know.

7. Difficult questions are a gift

It is worth comparing two versions of the same meeting. In the first, a proposal is presented, everyone nods, nobody challenges anything and the meeting ends in apparent agreement. In the second, the same proposal is presented and people ask about the assumptions, the alternatives, the risks, the costs and the second order consequences, and while some of the answers are straightforward, others reveal areas that clearly need more work. The first meeting probably felt better for everyone involved, but the second was far more likely to improve the decision.

The purpose of a meeting shouldn’t be to protect the confidence of the person presenting; it should be to improve the collective understanding of the people in the room. Seen that way, a difficult question isn’t something to survive but something to welcome, because the outcome is good either way. If you have a strong answer, the question gives you the chance to explain it and build confidence in the decision. If you don’t, the question has just shown you something important while it is still cheap to fix.

8. How you answer teaches more than what you say

Building a culture of curiosity isn’t only about encouraging people to ask questions; it is just as much about teaching people how to receive them, and this is where leaders have a disproportionate amount of influence. Imagine a senior leader being asked something they consider obvious and replying, “We’ve already covered this”, or “I’m surprised you’re asking that”, or saying nothing harsh at all but letting the irritation show in their face and tone. The person who asked feels embarrassed, everyone else in the room notices, and the whole group learns a lesson that has nothing to do with the subject under discussion and everything to do with the cost of asking.

Now imagine the same leader saying, “That’s a useful question, let me explain the reasoning”, or “I’m glad you raised that, because we should all be clear on it”, or simply walking through how the decision was reached. That response tells the room that questions are welcome, that understanding matters more than appearances, and that the leader’s authority isn’t so fragile it needs protecting from curiosity. In my experience the ability to answer a hard question calmly is one of the strongest signals of real competence there is, because people who understand their subject deeply usually enjoy the chance to explain it, and they don’t need everyone to accept their conclusions on trust. When they don’t know the answer, they can say, “I don’t know, but that’s a good question, so let’s find out”, and there is nothing weak about that at all; it is simply intellectual honesty.

9. There is no such thing as an obvious question

One of the most quietly destructive responses to a question is “Surely you know that?”, because it assumes the answer is obvious and therefore the question was unnecessary. The obvious follow up is: obvious to whom? What is obvious to someone with twenty years in the organisation can be completely unfamiliar to someone who joined last month, what is obvious to a specialist can be impenetrable to someone from another discipline, and what is obvious to the people who made a decision is often anything but obvious to the people expected to implement it.

Even when everyone should know the answer, that doesn’t mean everyone does. Someone asking an apparently obvious question might genuinely not understand, might have forgotten, might have spotted an inconsistency, might be checking an assumption, or might be asking on behalf of someone else who wouldn’t. None of those possibilities justifies embarrassment or hostility, and the right response in every case is simply to answer. If the answer really is obvious, explaining it should be easy, and if explaining it turns out to be surprisingly hard, the question was probably more valuable than it first appeared. Questions don’t become harmful because the answer should already be known; the harm comes from an environment where people are afraid to ask.

10. Separate the person from the proposition, then go looking for challenge

Underneath all of this sits one principle: challenging an idea is not the same as challenging the person who proposed it. A decision can be questioned without questioning the integrity of whoever made it, a strategy can be challenged without questioning its author’s intelligence, and a process can be scrutinised without accusing its owner of negligence. We need to get much better at holding those apart, because when our identity becomes fused with our recommendations, changing our minds starts to feel like losing, and we end up defending decisions simply because they are ours. A healthier view is that our ideas are provisional, representing our best understanding at a moment in time on the information we had, and that changing our minds in the face of better evidence is a strength rather than an admission of failure.

Cultures aren’t built by posters or values statements; they are built through repeated behaviour, particularly the behaviour of the people with authority. If a leader says questions are encouraged but becomes visibly irritated when their own reasoning is challenged, the organisation will quickly work out which message is the real one. So the most useful thing a leader can do at the end of a presentation is to stop asking “Does everyone agree?” and start asking questions that actively invite challenge, such as “What haven’t we questioned yet?”, “Which assumption would hurt us most if it turned out to be wrong?” or “What would someone who disagrees with this say?” Questions like those change the purpose of the conversation from seeking approval to seeking insight, and they turn disagreement from a threat into part of how a better decision gets made.

11. Thank the person who asks

The next time someone asks you a question that feels obvious, unnecessary or uncomfortable, try a different interpretation before you reach for a defence. They might genuinely not know the answer, they might see something you’ve missed, they might want to understand your reasoning, or they might already know the answer and be giving you the chance to explain it to everyone else. Before getting defensive, it is worth asking yourself one simple question: what if this person is trying to help? In most cases they are, and even when the question is genuinely challenging, the opportunity is the same, because you get to explain your reasoning, establish the facts, correct a misunderstanding, discover a weakness in your own thinking or bring the whole room onto the same page.

The best organisations don’t just tolerate difficult questions, they go out of their way to invite them, and the best leaders don’t measure a meeting by how few questions they received but by how much clearer everyone is when it ends. A question is not an accusation; it is an invitation to build shared understanding, and the leaders who get this right don’t just encourage people to ask difficult questions, they make people glad they asked.

References

1. Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350 to 383. https://doi.org/10.2307/2666999
2. Milliken, F. J., Morrison, E. W., and Hewlin, P. F. (2003). An Exploratory Study of Employee Silence: Issues that Employees Don’t Communicate Upward and Why. Journal of Management Studies, 40(6), 1453 to 1476. https://doi.org/10.1111/1467-6486.00387
3. Detert, J. R., and Edmondson, A. C. (2011). Implicit Voice Theories: Taken-for-Granted Rules of Self-Censorship at Work. Academy of Management Journal, 54(3), 461 to 488. https://doi.org/10.5465/AMJ.2011.61967925
4. Brooks, A. W., Gino, F., and Schweitzer, M. E. (2015). Smart People Ask for (My) Advice: Seeking Advice Boosts Perceptions of Competence. Management Science, 61(6), 1421 to 1435. https://doi.org/10.1287/mnsc.2014.2054
5. Morrison, E. W. (2014). Employee Voice and Silence. Annual Review of Organizational Psychology and Organizational Behavior, 1, 173 to 197.
6. Morrison, E. W. (2023). Employee Voice and Silence: Taking Stock a Decade Later. Annual Review of Organizational Psychology and Organizational Behavior, 10, 79 to 107. https://doi.org/10.1146/annurev-orgpsych-120920-054654