EC-301i · Module 1

What Hostile Questions Are Actually Saying

4 min read

A hostile question in an executive room is almost never about the stated subject. "Your data seems weak" is rarely a statement about the statistical validity of the dataset — it is often a statement about the presenter's credibility. "This seems risky" is rarely a pure risk assessment — it is often a statement about a previous experience where something similar went wrong. "I'm not sure this is the right time" is rarely a scheduling concern — it is often a statement that the executive has another priority they prefer to protect.

The presenter who answers only the stated question satisfies the literal challenge without addressing the actual concern. The data skeptic who receives better data does not automatically become a supporter — because the concern was not really about the data. The risk skeptic who receives a comprehensive risk register does not automatically relax — because the concern was not analytically about the risk register. Diagnose the concern behind the challenge before formulating the response.

  1. Identify the surface question What is the executive literally asking? This is the question they articulated. It is real and it deserves a direct answer. But it is not the complete question.
  2. Diagnose the underlying concern Why is this person asking this specific question at this specific moment? What organizational context, personal history, or positional concern is generating this challenge? The underlying concern is what you must address to move the decision forward. The surface question is the access point.
  3. Respond to both Answer the surface question directly and completely. Then name the underlying concern and address it specifically. "Here is the answer to your question about the data. I also want to address the broader concern about whether we have the right evidence to support a deployment decision — here is why I believe we do." The executive who hears their underlying concern named will lean in, not away.

Do This

  • Answer the literal question directly — do not dodge the surface challenge
  • Follow the direct answer with an acknowledgment of the underlying concern
  • Ask a clarifying question if you are uncertain what the underlying concern is: "Is the concern about the data quality specifically, or about whether we have enough data to support a deployment recommendation?"

Avoid This

  • Answer only the surface question and assume the concern is resolved — it is not
  • Assume the stated reason for the question is the actual reason — it usually is not
  • Respond defensively to the hostile framing — the framing is not the question