Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
The one core message and why a deck is not a document
The pyramid principle and assertion evidence structure
Audience analysis and the executive against the peer audience
The executive summary and the honest first page
Storyboarding and the slide as a unit of argument
Conclusion titles against topic titles
The assertion, the evidence and the so what
Choosing a chart and the defaults that mislead
Tables against charts and the honest exception
Data storytelling and leading with the finding
Slide density, the six line test and what to cut
Diagrams for systems, sequences and flows
The architecture review deck as a technical case study
Roadmap decks, sequencing and dependencies
Metrics decks, definitions and honest scales
Business case decks and the assumptions behind them
The pre-mortem and surfacing the risk slide
Question and answer preparation and the hostile question
Delivering the deck and handling interruption
Templates, masters, accessibility and reading in a room
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
A deck competes for attention against everything else in the room, so one message with three supporting pillars beats three messages with one support each.
The pyramid is a rule about order, not about geometry: the conclusion goes at the top and the reasoning hangs beneath it.
Audience analysis for a deck means three things: what they already believe, what they have to decide, and how much detail they can absorb in the time you have.
The first page carries the recommendation, the reason, the cost and the risk, and everything else is optional there.
A storyboard card holds the slide title, the point the slide makes and the evidence it uses, and nothing about layout yet.
A topic title such as latency by region is a label, and a conclusion title such as latency is only a problem in two regions is an argument.
Questions this pack covers
How do you find the single sentence that a deck argues?
Why does a second message in a deck weaken the first one?
What does the pyramid principle say about ordering an argument?
What does the number four at the top of a pyramid diagram actually mean?
What do you need to know about an audience before you write a single slide?
How do you find out how much technical depth an audience expects?
What actually belongs on an executive summary slide?
How much text fits on a first page and still stays readable?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
How many questions?
360, spread across 20 topics, written out in full across 336 pages.
Do the answers just list keywords?
No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
How do I get it?
Pay once and the PDF arrives by email immediately, with a signed download link.
Can I get it refunded?
Yes, if it is not what you expected. See the refund policy.
