The McNamara Fallacy

The Fallacy Defined

The McNamara Fallacy proceeds in four steps, as articulated by Daniel Yankelovich^[1]:

1. Measure whatever can be easily measured. This is fine as far as it goes.
2. Disregard what cannot be measured easily. Give it little or no weight.
3. Presume that what cannot be measured easily is unimportant. This is the critical error.
4. Presume that what can be measured easily is important. This completes the inversion of priorities.

The result is a decision-making framework that is internally consistent, data-driven, and completely wrong about what matters.

Historical Context: Vietnam War

Robert McNamara, a former Ford Motor Company executive who brought statistical analysis to the Pentagon, applied quantitative management techniques to the Vietnam War. Key metrics included:

• Body counts — enemy soldiers killed per engagement.
• Kill ratios — enemy vs. U.S. casualties.
• Sortie rates — bombing missions flown per day.
• Defector rates — Viet Cong surrendering under the Chieu Hoi program.

By these metrics, the U.S. was winning. Body counts were favorable, kill ratios were lopsided, and the bombing campaign was the largest in history. Yet the strategic situation deteriorated. The metrics measured tactical efficiency while completely missing strategic effectiveness:

• Body counts said nothing about political will.
• Kill ratios said nothing about the nature of a guerrilla war where "winning" a battle meant the enemy melted into the population.
• Sortie rates said nothing about whether bombing was converting civilians to the enemy's cause.

"Every quantitative measurement we had showed we were winning the war. Of course, we weren't. We were losing." — Robert McNamara, In Retrospect^[2]

The Fallacy in Business

The McNamara Fallacy is not confined to military strategy. It appears wherever quantitative metrics dominate decision-making:

Relationship to Efficiency vs. Effectiveness

The McNamara Fallacy is the "Efficient but Ineffective" quadrant of The Difference Between Efficiency and Effectiveness made concrete:

• Efficiency metrics are easy to define, collect, and compare. They give the illusion of control and objectivity.
• Effectiveness is harder to measure. It requires judgment, context, and qualitative assessment.
• The fallacy is to let the ease of measurement drive what you consider important — to mistake the map for the territory.

Drucker's warning — "no amount of efficiency can compensate for a lack of effectiveness" — is the McNamara Fallacy in a single sentence.

Defending Against the Fallacy

1. Ask what is not being measured. Every dashboard has blind spots. Name them explicitly.
2. Use qualitative alongside quantitative data. Stories, observations, and expert judgment are not inferior to numbers — they capture different information.
3. Test metrics against outcomes. Does improving this metric actually improve the real-world goal?
4. Rotate what you measure. No single metric should dominate for long.
5. Remember Goodhart's Law. Goodhart's Law warns that once a metric becomes a target, it ceases to be a good measure — the McNamara Fallacy is what happens when you forget this.

See Also

• The Difference Between Efficiency and Effectiveness — The Drucker distinction that diagnoses the fallacy's root cause.
• Goodhart's Law — The mechanism by which metrics corrupt the systems they measure.
• The Balanced Scorecard (Kaplan & Norton) — A framework designed to resist the McNamara Fallacy by balancing financial, customer, process, and learning metrics.
• Chesterton's Fence — A principle that warns against removing (or ignoring) what you don't understand.

References