Executive Summary Page

When to use

Use this skill once the board narrative is set and you need the single page that opens the pack. It is the right skill whenever a director must be able to read one page, understand the whole story, and know what is being asked of them, even if they read nothing else.

What it does

It produces a self-contained executive summary page: an action title carrying the governing thought, a short framing line, three to five proof points each with a number and a so-what, and a clearly marked ask. The page mirrors the pyramid built by the board-narrative skill and works as the cover argument for the entire pack.

Method

The skill applies the Pyramid Principle to a single page, with answer-first discipline.

1. Lead with the answer. The action title is the governing thought as a full sentence. The reader gets the conclusion in the first line, before any supporting detail.

2. Write one framing line under the title. It states the period and the lens (for example, "Q2 results against the board-approved plan"). It does not argue; it orients.

3. Lay out the proof points as the key-line messages from the narrative. Three is tight, five is the ceiling. Each proof point is one short paragraph or one tight bullet that pairs a fact with its implication. Order them to match the body sections.

4. Attach one number to each proof point. A proof point without a number is an opinion. Round to two significant figures unless precision is the point. Never state a number you cannot trace to a source page in the pack.

5. Make the so-what explicit. After each number, say what it means for the board. "Revenue grew 12 percent" is a fact. "Revenue grew 12 percent, on plan, so the top line is not the issue" is a proof point.

6. State the ask in its own block at the bottom, set apart. Name the decision and what approving it commits the board to. If the page is a read-ahead with no decision, label it "For information" so no one waits for a vote.

7. Cut to fit one page. The executive summary must never spill. If it does not fit, the story is not yet sharp. Push detail down into the body pages and keep only the apex here.

8. Reconcile every claim against the body. Each proof point must be supported by a later page. If the summary says margin is behind, the financial summary page must show it. No claim appears here that is not proven later.

Inputs

• The board narrative skeleton (governing thought, key-line messages, the ask).
• The headline numbers for the period, each with a traceable source.
• The decision or decisions being sought.

Output format

Return the page as structured prose:

• Action title: the governing thought, one sentence.
• Framing line: one sentence stating period and lens.
• Proof points: three to five items, each a fact plus a number plus a so-what.
• The ask: a separate labeled block naming the decision, or "For information" if none.
• Source notes: for each number, the page or system it traces to.

Example

Action title: We are on plan for growth but a quarter behind on margin, so we ask the board to approve a capital reallocation across initiatives.

Framing line: Q2 results measured against the eighteen-month plan the board approved in January.

Proof points:

1. Revenue reached the plan, up 12 percent year over year, so growth is not the concern.
2. Net new customers came in ahead of plan, confirming demand is intact.
3. Operating margin is one quarter behind the recovery curve, driven by three stalled cost initiatives.
4. Two other initiatives are over-delivering and can absorb reallocated capital.

The ask: Approve moving capital from the three stalled initiatives into the two over-delivering ones, as detailed on the capital allocation page. This commits no new funding; it reallocates within the approved envelope.

Source notes: revenue and customers from the KPI scorecard; margin from the financial summary; initiative status from the initiatives tracker.