Chapter 5: Questions at Scale

Individual questioning practice, however disciplined, runs into friction when it encounters an organization. Organizations are not passive vessels into which individual behaviors are poured — they are systems with their own dynamics, incentives, and emergent properties that are not reducible to the behaviors of the people in them.

This chapter is about how questioning works at the team and organizational level: what enables it, what destroys it, and what structural interventions have a track record of actually helping.

What “Questioning Culture” Actually Means

The term “questioning culture” appears in many corporate values documents and means very little in most of them. A genuine questioning culture is not one where people feel vaguely encouraged to ask questions — it is one where the structural conditions for good questioning are present and maintained.

Those conditions are:

Psychological safety — the belief that raising a question, especially an uncomfortable one, will not result in punishment or ridicule. Amy Edmondson’s research on this is extensive and consistent: teams with higher psychological safety perform better on complex, interdependent tasks, in part because they surface problems earlier and ask the questions that less safe teams avoid.

Psychological safety is not comfort. It is not the absence of challenge or accountability. It is specifically the safety to voice uncertainty, dissent, and questions without social penalty. A team can have high psychological safety and high standards simultaneously; they are not in tension.

Tolerance for uncertainty — the organizational capacity to sit with open questions rather than forcing premature closure. This is culturally specific and harder to engineer than psychological safety. It requires that leaders model uncertainty tolerance rather than projecting certainty, and that processes make space for questions to remain open while work continues.

Distributed authority to question — the condition in which questioning is not restricted to senior people or designated roles. In organizations where only certain people have the standing to raise certain questions, the question set is constrained to what those people think to ask. This is a structural limitation, not a capability limitation.

None of these conditions are achieved through exhortation. “We value questions here” posted on a wall does nothing. They are achieved through the design of processes, the behavior of leaders, and the consequences (or lack thereof) that follow when people actually ask difficult questions.

The Leader’s Role

Leaders have a disproportionate effect on questioning culture. Their behavior functions as a signal about what is legitimate, and people are highly attuned to these signals — often more attuned than the leaders themselves realize.

There are two behaviors that leaders frequently get wrong.

Answering When They Should Ask

The most common failure mode is the leader who always has an answer. In most rooms, the senior person’s opinion lands with authority that makes it difficult for others to contradict. When that authority is exercised early — before others have had the chance to form and voice their views — it forecloses the inquiry rather than contributing to it.

The practical implication: leaders who want to cultivate a questioning culture should ask more and answer later. Not as theater — but as a genuine attempt to hear what others think before contributing their own view. The question “what are you seeing that I’m not?” is not a rhetorical flourish; it is an acknowledgment that the senior person’s vantage point is incomplete.

Leaders who ask good questions also model that asking is legitimate. The normative power of this modeling is substantial and often underestimated.

Signaling That Questions Are Costly

The second failure mode is the leader who visibly dislikes having their positions questioned. This does not require explicit punishment — it can be as subtle as a slight change in expression, a brisk “we’ve already covered that,” or consistently deprioritizing follow-up on questions that were inconvenient.

People notice. They adjust. Over time, the questions that are raised in that person’s presence converge toward the ones that the leader will find comfortable. This is rational behavior for individuals, and it is devastating for the organization’s ability to find its own errors.

If you are in a leadership role, the relevant question is not “do I encourage questions?” but “what happens when questions are asked that I find uncomfortable?” The answer to the second question is what actually shapes behavior.

Meeting Design

Chapter 3 noted that the standard meeting format is hostile to good questioning. This section examines what to do about it.

Pre-Read and Async Questions

A significant portion of meeting-time questioning is low-quality because it is reactive: people hear something and respond to it in real time without the space to think carefully about what they want to ask. Moving the presentation layer out of the meeting — distributing materials in advance with a genuine expectation that people will read them — changes the dynamic. The meeting time can then begin with questions, not with information transfer.

Async question collection (a written input channel before the meeting) accomplishes two things: it decouples the question from the asker (reducing status anxiety), and it guarantees that questions survive the meeting even if time runs out. The questions submitted in advance are often better than the ones generated in real time.

The Question Phase

Designating an explicit questioning phase — before any discussion of answers or decisions — signals that questioning is a legitimate purpose of the meeting, not a deviation from it. The framing matters: “We’re going to spend 15 minutes generating questions about this proposal before we discuss responses” sets different expectations than “Any questions?”

“Any questions?” almost always produces silence or clarifying questions about minor details. It does not produce the generative questions that would improve the proposal.

Red Teams

For high-stakes decisions, a designated red team — a group explicitly charged with finding the flaws in a plan — is a structural mechanism for getting the questions asked that the proposers won’t ask. The red team’s questions do not need to be brilliant; they need to be thorough and genuinely adversarial.

Red teaming works because it creates a role for criticism that is formally legitimate. Without that role, the social cost of asking adversarial questions is borne by the individual, which suppresses them. With it, the cost is distributed and normalized.

The limitation of red teaming is that it is resource-intensive and tends to be applied only to the largest decisions. For most decisions, lighter structural interventions are sufficient.

Decision Reviews and Post-Mortems

The questions that get asked after a decision differ systematically from the questions that should have been asked before it. Post-mortems are useful primarily because they generate these retrospective questions — and the discipline of running them improves prospective questioning over time.

The main risk in post-mortems is that they become backward-looking in an unproductive way: attributing outcomes to specific individuals or decisions rather than to systemic patterns. A well-designed post-mortem asks “what questions did we not ask?” as prominently as it asks “what went wrong?” The first question is where the learning lives.

Scaling Questioning Practice

When you want questioning to work across a large organization — not just in individual teams or meetings — there are additional challenges.

Coordination across boundaries. The questions that cross organizational boundaries (between teams, between functions, between the organization and its environment) are the ones that most frequently go unasked. Nobody owns them; each party assumes the other is handling them. Explicit mechanisms for cross-boundary inquiry — joint retrospectives, shared question registers, forums for cross-functional problem-finding — are the structural response to this.

Institutional memory of questions. Organizations that have been through significant failures or changes have a set of questions they learned to ask the hard way. This knowledge tends to be informal — in the heads of the people who were there — and gets lost as those people leave. Making the question set explicit (what are the questions we always ask before decisions of type X?) is a form of institutional memory that is more durable than tribal knowledge.

Avoiding the ritualization problem. Any practice that becomes formalized in an organization tends to become ritualized — performed for its appearance rather than its function. The pre-mortem that produces the same list of risks every time because people know what’s expected. The retrospective that covers familiar ground rather than surfacing new problems. The red team that doesn’t actually challenge the proposal.

Ritualization is the enemy of genuine inquiry. The corrective is the same as it is for any ritual: periodically ask whether the practice is producing the outcomes it was designed for. Apply the question-driven method to your questioning methods.

A Note on Scale and Speed

Large organizations tend to move more slowly than small ones, and part of the reason is structural: more stakeholders mean more questions, more review cycles, more inquiry. This is sometimes correctly identified as a problem; the inquiry is disproportionate to the stakes of the decision.

The right frame is not “less questioning” but “better questioning.” The cost of organizational inquiry is proportional to volume, but the value is proportional to quality. An organization that asks twice as many questions is not necessarily doing twice as much useful inquiry — it may be doing less, spread across more people and more time.

What scales well is not more processes for generating questions but better judgment about which questions matter. That judgment is hard to codify, which is why chapter 6 focuses on building it as a habit rather than installing it as a process.

The next and final chapter is about the long-game: how to develop questioning as a durable practice, and how to know whether you’re improving.