The Handout Versus the Screen
You must deliver a 20-minute talk and also provide a handout. The screen deck is deliberately sparse: large images and one short line per slide, 18 slides. Stakeholders want the handout to contain the full argument, references, and the data tables, because they will read it without you. A previous attempt printed the slides three-to-a-page and reviewers said it was 'useless without the talk'. Time is short and you cannot rewrite everything from scratch.
1. How should you produce a handout that stands alone while keeping the on-screen deck sparse?
Read the worked answer
Separate the two artefacts by purpose. Keep the screen deck sparse for live delivery, and put the full argument, references, and tables into the notes pages or a companion document. Export the handout from the notes view (slides plus speaker notes) so each image is paired with the explanation it needs, or build a short Word/document handout from the same content. Printing slides three-to-a-page fails because it carries the sparse visual without the reasoning; notes pages carry both. This reuses existing content rather than rewriting, which fits the time constraint.
2. What checks ensure the handout is genuinely usable on its own, given the time pressure?
Read the worked answer
Read the handout as if you had not seen the talk: does each page state the point, and do references and tables appear where they are cited? Check that notes are complete sentences, not cues like 'pause here'. Confirm page order matches the deck, that images are legible in print (greyscale test if printed in mono), and that tables are not cut off. Verify page numbers and a title/date on the handout. A quick review by one colleague who missed the rehearsal is the fastest test of whether it stands alone.