Ignorance vs. Ineptitude

Definition

Drawing on philosophers Samuel Gorovitz and Alasdair MacIntyre, the book distinguishes two reasons we fail at things that are genuinely within our power to accomplish: ignorance, where science has only given us partial understanding, and ineptitude, where the knowledge exists but we fail to apply it correctly. For nearly all of history, ignorance dominated; in the last several decades, accumulated knowledge has grown so fast that ineptitude — the gap between what we know and what we reliably do — has become the bigger problem.

In the Book

Gawande opens with two surgical near-catastrophes told to him by a surgeon friend: a stabbing victim whose team did everything right except ask what weapon was used, and a routine stomach-cancer operation where the patient's heart stopped from a hundred-fold potassium overdose. Neither failure came from not knowing what to do — the relevant facts (ask about the weapon, watch for potassium toxicity) are textbook knowledge. He extends this into the heart-attack case study: in the 1950s we didn't know about blood pressure, cholesterol, or how to treat a heart attack (pure ignorance); today we have a dozen effective therapies, but applying all of them correctly, on every patient, every time, is where care now fails. The same shift shows up in the sheer volume of medical knowledge — one in-house study he cites found internists were now managing an average of a thousand-plus diseases, conditions, and clinical variables per patient population, far beyond what any single practitioner can reliably hold in mind. The book's diagnosis of modern failure is therefore not "we don't know enough" but "we know but don't consistently do."

Why It Matters

This distinction reframes what kind of intervention a failure calls for. If a system fails from ignorance, the fix is research — more knowledge. If it fails from ineptitude, more knowledge is useless; the fix has to be a mechanism that makes reliably applying existing knowledge easier than forgetting or skipping it. Recognizing which failure mode you're actually facing prevents the common mistake of throwing more expertise, training, or information at a problem that is actually a consistency and execution problem.