Reference

Templates and checklists for executive communication

Part of the Executive Communication skill · loaded on demand from SKILL.md

Read this when producing any deliverable from this skill. Placeholders in square brackets are allowed here and nowhere else; the worked example shows each template filled.

Contents

  1. Audience and decision sheet
  2. SCQ introduction
  3. Pyramid worksheet with horizontal-logic check
  4. Dot-dash storyline
  5. Ghost deck table and exhibit spec
  6. Action-title test card
  7. One-page executive summary
  8. Memo
  9. Speaking notes
  10. Objection table
  11. Pre-wiring plan
  12. Rhetoric annotation
  13. Partner review checklist
  14. Hand-off pack for pptx and docx

1. Audience and decision sheet

Decision to be taken: [one sentence, with the date and forum]
Decision-maker: [name, role]
Question in the audience's words: [one sentence]
Format: [deck read in advance and presented | memo read alone | spoken briefing] Time: [minutes]

| Person | Role in decision (decides / must agree / advises / executes) | Current belief | Stands to lose or gain | Trusts | Briefed |
|---|---|---|---|---|---|
| [name] | | | | | [yes/no, date] |

2. SCQ introduction

Situation: [one or two sentences the reader already accepts; no new information]
Complication: [what changed or went wrong; the trigger for the work]
Question: [the exact question the complication raises, in the audience's words]
Answer (governing thought): [one sentence, under 35 words, a claim that can be false, with a number and a time frame]
Question pattern: [something went wrong / might go wrong / we know what to do, how / we did it and it failed, why / which option]

3. Pyramid worksheet with horizontal-logic check

Governing thought: [sentence]
Reader's next question: [Why? / How? / How much? / Which?]

Key line, relationship: [deductive | inductive]
  If deductive, written as: [A]. [B, which comments on A]. Therefore [C].   Steps: [n, max 4]
  If inductive, plural noun: [e.g. "three sources of margin loss"]   Order: [time | structure | degree], because [reason]
  Summary test: the sentence above the group states [what they have in common / what they imply], not a count.

  1. [key-line point, full sentence]
     Reader's next question: [ ]
     Support, relationship: [deductive | inductive], plural noun / chain: [ ]
       - [evidence, with number] [have / pending / assumed]
       - [evidence]
  2. [key-line point]
     ...
  3. [key-line point]
     ...

Removal test: remove key-line point [n]. Does the governing thought fall? [yes: deductive as intended / no: inductive, present as such]
MECE test: overlaps [none / list]; gaps a reader will notice [none / list]

4. Dot-dash storyline

# Storyline: [client], [meeting], [date]
Governing thought: [sentence]

1. [Slide message as a full sentence; becomes the action title]
   - [evidence with number] (exhibit: [type]) [have / pending / assumed, owner, due]
   - [evidence]
2. [Slide message]
   - ...
...
Appendix: [list of supporting pages not in the storyline]

Rules applied: every dot has at least one dash; every dash supports its dot; every pending dash has an owner.

5. Ghost deck table and exhibit spec

| # | Action title | Exhibit: type, axes, the one comparison the eye must make | Source | Status (have / pending / assumed) | Owner |
|---|---|---|---|---|---|
| 1 | [title] | [e.g. margin bridge, FY22 to FY25, two bars: gross margin, opex] | [GL, transaction data] | | |

Exhibit spec for each slide:
- Title: [action title, the claim]
- Chart type: [bar / line / waterfall / scatter / table / diagram]
- What the eye must compare: [e.g. Northgate's dot against the peer median line]
- Data: [series, period, unit, source, date pulled]
- Annotation: [the one number to call out]
- Source line: [as it will appear on the slide]
- Fallback if the data comes back the other way: [what the title becomes]

6. Action-title test card

Apply to every title. Any fail means rewrite.

Title: [ ]
[ ] Claim: the title can be true or false.
[ ] One idea: cover the body, the title stands alone; cover the title, the body proves only that.
[ ] So-what: the title answers "so what?" rather than inviting it.
[ ] Specific: it could not sit over another client's slide unchanged; numbers where they exist.
[ ] Short: two lines, about 25 words or fewer.
[ ] Provable: every number in the title points to an element on this slide.
[ ] Sequence: read after the previous title and before the next, it links without "this" or "above".
[ ] No filler: no "overview", "analysis of", "key insights", "deep dive", "update on".
Rewrite if needed: [ ]

7. One-page executive summary

[Client]: [recommendation as a title, e.g. "Recovering margin through pricing and mix"]
[Forum, date]

[Situation sentence(s). Complication sentence(s). The question this work answers.]

[Answer: the governing thought as the first sentence. Then the key line compressed into two or three sentences with the headline numbers. Then the decisions needed, in one sentence.]

1. [Key-line point 1 as a sentence.] [Two to four sentences of evidence with numbers.]
2. [Key-line point 2.] [...]
3. [Key-line point 3.] [...]

Decisions requested: (1) [decision, owner, date]; (2) [ ]; (3) [ ].

Risks and unknowns: [the two or three risks with their mitigations; what was not analysed and why it does not change the answer].

Method: [data, sample sizes, reconciliation, interviews, peer set], one or two lines.

Checks: first sentence of paragraph two is the recommendation with a number and a time frame; every number appears in the deck; hedging matches the deck; readable in ninety seconds.

8. Memo

To: [decision-maker]   From: [team]   Date: [ ]
Subject: [the recommendation, not the topic]

[SCQ paragraph]

[Answer paragraph: governing thought first, then the key line in two or three sentences]

## [Key-line point 1 as a heading that is a claim]
[Three to five sentences of evidence. Numbers. Source in parentheses.]

## [Key-line point 2]
[...]

## [Key-line point 3]
[...]

## What we are asking you to decide
[Numbered decisions with owners and dates]

## What we do not know
[Unknowns, their possible effect on the answer, and how they will be resolved]

## Next steps
[The first 30 to 90 days, with owners]

Attachments: [deck, model, appendix]

9. Speaking notes

Slide [n]: [action title]
Say (one sentence): [ ]
Number to say aloud: [ ]
Point to: [the element on the slide]
Transition to next slide: [one sentence that links this title to the next]
Likely question, and from whom: [ ]
Answer, and the slide to turn to: [ ]
Time: [seconds]

Elevator version (30 seconds): [governing thought plus one reason plus the ask]
Five-minute version: [governing thought, key line, decisions]

10. Objection table

| Who | Objection (in their words) | Evidence that answers it | Slide | Fallback if not persuaded |
|---|---|---|---|---|
| [name] | "[ ]" | [ ] | [n] | [pilot, phasing, independent check, reframing] |

Rules: one row for every decision-maker and for the most senior sceptic; every answer cites a slide; every fallback is something the team is willing to offer in the room.

11. Pre-wiring plan

| Order | Person | Date | Shown (summary plus which slides) | Expected objection | Outcome and changes made |
|---|---|---|---|---|---|
| 1 | [data owner or ally] | | | | |
| 2 | [sceptic] | | | | |
| ... | | | | | |
| n | [most senior decision-maker, briefed on what the others said] | | | | |

Rules: allies and data owners first; sceptics next, in private; the decider last; thirty minutes each with the summary and the slides that concern them; record every dispute and every change; if the recommendation will not survive, change the recommendation.
Unbriefed attendees and why: [ ]

12. Rhetoric annotation

Mark the storyline with where each is delivered.

Ethos: method visible at [slide]; limits and unknowns at [slide]; reconciliation to audited figures at [slide]
Pathos: concrete case (one branch, one customer, one order) at [slide]; cost of inaction in the audience's terms at [slide]
Logos: section 3 worksheet complete [yes/no]
Arrangement: proem (SCQ) [minute 0-1]; statement (governing thought, key line) [1-3]; proof (body) [3-x]; refutation (known objections) [slide n, before decisions]; epilogue (decisions, next steps, cost of not deciding) [final slide]

13. Partner review checklist

[ ] Titles only, top to bottom, form the argument with the answer first.
[ ] The governing thought can be false, has a number and a time frame, and passes the elevator test.
[ ] SCQ contains nothing the reader will dispute and ends in the question the audience asked.
[ ] Every group is named by a plural noun or written as a chain; every summary is a claim, not a count.
[ ] Deductive chains are four steps or fewer; removal test run on the key line.
[ ] Every title number is proved on its slide; every summary number is in the deck.
[ ] Hedging in the summary matches the deck.
[ ] Refutation sits before the decisions slide.
[ ] Objection table has the most senior sceptic and cites slides.
[ ] Pre-wiring plan covers everyone in the room; outcomes recorded.
[ ] Deck survives with charts removed.
[ ] Method, limits and unknowns are stated (ethos); one concrete case and the cost of inaction are present (pathos).
[ ] Titles unchanged after rendering.

14. Hand-off pack for pptx and docx

One document containing, in order: the storyline with final titles (section 4); the ghost deck table and exhibit specs with every status "have" (section 5); the executive summary and memo text (sections 7 and 8); the speaking notes (section 9); house style (template, fonts, colour rules, source-line format); the appendix list with sources; and one instruction to the renderer: titles are fixed sentences, and a title that must be shortened to fit is returned for re-test, not edited.