Part VI — Presentations and Oral Communication
Everything changes when the reader becomes a listener. A reader controls the pace, rereads what they missed, and skips what they don't need. A live audience can do none of that. They move at your speed, can't rewind you, and — the fact that governs this entire part — cannot read and listen at the same time, because text and speech compete for the same verbal channel. A text-dense slide doesn't support your talk; it competes with it, and it wins. That single constraint reorders every choice you make about a deck, a talk, and a diagram.
So the work of this part is unlearning a habit. Most people treat a slide as a page they project and a presentation as a document read aloud. Both are wrong. A slide is a visual aid that should carry the one thing words can't — a picture, a relationship, a number — while your voice carries the argument. A talk is a performance you rehearse, not a file you build; finishing the slides is when you start, not when you're done. And a diagram is a sentence in a visual language that must say one thing, not an exhaustive map of the system. Cross these thresholds and you stop writing slides and start designing them, stop reading and start presenting.
By the end of Part VI you will be able to build assertion-evidence slides that make a point instead of listing topics; deliver a technical talk with a hook, a clear arc, controlled timing, and composure under hostile questions; recover from a crashed demo; and draw architecture, flow, sequence, and ER diagrams that communicate at a glance.
What's in this part:
- Chapter 30 — Slide Design: Visual Communication for Talks — the assertion-evidence slide, one point per slide, the back-row test, and redesigning the topic-and-bullets default.
- Chapter 31 — Delivering Technical Presentations: the spoken arc, finishing at 90% of your slot, speaking from a keyword outline, reappraising nerves, Q&A bridging, and the demo backup recording.
- Chapter 32 — Visual Storytelling: Diagrams, Flowcharts, Architecture — picking one level of abstraction (C4), labeling every arrow, captioning the idea, and the honest-diagram warning.
Read Chapter 30 first — it establishes the slide-as-visual-aid threshold that Chapter 31's delivery assumes. Chapter 32 stands alongside both and reaches back into Part II, since a diagram is a figure (Chapter 9) and lives on a designed page (Chapter 10). This part serves the Engineering/Science and Business/Professional tracks especially, but anyone who will ever stand in front of a room belongs here. Raj Patel returns in Chapter 31, his conference demo saved by the backup recording he was wise enough to make.
The themes converge on the live reader. Audience is everything is literal here: the listener who can't rewind sets every rule. Structure serves the reader shapes the front-loaded talk, the signposted transitions, the protected conclusion, and the diagram's single level of abstraction. The best writing is invisible becomes the best design is invisible — the slide aids the speaker and gets out of the way; the diagram reads without a tour guide. Every element earns its place drives one point per slide, cut content rather than raced delivery, and the pause that replaces a filler word. Chapter 32 also revives the Challenger lesson as the honest-diagram warning: a clean diagram persuades even when it's wrong, and omission is a choice.
The Communication Portfolio gains its presentation piece — the deck with speaker notes — across Chapters 30 and 31, the sixth of your seven artifacts.
These presentation skills generalize across fields, which sets up the next move. Part VII holds the principles constant and varies the conventions, showing how the same audience, structure, and clarity skills wear the specific costumes of engineering, computer science, science, medicine, and business.