Plan the reading order
Supply the audience, decision, source material and required coverage. Review the outline before generating. For a QBR, keep results, variance, risks and next decisions distinct instead of mixing them into a status collage.
Executive Summary Slide
An executive summary slide answers four questions on one slide: what happened, what it means, what we recommend, and what we need from you. It goes immediately after the title slide, and it should be complete enough that an executive who reads only that slide can act correctly.
Last reviewed: August 2026
Lumen · real output
Read the deck before you choose the workflow.
Open an actual exported deck, then compare its outline, source constraints and slide choices with the job you need to finish.
Governing Cybersecurity Risk: An Executive Briefing on NIST CSF 2.0
A 10-slide briefing for an organisation’s leaders on NIST’s Cybersecurity Framework 2.0, built only from the framework document: the six Functions as a set with Govern at the centre, what Govern covers, questions leaders can ask their teams, how Current and Target Profiles show the gap to close, and the four Tiers. It describes no company, so it has no performance data.
Inspect the source brief or data
A briefing for the executive leadership of an organisation of any kind; no company is named and none is described. Cover, in this order: what the framework is and why leaders should care; the six Functions, shown together as a set with Govern at the centre, with no numbering or order because the document says they are addressed concurrently; what the Govern Function covers, using the document's own list of Govern topics; questions leaders can ask their teams, in the document's own terms; what Current and Target Profiles are and how comparing them shows the gap to close; the four Tiers by name; and what to ask for next. Do not show any process as numbered steps. Say executives, leaders or the organisation wherever the document does: it mentions boards of directors only as readers, so do not give a board any role the document does not give it. Give at most one slide to how different kinds of organisation use the framework. Use only the supplied document. Where it gives no figure, date or finding, do not supply one: use no placeholders, no illustrative numbers and no made-up status data. Pictures should show technology, infrastructure or abstract subjects, not people. Workflow: Corporate executive. 10 slides requested. Document supplied as text (NIST, "The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 (26 February 2024)", https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf).
Read the sample review notes
A separate reviewer agent read the deck’s 70 claims, slides and speaker notes, against the framework document: 62 are supported, 8 loosen or go a little beyond its wording, and none is missing from it or contradicts it. 19 of the 70 are advice the deck gives, and all 19 are supported. It is not a person’s review.
Refine at the right scope
Edit structured slide fields, preview field alternatives or review a whole-slide rewrite. Ask Lumen can propose wider changes; inspect and select the changes before applying them to the saved deck.
Inspect the actual handoff
Check charts, speaker notes, images and contrast in presentation view and the downloaded file. A new-period deck is a separate draft with changed values and sources to review.
Outline planning and field alternatives
Choose a creation mode and workflow profile, supply source material and review the planned coverage. Slide fields have layout-specific budgets. Field assistance offers alternatives with rationale and word counts; whole-slide refinement shows field-level changes. Ask Lumen can propose wider structural edits, which require a reviewed preview before application.
Data, themes and the next reporting period
Paste spreadsheet rows, choose header handling and preview replacement chart data. Where offered, select Business metrics explicitly and inspect their source receipt. Review changes in values and sources before accepting a next-period draft. Theme controls cover brand colors, type, logo placement, background and contrast choices; a custom theme still needs visual review.
Presenting and the exported deck
Inspect full-screen and audience views, speaker notes, next-slide preview, navigation and timer. Check PDF and PowerPoint separately. Supported elements can become native editable shapes or charts; complex visuals can use a flattened fallback. Speaker notes and per-slide handoff choices should be inspected in the actual file.
PowerPoint export is hybrid: supported content may remain editable while complex visuals can be flattened. Conversion between a responsive story and slides requires a preview; it is not lossless.
The four-part structure
Each part is one or two lines. If any part needs a paragraph, it belongs in the body of the deck, not here.
- Situation — what happened. The facts, with numbers. "Revenue grew 14% to $4.2M; gross margin fell 6 points to 61%."
- Implication — what it means. The reading of those facts. "Growth is being bought with discounting, not won on product."
- Recommendation — what we propose. A specific course of action. "Hold list price and cut the discount ceiling to 15%."
- Ask — what we need. The decision, resource or approval required, with an owner and a date.
The test: hand the slide to someone who was not in the room. If they can state the decision
being asked for and the reason behind it, the slide works. If they ask "so what do you want?", the ask is
missing or buried — the single most common failure.
Worked examples
Board deck
- Situation: ARR reached $4.2M, up 14% on Q2; net revenue retention 96%.
- Implication: New business is on plan, but churn in the sub-$1k cohort is capping net growth.
- Recommendation: Stop new sales below $1k ACV and move that cohort to self-serve.
- Ask: Approve the pricing change effective 1 October. Owner: CRO.
Client or consulting deck
- Situation: Proposal turnaround averages 9 working days across three teams.
- Implication: You are missing roughly 1 in 5 deadlines on inbound RFPs.
- Recommendation: Consolidate on one template library with a two-stage review.
- Ask: Agree a six-week pilot with the enterprise team.
Investor update
- Situation: 18 months runway; $310k net burn per month.
- Implication: A raise must open by March to close before runway drops under 9 months.
- Recommendation: Begin partner conversations in January on the current metrics.
- Ask: Three warm intros to Series A funds this quarter.
Executive summary vs agenda vs overview
These three sit in the same place in a deck and are routinely confused.
| Slide | Answers | Contains numbers? | Can stand alone? |
|---|---|---|---|
| Executive summary | What we found and what we want | Yes — it is mostly numbers | Yes, by design |
| Agenda | What this session covers, in order | Only timings | No |
| Overview / context | Background needed to follow the deck | Sometimes | No |
| Key takeaways | What to remember afterwards | Sometimes | Partly — usually lacks the ask |
Common mistakes
- Summarising the deck instead of the findings. "This deck covers our Q3 performance" tells the reader nothing.
- No numbers. An executive summary without figures is an opinion.
- Burying the ask. If the decision is in the last sub-bullet, it will be missed.
- Writing it first. Write it last, from the conclusions you actually reached.
- Too long to read while listening. Keep to roughly 120 words. Beyond that the audience reads instead of listening to you.
- Hedging. "We may wish to consider" is not a recommendation. Say what you would do.
Frequently asked questions
What is an executive summary slide?
A single slide near the front of a deck that states what was found, what it means, what is recommended and what is being asked for. It is written so an executive who reads nothing else can still act correctly.
How long should an executive summary slide be?
About 120 words, or four short blocks. Longer than that and the audience reads the slide instead of listening, which defeats the purpose of presenting it.
Where does the executive summary slide go?
Straight after the title slide, before the agenda. Executives frequently read only the first two slides, so the summary needs to be inside that window.
Should you write the executive summary first or last?
Last. It should reflect the conclusions the analysis actually produced. Written first, it becomes a plan you then argue backwards from.
What is the difference between an executive summary and key takeaways?
An executive summary includes the ask — the decision or resource you need. Key takeaways usually stop at what to remember, which makes them weaker for decision meetings.
Can an executive summary slide have a chart?
One small chart can work if it carries the central number. Two or more turn the slide into an analysis page and break its ability to be read in 30 seconds.
Do investor decks need an executive summary slide?
Seed pitches usually do not — they open on the hook. Later-stage updates and diligence decks benefit from one, because the reader is often reviewing several companies in sequence.
How do I make sure the ask is not missed?
Give it its own labelled block, state one decision rather than three, and name the owner and date. If the ask needs a sentence of setup, it is not specific enough yet.
Related slide and deck guides
Updated
More from Gixo