Introduction: We Have an Answer Problem

In 1965, Intel didn’t exist. Fairchild Semiconductor did, and it employed most of the people who would later build the semiconductor industry. At some point during that era, a young engineer named Gordon Moore noticed something odd: the number of components on an integrated circuit had been doubling roughly every year. He wrote a paper about it. He asked, in effect: if this pattern holds, where does it go?

The observation became Moore’s Law. The question behind it shaped the next five decades of computing.

Moore wasn’t smarter than his colleagues. He had access to the same data they did. What he did differently was ask a question nobody else had bothered to frame.

This book is not about answers.

Answers are everywhere. Search engines return them in milliseconds. Language models generate them faster than you can read. The bottleneck has never been more clearly visible: it is not the supply of answers, but the quality of questions that precede them.

A good answer to the wrong question is worse than useless — it’s a distraction with a confidence rating attached.

The skill that actually compounds is knowing which questions to ask. Not the reflexive questions that arrive automatically when you encounter a problem. Not the polite questions that fill time in meetings. The generative questions — the ones that, once posed, make it hard to un-see what they’ve revealed.

This is a trainable skill. The evidence for this is everywhere: in the careers of people who consistently produce original work, in the structure of scientific discovery, in the design of institutions that do not stagnate. In all cases, there is a questioning practice underneath the results. It is rarely accidental and almost never unteachable.

What makes it feel unteachable is that it gets conflated with intelligence, or creativity, or personality. “Some people are just naturally curious.” True, as far as it goes. But curiosity is a disposition, and questioning is a technique. You can be highly curious and ask terrible questions. You can be methodical and uninspired and develop the habit of asking the right ones.

What This Book Covers

The chapters that follow are organized around a practical progression:

Chapter 1: The Anatomy of a Good Question — What properties distinguish a question worth asking from one that isn’t. Specificity, falsifiability, generativity, scope. Not all questions are equal, and learning to evaluate them is the first step to generating better ones.

Chapter 2: Finding Questions Worth Asking — The harder problem: not evaluating questions you’ve already formed, but finding the ones that haven’t occurred to anyone yet. This is where most of the leverage is, and most of the techniques are counterintuitive.

Chapter 3: Why Nobody’s Asking — The cognitive and social mechanisms that suppress questioning. Confirmation bias, status anxiety, expertise traps, meeting culture. Understanding why good questions don’t get asked is essential to getting them asked.

Chapter 4: Question-Driven Thinking in Practice — Applied techniques. Pre-mortems, assumption audits, Socratic method adaptations, working backwards from conclusions. The day-to-day mechanics of thinking with questions rather than despite them.

Chapter 5: Questions at Scale — How questioning works (and fails) in teams and organizations. Meeting design, review culture, what leaders do that either enables or extinguishes honest inquiry.

Chapter 6: Building the Habit — Making it stick. The question journal, daily calibration, the difference between asking more and asking better.

A Note on Voice

This book does not celebrate curiosity as a virtue or wonder as a mindset. It treats questioning as a technical discipline with identifiable components, known failure modes, and practices that improve performance. If you want inspiration, there are plenty of other books. If you want a working method, read on.

The examples are drawn from software, science, strategy, and a handful of places where the cost of asking the wrong question — or not asking at all — was unusually visible. None of them require domain expertise to follow. They’re here because clarity beats abstraction, and specificity beats encouragement.

One more thing: this book will not tell you to “ask more questions.” You probably already ask plenty. The goal is to ask better ones, fewer of them, and in the moments that actually matter. Volume is not the point. Precision is.

Let’s start with what a good question looks like.