The Executive Summary Is Not a Summary

For years, when I thought about the first page of a technical document or report, my mental model was the abstract of a research paper.

An abstract compresses the work. It usually answers some version of these questions:

What was the question?
What did we do?
What did we find?

It also serves a particular reader and purpose. A researcher can read the abstract, skim a few sections, and quickly decide whether the paper deserves a complete read.

That mental model worked well for me for a long time.

The problem started when my work moved from mostly research toward more applied work, and I started using something that looked very similar: the executive summary.

After some struggle, I realized that it was solving a different problem.

Abstract: What does this research say?

Executive summary: What does this mean for us?

That doesn’t mean the abstract is wrong. It is simply serving a different purpose.

In research, something like:

“Model A reduced error from X to Y under these conditions.”

can be a meaningful endpoint.

In a startup, that same statement is often only the beginning.

• Is Y good enough?
• Does it save anyone time?
• Does it reduce cost?
• Is the difference large enough to matter?
• Should we ship it?
• Should we do nothing?

Sometimes the answer is that we still don’t know enough and need another experiment. That is useful too.

The point is that the executive summary cannot just compress the analysis. It has to translate the analysis into its implications.

So the executive summary isn’t just a different literary form. It sits one level above the analysis.

The abstract tells me what the work says.

The executive summary tells me what changes because of it.